Windows 10: Inaccessible boot device after changing RAID controller

My W10 1909 x64 system that used a built in RAID controller (LSI 1038) didn't support large drives, so I bought an IBM 5016.

I backed up the RAID 1 boot device using Macrium Reflect

Installed the new RAID controller and deleted the old RAID 1 array, and then created a new one using the same drives.

I then used Macrium Reflect Recovery CD to restore the partitions to the new RAID 1

Problem is that I get "Inaccessible Boot Device" and Macrium's Boot Recovery Option doesn't seem to solve it.

I suspect (but don't know for sure) that I need somehow to install the AVAGO (LSI) Megaraid SAS (megasas.sys) into the restored W10 partition, but don't know how to achieve that!

If it's something else that needs to be done I'm all ears!

Keeping my fingers crossed!
David

:)

 

Inaccessible boot device - reinstall storage controller

Hi,

I have a Dell Precision 3530 with a PCIe SSD. In a try to get Windows to see my newly installed secondary m.2 SATA SSD, I've set the "BIOS" (UEFI) from RAID mode to AHCI mode. The boot was unsuccessful, now I get BSOD with "Inaccessible boot device" even
after reverting to RAID mode.

Prior to the AHCI reboot, I've also removed both* Intel Rapid Storage controller drivers so that the default Microsoft Storage Space controller be used in the AHCI mode.

* In the Storage controllers branch in Device Manager, I had four entries: An Intel RST, an Intel RST Premium, and two MS Storage Space controller instances. This is how I received the laptop from the reseller.

Right now Windows sees my system disk, partitions and files. I can use the recovery command line, or boot to a recovery safe mode (e.g., not my OS). No booting though. Automatic repair cannot fix the problem.

The system disk has GPT partitions. diskpart / list vol shows my partitions with no flags in the Info column, except for the ESP partition which is hidden.

Is there any way to reinstall/reset the missing/problematic storage controller drivers?

 

Inaccessible boot device

This is a Microsoft link on inaccessible boot device:
https://docs.microsoft.com/en-us/win...le-boot-device

It is an intermediate level link.
There are more advanced steps that can be ran once the partition structure is known.
There are steps for repair of the boot sector, operating system, etc.
Sometimes this bugcheck can be caused by windows updates.

A reset save files equivalent may be able to be performed.
Alternatively a clean install can be performed once important files are backed up.

 

Inaccessible boot device

"INACCESSIBLE BOOT DEVICE" msg suggests it is hardware (or driver) problem; in addition to missing disk. Try to disconnect your ntb from power supply and to remove battery for one minute. Then check your BIOS settings (SATA/AHCI/RAID). If it does not help, open your ntb and check your disk-related HW (SATA & power cables, connectors, disk itself).