2.3.3. Hot-Swappable Components and Firmware
💡 First Principle: Hot-swap capability requires both hardware design (backplane connectors that support live insertion) and software support (drivers and OS that can detect and configure components while running). Not every slot or bay is hot-swap capable even if the server is running—the component and the server must both support it.
Hot-Swappable Components
Components that servers commonly support for hot-swap:
| Component | Hot-Swap Status | Notes |
|---|---|---|
| Drives (in hot-swap bays) | ✅ Yes | Most enterprise server drive bays are hot-swap; must be in a RAID array for zero-downtime replacement |
| Power supplies | ✅ Yes | Redundant PSUs are designed for hot-swap; remaining PSU carries load |
| Fans (in hot-swap cages) | ✅ Yes | Server maintains cooling during replacement; brief temperature spike possible |
| Drive cages | ✅ Some | Depends on server model and backplane design |
| Expansion cards (hot-plug PCIe) | ✅ Some | Requires PCIe hot-plug support in server and OS |
| CPU | ❌ No | Requires full power-down |
| RAM (DIMMs) | ❌ No | Requires full power-down (unless server supports Online Spare Memory, which is different) |
| Motherboard | ❌ No | Requires full power-down |
Firmware
Firmware is software permanently stored in hardware components (BIOS/UEFI, NIC firmware, RAID controller firmware, drive firmware). Unlike the OS, firmware runs before the OS loads and controls the hardware at the most fundamental level.
- BIOS (Basic Input/Output System): Legacy firmware interface. Initializes hardware at boot (POST), provides the pre-OS environment, and configures hardware settings. Limited to 2TB boot drives (MBR limitation).
- UEFI (Unified Extensible Firmware Interface): Modern replacement for BIOS. Supports drives larger than 2TB for boot, faster boot times, Secure Boot (cryptographic verification of boot process), and a more capable pre-OS environment.
Firmware updates fix bugs, patch vulnerabilities, improve compatibility, and sometimes add features. Best practices:
- Check release notes before updating—some firmware updates are non-reversible
- Test firmware updates in non-production before production rollout
- Ensure a power outage during firmware update doesn't occur (use UPS)
- Some firmware updates require specific intermediate versions—follow the upgrade path
BIOS/UEFI passwords provide hardware-level access control:
- BIOS/UEFI password: Required to access firmware settings. Prevents unauthorized configuration changes.
- Boot password: Required before the OS loads. Stronger than an OS login because it can't be bypassed by booting from external media (without knowing the password).
⚠️ Exam Trap: Replacing a hot-swap drive in a RAID array doesn't immediately restore redundancy. The RAID controller must rebuild the array, and how it does that depends on the level: RAID 1/10 copy the surviving mirror; RAID 5/6 reconstruct the missing blocks by XOR-ing the surviving data and parity together — the controller does not simply copy parity onto the new drive. During rebuild the array is degraded and vulnerable to another drive failure. Rebuild time depends on drive size and controller load — and because a RAID 5 rebuild must read every surviving drive end to end, it is exactly when a second drive is most likely to fail.
Reflection Question: A RAID 5 array with three 4TB drives loses one drive to failure. You hot-swap a new drive in. How long is the array still at risk of data loss, and what could you do during this window to minimize that risk?
