INACCESSIBLE BOOT DEVICE after RAID Software Installation

Page 3 of 3 FirstFirst 123

  1. 3Bit
    Posts : 341
    W10 22H2 19045.4355
       New #21

    AKazak said:
    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:
    Attachment 408619....

    ...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...
    if you can see both drives, can you access the files? booted with Strelec and after entering diskpart then entering "list disk", do you see all the discs? At least the physical ones ( still not sure what you mean by virtual and your setup)

    Boot problems typically are buried in the BCD, the Boot Configuration Data.
    Few things are important: are you booting BIOS or UEFI?
    What exactly do you understand by "virtual drive"? What's your current configuration/setup?

    Another thing to watch out for is what is the storage device format: MBR or GPT?
    the fact that you get this error message tells that there's something else buried somewhere.

    First of all, is the RAID properly configured [what type?] Internal? external? how is it partitioned? what are the primary/logical drives?
    does the BIOS and boot information points to the proper drive and partitions as an UEFI boot holds the boot information in a separate around 100 MB in size FAT32 partition.

    Don't mess with the registry!
    The problem is somewhere else!
    Chances are you can really make it worse! Like saddling up a horse by starting from the rear...
      My Computer
    Quote Quote

  3. Pentagon
    Posts : 702
    WIN 10 19045.4291
       New #22

    To finalize the BCD-Clearance in addition to #20 run cmd:

    bcdedit /delete {1a04f6db-5a86-11e6-a472-1866da10e8fe}
    bcdedit /delete {7254a080-1510-4e85-ac0f-e7fb3d444736}

    bcdedit /set {fwbootmgr} displayorder {7fc884f2-5a91-11e6-8241-806e6f6e6963} /addlast


    There is nothing that points to a clean W10 installation and you must have made an Inplacement.
      My Computer
    Quote Quote

  4. AKazak
    Posts : 13
    Windows 10
    Thread Starter
       New #23

    Pentagon said:
    In order to heal the Recovery Situation on disk 0
    cmd (admin)
    step by step copy & paste

    bcdedit /delete {daed529a-5a8e-11e6-be1d-1866da10e8bc}
    bcdedit /delete {daed529b-5a8e-11e6-be1d-1866da10e8bc}

    reagentc /disable

    diskpart
    sel disk 0
    sel par 7
    delete partition override
    sel par 6
    delete partition override
    create partition primary
    format quick fs=ntfs label="Recovery"
    set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
    gpt attributes=0x8000000000000001
    exit

    reagentc /enable

    Problem solved!

    Edit:
    last change: cmd (admin)

    Bcdedit /set {fwbootmgr} displayorder {bootmgr} /addfirst
    Here is the results:

    bcdedit /delete {daed529a-5a8e-11e6-be1d-1866da10e8bc}
    The boot configuration data store could not be opened.
    The system cannot find the file specified.

    bcdedit /delete {daed529b-5a8e-11e6-be1d-1866da10e8bc}
    The boot configuration data store could not be opened.
    The system cannot find the file specified.

    reagentc /disable
    diskpart
    sel disk 0
    sel par 7
    delete partition override
    sel par 6
    delete partition override
    create partition primary
    format quick fs=ntfs label="Recovery"
    set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
    gpt attributes=0x8000000000000001
    exit
    reagentc /enable
    done with no errors

    bcdedit /set {fwbootmgr} displayorder {bootmgr} /addfirst
    The boot configuration data store could not be opened.
    The system cannot find the file specified.

    What would be the next steps?
      My Computer
    Quote Quote

  6. Pentagon
    Posts : 702
    WIN 10 19045.4291
       New #24

    You must have a 2nd EFI!

    step by step and watch the system response after each input. Don't continue if s.th. was not successful

    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /delete {1a04f6db-5a86-11e6-a472-1866da10e8fe}
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /delete {7254a080-1510-4e85-ac0f-e7fb3d444736}
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /delete {daed529a-5a8e-11e6-be1d-1866da10e8bc}
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /delete {daed529b-5a8e-11e6-be1d-1866da10e8bc}

    we need Explorer++ 1.4.0
    Explorer++ - Download

    and above 4 command results?
    I am here to help and not to wait for you!
    Last edited by Pentagon; 15 Hours Ago at 11:12.
      My Computer
    Quote Quote

  7. AKazak
    Posts : 13
    Windows 10
    Thread Starter
       New #25

    Pentagon said:
    You must have a 2nd EFI!

    step by step and watch the system response after each input. Don't continue if s.th. was not successful

    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /delete {1a04f6db-5a86-11e6-a472-1866da10e8fe}
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /delete {7254a080-1510-4e85-ac0f-e7fb3d444736}
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /delete {daed529a-5a8e-11e6-be1d-1866da10e8bc}
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /delete {daed529b-5a8e-11e6-be1d-1866da10e8bc}
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /delete {1a04f6db-5a86-11e6-a472-1866da10e8fe}
    The operation completed successfully.
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /delete {7254a080-1510-4e85-ac0f-e7fb3d444736}
    The operation completed successfully.
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /delete {daed529a-5a8e-11e6-be1d-1866da10e8bc}
    The operation completed successfully.
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /delete {daed529b-5a8e-11e6-be1d-1866da10e8bc}
    The operation completed successfully.

    What would be the next step?
      My Computer
    Quote Quote

  8. Pentagon
    Posts : 702
    WIN 10 19045.4291
       New #26

    AKazak said:
    What would be the next step?
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /set {fwbootmgr} displayorder {7fc884f2-5a91-11e6-8241-806e6f6e6963} /addlast

    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /set {fwbootmgr} displayorder {bootmgr} /addfirst


    2 minutes only

    and a new bcd_output.txt and an updated "Diskmanagement" screenshot
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /enum all >C:\bcd_output.txt

    My time is limited and I will be back tomorrow.
      My Computer
    Quote Quote

  9. AKazak
    Posts : 13
    Windows 10
    Thread Starter
       New #27

    Pentagon said:
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /set {fwbootmgr} displayorder {7fc884f2-5a91-11e6-8241-806e6f6e6963} /addlast

    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /set {fwbootmgr} displayorder {bootmgr} /addfirst


    2 minutes only

    and a new bcd_output.txt and an updated "Diskmanagement" screenshot
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /enum all >C:\bcd_output.txt

    My time is limited and I will be back tomorrow.
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /set {fwbootmgr} displayorder {7fc884f2-5a91-11e6-8241-806e6f6e6963} /addlast
    The operation completed successfully.

    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /set {fwbootmgr} displayorder {bootmgr} /addfirst
    The operation completed successfully.

    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /enum all >C:\bcd_output.txt
    GS20QD2 W10 BCD Output 2024-04-30.txt

    Have a great evening!
    Looking forward to continuation tomorrow.
      My Computer
    Quote Quote

  10. Pentagon
    Posts : 702
    WIN 10 19045.4291
       New #28

    The BCD_Cleanup was successful

    "Diskmanagement" screenshot update was also needed!

    3 long Commands to get the Recovery working

    1.
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /set {a0a94cac-356a-11ee-9e95-aeb6ae704582} device ramdisk=[\Device\HarddiskVolume6]\Recovery\WindowsRE\Winre.wim,{a0a94cad-356a-11ee-9e95-aeb6ae704582}

    2.
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /set {a0a94cac-356a-11ee-9e95-aeb6ae704582} osdevice ramdisk=[\Device\HarddiskVolume6]\Recovery\WindowsRE\Winre.wim,{a0a94cad-356a-11ee-9e95-aeb6ae704582}

    3.
    bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /set {a0a94cad-356a-11ee-9e95-aeb6ae704582} ramdisksdidevice partition=\Device\HarddiskVolume6

    4.
    reagentc /info

    Edit:
    what is the system response to this command:

    bcdedit /enum active
    ?
    Last edited by Pentagon; 1 Hour Ago at 01:13.
      My Computer
    Quote Quote

 

  Related Discussions
Just a disclaimer upfront: This is about Windows Server 2019 but I believe it will be the same for Windows 10. Win Server 2019 is build 17763 which is version 1809 (October 2018 Update). The boot disk (SSD) was attached to the mainboard's onboard...
Dear all, I have tried searching online for a fix but perhaps my issue is rather unique. (I do not have much IT knowledge) 1. BSOD came while having some common programmes running - Chrome, Telegram and Game(COD) 2. PC reboots itself:...
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...
Inaccessible boot device
in General Support

So needing some help here.. I recently installed windows 10 on my pc i downloaded iobit driver updater and let it do its thing, i also installed total av antivirus everything was good as gold until i had to restart my pc now im getting the...
Getting Inaccessible Boot Device
in AntiVirus, Firewalls and System Security

So I have a HP laptop running Windows 10, 1 day last week system will not post. Tried repair, system rollback, advanced setting, checked BIOS setting. Noticed BIOS was out of date, Loaded the update to a flash drive and updated BIOS. Pulled the...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 03:02.
Find Us




Windows 10 Forums