By AndyZBell - 18 September 2023 12:07 PM
I have an old Windows 7 Pro 64 bit PC with a RAID 1 1gb system disk and a duplicate 1gb backup disk.
This morning the PC would not boot - it just got to the Windows logo display and then rebooting. Turning off automatic reboots let to a BSOD INACCESSABLE_BOOT_DEVICE error.
After trying to boot to safe mode or to the last known good configuration, both of which failed, I decided to try to use my Macrium restore disk.
I tried rebuilding the rescue media - this reported every step succeeded except ,Updating Partition Boot Sector, which displays a nasty looking red X and the PC still won't boot.
So I tried restoring my Macrium backup. The backup restored successfully, but now the PC just shows a light blue screen for a about 30 seconds when I reboot it, after which it reboots itself and the cycle continues.
I would have thought restoring the image would fix the boot issues but things seem worse...
Any suggestions would be appreciated.
Andy
|
By jphughan - 18 September 2023 1:17 PM
If you restored from a RAID 1 virtual disk onto a single disk, you will probably need to run ReDeploy from the Rescue Media environment. The “inaccessible boot device” error can occur when Windows is set up to load the wrong type of storage driver for the actual environment, namely loading a RAID driver when there’s no longer a RAID virtual disk. Windows does not have plug and play adaptation for every type of hardware change. ReDeploy exists to facilitate those types of changes to address hardware differences that would otherwise prevent a successful boot.
|
By jphughan - 18 September 2023 1:21 PM
I’m unclear about rebuilding Rescue Media, that error message, and the connection to your PC still not booting. A Rescue Media build wouldn’t affect the ability to boot the PC normally one way or the other, and is that error truly something you saw during the build process rather than when running the Fix Boot Problems wizard IN the Rescue Media environment? Have you run that yet?
|
By AndyZBell - 18 September 2023 1:31 PM
+xI’m unclear about rebuilding Rescue Media, that error message, and the connection to your PC still not booting. A Rescue Media build wouldn’t affect the ability to boot the PC normally one way or the other, and is that error truly something you saw during the build process rather than when running the Fix Boot Problems wizard IN the Rescue Media environment? Have you run that yet?
Sorry - my mistake. I should have said: I Tried the Fix Boot Problems from the Rescue Media...
And then I got the 'Updating Partition Boot Sector' failure...
Andy
|
By AndyZBell - 18 September 2023 2:09 PM
+xIf you restored from a RAID 1 virtual disk onto a single disk, you will probably need to run ReDeploy from the Rescue Media environment. The “inaccessible boot device” error can occur when Windows is set up to load the wrong type of storage driver for the actual environment, namely loading a RAID driver when there’s no longer a RAID virtual disk. Windows does not have plug and play adaptation for every type of hardware change. ReDeploy exists to facilitate those types of changes to address hardware differences that would otherwise prevent a successful boot.
Hi
ReDeploy fixed the issues.
Thanks you for your help...
Andy
|
|