Objective. Students will create RAID 1 and RAID 5 virtual disks using a hardware RAID controller utility, explain the fault-tolerance and capacity trade-offs of each level, and simulate a drive failure and rebuild.
This lesson, its worked examples and its practice questions has not yet been verified by an industry-certified professional or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
RAID stands for Redundant Array of Independent Disks. A RAID system combines multiple physical drives so that the server sees one or more logical storage units called virtual disks. Depending on the RAID level chosen, the array can improve read/write performance, protect data against drive failure, or do both. In data centers, RAID is a standard layer of protection beneath the operating system and above the physical drives.
A hardware RAID controller is a dedicated card (or chipset built into a server board) that manages all RAID operations independently of the CPU and operating system. The OS sees only the virtual disk, not the individual drives. Hardware controllers maintain a battery-backed or flash-backed cache, which improves write performance and protects in-flight data during a power interruption. Software RAID uses the OS and CPU instead; it costs less but adds CPU overhead and offers no cache protection. Data centers almost always use hardware RAID controllers.
Data is split in blocks (stripes) across all drives. All drive capacity is usable, and read/write throughput is high. However, if any single drive fails, all data is lost. RAID 0 is used only where speed matters and data loss is acceptable (scratch storage, rendering caches).
Data is written identically to two drives simultaneously. Usable capacity equals the size of one drive regardless of how many drives are in the mirror set. The array survives the failure of all but one drive. Read performance may improve because the controller can service reads from either drive. Write speed is limited to the slower of the two drives. RAID 1 is common for operating system volumes.
Data and parity information are striped across all drives. Parity is distributed—no single drive holds all parity. With n drives, usable capacity equals (n − 1) × drive size. The array tolerates one drive failure; the missing data is reconstructed from parity. RAID 5 requires a minimum of three drives. It balances capacity efficiency and fault tolerance and is widely used for application data volumes.
Similar to RAID 5 but with two independent parity calculations per stripe. Usable capacity equals (n − 2) × drive size. The array tolerates two simultaneous drive failures. Minimum four drives required. RAID 6 is preferred when drives are large and rebuild times are long, because a second failure during rebuild is a real risk with large-capacity drives.
| Level | Min Drives | Drives Tolerated Lost | Usable Capacity |
|-------|-----------|----------------------|------------------|
| RAID 0 | 2 | 0 | n × size |
| RAID 1 | 2 | n − 1 | 1 × size |
| RAID 5 | 3 | 1 | (n − 1) × size |
| RAID 6 | 4 | 2 | (n − 2) × size |
Always match the RAID level to the workload. High-transaction databases often use RAID 10 (mirrored stripes). Boot volumes use RAID 1. Large sequential workloads use RAID 5 or 6.
Most enterprise RAID controllers provide a utility accessible at server POST (commonly by pressing a key combination such as CTRL+R for Dell PERC controllers, or through a browser-based interface). Steps are broadly:
1. Enter the controller configuration utility.
2. Select physical drives and choose a RAID level.
3. Set stripe size (common choices: 64 KB for general use, 256 KB for large sequential files).
4. Name the virtual disk and confirm creation.
5. Allow initialization to complete (fast init marks the disk available immediately; full init writes zeros and takes longer).
Always verify the virtual disk properties after creation: capacity, stripe size, and RAID level should match your design.
Enterprise RAID controllers support hot-swap: drives can be removed and replaced while the server stays powered. When a drive is removed from a RAID 5 or RAID 6 array, the controller immediately marks the virtual disk degraded. In degraded state:
When a replacement drive is inserted, the controller begins a rebuild. Rebuild time depends on drive capacity and the load on the array. The controller event log records the failure, the degraded state, the start of rebuild, and completion. Documenting these log entries is a required skill for CompTIA Server+ and for real-world incident reporting.
Electrical safety: Before working inside any server chassis, follow your facility's lockout/tagout (LOTO) procedure to de-energize equipment unless the task specifically requires the system to be powered (as in a hot-swap exercise). Hot-swap drive replacement is designed to be done with power on, but keep hands clear of fan modules and power supplies.
ESD (Electrostatic Discharge): Always wear an anti-static wrist strap bonded to the server chassis ground, or use an ESD mat. Physical drives contain sensitive electronics that can be destroyed by static discharge that you cannot feel.
PPE: Safety glasses are not required for this specific task, but closed-toe shoes are required in any server room per standard facility rules. Follow your site's PPE policy.
Lifting: Servers and drive trays can be heavy. Use two-person lifts for chassis weighing more than 35 lb, and use a server lift cart when racking equipment.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.