Issue with existing OS and adding RAID1

[nowikovs12]

Hi everyone. 

In my ASUS motherboard (Z9PE-D8 WS) workstation I have an existing windows 10 which I am using as normal. OS is installed on SSD 1TB Samsung Evo. 

 

I now have purchased additional 2x 6TB Western Digital Red drives which I would like to place as RAID1 configuration, so that I have another volume in system to store my files and rest in peace knowing that 2x drives are mirroring information in case one is to fail.

 

I fallowed all the procedures on my motherboard manual and in BIOS enabled from SATA Mode to RAID Mode. Once that was done, I rebooted computer, pressed ctrl + I and completed set up of two WD drives as RAID1. 

 

Once I restarted the device I got the blue screen with sad face. I looked online and from my understanding (and this is where I would like to receive confirmation from intelligent people here) I should only change SATA Mode to RAID Mode if I am to install OS after RAID setup. If I already have an existing OS set up and go in BIOS to change the mode settings, the blue error screen is normal. 

 

So my understanding is that I should instead of using hardware RAID1 setup, use software RAID1 (mirror) set-up such as "Disk Management" built in Windows 10. 

 

Could you please confirm on the above.

 

What is also interesting, now that I have setup the RAID1 volume using ctrl+I (when RAID mode was enabled in BIOS, now I have it set back to SATA mode and don't have the blue screen), it appears in "Disk Management" as a single drive (see attachment). I also get a pop-up window (see attachment) asking me to "Initialize Disk". Does this mean the RAID1 configuration is working fine for those drives and I will have both drives mirrored? 

 

I really look forward to your responses. 

 

Thank you everyone! 

[Tabs]

The array won't work unless you're in RAID mode. Everything you said was essentially correct; you CAN swap an AHCI/Sata install to one set up to use RAID however - it's a bit of a pain in the ass.

 

Your choices at this point are either:

 

1. Reboot back in RAID mode, dismantle the array using the same rom you created it in the first place, and then swap back to SATA - at which point you'll see both drives individually in Windows and can set up Software mirroring.

 

2. Follow instructions such as here in order to convert your current install from SATA/AHCI mode to Raid. It basically involves rebooting to safe mode, then rebooting again back into normal windows. I have not tested these instructions on Windows 10, but I know they worked for 8 and 8.1.

 

Option #2 would let you use the array that's technically set up right now. 

 

I would personally recommend you go through option 1 to use windows built in software mirroring - if you ever have to replace a motherboard and you're using quasi-hardware raid, there's zero guarantee that your array will mount properly on the new board. With software mirroring, so long as you're using both drives in any system with Windows 7+ on it, the array should be able to be imported with no issues.

[nowikovs12]

Thank you Tabs for your clear reply. 

 

One last question:  

 

"so long as you're using both drives in any system with Windows 7+ on it, the array should be able to be imported with no issues." Say, I have successfully set up the software mirror using windows "Disk Management" and one of the two drives fails, my information will be safe with the other drive, correct?

 

Thanks Tabs, I will now proceed with deleting the RAID FROM bios and then setting up the software version instead. 

[Jarsky]

Are you sure you were in SATA mode before, and not in IDE mode?

The problem generally occurs when you switch from IDE mode to AHCI mode which is used for both SATA and RAID in the BIOS.

 

When that happens Windows either needs a *registry hack* to function in AHCI mode (Boot safemode and change a registry key), or more commonly - to reinstall the OS.

You can switch RAID mode on or off at will when your OS is already installed in AHCI mode. 

 

Other than that, I'm not sure what else would cause a blue screen...