RAID 1 HDD Boot dependency issue

Associate
Joined
14 Nov 2003
Posts
544
One of the drives in my NAS failed (a WD20EARS...2nd failure in approx same number of years...), so I thought I would replace it with the exact same drive I had in my pc which was being used as a non RAID storage drive..

For some reason PC would not let me format the non RAID drive, so I just erased it (manually deleted all folders) and took it out...however, upon switching back on pc wouldn't boot even though the RAID 1 array is set as primary boot drive and has windows installed on it etc...

At first I thought that there might be a funny h/w requirement of having at least one non RAID drive connected in order to boot, so I tried a spare Maxtor I had lying around and put it in place of the WD I had taken out..still no boot...

So I plugged the WD back in and PC finally booted!

So it seems that my PC booting is dependent on having the WD drive in the system which defeats the purpose of my RAID 1 boot array...ie if the non RAID drive fails, I still would not be able to boot!

Any ideas how I can remove the boot dependency from the non RAID drive? I checked the drive volume and it is empty, except for a few gigabytes which seem to be in use even though no files and folders are showing?...

Cheers
 
boot from your windows CD and goto the repair options and do a fix Boot (its in the list of fix options)

Should sort you out.

When you installed windows you mush of had the RAID array and the drive attached and for some reason the boot loader was put on the single drive not the RAID array.
 
thanks!

i ran the windows repair disk, it couldn't find any windows installation on my PC!
so i rebooted, went back into windows , had a look in disk management and noticed that my C: wasn't set as 'active' though the other drive was...so I made C: active, rebooted and this time PC wouldn't boot at all and said BOOTMGR is missing!...

so I ran the Windows repair disk again and this time it did recognise a windows installation on my C: ... selected that, clicked on Repair and everything's working fine now :)
 
Back
Top Bottom