2 × 16 TB in RAID 1: the numbers
| Usable space | 16 TB (14.6 TB in Windows) |
|---|---|
| Raw space | 32 TB |
| Used for protection | 16 TB |
| Efficiency | 50% |
| Drives that can fail | Any 1 |
| Rebuild at 150 MB/s | 29 h |
| Rebuild at 50 MB/s (busy) | 3.7 days |
| Data read during rebuild | 16 TB |
| Read error risk, desktop drives | 72% |
| Read error risk, NAS drives | 12% |
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. Only the mirror partner is read, so the other drives are not stressed.
Read errors
Reading 16 TB, the chance of at least one unreadable sector is 72% with desktop drives (1 per 1014 bits) and 12% with NAS drives (1 per 1015). Nothing is left to correct it, so the affected file, or on some controllers the whole rebuild, fails. These are worst-case datasheet rates; real drives usually do better.
Our take
A mirror is the simplest safe setup for two drives. During a rebuild the remaining drive is the only copy, so with 16 TB drives keep a separate backup current. If you add drives later, three 16 TB drives in RAID 5 would give 32 TB, and four in RAID 6 32 TB with two-drive protection.