4 × 16 TB in RAID 6: the numbers
| Usable space | 32 TB (29.1 TB in Windows) |
|---|---|
| Raw space | 64 TB |
| Used for protection | 32 TB |
| Efficiency | 50% |
| Drives that can fail | Any 2 |
| Rebuild at 150 MB/s | 29 h |
| Rebuild at 50 MB/s (busy) | 3.7 days |
| Data read during rebuild | 48 TB |
| Read error risk, desktop drives | 98% (corrected) |
| Read error risk, NAS drives | 32% (corrected) |
Rebuild
Replacing a failed drive means writing a full 16 TB drive. At 150 MB/s with no other load that takes about 29 h; on a busy array running at 50 MB/s, about 3.7 days. The rebuild reads every surviving drive: 48 TB in total.
Read errors
Reading 48 TB, the chance of at least one unreadable sector is 98% with desktop drives (1 per 1014 bits) and 32% 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 32 TB. RAID 6 survives any two failures; RAID 10 writes and rebuilds faster. For 16 TB drives this is the setup most administrators would choose: the rebuild takes 29 h, and the array stays protected the whole time.