New build RAID 0 Setup Issue

M3htal · November 18, 2015

Good Morning All.

I wanted to jump right in but I need to give you a list of what I am using:

GIGABYTE GA-990FXA-UD3 R5 (rev. 1.0)

SAMSUNG 850 EVO 2.5" 250GB SATA III x2 For RAID 0 setup

Windows 8.1 PRO on USB

So with this motherboard, there are three ways to configure read. UEFI, the old SB950 way, and the Marvell Controller.

The only one I can get to post correctly for an unknown reason is the SB950 controller using the CTRL+F feature for AMD chipsets.

Now this isn’t the end of the world. What is though is once the LD is configured in the bios menus, I then boot to the USB to install Windows.

I am having an issue where the drives will not show up in the windows install. Side not but important, the 2 SSDs are in SATA 0 and SATA 1 slot recommended per mfg install guide.

I have tried using the DVD that was in the mob box but no luck there. I tried going to mfg website:

http://www.gigabyte.us/products/product-page.aspx?pid=5294&dl=1#driver

No luck at all. I get a 404 Not Found for the drivers. I even used the Russia HTTP link and downloaded them very very slow I might add.

So all this ended at 3am when I got frustrated after working on this new build for 8 hours trying everything I could possibly think of.

If someone can point me in the right direction that would be great. Thanks.

M3htal · November 18, 2015

Anyone have any recommendations? Could it be a bad mobo?

I removed the SB950 raid and then booted into Windows Install. I am able to see the drives without them being in raid and have installed windows on one for testing and everything is working fine.

Raid Controls seems weird on this mobo/build.

tbroadwater2010 · November 18, 2015

Anyone have any recommendations? Could it be a bad mobo?

I removed the SB950 raid and then booted into Windows Install. I am able to see the drives without them being in raid and have installed windows on one for testing and everything is working fine.

Raid Controls seems weird on this mobo/build.

Have you updated the BIOS? maybe it was a known issue?