Unraid controller buying guide
Best HBA for Unraid: Ports, IT Mode & Expansion
Unraid can spread storage across multiple controllers, but the controller must preserve the direct disk identity that parity, monitoring and maintenance depend on. Current Unraid documentation recommends non-RAID HBAs and explicitly tells users to use HBA rather than RAID mode. That makes enterprise LSI/Broadcom HBAs attractive for large arrays, yet the right choice still depends on port count, SATA/SAS mix, PCIe lanes, cable direction, thermal conditions and how far the server is expected to grow.
Quick answer
What HBA should an Unraid server use?
For a typical HDD array, use a compatible non-RAID HBA with enough direct ports for the final drive plan. An 8-port 9207-8i or 9300-8i class card is a common scale point; 16- or 24-port SAS3 cards reduce slot pressure in larger chassis. Keep RAID disabled, verify disk serial visibility, and test spin-down and SMART behavior on the exact installed hardware before relying on it.
Live Amazon hardware
Current HBA, expander, cable and controller listings for this decision
The Sprint 6A catalogue separates HBAs, SAS expanders, PCIe SATA cards, cable families and cooling hardware. Used and refurbished enterprise controllers remain eligible when the listing matches the exact model, but marketplace IT-mode wording is treated only as evidence to verify after delivery.
Buying decision
Buy for direct access, parity maintenance and future drive count
Unraid does not need a hardware RAID engine to protect the array; it needs predictable access to each assigned disk. Size the HBA around the number of array and pool devices that will attach to it, then check motherboard lanes, connector family and cooling. If SAS drives are involved, note the current Unraid documentation caveat that its SMART monitoring is not available for SAS drives, so monitoring expectations differ from SATA.
Interactive decision tool
Unraid HBA Selector
Use this planner to screen controller class, port count, expander need, PCIe budget, cabling and storage ownership before buying hardware. Results are planning guidance; they cannot inspect your motherboard lane map, firmware, IOMMU groups, backplane wiring or the exact card delivered by a marketplace seller.
Compatibility checklist
Four checks before adding more NAS drives
Keep direct disk visibility
TrueNAS and Unraid both benefit from controllers that expose individual disks rather than hiding them behind a hardware RAID virtual disk.
Count connectors, not just ports
Match SFF-8087, SFF-8643, direct SATA and backplane connectors, and confirm breakout direction before buying cables.
Budget PCIe bandwidth and slots
A physical x16 slot can be electrically narrower. Plan controller throughput, free slots and lane sharing around the final drive count.
Treat airflow as part of the controller
Enterprise HBAs and expanders were designed for server airflow. Desktop NAS cases often need deliberate fan placement over the controller heatsink.
Unraid explicitly prefers HBA mode over RAID mode
Current Unraid deployment guidance tells users to configure storage controllers in HBA mode rather than RAID. Its hardware FAQ similarly recommends non-RAID HBAs and warns that hardware RAID can obscure drive health information and complicate maintenance.
That architecture aligns with how Unraid assigns individual disks to the array and pools. A controller should not turn eight physical disks into one opaque virtual volume before Unraid sees them.
Parity makes stable disk identity especially important
Unraid parity protection depends on the correct physical disks remaining correctly assigned. Direct serial visibility helps you identify a failed drive, replace the correct device and avoid confusing controller port order with persistent identity.
Before any controller migration, capture a screenshot or written record of every disk serial and assignment. Then compare the new controller view before starting the array. A successful boot is not enough evidence that all assignments are correct.
SAS2 is a sensible HDD expansion tier
Spinning disks rarely approach a 6Gb/s link individually, so a SAS2 HBA can serve a large capacity-oriented Unraid array efficiently. The 9207-8i is particularly attractive when an existing build already uses SFF-8087 cables.
If the future system is mostly SATA SSDs or a 12Gb/s expander/backplane, SAS3 offers more aggregate headroom. Buy the generation around the workload and physical topology instead of equating newer with automatically necessary.
SAS3 and high-port cards reduce slot pressure
A 9300-8i gives eight SAS3 lanes, while 9305-16i and 9305-24i class cards consolidate many ports onto one PCIe slot. That can matter in an Unraid server that also needs a GPU for transcoding, a 10GbE NIC or another PCIe accelerator.
The tradeoff is heat concentration and a larger single failure domain. Verify airflow around the controller and avoid placing an extremely hot GPU directly against a passively cooled HBA.
Spin-down behavior should be tested on the real combination
Low-power Unraid builds often depend on idle disks spinning down. Controller firmware, driver behavior, SAS/SATA translation, periodic polling and applications can affect whether drives actually remain idle.
Do not buy a controller solely because another user reported spin-down years ago. Test your exact Unraid release, HBA firmware and disk set, and inspect which process or device is generating I/O if a drive repeatedly wakes.
SATA and SAS have different monitoring expectations in Unraid
Unraid supports storage layouts that include SATA and SAS devices, but its current SMART documentation states that SMART monitoring in Unraid works for SATA drives and is not available for SAS drives.
That does not make SAS unusable; it changes the health-monitoring workflow. If rich per-drive SMART visibility in the WebGUI is a requirement, validate it against the exact interface and current release before committing to a large SAS purchase.
Cable direction is a common silent failure
Direct SATA fan-out from an HBA normally requires a forward breakout cable. Reverse breakout cables may have the same visible connectors but are wired for a motherboard-to-backplane direction instead.
Label controller-end and drive-end cables. If a newly installed HBA detects no disks, verify signal direction and connector family before assuming the controller is defective.
PCIe sharing can affect parity checks and rebuilds
Parity checks and rebuilds can keep many disks active at once. A controller in a reduced-width slot can therefore become an aggregate bottleneck even when normal single-file reads seem fast.
Use the motherboard manual to identify the electrical lane width and any M.2 sharing. The calculator estimates controller-side demand but cannot discover chipset uplink limits or hidden motherboard switches.
SAS expanders make large arrays cleaner but share uplinks
A SAS expander can let an 8-port HBA address many more drives. This is useful in 16-, 24- and 36-bay chassis where direct fan-out would otherwise require several cards.
The expander does not create unlimited upstream bandwidth. Parity checks, rebuilds and simultaneous reads can make uplink sharing visible, so size the HBA-to-expander links for the real active-drive workload.
Used HBA listings need a verification workflow
Unraid builders often buy decommissioned enterprise cards. That is reasonable because the controllers were designed for continuous service, but marketplace titles can be inaccurate and OEM boards can be cross-flashed.
Verify exact model, PCI identifier, firmware mode and connector count after arrival. Retain a known-good spare or at least a documented replacement path if the server contains many drives behind one controller.
Keep array, pool and boot-device topology separate
Unraid boots from its licensed USB device, while array and pool drives attach through SATA/HBA paths. Do not create unnecessary boot-order dependencies on a storage HBA; Unraid documentation notes that large drive counts can interact with motherboard boot-device enumeration.
When possible, disable unneeded HBA boot-ROM/INT13 behavior so attached data disks do not compete for boot entries. Make such changes only after confirming the controller remains accessible to the OS.
Validate the controller before starting a protected array
After installing the HBA, confirm every serial, SMART status where supported, negotiated link, temperature and cable path. Run sustained reads before trusting the setup with a parity rebuild.
Back up critical files independently. Unraid parity is valuable fault tolerance, but an HBA, parity disk or controller does not replace an offline or remote copy of important data.
Questions people ask
Best HBA for Unraid questions
What controllers does Unraid recommend?
Current Unraid documentation recommends non-RAID HBAs and advises HBA/IT mode rather than RAID mode so Unraid retains direct disk access.
Is the 9207-8i enough for an Unraid HDD array?
Often yes. Eight 6Gb/s SAS/SATA lanes are ample for typical HDDs, provided the PCIe slot and cabling match the build.
Why use a 9300-8i for Unraid?
It is useful when you want SAS3/SFF-8643 cabling, a newer backplane or more aggregate headroom for SSD-heavy traffic.
Can Unraid use more than one HBA?
Yes. Unraid documentation says storage can expand across multiple controllers. Check slots, lane sharing and cooling before adding cards.
Can I use SAS drives with Unraid?
They can be used, but current Unraid SMART documentation says its SMART monitoring is not available for SAS drives. Factor that monitoring limitation into the design.
Will an HBA let my disks spin down?
It can, but spin-down is affected by firmware, drivers and workload. Test the exact card and Unraid release instead of assuming every HBA behaves identically.
Should I flash a RAID card to IT mode?
Only if you understand the exact board and supported firmware path. A listing that says IT mode is not proof of the delivered firmware state.
What is the best HBA port count for Unraid?
Choose around the final planned drive count and free PCIe slots. Eight ports are economical; 16 or 24 ports can preserve slots in larger systems.
Does Unraid require hardware RAID?
No. Its own array and pool layers manage storage. Current documentation explicitly recommends HBA rather than RAID mode for storage controllers.
What should I verify after installing an HBA?
Verify every disk serial and assignment, controller mode, cable direction, SMART visibility where supported, temperatures, link stability and parity-check performance.
Official references and methodology
Verify the exact controller, cable path and operating-system behavior
Unraid architecture statements are tied to current official deployment, FAQ and SMART documentation. Controller specifications are sourced from manufacturer material. Amazon listing terms are used only as marketplace evidence and are never treated as proof of firmware, authenticity or delivered condition.
- Unraid Deploy & Configure
- Unraid Hardware FAQ
- Unraid SMART & Disk Health
- Unraid Configure Your Array
- Broadcom SAS 9207-8i Product Brief
- Broadcom SAS3008 Product Brief
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Marketplace model names, firmware claims, condition, connector layouts, cable direction and seller descriptions can be wrong or change. Verify the delivered board, firmware and cable path before connecting production disks.