BSOD 'INACCESSIBLE BOOT DEVICE' on ML30 Gen10+ with VROC RAID

[AlexRomain]

Hardware : ML30 GEN10+ / VROC RAID

Problem : after FW update & Intelligent Provisioning install of Hyper-V 2K19 --> BSOD 'Inaccessible boot device'

Solution :

1. Boot on the Hyper-V ISO (either from USB or iLo), select 'install'. The VROC RAID will not be found
2. Add the drivers (https://support.hpe.com/connect/s/softwaredetails?softwareId=MTX_0699b12ff27e4c799c94aeab31), using a USB key. RAID is now found 
3. use the <- arrow to go back at the beginning, canceling the installation
4. choose 'repair the computer', go to command line
5. use diskpart, list volume to identify both the Windows installation letter (Hyper-V) and the USB key letter (with the drivers)

6. run :

DISM /image:C:\ /Add-driver /Driver:E:\drivers/iaStorE.inf

 Where c:\ is the Windows installation and E:\ is the USB key

Now it works

[Sunitha_Mod]

Hello @AlexRomain,

We appreciate you for sharing the solution. We hope this helps other users in the Community. 

[PipingRockIT]

Thank you so much. had this same issue with our new DL20 Gen10 Plus's. I dont understand why the intelligent provisioning doesn't handle this properly.

[johnk1]

Simular issue, with a BSOD after using CloneZilla to get a Gen10 image onto a Gen11 server with the MR408i-o Storage RAID Controller.

Following the above steps with the correct driver fixed the issue.

[mcbsys]

i ran into this with a MicroServer Gen10 Plus v2, using the latest Intelligent Provisioning (3.90) to try to load HPE Server 2025 Essentials Reseller Option Kit (ROK).

I did not see a back arrow (step 3) but while still on the Choose Drive pane, I pressed Shift + F10 to load a command prompt and was able to continue with step 5.

[Zlika2]

I can't thank you enough for posting this spot-on tip.

I had the same BSOD after a fresh Windows Server installation on an AsRock rack server with a VROC RAID controller. Finding your post and the Shift-F10 tip in the comments got me running in (nearly) no time.

Cheers!

[mcbsys]

@Zlika2, glad it helped. I had meant to come back and post a link to the blog article I wrote about the overall experience, including the BSOD and its workaround:

https://www.mcbsys.com/blog/2025/02/hpe-intelligent-provisioning-server-2025-and-vroc/