Inaccessible Boot Device on 64bit with RAID 0

Status
Not open for further replies.

eyanosa

Distinguished
Sep 23, 2015
13
1
18,510
My current hard drive is failing and, since I have two brand new identical hard drives lying around, I decided to do a RAID 0 set-up. I went into the BIOS and set SATA 1-4 as RAID and 5-6 as IDE. I left the Raid ROM as Legacy. I then went into the RAID set-up and turned both hdds into a RAID 0. I then inserted my usb stick with Windows 10 and started the installation process. The installer saw the raid without any issues, installed windows, and then rebooted. Unfortunately, it was at this time the error in the title appeared. No matter what I did, it would not stop producing the error. Even attempting to boot to my previous hdd (which was not included in the raid set), would produce the same error. The only way to stop it was to turn off the raid and completely remove all of the raid set partitions. This allowed me to boot into my old drive at least. Anyways, any help you can provide on how to make this work would be appreciated. Also, I am new to raid sets, so please keep it in mind when you offer solutions.

Thanks.


  • Specs:
    Operating System
    Windows 10 Pro 64-bit
    CPU
    AMD FX-8120 34 °C
    Zambezi 32nm Technology
    RAM
    32.0GB Dual-Channel DDR3 @ 2400MHz (11-11-11-28)
    Motherboard
    ASUSTeK COMPUTER INC. CROSSHAIR V FORMULA-Z (Socket 942) 28 °C
    Graphics
    G276HL (1920x1080@60Hz)
    2047MB NVIDIA GeForce GTX 750 Ti (EVGA) 28 °C
    Storage
    465GB Seagate ST9500325AS (SATA) 26 °C
    1397GB Western Digital WDC WD15EARS-00Z5B1 (SATA) 33 °C
    465GB Seagate ST9500325AS (SATA) 24 °C
    298GB Seagate ST3320620AS (SATA) 32 °C
    232GB Maxtor 6L250S0 (SATA) 35 °C
    7GB Memorex TRAVELDRIVE 005B USB Device (USB)
    Optical Drives
    HL-DT-ST BD-RE WH12LS30
 
Solution
Sounds like the (new) UEFI messed with your RAID setup. Try reinstalling it using the media and load the drivers for the system before installing. Just make sure that the only disks in the system are the two you will be using.

Also remember that you have to use identical disks for RAID 0 or 1 (I believe all RAID levels using the Intel chipset), so in this case you'll be using your two 500GB seagates.
Sounds like the (new) UEFI messed with your RAID setup. Try reinstalling it using the media and load the drivers for the system before installing. Just make sure that the only disks in the system are the two you will be using.

Also remember that you have to use identical disks for RAID 0 or 1 (I believe all RAID levels using the Intel chipset), so in this case you'll be using your two 500GB seagates.
 
Solution
Welcome, eyanosa!

@basroil make some pretty good points. You should be careful with RAID 0 as this particular array has no redundancy, thus I'd strongly recommend you to keep regular backups if you plan to store any important data on it.
Since you want a bootable array, you'll need to set it up from the RAID BIOS. Make sure you have all the needed RAID controller drivers from your motherboard manufacturer.
I'd try installing Windows again afterwards, just make sure you have only the RAID 0 array HDDs plugged in during the installation, otherwise you might encounter an OS confusion that would result in a lot of booting issues.

Good luck! Keep us updated! :)
SuperSoph_WD
 


Turned out your suggestion about making sure the raid were the only drives in the system during the install was the answer. As for the redundancy issue, I am not worried about it, it is only a gaming pc and I keep constant backups of my personal folders anyways using Macrium Reflect. Thanks for the help.
 
Status
Not open for further replies.