Newegg.com - A great place to buy computers, computer parts, electronics, software, accessories, and DVDs online. With great prices, fast shipping, and top-rated customer service - once you know, you Newegg.
If you are reading this message, Please click this link to reload this page.(Do not use your browser's "Refresh" button). Please email us if you're running the latest version of your browser and you still see this message.
Yes. There are a few ways to do RAID. Logical RAID is by software in the OS/Kernel layer. Or they will just work fine with a RAID hardware controller. This is my preferred method. The interfaces from all SSD drives work backwards compatible to SATA controllers which prerform the RAID function. When one drive fails, the controller notifies administration. That drive can be deactivated AND replaced. This is the concept.
The type of hard drive (SSD vs. Platter) is transparent to the Raid Controller. It doesn't know what type of drive is connected, only that one is. One of the limitations of SSD is that it's memory can only be written to a finite number of times before it "wears out". For this reason the firmware for the drive has a wear limit indicator beyond which the warranty is void regardless of the age of the drive. For this reason they are not recommended for storage arrays in a server.
I have a workstation running two SSD's striped with no parity foe the boot drive and three WD 500 GB Velocitor SATA drives striped with parity for the storage array. The key thing here is that I've moved the temp files and virtual memory to the SATA array. These two types of files account for a great deal writes/re-writes and will eventually ""wear out" the SSD.
Concerning Phillip A.s answer:
I know that there is a finite amount of reads per memory location (some are 1000) but most people aren't running a RAID 5 setup as a secondary, so moving the temp files and the page file off the SSD will kill much of the performance enhancement that SSD gives to a system. Most SSDs have firmware that tries to not use the same memory location over until all the others have been used, so should take some time to kill enough memory locations to make the drive unusable.. probably long enough to make the drive obsolete.