I am unable to get Windows installed on of my SSDs if they are set in a RAID volume. Windows tells me the drives are not bootable, and the BIOS won't let me select them as bootable, either; it only reads the two ODDs I have connected.
If I setup the RAID array through EZSetup, I can boot into Windows but I run into the problem above. If I reboot the computer, the BIOS pretends the RAID array is not usable entirely when I go to the EZSetup; it will detect it but I cannot do anything with it other than delete the array in advanced mode and start over. Windows won't even let me format the drives, whether installed as a RAID array or independent.
Resetting the BIOS didn't help. ASUS tech support suggested calling Intel, but that basically just means that I need a new motherboard. What gives? These drives are leftover from a previous system in which they were the boot drives, but I should just be able to overwrite them.
Any help that means I don't need to turn my motherboard in for a return would be greatly appreciated! I am on vacation from work this whole week, so an RMA basically means I won't get anything back until my vacation is over and free time is gone.
Edit: OK, I managed to get Windows to install on a single SSD. But, if I enabled RAID in the BIOS, everything goes kaput again. Is a RAID volume not a possible boot device anymore? If not, I'll have to go M.2 for games. Someone just tell me this is all normal and I don't need to RMA, please!
I finally figured out what this guy was talking about:
And now it works. Why would using the new BIOS type (UEFI) make bootable RAID impossible? This seems like a huge boo boo on the part of the tech people who developed this. Surely there is a reason...Edited by stargate125645 - 2/22/16 at 5:52pm