RAID (Redundant Array of Independent Disks) is a method of combining multiple physical drives into one logical unit to improve performance, redundancy, or both.
+| RAID Level | +Description | +
|---|---|
| RAID 0 | +Striping only. No redundancy. Fast but risky—if one drive fails, all data is lost. | +
| RAID 1 | +Mirroring. Data is duplicated across drives. High redundancy, low capacity efficiency. | +
| RAID 5 | +Striping with parity. Can tolerate one drive failure. Balanced speed and redundancy. | +
| RAID 6 | +Double parity. Can survive two drive failures. | +
| RAID 10 | +Mirrored pairs striped together. High performance and redundancy. | +
| RAID-Z1/Z2/Z3 | +ZFS-based RAID levels with single, double, or triple parity. Designed for data integrity. | +
| RAID 50 | +Stripe of RAID 5 arrays. Combines performance of RAID 0 with redundancy of RAID 5. | +
The average time (in hours) a drive is expected to operate before failing. Higher MTBF means more reliable hardware.
+ +The time required to reconstruct data on a replacement drive after a failure. Longer rebuild times increase the risk of a second failure during recovery.
+ +A statistical estimate of how long a RAID system can operate before data loss occurs. It considers drive failures, rebuild time, and RAID redundancy. Higher MTTDL means a safer system.
+ +The probability that a bit read from a disk will be incorrect due to hardware limitations. Even tiny BERs (like 1 in a trillion) can cause issues during rebuilds, especially with large drives.
+ +Occurs when a drive fails to read a sector during rebuild. BER contributes to URE risk, which can compromise RAID recovery.
+ +Total storage per drive. Larger drives take longer to rebuild and are more susceptible to BER-related errors.
+ +The chance that the RAID system will experience data loss over a given time period (e.g., 5 years). Calculated using MTTDL and exponential failure models.
+