RAID 10 with 13 disks — not possible

RAID 10

Disks are mirrored in pairs, and the pairs are striped together. Half is usable and rebuilds are fast.

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.