RAID 5 calculator

RAID 5 gives up one drive's worth of space for parity and survives one failed drive. It is the most space for the least cost, and the riskiest to rebuild on large drives.

TB

Size printed on the drive label. Different sizes? The array uses the smallest one for every drive.

Advanced settings
MB/s

Typical hard drive: 100–200 MB/s with no other load. SSD: 400 MB/s or more.

From the drive datasheet. It is a worst-case spec, so real drives usually do better.

Show capacity in
24TB usable

Array healthy
Your data Parity or mirror copy Failed drive Click a drive to make it fail.
Drawing4 × 8 TB in RAID 5
Raw32 TB
Efficiency75%

Drives that can fail

Rebuild of one drive

Read error during rebuild

Checks for this setup

The same drives in every RAID level

4 drives of 8 TB each.

LevelUsableEfficiencyDrives that can failRebuildRead error in rebuild
32 TB
100%
None
—
—
8 TB
25%
Any 3
14 h
Fixed by another copy
24 TB
75%
Any 1
14 h
17%
16 TB
50%
Any 2
14 h
Fixed by parity
16 TB
50%
1 to 2
14 h
6.2%
Needs at least 6 drives
Needs at least 8 drives

RAID 5 at a glance

Minimum drives3
Usable space(drives − 1) × size of the smallest drive
Drives that can failAny 1
Read speedClose to the sum of all drives but one
Write speedSlower for small writes (4 operations per write)
RebuildReads every surviving drive in full

Common RAID 5 setups

Usable space for each number and size of drives. Every cell opens a page with the full numbers for that setup.

Usable space in TB. Pick a cell for the full numbers.
Drives2 TB4 TB6 TB8 TB10 TB12 TB14 TB16 TB18 TB20 TB22 TB24 TB
3 drives4812162024283236404448
4 drives61218243036424854606672
5 drives81624324048566472808896
6 drives102030405060708090100110120
7 drives1224364860728496108120132144
8 drives14284256708498112126140154168

How RAID 5 works

RAID 5 stripes data across all drives and adds one parity block to every stripe. Parity is the XOR of the data blocks in that stripe, so any one missing block can be calculated from the others. The parity block moves to a different drive in each stripe, so no single drive does all the parity work (a fixed parity drive is RAID 4).

Usable space = (number of drives − 1) × size of the smallest drive

Because parity always costs one drive, RAID 5 gets more efficient as you add drives:

DrivesUsableEfficiency
3 drives2 drives' worth67%
4 drives3 drives' worth75%
5 drives4 drives' worth80%
6 drives5 drives' worth83%
8 drives7 drives' worth88%
10 drives9 drives' worth90%
12 drives11 drives' worth92%

The rebuild problem

When a drive fails, the array keeps running, but it has no protection left. The new drive is filled by reading every block on every surviving drive and calculating the missing data. On a four-drive array of 16 TB drives, that is 48 TB that must be read without a single unreadable sector.

Drive makers quote how often a sector cannot be read: about 1 per 1014 bits for desktop drives and 1 per 1015 for NAS and enterprise drives. These are worst-case specs, and real drives usually do better, but they show how the risk grows. Chance of at least one read error during a rebuild of a four-drive RAID 5:

ArrayRead during rebuildDesktop drives (10¹⁴)NAS drives (10¹⁵)
4 × 4 TB12 TB62%9.2%
4 × 8 TB24 TB85%17%
4 × 12 TB36 TB94%25%
4 × 16 TB48 TB98%32%
4 × 20 TB60 TB99%38%
4 × 24 TB72 TBover 99%44%

What happens on a read error depends on the system. Some hardware controllers stop the rebuild. Linux mdadm, ZFS and most NAS systems continue and lose only the affected file or block. Either way, nothing is left to fix it. That is the reason most people move to RAID 6 once drives reach about 8 TB.

Why RAID 5 writes are slower

Changing one small block means reading the old data and the old parity, then writing the new data and the new parity: four operations instead of one. This is the RAID 5 write penalty. Large sequential writes that fill whole stripes avoid most of it, so RAID 5 is fine for media libraries and backups, and weaker for databases and virtual machines.

When RAID 5 is still a good choice

  • Drives of about 4 TB and smaller, where rebuilds finish in hours.
  • SSD arrays: SSDs rebuild fast and rarely hit read errors.
  • Three to five drives, with a separate backup of anything you cannot replace.

Avoid it for large hard drives, for more than about eight drives in one group, and for the only copy of important data.

Questions

What is the minimum number of drives for RAID 5?

Three. With three drives you get the space of two.

How much space do four 8 TB drives give in RAID 5?

24 TB, which Windows shows as 21.8 TB. One drive's worth (8 TB) holds parity.

Is RAID 5 dead?

No, but it fits fewer cases than it used to. With small drives and SSDs it is fine. With large hard drives, RAID 6 is the safer choice because the rebuild takes long and reads a lot of data.

Can I add a drive to RAID 5 later?

Linux mdadm and most NAS systems can grow a RAID 5 by one drive. The reshape can take a day or more, and the array is under stress the whole time, so make a backup first.

Is Synology SHR-1 the same as RAID 5?

With drives of the same size, SHR-1 gives the same space and protection as RAID 5. With mixed sizes, SHR uses more of the larger drives.