INACCESSIBLE BOOT DEVICE after RAID Software Installation

Greetings!

Windows Version: Windows 10 Pro English (US) 22H2 x64

I was running the OS on a Dell 7910 workstation featuring AVAGO MegaRAID SAS 9361-8i controller loaded with 1 SSD (virtual drive 1) hosting the OS itself and 3 WD large-volume HDDs (virtual drive 2) for the data.

After installation of new RAID software update I started getting INACCESSIBLE BOOT DEVICE BSOD during the boot stage:


If I boot in the Windows Recovery Environment (Recovery Mode) none of Advanced Options works, except for Command Prompt.

If I run Command Prompt, DISKPART, LIST DISK it answers me: "There are no fixed disks to show."
So it seems that the Windows Recovery Environment does recognize virtual drives served by the AVAGO MegaRAID SAS 9361-8i controller (no/bad driver?).

I have no restore point or previous image.
So I have two options: repair or clean install.
Since I have many software items in the failed Windows installation, I want to try recovering it first.

Thank you.

- - - Updated - - -

How do I run V2_log_collector_1.11 script in this case?

Was it a Software-Update or Firmware-Update? In case it was a firmware update, restore points or backups are useless and you need a clean install.
Years ago, I had a similar LSI-Controller and after a firmware update everything was lost.

Pentagon said:

Was it a Software-Update or Firmware-Update? In case it was a firmware update, restore points or backups are useless and you need a clean install.
Years ago, I had a similar LSI-Controller and after a firmware update everything was lost.

No, it was definitely software, not firmware update.
I managed to boot Sergei Strelec's WinPE from USB and I can see the contents of both OS virtual drive 1 and Data virtual drive 2.
Therefore the information itself is still there on drives and AVAGO MegaRAID SAS 9361-8i controller works properly.

- - - Updated - - -

I followed the steps to fix MegaRAID Console error: “Server could not be found because server may be down or server not installed in the host system.” by downloading https://download.lenovo.com/servers/...ows_x86-64.zip and installing.
After installation and system restart I started getting the INACCESSIBLE BOOT DEVICE BSOD during the boot stage...

MegaRAID Storage Manager Application for Windows (17.05.01.02) - Lenovo Support LK shows that this software packages is designed for:

• Windows Server 2012
• Windows Server 2012 R2
• Windows Server 2016

Possible this incompatibility caused the error...

"INACCESSIBLE BOOT DEVICE BSOD" is difficult to fix.
Usually you need additional drivers and from a Recovery you have to load the reg hive and find the error. Can take hours.

Pentagon said:

"INACCESSIBLE BOOT DEVICE BSOD" is difficult to fix.
Usually you need additional drivers and from a Recovery you have to load the reg hive and find the error. Can take hours.

Let me give a try?
What are the steps to begin?

You boot into recovery environment cmd
type regedit
in the registry you load the hive of the os
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services
name it OFFLINE
it appears in the current recovery registry as
HKEY_LOCAL_MACHINE\OFFLINE\ControlSet001\Services

Here you find the drivers and their settings during startup
under start it should be "0"

Pentagon said:

You boot into recovery environment cmd
type regedit
in the registry you load the hive of the os
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services
name it OFFLINE
it appears in the current recovery registry as
HKEY_LOCAL_MACHINE\OFFLINE\ControlSet001\Services

Here you find the drivers and their settings during startup
under start it should be "0"

Got it!
I managed to export Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services to the attached file.
GS20QD2 W10 Services 2024-04-23.reg

I searched the file in a text editor and found a number of suspects:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\megas*

However, it seems like all of them have:
"Start"=dword:00000000

Is there a way to turn on the verbose logging of all the steps and attempts during the initial boot phase of Windows 10?
Since I can get to the Windows Recovery Environment (Recovery Mode) I assume that boot sector of the SSD (virtual drive 1) of RAID array is accessible to the OS. However, when it comes to boot the main system from it partition it fails to access the same SSD (virtual drive 1)...

Pentagon said:

You are wrong! It must be the offlinehive and look like this:

HKEY_LOCAL_MACHINE\Offline\ControlSet001\Control

Search for UpperFilters

UpperFilters = partmgr

Example:

Computer\HKEY_LOCAL_MACHINE\Offline\SYSTEM\ControlSet001\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}
Computer\HKEY_LOCAL_MACHINE\Offline\SYSTEM\ControlSet001\Control\Class\{53487c23-680f-4585-acc3-1f10d6777e82}

Delete UpperFilters entries not having partmgr

No AVAGO MegaRAID Hotline?

How does you BCD look?

A specialist in these things is "Tekkie Boy"

I booted Windows Recovery Environment (Recovery Mode), CMD, REGEDIT and checked again: no HKEY_LOCAL_MACHINE\Offline hive is not in the list at all...

BCDEDIT responds:
The boot configuration data store could not be opened.
The requested system device cannot be found.

It seems that Windows Recovery Environment (Recovery Mode) does not have an access to the RAID array volumes (weird).

I will try to boot from USB bootable drive and check again.