RAID Redundancy Explained: Mirroring, Parity and Fault Tolerance
“Redundant” is the R in RAID, and it’s the main reason most people build an array. But RAID redundancy is narrower than it sounds. It means the array can lose a certain number of drives and keep serving your data. It doesn’t mean your data exists in two independent places, and it doesn’t protect against most of the ways people actually lose files. Here’s what redundancy really buys you, how each RAID level provides it, and where it stops.
What RAID redundancy means
Redundancy in RAID is extra information stored across the drives so that the array can rebuild whatever was on a failed drive. There are two ways to do it.
Mirroring
Every block is written to two (or more) drives. If one drive dies, its twin has a complete copy. Mirroring is simple and rebuilds are fast, because the replacement drive is just copied from its partner. The cost is capacity: a two-drive mirror gives you one drive’s worth of space.
Parity
Instead of a full copy, the array stores a calculated value (parity) for each stripe of data. If one drive’s piece of a stripe is missing, the controller can work it out from the remaining pieces plus the parity. Parity uses less space than mirroring, but every write involves extra calculation, and rebuilding a failed drive means reading every remaining drive in full.
Our what is RAID guide covers striping, mirroring and parity in more depth if you’re new to the terms.
Fault tolerance by RAID level
Fault tolerance is how many drive failures the array can survive before data becomes unavailable.
| Level | How redundancy works | Drive failures survived |
|---|---|---|
| RAID 0 | None (striping only) | 0 |
| RAID 1 | Mirroring | All but one drive in the mirror |
| RAID 5 | Single parity | 1 |
| RAID 6 | Dual parity | Any 2 |
| RAID 10 | Mirrored pairs, striped | 1 per mirror pair, at most |
| JBOD / span | None | 0 |
A few points the table can’t show:
- RAID 0 has no redundancy at all. Despite the name, losing any member loses the array.
- RAID 10’s tolerance depends on which drives fail. It can survive several failures if each is in a different pair, but losing both drives in one pair takes the array down.
- “Survives one failure” assumes the other drives are perfect. If a second drive has unreadable sectors, a RAID 5 rebuild can stall or fail. That’s the main argument for RAID 6 on large drives. See RAID 5 vs RAID 6.
Degraded mode: when redundancy is already used up
When a drive fails in a redundant array, the array keeps running in degraded mode. Your files are still there, but:
- The safety margin is gone (or reduced). A degraded RAID 5 has no redundancy left; one more failure and the array goes offline. A degraded RAID 6 can still take one more.
- Performance drops, because parity arrays have to calculate missing data on every read.
- The remaining drives work harder, especially during a rebuild, which reads everything. Drives bought together and run together often age together, which is why second failures during rebuilds aren’t unusual. See multiple drive failure.
Degraded arrays are easy to miss. Many NAS units and servers only beep, show an amber light, or send an email that goes to an inbox nobody checks. If you’re in this state now, our guide on RAID 5 degraded and failed rebuilds explains the safe order of operations: back up first, then replace and rebuild.
Hot spares
A hot spare is an extra drive installed in the array but left idle. When a member fails, the controller automatically starts rebuilding onto the spare, without waiting for someone to notice and swap a drive.
- Pro: it shrinks the time the array spends degraded, often the riskiest window.
- Con: a rebuild starts immediately, without a chance to take a backup first. If another drive is marginal, the automatic rebuild can be what pushes it over.
- A hot spare doesn’t add fault tolerance at the same moment; it only restores it after a rebuild finishes.
For many small arrays, moving from RAID 5 plus a hot spare to RAID 6 gives similar drive count with better protection, since the second parity is already in place.
Redundancy is not a backup
This is the part that matters most. RAID redundancy protects against one specific problem: a drive failing. Anything that changes the data, rather than the hardware, is copied to every drive instantly:
- Accidental deletion or overwrite. The mirror deletes it too.
- Ransomware. It encrypts the array as a single volume. See ransomware file recovery.
- File system corruption or a buggy update. Parity faithfully protects corrupted data.
- Controller or NAS failure, which can make the whole array inaccessible even with healthy drives.
- Theft, fire, flood or a power surge, which can take every drive at once.
A backup is a separate copy on separate hardware, ideally with one copy offsite. The 3-2-1 backup rule is a good baseline. Think of RAID as keeping the system running through a drive failure, and backup as getting your data back after everything else.
When redundancy runs out
Arrays usually fail in a predictable way: one drive drops, the array runs degraded, and a second drive fails or hits bad sectors during the rebuild. Other common routes are a failed controller, a NAS that won’t boot, or an array that someone reinitialized while trying to fix it. See RAID rebuild failure.
If you’re there:
- Stop. Don’t force drives online, start another rebuild, or run repair tools.
- Label each drive with its slot or port number before removing anything.
- Don’t reinitialize or create a new array on the same disks.
Even when the array won’t mount, the data is often still on the drives. Recovery works by imaging every member individually, working out the array’s layout, and rebuilding it virtually from the images without writing to the originals. For more, see RAID failure: what to do.
The bottom line
RAID redundancy uses mirroring or parity to let an array survive one or more drive failures: zero for RAID 0, one for RAID 5, two for RAID 6, and one per mirror for RAID 10. A degraded array has used up some or all of that margin, hot spares shorten the risky window but trigger rebuilds automatically, and none of it replaces a backup.
If your array has failed, our RAID data recovery service reconstructs every common RAID level and NAS by mail-in. Each case gets a custom quote after a free evaluation, and you pay nothing unless we recover your data.