Raid Configuration For New Bios-ASUS

neverknowu

Distinguished
Sep 19, 2012
202
1
18,695
My computer was acting up, with sometimes on a startup I'd have the BIOS screen show up twice before windows would boot. I looked at the BIOS version and it was outdated, so I figured I'd update it. The update went fine, but two drives I had in RAID0 configuration are now corrupted (chdsk didn't work). It's okay, they're backed up, just annoying. So I go into the BIOS and there's Sata Controller 1 and 2. I change SATA controller 1 from AHCI to RAID.

When I did that, the computer begins to start up normally, but then goes automatically into BIOS and does a weird graphic thing, where the image of the BIOS doesn't appear until I brush the mouse over the screen, a pixel at a time. I restarted and entered the BIOS to switch back to AHCI from RAID. I noticed that the two drives I had as RAID0, one is corrupted and another needs to be formatted.

Should I need to reformat the drives first, then go into the BIOS and set SATA controller 1 to RAID to cntrl-I and reconfig the RAID?

Please feel free to comment if what I did was not the right way. I'm still learning.

Thanks!

ASUS X99-E WS 3.1
 
Solution


This, to me, has nothing to do with drives and could be a more serious issue. Is it behaving like this every time? Troubleshooting your RAID should be a last measure until this part behaves properly.

neverknowu

Distinguished
Sep 19, 2012
202
1
18,695


RAID0 because of the amount of HiRes Video footage I work on and need the fastest possible read/write speeds when outputting renders.

Yes, I'm aware. After a job I back up the footage immediately.
 
Well ok - if you really need that extra performance and keep regular backups, then this makes sense.


Not really. You create RAID first, then partition and format.
 

neverknowu

Distinguished
Sep 19, 2012
202
1
18,695


I've done that, but it still won't boot up properly when I set the SATA Mode Selection to RAID. It will only boot up in AHCI.
 

Bootrec

Reputable
Jan 8, 2016
35
0
4,560


This, to me, has nothing to do with drives and could be a more serious issue. Is it behaving like this every time? Troubleshooting your RAID should be a last measure until this part behaves properly.
 
Solution