RAID Controller Buyer's Guide
A RAID controller is the difference between drives that look like a fast storage array and drives that look like a slow pile of disks. Pick the wrong controller and your $30,000 of SSDs delivers $5,000 worth of IOPS. Pick the right one and the array hits theoretical peak performance. This guide covers controller selection, cache and battery decisions, RAID-level planning, IT-mode vs RAID-mode firmware, and OEM compatibility constraints.
Hardware vs Software RAID
Hardware RAID dedicates a controller card to the array. Pros: offloads parity calculation from CPU, persistent cache, fast rebuild speeds. Cons: cost ($300-2500 per controller), proprietary stacks, vendor lock-in on drive validation.
Software RAID runs entirely on the host CPU (Linux mdadm, Windows Storage Spaces, ZFS, vSAN). Pros: no special hardware, full visibility into health, drive portability across hosts. Cons: CPU overhead on heavy writes, no persistent cache without separate UPS-backed buffer.
For tier-1 production OLTP databases, hardware RAID with battery-backed cache wins. For modern hyperconverged storage (vSAN, Ceph, ZFS), software RAID is the dominant pattern.
Cache and Battery / Capacitor Backup
Hardware RAID controllers typically have 1-4 GB of onboard cache RAM. Cache absorbs write bursts and accelerates random reads. Persistent cache (battery-backed or supercap-backed) is essential — volatile cache loses data on power loss and corrupts the array.
BBU (Battery Backup Unit) is the legacy approach. Recharges in 24 hours, lifetime ~3 years. Replace at end of life or the cache reverts to write-through mode (no acceleration).
Supercap + flash is the modern approach. Caches contents flash to onboard NAND on power loss. No battery replacement cycle. More expensive controllers ($600+).
For production use, never deploy hardware RAID without persistent cache backup.
RAID Level Selection
RAID 0: stripe across N drives. No redundancy. Use only for scratch / ephemeral data.
RAID 1: mirror across 2 drives. 50% capacity efficiency. Use for boot drives, transaction logs.
RAID 5: stripe with single parity. N-1 capacity efficient. Acceptable for arrays of < 4TB drives; for larger drives the rebuild window exceeds typical MTBF and a second failure during rebuild is non-negligible.
RAID 6: stripe with dual parity. N-2 capacity efficient. The right choice for any HDD-based array using 4TB+ drives, and most SSD arrays where rebuild time matters.
RAID 10: stripe of mirrors. 50% capacity efficient. Fastest write performance. Use for OLTP databases, VDI write caches, latency-sensitive workloads.
IT-Mode vs RAID-Mode Firmware
HBAs (host bus adapters) can ship in IT mode (pass-through, no RAID) or RAID mode (full hardware RAID). The same physical card can run either firmware depending on flash.
For software-RAID workloads (ZFS, Ceph, vSAN), IT-mode is required. The OS sees each drive directly and manages parity at the software layer.
For hardware-RAID workloads, RAID-mode firmware is required. The OS sees the assembled virtual disk, not the underlying drives.
LSI/Broadcom 9300 / 9400 / 9500 series HBAs are the workhorse cards that flash easily between modes. Dell PERC and HPE Smart Array cards are mostly RAID-mode locked, with IT-mode availability varying by model and firmware tier.
OEM Compatibility Constraints
Dell PERC H7xx / H8xx series support specific Dell-branded drives by default. Non-Dell drives boot warnings on Gen11+ PowerEdge platforms. Workaround: flash to MegaRAID-equivalent firmware (loses Dell-specific features) or accept the warnings.
HPE Smart Array P408i / S100i family is more permissive on Gen10 and earlier; Gen11 MR-series controllers (P408i-p, MR416i) enforce stricter drive validation.
Cisco UCS M5 / M6 / M7 use specific HBA models bound to UCS firmware. Mixing third-party drives works but is not TAC-supported.
Whitebox / Supermicro chassis are the most flexible — any LSI / Broadcom HBA works with any SAS/SATA/NVMe drives.
Need help picking?
Pro Disk Network engineering can validate a specific configuration against your chassis, workload, and budget. Email sales@prodisknetwork.com with your server model and target spec. Response within one business day.