10 × 4 TB in RAID 6: the numbers
| Usable space | 32 TB (29.1 TB in Windows) |
|---|---|
| Raw space | 40 TB |
| Used for protection | 8 TB |
| Efficiency | 80% |
| Drives that can fail | Any 2 |
| Rebuild at 150 MB/s | 7 h 24 min |
| Rebuild at 50 MB/s (busy) | 22 h |
| Data read during rebuild | 36 TB |
| Read error risk, desktop drives | 94% (corrected) |
| Read error risk, NAS drives | 25% (corrected) |
Rebuild
Replacing a failed drive means writing a full 4 TB drive. At 150 MB/s with no other load that takes about 7 h 24 min; on a busy array running at 50 MB/s, about 22 h. The rebuild reads every surviving drive: 36 TB in total.
Read errors
Reading 36 TB, the chance of at least one unreadable sector is 94% with desktop drives (1 per 1014 bits) and 25% with NAS drives (1 per 1015). The second parity corrects it, so the rebuild finishes without losing data.
Our take
Up to about 12 drives in one RAID 6 is common. Beyond that, two RAID 6 groups (RAID 60) keep rebuilds shorter. For 4 TB drives this is the setup most administrators would choose: the rebuild takes 7 h 24 min, and the array stays protected the whole time.