INACCESSIBLE BOOT DEVICE after RAID Software Installation

AKazak · 5 Days Ago

Pentagon said:

But your feedback has to be faster!

I apologize for having delays with providing the feedback and will do my best to do it faster...

Pentagon said:

go back to the (F:)-Boot Option (first change UEFI to BIOS) again

Done!

Pentagon said:

and do that what is explained in #34

Pentagon said:

I see that you boot from (F:) but what happens if you doubleclick on the desktop icon "My PC"
or you open the explorer? Try to run a Program that you start from C:\Program Files

Here is what I have:

INACCESSIBLE BOOT DEVICE after RAID Software Installation-image1.png

Pentagon said:

Everything looks like a typical Dual-Boot arrangement. You run Windows (C:) and boot successfully from (F:)
Machines that do not support NVMe boot often run Windows (C:) perfectly, but need the bootmanager on a SATA Disk.
But do that what is mentioned in #34 first. And I do not tell that again. When it is what I believe now, your RAID-Controller-Update changed UEFI bootsettings.
BIOS: \Windows\system32\winload.exe ==> is working
UEFI: \Windows\system32\winload.efi ==> not working
Instead of a USB-Disk you could try a SATA-Disk as well. But keep your (F:)-Disk safe.

Currently I boot from a USB stick with WinPE installed on it.
Do you mean taking a new SATA drive, connect to the workstation, installing a fresh W10 to the new SATA and start from there?
If positive, then I will proceed with the new SATA drive.

Pentagon said:

Then the cmd command
diskpart
sel disk 0
sel par 1
assign letter=S
exit

INACCESSIBLE BOOT DEVICE after RAID Software Installation-image2.png

Pentagon said:

allows you to explore the boot-partition using Explorer++ running in Admin-Mode
But your BCD is OK!
It should look like that.

INACCESSIBLE BOOT DEVICE after RAID Software Installation-image9.png

INACCESSIBLE BOOT DEVICE after RAID Software Installation-image3.png

INACCESSIBLE BOOT DEVICE after RAID Software Installation-image4.png

INACCESSIBLE BOOT DEVICE after RAID Software Installation-image5.png

INACCESSIBLE BOOT DEVICE after RAID Software Installation-image6.png

INACCESSIBLE BOOT DEVICE after RAID Software Installation-image7.png

INACCESSIBLE BOOT DEVICE after RAID Software Installation-image8.png

Pentagon said:

when finished
run cmd
diskpart
sel disk 0
sel par 1
remove
exit

INACCESSIBLE BOOT DEVICE after RAID Software Installation-image10.png

Pentagon · 4 Days Ago

All that looks good. The EFI\Microsoft\Boot-Folder would have been more interesting, but it's ok
The BCD in S:\EFI\Microsoft\Recovery is a secondary BCD, normally unused.The right one is S:\EFI\Microsoft\Boot

Try to run any program from (C:) you usually used.

I would attach a SATA-Disk, convert to MBR and install WIN 10 in BIOS-Mode. (50 GB is enough) Then you don't get a conflict with the EFI-Partition on your current Disk 0. You can also unplug the SATA cable from the current C-Disk during the installation.

Once you have installed and booted you should see the new Installation as (C:) and the old (C:) with a new drive letter (?:).
Then type
bcdboot ?:\Windows
(?=new drive letter of old C)

Then type
bcdedit

You should find:
Windows Boot Loader
-------------------
identifier {default}
path \WINDOWS\system32\winload.efi

If it's there, type

bcdedit /set {default} description "Windows old"

reboot and you should be able to run the old system in BIOS-Mode.

(The first time you show your (X:))

AKazak · 4 Days Ago

Pentagon said:

All that looks good. The EFI\Microsoft\Boot-Folder would have been more interesting, but it's ok
The BCD in S:\EFI\Microsoft\Recovery is a secondary BCD, normally unused. The right one is S:\EFI\Microsoft\Boot

Great news!

Pentagon said:

Try to run any program from (C:) you usually used.

Here is the result:

Pentagon said:

I would attach a SATA-Disk, convert to MBR and install WIN 10 in BIOS-Mode. (50 GB is enough) Then you don't get a conflict with the EFI-Partition on your current Disk 0. You can also unplug the SATA cable from the current C-Disk during the installation.

I will try getting a new SATA disk for fresh installation of W10, but it will take time.
Can we continue with the current USB-drive W10 installation?

Pentagon · 4 Days Ago

I don't know the influence of the StrelecPE, so it's better to get any SATA. It can be an old one. I know that it can take some time, to get it. So don't worry

We could also try to install a BIOS-Bootmanager on your current disk 0 (750 MB) Recovery drive (Partition 4)

It goes like this:
diskpart
sel disk 0
sel par 4
format quick fs=ntfs label="BIOS"
assign letter=S
active
exit
bcdboot c:\windows /s S: /f BIOS

Watch the system response after the last bcdboot-input!

check:
bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition4\Boot\BCD

Remove the attached USB-Disks
and reboot in PC in BIOS-Mode

But the Raid controller still can create a problem. Learning by Doing: Try & error method

Edit:
download Registry Finder:

Registry Finder