RAID capacity·RAID 0 · 3disks
RAID 0 · 3disks
3disks
Capacity efficiency 100%

RAID 0 with 3 disks — 3 usable

3 disks in RAID 0 give you 3 disks’ worth, with 0 spent on parity or mirroring. That is 100% efficiency, and it always survives 0 failures.

Disks
3
Usable disks
3
Spent on parity or mirror
0
Capacity efficiency
100%
Failures always survived
0
Best case
0
Groups
1
Disks per group
3

RAID 0

Data is simply spread across the disks. Capacity and speed scale with the count, but one failure loses everything.

TB on the label, TiB on the screen

  • 1 TB × 33 TB · 2.73 TiB
  • 2 TB × 36 TB · 5.46 TiB
  • 4 TB × 312 TB · 10.91 TiB
  • 6 TB × 318 TB · 16.37 TiB
  • 8 TB × 324 TB · 21.83 TiB
  • 10 TB × 330 TB · 27.28 TiB
  • 12 TB × 336 TB · 32.74 TiB
  • 14 TB × 342 TB · 38.2 TiB
  • 16 TB × 348 TB · 43.66 TiB
  • 18 TB × 354 TB · 49.11 TiB
  • 20 TB × 360 TB · 54.57 TiB
  • 22 TB × 366 TB · 60.03 TiB
  • 24 TB × 372 TB · 65.48 TiB

One TB on the box is 10¹² bytes, while the operating system counts in units of 2⁴⁰ bytes. The names look alike but the units differ, so the same disk reads about 9% smaller. Nothing went missing — the ruler changed.

Same disk count, other levels

Same level, other disk counts

The rebuild is the dangerous part

When a single-parity array loses a disk, you put a new one in and every remaining disk is read end to end to rebuild it. That is precisely when the survivors work hardest and longest. The bigger and more numerous the disks, the longer the rebuild — days, sometimes — and a second failure during it ends the array. This is why RAID 6 or 10 is preferred over RAID 5 on large arrays.

How to read it

  • Usable = total − parity × groups. Every level is that one line.
  • RAID 5 spends one parity disk in a single group, so n−1; RAID 6 spends two, so n−2.
  • RAID 50 and 60 run several such groups striped together, so the parity is multiplied by the group count.
  • RAID 1 holds one copy on every disk, so one disk’s worth; RAID 10 mirrors in pairs, so half.
  • Groups must be equal in size, so the group count can only be a divisor of the disk count.
  • TB on the box and TiB on the screen are different units — about 9% apart.

RAID is not a backup

RAID protects against exactly one thing: a disk dying. A file deleted by mistake, a file overwritten, ransomware, a failed controller, fire or theft all propagate to every disk at once — a mirror deletes just as faithfully as it writes. A backup is a separate copy on separate hardware, and RAID is not doing that job.

Common questions

Q. How much do 3 disks give in RAID 0?

3 disks’ worth. 0 go to parity or mirroring, for 100% efficiency.

Q. How many failures does it survive?

0 always, and up to 0 if they land in the right places.

Q. How many TB with 4 TB disks?

12 TB, which the operating system shows as 10.91 TiB — different units, same bytes.

Q. What is this level?

Data is simply spread across the disks. Capacity and speed scale with the count, but one failure loses everything.