Understanding RAID Fault Tolerance, Consistency Checks, Hot Spare, Rebuild, and Data Protection Features

Disk fault tolerance ensures data integrity and processing capability when a subsystem experiences hard‑disk errors or failures; RAID controllers achieve this on RAID 1, 5, 6, 10, 50, and 60 through redundant disk groups.

In RAID 1, data is mirrored on paired disks, so a single disk error does not cause data loss; RAID 5 tolerates one failed disk, and RAID 6 tolerates two.

For multi‑subgroup RAID configurations, RAID 10 and RAID 50 allow a number of failed disks equal to the number of sub‑groups (one per sub‑group), while RAID 60 permits twice the number of sub‑groups (up to two failures per sub‑group).

RAID 0 provides no fault‑tolerance; any disk failure renders the array unusable and results in data loss.

Improved fault‑tolerance enhances system availability, allowing continued operation despite disk failures.

1 Consistency Check

RAID controllers can perform consistency checks on redundant RAID levels (1, 5, 6, 10, 50, 60) by verifying and comparing data across disks; mismatches trigger automatic repair and error logging. RAID 0 lacks redundancy and therefore does not support consistency checks.

2 Hot Backup

Hot backup is realized through hot spares and emergency backup functions.

Hot Spare

A hot spare is an idle disk that automatically replaces a failed member disk and reconstructs its data when a failure occurs.

It must have equal or greater capacity, the same media type, and interface as the member disks.

Two types of hot spares are supported:

Global hot spare: shared by all configured RAID groups on the controller; multiple global spares can be configured.

Local hot spare: dedicated to a specific RAID group; each group can have one or more local spares.

Hot spares are only used for RAID groups with redundancy (RAID 1, 5, 6, 10, 50, 60) and must reside on the same controller as the failed disk.

Emergency Backup

If a RAID group with redundancy experiences a disk failure and no hot spare is assigned, an idle disk of sufficient capacity and matching media type will automatically replace the failed disk and start reconstruction, preventing data loss.

3 RAID Rebuild

When a disk fails, the controller can reconstruct the lost data onto a new disk. Rebuild is available only for redundant RAID levels (1, 5, 6, 10, 50, 60).

If a hot spare is present, it automatically takes over and starts reconstruction; otherwise, reconstruction begins after a new disk is manually inserted.

The rebuild rate (0 %–100 %) controls the CPU resources allocated to the task; 0 % runs only when the system is idle, while 100 % uses all available CPU.

4 Virtual Disk Read/Write Policies

Read Policy : Two options are supported—pre‑read (e.g., “Always Read Ahead”, “Read Ahead”) which caches upcoming data to reduce seek time, and non‑pre‑read where data is read only on demand.

Write Policy includes several modes:

Write‑Back: data is first written to cache and later flushed to the virtual disk, requiring power‑loss protection.

Write‑Through (direct write): data is written directly to the virtual disk without caching, offering lower performance but no power‑loss risk.

Write‑Back with BBU: uses a battery‑backed unit when present; otherwise falls back to Write‑Through.

Write‑Back Enforce: forces Write‑Back even if the capacitor is missing or damaged (not recommended).

5 Data Power‑Loss Protection

Because cache writes are faster than disk writes, enabling cache improves performance but risks data loss on sudden power loss. Super‑capacitors store cached data to NAND flash during power loss, preserving it.

Super‑capacitor calibration follows a three‑stage charge‑discharge‑recharge cycle; during calibration the controller switches to Write‑Through mode to ensure data integrity.

6 Disk Striping

Striping distributes I/O load across multiple physical disks by dividing data into small blocks and writing them to different disks, improving parallel I/O performance while not providing redundancy.

Key concepts: stripe width (number of disks), RAID‑group stripe size (size of data written across all disks), and individual disk stripe size (size of each block on a single disk).

7 Disk Mirroring

Mirroring (used in RAID 1 and RAID 10) writes identical data to two disks simultaneously, achieving 100 % redundancy at the cost of double storage usage.

8 Foreign Configuration

A foreign configuration appears when a newly installed disk contains RAID metadata, after a controller replacement, or after hot‑plugging a disk; it can be imported, deleted, or ignored based on the server’s needs.

9 Disk Power‑Saving

The controller can spin down idle SAS/SATA disks to save power; disks wake automatically when required for operations such as RAID creation or rebuild.

10 Disk Pass‑Through (JBOD)

Enabling pass‑through allows direct command transmission to disks without RAID processing, useful for OS installations or applications that need raw disk access.