VM server locking up with 153 Disk warnings

Question

I have a 2012 host running Hyper-V. There are 3 guest VMs all running Server 2012. One of them has started experiencing a problem where it will lock up with the only way to get at it is to do a Turn Off in Hyper-V Manager.
The problem always occurred during the nightly backups. Windows Server Backup is used and the destination is a VHDX file located on a removable cartridge on the host server. This is the same setup for all 3 VMs. The other two do not have any problem with
this and this one has operated for about a year without a problem with this. I can do a one time backup using the same parameters as the scheduled backup and they all complete successfully with no lockup of the server.
I finally deleted the VHDX file and created a new one. I also deleted the backup job and created a new one. Backups ran fine for just over a week, then the lockups of the server started again.
The only seemingly consistent evidence I can find is 153 Disk warnings in the System log. These seem to occur during the backup process. My research indicates some sort of disk system problem.
Any ideas?
Jonathan

Answer 1

This post
suggests that IO requests are timing out and that you should investigate the physical disks' health. 
Also, upgrade to 2012 R2 on the host if you could, make sure the host is fully patched, and that the guest has the correct version of Hyper-V Integration Service.
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx
These are virtual disks so there is nothing physical to investigate. As I said I created a new virtual disk and it helped for a short while.
Upgrading to R2 is not an option as everything else concerning this Hypver-V setup is working just fine, this is the only problem. And the customer is not going to fork out money for a new license just because of this one problem. This is something that
needs fixing with what OS is there.
Jonathan
The post suggests you investigate the physical disks on top of which the VHDX file lie.
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx