I have a 2012 server with the hyper-v role hosting 3 VM's. I keep receiving errors from what I believe was a USB drive that was temporarily attached to transfer som files over originally. These errors usually occur during the backup process (using veeam for now).
Error 27 volsnap system The shadow copies of volume \\?\Volume{2abab8d0-891d-11e3-93f1-842b2b007d02} were aborted during detection because a critical control file could not be opened.
Error 153 disk system The IO operation at logical block address 2f8c38 for Disk 3 was retried.
There is no volume guid attached as listed in the error nor is there a Disk 3 attached. Only disk 0,1, and 2.
These files are not selected for backup nor are shadow copies enabled on the host. This drive is not listed under disk management nor is it listed when I do a vssadmin List Volumes.
Basically, what can I do to get rid of the errors???
Steve
In Hyper-V Management bring up the settings for the VM and make sure that the USB drive is no longer mounted in the VM via IDE or SCSI bus. If it is the VM will not start on reboot without the drive being connected.
Philip