How To Set Up RAID With SSDs: Beginners Guide
You’ve got a fast SSD, maybe even a blazing NVMe drive, and you’re wondering if you can make things even faster by combining multiple drives in a RAID array. Or maybe you’re more concerned about protecting your data and want a mirror of your boot drive just in case something fails. Either way, RAID with SSDs is absolutely doable, and it can be incredibly powerful when set up correctly.
But RAID was originally designed in an era of slow, mechanical hard drives. With modern SSDs already delivering read speeds measured in thousands of megabytes per second, does RAID even make sense anymore? The short answer is: it depends on what you’re trying to accomplish. And this guide will walk you through exactly how to figure that out and get everything configured.
Whether you’re building a home NAS, setting up a workstation for video editing, or just want some extra insurance against drive failure, this guide covers what you need to know about RAID with SSDs from the ground up.
What Is RAID and Why Would You Use It With SSDs?
RAID stands for Redundant Array of Independent Disks. It’s a method of combining multiple storage drives into a single logical unit. Depending on the RAID level you choose, this can give you faster performance, data protection against drive failure, or both.
With traditional hard drives, RAID was often the only way to get acceptable performance for demanding tasks. SSDs have changed that equation significantly, but RAID still serves important purposes. A RAID 1 mirror protects you if a drive dies unexpectedly. A RAID 0 stripe across two NVMe drives can push sequential read speeds past 10,000 MB/s. For NAS builds serving multiple users, RAID 5 or RAID 10 with SSDs provides both speed and fault tolerance that a single drive simply can’t match.
Understanding the Common RAID Levels
RAID 0: Pure Speed, Zero Safety Net
RAID 0 stripes data across two or more drives. Every read and write operation gets split between the drives, which roughly doubles your throughput with two drives, triples it with three, and so on. If you’re doing large file transfers, video editing, or working with massive datasets, RAID 0 with SSDs is genuinely impressive.
The catch with RAID 0 is that there’s no redundancy at all. If one drive fails, you lose everything on the entire array. With two drives in RAID 0, you’ve actually doubled your chance of catastrophic data loss compared to a single drive. Only use RAID 0 for data you have backed up elsewhere, like a scratch disk for video projects or a game library you can re-download.
For RAID 0, two matched SATA SSDs like the Samsung 870 EVO will give you sequential speeds rivaling a single NVMe drive. Two NVMe drives in RAID 0 will blow past anything a single drive can do.
RAID 1: The Safety Mirror
RAID 1 mirrors data identically across two drives. Everything written to one drive is simultaneously written to the other. If either drive fails, you keep working on the surviving drive without any data loss. You get the full capacity of only one drive (the other is a copy), but your data stays safe.
Read speeds can actually improve in RAID 1 since the controller can read from both drives simultaneously. Write speeds stay roughly the same as a single drive. RAID 1 is ideal for your operating system drive, critical work files, or any data you can’t afford to lose.
For a reliable RAID 1 setup, the Samsung 990 EVO Plus 2TB is a strong choice thanks to its excellent endurance rating and consistent performance under sustained loads.
Samsung 990 EVO Plus 2TB NVMe SSD
Excellent endurance and consistent write speeds make this ideal for RAID 1 mirror configurations where reliability matters most
RAID 5: The Balanced Option
RAID 5 requires a minimum of three drives and distributes parity data across all of them. You can lose any single drive without losing data. Your usable capacity equals the total capacity minus one drive (so three 1TB drives give you 2TB of usable space).
RAID 5 with SSDs eliminates one of the biggest historical complaints about this configuration: the write penalty. With hard drives, RAID 5 writes were painfully slow because of the parity calculations. SSDs handle random I/O so well that this penalty becomes far less noticeable. For a home NAS or small business file server, RAID 5 with SSDs is an excellent middle ground between capacity, protection, and cost.
One important note: RAID 5 rebuild times with very large drives can be lengthy, and during a rebuild, you’re vulnerable to a second failure. With drives larger than 4TB, many experienced builders prefer RAID 6 (which can survive two simultaneous failures) or RAID 10.
RAID 10: The Best of Both Worlds
RAID 10 combines RAID 1 and RAID 0. It requires a minimum of four drives. Data is mirrored in pairs (RAID 1), and those pairs are striped together (RAID 0). You get both the speed of striping and the safety of mirroring.
The downside is cost. You lose 50% of your total capacity to mirroring. Four 2TB drives give you 4TB of usable space. But for performance-critical applications that also need data protection, like database servers, virtual machine hosts, or professional media production, RAID 10 with SSDs is the gold standard.
Hardware RAID vs. Software RAID: Which Should You Choose?
Hardware RAID
A dedicated hardware RAID controller has its own processor and memory to handle all RAID calculations independently of your system’s CPU. High-end cards from manufacturers like LSI (Broadcom) and Adaptec offer battery-backed cache, which protects data in transit during a power failure.
Hardware RAID controllers aren’t cheap, and the good ones can cost as much as the drives themselves. They also lock you into a specific vendor. If the RAID card itself fails, you’ll typically need the same model (or at least the same family) to recover your array. For enterprise environments and professional use, hardware RAID makes sense. For most home users and enthusiasts, it’s overkill.
Also, be aware of “fake RAID” or “host RAID” built into many motherboard chipsets (like Intel Rapid Storage Technology). These rely on your CPU for processing and are really a hybrid between hardware and software RAID. They work fine for basic setups but don’t offer the same reliability as a true hardware controller.
Software RAID
Software RAID uses your operating system and CPU to manage the array. Modern CPUs are powerful enough that the performance overhead is negligible for most use cases. Windows has Storage Spaces, Linux has mdadm, and macOS has Disk Utility (though Apple has been scaling back RAID support in recent years).
For most home users and even many small businesses, software RAID is the better choice. It’s free, it’s flexible, and it doesn’t tie you to a specific hardware controller. If your motherboard dies, you can move the drives to a completely different system and reassemble the array.
Linux’s mdadm in particular is battle-tested and extremely reliable. If you’re building a NAS with TrueNAS or Unraid, those platforms have their own excellent software RAID implementations (ZFS and Unraid’s parity system, respectively).
Step-by-Step: Setting Up a Basic RAID Array
Setting Up RAID in BIOS (Motherboard RAID)
- Install your drives. Make sure all SSDs are the same model and capacity for best results. Mismatched drives will work but the array will be limited to the size and speed of the smallest/slowest drive.
- Enter BIOS/UEFI. Restart your computer and press the appropriate key (usually DEL or F2) to enter your motherboard’s BIOS.
- Change SATA mode to RAID. Look under your storage or advanced settings. Change the SATA controller mode from AHCI to RAID. For NVMe drives, look for an NVMe RAID option if your motherboard supports it (most AMD X570/X670 and Intel Z690/Z790 boards do).
- Save and reboot. Your system will restart and you should see an option to enter the RAID configuration utility (often Ctrl+I on Intel systems).
- Create your array. Select the drives, choose your RAID level, set the strip size (128K is a good default for SSDs), and create the volume.
- Install your operating system. You may need to load the RAID driver during OS installation. Download the driver from your motherboard manufacturer’s website and put it on a USB drive beforehand.
Setting Up Software RAID in Windows (Storage Spaces)
- Open Control Panel and navigate to Storage Spaces.
- Click “Create a new pool and storage space.”
- Select the drives you want to include. These must be non-system drives (you can’t add your Windows boot drive to a Storage Space).
- Choose your resiliency type: Simple (RAID 0), Two-way mirror (RAID 1), Three-way mirror, or Parity (similar to RAID 5).
- Set the size and drive letter, then click Create.
Storage Spaces works well enough for basic configurations, though it historically hasn’t performed as well as Linux alternatives for parity setups. For RAID 0 and RAID 1 equivalents, it gets the job done.
Best SSDs for RAID Configurations
Not all SSDs are equally suited for RAID. You want drives with consistent performance, good endurance ratings, and ideally a DRAM cache for sustained workloads. Here are some solid picks for different scenarios.
For SATA RAID arrays, the Samsung 870 EVO remains one of the most reliable options. It offers excellent endurance, consistent speeds, and Samsung’s track record for reliability is hard to beat. Grab two or more of the same capacity for your array.
For NVMe RAID, the WD Black SN7100 is a fantastic option, especially for a RAID 0 setup aimed at maximum throughput. It’s a PCIe Gen 4 drive with excellent sustained write performance.
WD Black SN7100 NVMe SSD
Fast PCIe Gen 4 drive with strong sustained write speeds, perfect for NVMe RAID 0 or RAID 1 configurations
For NAS RAID arrays that will run 24/7, look for drives specifically designed for NAS use. The Synology SAT5210 and similar enterprise-grade SATA SSDs offer power loss protection and higher endurance ratings that matter for always-on systems.
Does RAID Still Make Sense With Modern NVMe SSDs?
This is a fair question. A single PCIe Gen 4 NVMe drive already delivers around 7,000 MB/s sequential read speeds. Gen 5 drives are pushing past 12,000 MB/s. For everyday computing, gaming, and even most professional workloads, a single fast NVMe drive is more than sufficient.
RAID 0 for speed only makes sense when you’re regularly working with files large enough to actually benefit from the extra throughput. Think 4K/8K video editing, large database operations, or scientific computing with massive datasets. If you’re mostly gaming or doing general productivity work, you won’t notice the difference between a single NVMe and a RAID 0 array in daily use.
RAID 1 for redundancy, on the other hand, still makes plenty of sense. SSDs can and do fail, sometimes without warning. Having a mirror of your critical data provides protection that no amount of speed can replace. Just remember that RAID is not a backup. A mirror protects against hardware failure, but it won’t save you from accidental deletion, ransomware, or file corruption. You still need a proper backup strategy.
For NAS builds, RAID (or RAID-like systems such as ZFS and Unraid parity) remains essential. These systems serve data to multiple users and devices simultaneously, making both redundancy and aggregate throughput genuinely important.

Samsung 870 EVO SATA SSD
The go-to SATA SSD for RAID arrays in NAS builds due to its proven reliability and excellent endurance ratings
Common Mistakes to Avoid
- Mixing different drive models or capacities. Your array will be limited to the smallest drive’s capacity and the slowest drive’s speed. Always use identical drives.
- Treating RAID as a backup. RAID protects against drive failure only. It does not protect against data corruption, accidental deletion, viruses, or theft. Always maintain a separate backup.
- Forgetting about TRIM support. Make sure your RAID controller or software supports TRIM passthrough for SSDs. Without TRIM, SSD performance degrades over time. Most modern software RAID solutions handle this correctly, but some older hardware controllers don’t.
- Using consumer SSDs in 24/7 NAS environments. Consumer SSDs aren’t designed for constant read/write operations. For NAS use, choose drives rated for higher endurance (look for DWPD, or Drive Writes Per Day, ratings of 1.0 or higher).
- Not monitoring drive health. Set up SMART monitoring for all drives in your array. Catching a failing drive early lets you replace it before the array degrades.
Frequently Asked Questions
Can I RAID NVMe and SATA SSDs together?
Technically, some software RAID solutions will let you combine drives of different interface types. However, this is a bad idea in practice. The array’s performance will be bottlenecked by the slower SATA drive, wasting the potential of the NVMe drive. Always match your drives by interface type, model, and capacity for the best results.
Will RAID void my SSD’s warranty?
No. Using SSDs in a RAID array does not void the manufacturer’s warranty. However, if a drive fails and you need a warranty replacement, you’ll typically need to send in just the failed drive. The manufacturer won’t help you rebuild your array. That’s on you.
How many SSDs do I need for different RAID levels?
RAID 0 requires a minimum of two drives. RAID 1 requires exactly two drives (for a standard mirror). RAID 5 requires a minimum of three drives. RAID 6 requires a minimum of four drives. RAID 10 requires a minimum of four drives (and must be an even number). For home use, most people start with two drives in either RAID 0 or RAID 1, depending on whether they prioritize speed or safety.
Is ZFS better than traditional RAID for SSDs?
ZFS is a filesystem and volume
James Kennedy is a writer and product researcher at Drives Hero with a background in IT administration and consulting. He has hands-on experience with storage, networking, and system performance, and regularly improves and optimizes his home networking setup.

