I'm going to have the SSD as my main boot drive and I want to have two normal HHDs in raid 0. I gather you have to set sata in AHCI mode in the BIOS for the SSD, though I seem to remember it was an either or thing between ACHI and RAID last time I checked my bios, can't check for sure at the mo cos it is in bits. What is the best way to configure this if it is either or, or is it likely that I am mistaken about this (asus rampage II extreme)? Do you need to install both the RST drivers and the raid drivers in windows as well?
Noddy question: Setup for SSD + spinner RAID
- Thread starter Bubo
- Start date
After doing some digging I think I am in a position to answer my own question.
There are two conflicting bits of information on the Intel site...
From the Intel SSD Toobox software user guide, page 11 it says...
"Intel Rapid Storage Technology driver V9.6 supports the Windows 7 Trim command, but for Non-Raid configurations only. In these configurations Intel SSD Optimiser is not required to enable trim"
This wording kind of suggests that any hint of raid borks trim support, I guess including the event that Sata set to raid mode in bios but only hdds in the array. This paragraph in the user guide is not exactly clear though, as you could equally read it as saying that you are okay as long as the ssd is not part of an array.
However, a separate bit in the intel site says...
"Intel® Rapid Storage Technology 9.6 supports TRIM in AHCI mode and in RAID mode for drives that are not part of a RAID volume."
This seems much more emphatic about it and answers my question, though it would be nice if they could make their own user guide pdf as clear as this.
So as long as your SSD is recognised by the BIOS when you initially install windows with raid enabled in bios then it should work ok and have trim support as standard, as long as you don't put the SSD in an array.
There are two conflicting bits of information on the Intel site...
From the Intel SSD Toobox software user guide, page 11 it says...
"Intel Rapid Storage Technology driver V9.6 supports the Windows 7 Trim command, but for Non-Raid configurations only. In these configurations Intel SSD Optimiser is not required to enable trim"
This wording kind of suggests that any hint of raid borks trim support, I guess including the event that Sata set to raid mode in bios but only hdds in the array. This paragraph in the user guide is not exactly clear though, as you could equally read it as saying that you are okay as long as the ssd is not part of an array.
However, a separate bit in the intel site says...
"Intel® Rapid Storage Technology 9.6 supports TRIM in AHCI mode and in RAID mode for drives that are not part of a RAID volume."
This seems much more emphatic about it and answers my question, though it would be nice if they could make their own user guide pdf as clear as this.
So as long as your SSD is recognised by the BIOS when you initially install windows with raid enabled in bios then it should work ok and have trim support as standard, as long as you don't put the SSD in an array.
Soldato
Having just realized I might have a problem with the wish to use 40gb ssd as o.s. drive with 2 x Samsung F4 in Raid 0 this information came as a relief. Many thanks
For a couple of versions now (9.6?) Intels RST drivers have supported exactly what you want - Trim pass through to a single SSD when the SATA controller is in RAID mode.
What it does not support is Trim on SSDs that are part of an array
Edit: On actually reading your second post properly, I realise this is redundant, sorry.
On topic though, Trim isn't as big a deal as it's made out to be. It's worth around 10-20% at best on any decent drive, and then only if you are hammering it with benchmarks or databases. Under normal conditions it's a non-issue.
What it does not support is Trim on SSDs that are part of an array
Edit: On actually reading your second post properly, I realise this is redundant, sorry.
On topic though, Trim isn't as big a deal as it's made out to be. It's worth around 10-20% at best on any decent drive, and then only if you are hammering it with benchmarks or databases. Under normal conditions it's a non-issue.
Last edited: