Windows server 2016 INACCESSIBLE_BOOT_DEVICE Hyper-V

%3CLINGO-SUB%20id%3D%22lingo-sub-1700943%22%20slang%3D%22en-US%22%3EWindows%20server%202016%20INACCESSIBLE_BOOT_DEVICE%20Hyper-V%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1700943%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20I%20have%20this%20server%20based%20on%20Supermicro%20X10SRi-F.%20It%20has%20an%20Intel%20software%20RAID%2010%20with%204%20disks.%20It%20was%20running%20for%20about%20a%20year%20just%20fine%20with%20Windows%202016%20Standard%20as%20Hyper-V%20host%20for%20two%20guests.%20One%20day%20it%20crashes%20with%20BSOD%20%22INACCESSIBLE_BOOT_DEVICE%22.%20The%20raid%20listed%20as%20degraded%2C%20so%20a%20disk%20is%20replaced.%20No%20change%2C%20still%20BSOD.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20found%20that%20the%20machine%20runs%20fine%20in%20safe%20mode%20or%20when%20the%20boot%20options%20are%20changed%20so%20that%20hypervisorlaunchtype%20is%20set%20to%20off.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20then%20make%20a%20fresh%20install%20of%20Windows%20Server%202016%20on%20a%20new%2C%20single%20disk.%20All%20is%20fine%20until%20the%20Hyper-V%20role%20is%20installed%20and%20the%20server%20attempts%20to%20boot.%20Same%20BSOD%20(and%20the%20same%20disk%20is%20then%20put%20in%20a%20fully%20different%20computer%20where%20it%20runs%20fine%20as%20Hyper-V%20host).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20now%20have%20a%20fresh%20install%20of%20Windows%20Server%202016%20on%20the%20original%20RAID.%20As%20soon%20as%20hypervisorlaunchtype%20is%20set%20to%20%22auto%22%2C%20the%20BSOD%20returns.%20All%20updates%20are%20installed.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECoreinfo%20shows%20that%20hypervisor%20is%20enabled%20in%20BIOS%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tried%20fresh%20install%20on%20two%20different%20disks%20(one%20spinning%20disk%20and%20one%20old%20SSD)%20in%20addition%20to%20on%20the%20RAID.%20I%20am%20out%20of%20ideas.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1700943%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1702563%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20server%202016%20INACCESSIBLE_BOOT_DEVICE%20Hyper-V%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1702563%22%20slang%3D%22en-US%22%3E%3CP%3EMight%20check%20here%20for%20later%20firmware%2C%20chipset%20and%20driver%20support.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.supermicro.com%2Fen%2Fsupport%2Fresources%2Fdrivers%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.supermicro.com%2Fen%2Fsupport%2Fresources%2Fdrivers%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ealso%20the%20manufacturer%20will%20be%20your%20best%20resouce%20for%20debugging%20problems%20with%20the%20hardware.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.supermicro.com%2FFAQ%2Findex.php%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.supermicro.com%2FFAQ%2Findex.php%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

So I have this server based on Supermicro X10SRi-F. It has an Intel software RAID 10 with 4 disks. It was running for about a year just fine with Windows 2016 Standard as Hyper-V host for two guests. One day it crashes with BSOD "INACCESSIBLE_BOOT_DEVICE". The raid listed as degraded, so a disk is replaced. No change, still BSOD.

 

It is found that the machine runs fine in safe mode or when the boot options are changed so that hypervisorlaunchtype is set to off. 

 

I then make a fresh install of Windows Server 2016 on a new, single disk. All is fine until the Hyper-V role is installed and the server attempts to boot. Same BSOD (and the same disk is then put in a fully different computer where it runs fine as Hyper-V host).

 

I now have a fresh install of Windows Server 2016 on the original RAID. As soon as hypervisorlaunchtype is set to "auto", the BSOD returns. All updates are installed. 

 

Coreinfo shows that hypervisor is enabled in BIOS

 

I have tried fresh install on two different disks (one spinning disk and one old SSD) in addition to on the RAID. I am out of ideas.

1 Reply

Might check here for later firmware, chipset and driver support.

https://www.supermicro.com/en/support/resources/drivers

 

also the manufacturer will be your best resouce for debugging problems with the hardware.

https://www.supermicro.com/FAQ/index.php