4 × 10 TB in RAID 6: the numbers
| Usable space | 20 TB (18.2 TB in Windows) |
|---|---|
| Raw space | 40 TB |
| Used for protection | 20 TB |
| Efficiency | 50% |
| Drives that can fail | Any 2 |
| Rebuild at 150 MB/s | 18 h |
| Rebuild at 50 MB/s (busy) | 2.3 days |
| Data read during rebuild | 30 TB |
| Read error risk, desktop drives | 91% (corrected) |
| Read error risk, NAS drives | 21% (corrected) |
Rebuild
Replacing a failed drive means writing a full 10 TB drive. At 150 MB/s with no other load that takes about 18 h; on a busy array running at 50 MB/s, about 2.3 days. The rebuild reads every surviving drive: 30 TB in total.
Read errors
Reading 30 TB, the chance of at least one unreadable sector is 91% with desktop drives (1 per 1014 bits) and 21% with NAS drives (1 per 1015). The second parity corrects it, so the rebuild finishes without losing data.
Our take
With four drives, RAID 6 and RAID 10 both give 20 TB. RAID 6 survives any two failures; RAID 10 writes and rebuilds faster. For 10 TB drives this is the setup most administrators would choose: the rebuild takes 18 h, and the array stays protected the whole time.