I have come across this several times in the last year and decided to document the answer myself so I can find it more quickly next time! The best answer is to be found here if you want full details:
http://www.minasi.com/forum/topic.asp?TOPIC_ID=31980
The scenario is:
Take a windows backup of a Dell (and probably other manufacturers) Server 2008R2 with a PERC (or equivalent) disk controller:
eg wbadmin start backup -backuptarget:\\remoteserver\remoteshare -include:c:,d:,e: -allcritical -vssfull
This creates a VHD(s).
Then go to Hyper-V and restore this backup to a new VM.
Lo and behold when you boot the VM you will get a stop 7b - inaccesible boot device.
Then mess around looking for the answer for half an hour.
The answer is simple.
Mount the VHD
Load the registry of your newly restored server.
Go to:
HKLM\System\ControlSet001\Services\Intelide and change Start to 0
HKLM\System\ControlSet001\Services\Pciide and change Start to 3
Restart - it boots perfectly. Why the bare metal restore cannot sort out the above automatically I just cannot fathom. This type of problem has been going on for ages and plagued moving XP/2003 disks to different hardware. The bizarre thing is that on NT4 you could manually 'preload' another driver (I admit the number of drivers was very limited!) and move to different hardware more simply - so much for plug and play! I should point out that using disk2vhd always works perfectly in the above scenario so it must have code to workaround the problem, although it does have the advantage of guaranteeing the hardware that will be presented to to the VM!
I have not tried to see if it is 'fixed' on Server 2012, but it probably isn't.
No comments:
Post a Comment