It is possible you are not getting TRIM from the Intel® Chipset to the SSDs.
You may need to mount each drive in different SATA controller or computer and optimize it there.
Check the following discussion in regards of RAID 5: https://communities.intel.com/thread/18400?start=45&tstart=0
Thanks, so TRIM won't run over RAID?
I did break the array trying to go back to single disk mode. Is there any way to tell RST when the RAID1 is degraded to just send the remaining good disk back as a regular volume? I thought it would be cool and noble to do R1 SSD, but I'm regretting my decisions and will just rely on backup and single disk SSD performance going forward. Can you help with getting my system back to single disk without rebuilding?
You were right, and further research seems to elude to that RST doesn't TRIM RAID1 at all (although RAID0 it does). Such a shame...
What I did was:
1. Removed one SSD from that system and put it into another desktop
2. Ran CrystalDisk on that SSD as is in the new system, got 40 MB/s write
3. Used SanDisk SSD Dashboard to TRIM that SSD
4. Re-ran CrystalDisk and immediate got 164 MB/s write
After that, I sanitized the disk and put it back in, rebuilt the RAID array (which took only like 2 minutes), then removed the other drive, TRIM'd, sanitized and am now rebuilding it again. So the issue is related to RST especially in RAID1 where it never TRIMs.
I imagine I can do this in the future without sanitizing and just running TRIM from a separate client, but that's a pretty involved task. I hope Intel comes around to adding TRIM support for R1.
I am not sure what you meant by “sanitizing” but I suspected that the lack of TRIM was causing the poor write performance.
Just as a side note, you can reset RAID 1 volumes to non-RAID disks without losing data because it is a mirror. This cannot be done in any other RAID type; the data will be destroyed in the process.
Joe, I understand RAID mirrors, but my question was how I can actually take a single drive and through Intel RST remove all memory of the R1 array? This way I could:
1) Remove R1 array, select SSD1 as new C Drive
2) TRIM SSD2
3) Rebuild R1 array with SSD2
4) Remove R1 array, select SSD2 as new C Drive
5) TRIM SSD1
6) Rebuild R1 array
Even when I physically removed an SSD, RST complained about degraded array, but where is the option to convert that to a single drive (non-array)?
1 of 1 people found this helpful
The option “Reset disks to non-RAID” is available through the Option ROM (RAID BIOS) by pressing Ctrl + I before the operating system starts booting.
However, when creating a new RAID array, you can only keep the existing data when using Intel(R) Rapid Storage Technology in Windows*; otherwise the data will be destroyed if the array is created in the Option ROM.
Thank Joe, I hadn't thought to check the BIOS setting. That is helpful! Thanks for all of your help.
I just wanted to mention that I don't believe your particular mboard supports server 2012r2, in fact it's not even a full size board. Here is a suitable product that would reuse your cpu and memory but in micro atx form, not sure mini itx can be used for a server, maybe it's available but that is real small
I believe that part of your problem is that you are trying to run a server on a low end board meant for windows 7 or 8. I have many systems built on the 1155 platform with dual intel ssds in raid 1 and have not had any issues. Also, if you are using the lower end Intel ssds, you may wish to try the S3500 or S3700 datacenter series, they are meant to work on a server without the benefits of idle time for garbage collection and trim. See this from the http://www.intel.com/content/dam/www/public/us/en/documents/white-papers/ssd-server-storage-applications-paper.pdf page 13--
It is best to test the use of TRIM in your environment before wide adoption. TRIM does not always
improve performance in enterprise applications due to the possibility of increasing latency. Intel SSD
DC S3700 Series drives contain more spare area than many other SSDs. This increased spare area
gives the SSD more room to move blocks of data as it performs its tasks, thereby diminishing the
benefit of using TRIM.