Hello All,
We have recently observed that as soon as the Hyper-V VSA backups were triggering the hosts were randomly rebooting. While going through the windows event logs, we observed there were multiple error messages getting logged during the backup window:
-
An error was detected on device \Device\Harddisk14\DR385 during a paging operation.
-
The shadow copies of volume \\?\Volume{20628861-0000-0000-0000-100000000000} were aborted during detection because a critical control file could not be opened.
-
Filter Manager failed to attach to volume '\Device\HarddiskVolume26'. This volume will be unavailable for filtering until a reboot. The final status was 0xC03A001C.
-
The IO operation at logical block address 0x800 for Disk 8 (PDO name: \Device\000000d2) was retried.
The Volumes and Harddisk drives that were reported in these logs were not local to the hosts, these were the VHDX files being mounted during backups. Automount on these hosts was enabled. The paging error led us into thinking that the system might be trying to write page files to the disks as soon as those are getting attached to the system as the page file setting are set to “Automatically balance across all drives” and automount being enabled. After disabling the automount, the error messages went away and those nodes stopped rebooting.
We wanted to check if someone can validate if this theory is correct or if anyone has seen similar issue.?
Thank you
Abdul
Best answer by Aplynx
View original
