Help with a RAID config

[Bhavzzz]

Hello good people of LTT

 

So, a quick question, I want to introduce a RAID 1 array to my machine for redundancy but I seem to be running into a snag.  I have Windows 10 installed on my 960 EVO and created the RAID 1 volume in my UEFI, but Windows keeps giving me a "boot drive not accessable" BSOD. 

 

I've already tried forcing the next boot to be in safe mode in windows before enabling RAID but the error still comes. 

 

Any idea?

[AdamBGames]

5 minutes ago, Bhavzzz said:

Hello good people of LTT

 

So, a quick question, I want to introduce a RAID 1 array to my machine for redundancy but I seem to be running into a snag.  I have Windows 10 installed on my 960 EVO and created the RAID 1 volume in my UEFI, but Windows keeps giving me a "boot drive not accessable" BSOD. 

 

I've already tried forcing the next boot to be in safe mode in windows before enabling RAID but the error still comes. 

 

Any idea?

there are 2 sets of sata ports on your motherboard, one is connected to the cpu the other is connected to the chipset. move the hard drives onto the other set of sata ports and try again, if you look at this image, there are 2 sets of ports

[Anghammarad]

Another question from me, did you install windows 10 after creating the raid, or afterwards?

 

If afterwards it is no surprise that you get this.

 

In worst case you could have erased your main drive doing it after the installation, because the board uses the empty drive as primary drive then mirrors it onto the secondary giving you a fresh empty system.

[Electronics Wizardy]

16 minutes ago, Bhavzzz said:

Hello good people of LTT

 

So, a quick question, I want to introduce a RAID 1 array to my machine for redundancy but I seem to be running into a snag.  I have Windows 10 installed on my 960 EVO and created the RAID 1 volume in my UEFI, but Windows keeps giving me a "boot drive not accessable" BSOD. 

 

I've already tried forcing the next boot to be in safe mode in windows before enabling RAID but the error still comes. 

 

Any idea?

don't use raid 1 here, use backups. There much better at keeping your data safe. 

[Electronics Wizardy]

14 minutes ago, AdamBGames said:

there are 2 sets of sata ports on your motherboard, one is connected to the cpu the other is connected to the chipset.

With intel, there are no sata connected to the cpu.

 

 

[AdamBGames]

Just now, Electronics Wizardy said:

With intel, there are no sata connected to the cpu.

 

 

ah, is that only with AMD? My B

[Electronics Wizardy]

5 minutes ago, AdamBGames said:

ah, is that only with AMD? My B

only with ryzen and newer.

 

All other platforms are running sata off the chipset. The os drive stick is bs, you can use any port. you can't run mobo raid between a intel/amd chipset and a third party one if the board added one.

 

You shouldn't be running raid on the motherboard anyways, it sucks. Use software raid for most uses.

 

For this use use backups instead much better.

[Bhavzzz]

16 minutes ago, Anghammarad said:

Another question from me, did you install windows 10 after creating the raid, or afterwards?

 

If afterwards it is no surprise that you get this.

 

In worst case you could have erased your main drive doing it after the installation, because the board uses the empty drive as primary drive then mirrors it onto the secondary giving you a fresh empty system.

After, but I know my windows drive is fine. Just a simple switch back to AHCI and I'm back in windows. 

[Anghammarad]

then you need to infuse the raid drivers into windows, and change some registry settings before booting the next time.

 

Don't have them at hand, but google helps =) 

[Electronics Wizardy]

15 minutes ago, Bhavzzz said:

After, but I know my windows drive is fine. Just a simple switch back to AHCI and I'm back in windows. 

because your using a different driver to access the drives, you can load the kernel just fine, but it can't access the root volume.

 

Why do you need raid1, use backups.