UK’s trusted IT infrastructure partner since 2003
Servnet
ConfiguratorGet in Touch

RAID 5 calculator

Single distributed parity — capacity-efficient, one-drive protection. Set your drives below for live usable capacity, fault tolerance, IOPS, rebuild time and URE risk.

DataDistributed parity

1 · Choose a RAID level

Stripe & mirror
Single parity
Dual / triple parity
Nested
ZFS RAID-Z

Block striping with distributed parity. Survives one failure.

2 · Configure drives

3 · Drive class

3.5" nearline SAS/SATA capacity HDD — indicative figures.

Advanced — read/write mix, URE rate
RAID 5 · 5 × 8 TB
32 TB usable
of 40 TB raw · 80% efficiency
Fault tolerance1 drive
Write penalty×4
IOPS estR ≈600 · W ≈150 · mix ≈316
Throughput estR ≈1K · W ≈1K MB/s
Rebuild / drive est≈ 27.8 h
URE on rebuild risk22.6%

During a single-drive rebuild there is no remaining redundancy — a URE on a surviving drive means data loss for the affected stripe. Real controllers mitigate via patrol reads/scrubs, so field results are often better.

Capacity distribution80% usableUsable: 32 TB32Parity: 8 TB8Usable · 32 TBParity · 8 TB
Fault tolerance — parity per arrayDDDDPDataParity1 drive
IOPS — back-end budget vs deliveredBack-end budget600Front-end read600Front-end write150Write penalty ×4 — each host write costs 4 back-end I/Os
URE risk during a single-drive rebuild0%25%50%75%100%23%data read during rebuild (64 TB →)URE 1 in 10^15

Calculated for planning. We don't publish prices — a 24-year UK reseller, Servnet confirms the exact drives, array and pricing on quote. IOPS, throughput & rebuild are indicative estimates.

Overview

What RAID 5 is

RAID 5 stripes data with one distributed parity block per stripe, so usable capacity is (n−1) × drive size and the array survives a single drive failure. It is one of the most space-efficient redundant levels — five drives give 80% efficiency.

The catch is the rebuild. After a drive fails, RAID 5 must read every surviving drive in full to reconstruct the replacement, with no redundancy left. On large nearline drives, the chance of hitting an unrecoverable read error (URE) during that read becomes significant — which is why RAID 6 has largely replaced RAID 5 for big arrays. Use the calculator to see your own URE-on-rebuild figure.

At a glance
Usable capacity(n − 1) × drive size
Minimum drives3
Fault tolerance1 drive
Write penalty×4
Worked example
5 × 8 TB nearline HDD32 TB usable, survives 1 failure

Five 8 TB nearline drives give 32 TB usable at 80% efficiency. But a rebuild must read 32 TB across the survivors with no safety net — at a consumer 10¹⁴ URE rate that carries a real chance of a failed rebuild, which is the case for RAID 6 on drives this size.

Advantages

  • High capacity efficiency — (n−1)/n
  • Survives one drive failure
  • Good read performance
  • Widely supported by every controller

Trade-offs

  • ×4 write penalty (read-modify-write)
  • No redundancy during rebuild — a URE means data loss
  • Long, risky rebuilds on large drives
  • Cannot survive a second failure

Best for

  • Smaller arrays of modest-capacity drives
  • Read-heavy workloads
  • Where capacity efficiency matters and a backup exists

Consider another level when

  • Large nearline (8 TB+) HDD arrays — use RAID 6
  • Write-heavy databases
  • Mission-critical data without a backup
Level landscape — efficiency vs fault tolerance (typical)012325%50%75%100%drives survivedspace efficiency →RAID 0RAID 5RAID 50RAID-Z1RAID 6RAID 60RAID-Z2RAID-Z3RAID 10RAID 1

RAID 5 — common questions

How is RAID 5 usable capacity calculated?

Usable capacity is (number of drives − 1) × drive size, because one drive’s worth of capacity is consumed by distributed parity. Five 8 TB drives give (5−1) × 8 = 32 TB usable, an 80% efficiency.

Why do people say RAID 5 is dead?

On large drives, a single-drive rebuild reads all surviving drives with no redundancy left. If an unrecoverable read error (URE) occurs during that read, the rebuild fails and data is lost. The bigger the drives, the higher that probability — the calculator shows it for your config. RAID 6 (dual parity) survives a URE during a single-drive rebuild.

What is the RAID 5 write penalty?

RAID 5 has a ×4 write penalty: each random write requires reading the old data and parity, then writing the new data and parity — four back-end I/Os per host write. This is why RAID 10 is preferred for write-heavy databases.