990FX RAID 0 with EVO SSDs: Windows doesnt recognized array during installation

[mnick]

I'm having a hard time trying to setup my new Asus Sabertooth 990FX R2.0 motherboard with Windows 8 64bit using the onboard AMD RAID controller. What I'm trying to achieve is to install Windows 7/8 Pro 64 bit on the Samsung SSD drives in a RAID 0 configuration. I've tried a lot of different configurations which I'll go over in a moment. I've spent the better half of this last weekend reading the forums and I just can't find a solid answer. I'm starting to believe its unsupported?

Here is a overview of the hardware environment-

* 990FX R2.0 running Firmware 2501 (latest)
* SAMSUNG 850 EVO-Series MZ-75E250B/AM 2.5" 250GB SATA III 3-D Vertical SSD ** Running as RAID 0 ** (OS Drive)
* WD Red NAS Hard Drive WD30EFRX 3TB IntelliPower 64MB Cache SATA 6.0Gb/s 3.5" ** Running as RAID 1 ** (Storage Drive)

// * RAID Hard Drive Configuration *

I've confirmed that I'm using the AMD RAID controller.
I've configured the BIOS to use the SATA configuration as RAID.
I've built the RAID0 in the Legacy RAID ROM with the Samsung disks, with default settings (I've also tried with other settings within the RAID configuration).
I've built the RAID1 in the Legacy RAID ROM with the WD disks.
I've verified that after configuring the two RAID arrays that the BIOS sees the logical disks.

// * Attempt at installing Windows OS *

I get the same results whether I'm using a USB drive(s) or DVD ROM discs, I've gone as far as using different *.ISOs even when creating them with Rufus. The part that I get stuck on is the Windows installation does not recognize the RAID array containing the EVO drives. I've tried RAID 0/1 and both don't show up. The RAID 1 WD array shows up, no problem. I haven't tried to install to this as this isn't my end goal,

I go to load the RAID controller drivers from Asus's website and AMD's website and they don't work. I'm not able to get the AMD driver to even display on the list. Asus's driver shows the driver available and it loads it but still does not display the RAID 0 SSD array. On that note here are some details as to what I've tried-

I removed the WD drives from the equation (only the SSDs are connected) but the array does not show up under Windows Vista/7/8 Pro 64 bit installations.
I've unchecked the "hide drivers that aren't compatible with my system" when loading the drivers and individually loaded each of the the drivers on the list (even though they all show the same driver ahcix64s.inf).
I've canceled out of the loading drivers screen and swap USB ports (wild guess as previously suggested)
I've tried different USB drives, different USB ports (2.0 vs 3.0).
I've removed all the disks from arrays and they all show up during the Windows installation when the board is configured for AHCI.
I've tried the AMD SATA 3.0 controller ports on the board.
I've tried to install AMD's drivers even with "hide drivers that aren't compatible with my system" unchecked, including 32 bit as this supposedly has worked for some, without luck.

I'm sure there is more that I've tried but honestly, my head hurts. I'm open to suggestions at this point hence this forum post.

What is the workaround? Install the OS on a drive I don't need, as a temporary OS and then install Win8 64 bit Pro onto the RAID 0 from the GUI and reboot but upon rebooting, unplug all the drives except for the RAID 0 which contains the SSDs?

I was going to check the firmware on the EVO drives as I haven't explored that avenue yet.

Anyhow, thanks for reading

Cheers!

 

[Carbongrip]

there's FAR easier ways to expand storage, like making symbolic links. they can be added on-the-fly (within the OS) and spread over as many SSDs as you can connect.

Only your solution requires you to backup many disks, where my raid solution is 1 logical disk that can backup to 1 external drive on the fly. I just think you are scared of raid when really it's been used by enterprises for years.

 

[giantbucket]

6 of one, half dozen of the other. nobody is scared of raid, where'd you come up with something as stupid as that? clearly, this amd board is simply being a pain for the OP. typically, most (silly) people try to do a raid-0 of ssd for the speed, not for storage. they then run benchmarks to prove that they can get more speed, even though for the vast majority of their actual use, they get very minor benefits for their effort. or in this case, a ridiculous amount of effort.

raid is far from being the only and perfect solution to every life problem. as this whole thread clearly illustrates.

 

[m00ntan]

Just to keep this alive, I had a need for raid 1 since hdd failure is not an option. The issue is with the 990FX chip. The instructions indicate there are no issues. Unfortunately, if you configure the controller as RAID, the SSD drives simply are not there.

 

[Adomas]

Hello,

Another guy with the same problem MSI Gaming 970 + 2x Samsung EVO 850 250GB.
Anyone managed to get this working somehow? I still want to use RAID0 as I already have bought two SSD`s...

 

[giantbucket]

i think the choices are Intel or a RAID card... or just use one SSD since the benefits of RAID 0 with SSDs are marginal.

 

[Adomas]

Well I managed to find out that even Acronis Disk Director finds this RAID0 created from EVO SSDs. I tried to clone my current RAID0 (2GBx64 Adata`s) to the RAID0 consisting of 2 EVO`s - windows magically find "something" from the secondary array (picture attached). I then tried to boot from the new array and all most went cheering when Windows started loading... And encountered BSOD.
I`m confused now again, is it a Windows/AMD driver problem, or Samsung SSD`s itself?

 

[dhansen105]

Hello everyone I feel your pain whoever has been having this problem. I just today got my two 250gb 850 evo's. i was extremely excited to throw them in a raid 0 array on my windows 10 box. This quickly turned it to disappointment and then into anger...

Motherboard - ASUS Sabertooth 990FX R2.0

I did it though finally. I cannot speak for what 100% came to be the reason because I have no idea for sure what worked.

Here is the final steps I took between when I last checked if windows recognized my drive to when windows finally did recognize my raid array. I hope it will work for some of you as well!!!!

First off what clued me in... I installed a live linux distro and checked if this recognized the raid array. It did and worked flawlessly.
This clued me into it must be either a driver issue or windows itself.

1) I took my drives out of my box and hooked them up to my laptop one after the other and did the following steps 2 - 4

2) I downloaded Samsung Magician Software and updated the ssd to the latest Firmware release. (Requires restart for each)

3) I opened up windows disk management tool. Right clicked on the 850 evo drive and followed the steps to create a new volume and partition. (all default values)

4) Safely Removed drive.

5) Hooked both drives back up to my pc.

6) Booted windows under UEFI (drives visible) no suprise, just double checking

7) Booted windows under RAID (drives visible) a little surprise but no hopes up yet since this is the first time I attempted this with drives volumed.

8) Booted into Amd raid rom utility and created raid 0 array (with all settings as default)

9) Restarted and booted into windows.

10) Boom 498GB drive found!!!!! Didn't even need to install drivers. Couldn't believe all the hours I spent on that.

I really hope this works for you guys. Let me know thanks!

 

[giantbucket]

hmm.... maybe it's an alignment thing? could be that Windows formatting of individual drives does the right alignment, but the AMD RAID utility doesn't alight things correctly when making new partitions?

 

[dhansen105]

hmm.... maybe it's an alignment thing? could be that Windows formatting of individual drives does the right alignment, but the AMD RAID utility doesn't alight things correctly when making new partitions?

It is possible I suppose. It still brings up the question, why the heck did the Linux driver have no problem picking it up. Knew it was raid and everything. Maybe the Linux raid driver just supports more configurations. I honestly don't know. None the less it is fixed now the benchmarks proved it was working correctly for me.

And FYI to all the people bashing on the need for raid0 for ssds. You must remember some of us computer guys are really bull headed. Once we set our minds to something it has to be done. It will not satisfy us until it is fixed. I don't believe the guys question was help me decide whether I should do raid or not with ssds. This thread would be a single page if it weren't for the all the arguments going on. A single hint is just fine. No need to bash. =)

 

[Gabriel51]

I have talked to Samsung twice about my 850 EVO not having the performance claimed and I have been told twice it is the limitations of my AMD chipset (SB950).
The second call was to ask if using a PCIe adapter would allow full performance, no was the answer. I was thinking the converter between SATA and PCI was a bottle neck but no according to Samsung...

 

[Palorim12]

I have talked to Samsung twice about my 850 EVO not having the performance claimed and I have been told twice it is the limitations of my AMD chipset (SB950).
The second call was to ask if using a PCIe adapter would allow full performance, no was the answer. I was thinking the converter between SATA and PCI was a bottle neck but no according to Samsung...

PCI-E adapters will usually give you better than SATA II performance, but don't always give full SATA III perfromance.

Also, from:
http://us.hardware.info/reviews/2712/3/six-ssds-in-raid-0-intel-vs-amd---which-chipset-scales-the-best-amd-990x--sb950-chipset

"The AMD SATA controllers have inferior performance compared to Intel's... In practice, Intel scales better than AMD... Despite the fact that AMD has six SATA 600 ports, it doesn't scale as well."