Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So one of our older VM's, which usually has no issues, is giving this error now when starting. It keeps going in a loop restarting and turning off with this error message.

enter image description here

I figure it's probably some issue with the VHD corrupting.

What's the next step? How would I run CHKDISK if I can't even load into the VM? This is with Hyper-V on Windows Server 2008 R2.

share|improve this question
What's your backup situation? – EEAA Apr 23 '14 at 13:12
Spin up a new VM and recover from backups ? – Iain Apr 23 '14 at 13:13
Did you do a VM hardware-level upgrade? Or change the storage controller mode? 0x7B usually is a Disk Controller driver issue. – msemack Apr 23 '14 at 15:21

I'd suggest booting to installation media for the guest OS and attempting a chkdsk or recovery from there. Where you go next will depend on the results of that...

share|improve this answer
How do you do this in Hyper-V? just starting the VM doesn't allow me to do that. – user57862 Apr 23 '14 at 20:10

The VM is not likely corrupted, you would treat this like any other 0x7B error, which is storage controller. Load the ISO for the OS and boot from it, then run CHKDSK/ R like the error suggests.

Did this VM have the latest Integration Services loaded for your version of Hyper-V? You can attempt a re-install of Integration Services in Safe Mode, and this may very well correct the issue.

Was this originally a P2V conversion? If so, look here:

share|improve this answer

Another great option if we are solely talking about the VHD (I know it could be just the VM to which user1467163's suggestion could help with that too) is to attach this VHD to a known working VM as a secondary drive. Once it's attached to a good VM, THEN perform a chkdsk /r and sfc /scannow on the possibly corrupted drive and let them both finish. If there is anything wrong it will be fixed with the switches I've recommended and then you can recreate a new VM and attach this freshly fixed VHD to it.

Just another option. The other two are where I would go too if this didn't work.

share|improve this answer

If it were me, where I have complete control of my environment, here is what I would do: Get screenshots of ALL settings for the VM in Hyper-V Shut down the VM if it is in any state besides "Off" On the host, copy all VHD's to a safe backup location Delete the VM in Hyper-V manager Create a new VM (Call it the same name if you want) Copy the VHD's you backed up into the new VM directory where they belong Attach the VHD's to the new VM

This is how you rule out VM corruption. I hope this is on-target with your problem- I could not read the error because the image host was flooded.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.