Unraid HBA setup checklist
Unraid HBA Setup & Compatibility Guide
An Unraid HBA is compatible only when the full combination works: controller mode, driver, disks, cable direction, SMART visibility, spin-down behavior, PCIe slot and current Unraid release. Current Unraid documentation recommends HBA rather than RAID mode and says additional compatible HBAs can expand storage when onboard ports are full. That is the architectural baseline; the setup still needs to be verified on the exact card before starting the array.
Quick answer
What should you check before connecting an Unraid array to a new HBA?
Confirm HBA/non-RAID mode, photograph or record current drive serial assignments, verify the correct forward breakout or backplane cables, and check that every SATA drive exposes expected identity and SMART data. If SAS drives are used, account for the current Unraid documentation note that SMART monitoring is not available for SAS drives. Then test spin-down, parity-check performance and controller temperature.
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
Compatibility means operational behavior, not only “the driver loaded”
A controller can appear in Linux and still be a poor NAS choice if it hides disk identity, repeatedly resets under load or prevents the power behavior you expect. Treat installation as a commissioning process. Do not start a parity rebuild until the mapping and health data make sense.
Interactive decision tool
Unraid HBA Setup Planner
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.
Set the controller to HBA/non-RAID operation
Unraid’s current deployment checklist says to set the storage controller to HBA mode, not RAID. Its FAQ reinforces that non-RAID HBAs are preferred because hardware RAID can obscure drive health and complicate maintenance.
If a used card arrives with unknown firmware, do not assign production disks until its operating mode is understood. Document the exact firmware and controller identity after verification.
Record every disk serial before changing controllers
Drive assignments are more important than cable order. Before moving disks, save the Main-page assignments and exact serial numbers for parity, array and pool devices.
After the HBA is installed, match serials one by one. If anything is missing or unexpectedly renamed, stop and resolve it before starting the protected array.
Verify SATA SMART visibility immediately
Current Unraid documentation uses SMART data for SATA drive health monitoring. A suitable controller should allow the OS to access the identifying and health information needed for replacement decisions.
Run SMART checks on every SATA disk after migration. If a controller hides details or reports errors, investigate firmware, driver and cabling before trusting the path.
SAS drive monitoring has an explicit Unraid caveat
Unraid’s current SMART documentation says SMART monitoring works for SATA drives but is not available for SAS drives. That is an important design constraint for builders considering inexpensive enterprise SAS disks.
Do not claim the HBA will restore a feature the OS does not currently expose. Decide whether the monitoring tradeoff is acceptable or whether SATA media better fits the operational requirements.
Test disk spin-down if power efficiency matters
A low-power media server may depend on idle array disks staying spun down. Controller firmware, device type and periodic services can all affect this behavior.
Test with the actual HBA, disks and Unraid release. If drives wake, correlate activity before blaming the controller; Docker workloads, shares and health polling can also generate I/O.
Forward breakout cable direction must be explicit
For direct SATA drives attached to an HBA, forward breakout is normally required. Reverse breakout products can look nearly identical and produce a completely dead drive path.
Check connector family and direction at purchase, then label cables. If four drives disappear together, inspect the shared breakout before replacing every disk.
SFF-8087 and SFF-8643 are not interchangeable
SAS2-era 9207/9211 cards commonly use SFF-8087, while SAS3 9300-class cards use SFF-8643. A controller upgrade often requires new internal cables even if the drive side remains SATA.
Transition cables can be useful with backplanes, but verify the exact HBA-to-backplane path and direction. Avoid a chain of adapters when a direct cable is available.
Parity checks are a useful controller stress test
A full parity check makes many disks active and exposes aggregate PCIe, cabling and thermal problems that ordinary streaming can hide. Watch for link resets, CRC errors and unexpectedly low throughput.
Do not use speed alone as the pass criterion. Stability, zero increasing error counters and predictable temperatures are more important than a short benchmark peak.
Motherboard lane sharing can limit a good HBA
A PCIe x8 HBA in a physically long slot may run at x4 because the motherboard shares lanes with M.2 or another slot. That may still be sufficient for HDDs but should be intentional.
Read the board manual and check the negotiated link. Avoid adding a second HBA or GPU without recalculating how the slots change when both are populated.
Cooling failures can look like compatibility failures
Intermittent disk drops under parity load can come from overheated controllers or poorly seated cables, not only driver bugs. Enterprise HBA heatsinks assume steady chassis airflow.
Run a directed fan when needed and measure temperatures during long operations. Keep airflow paths clear around both the HBA and nearby NIC/GPU.
Firmware updates should be controlled, not reflexive
A firmware update can fix issues, but cross-flashing the wrong OEM board or applying an inappropriate package can brick a controller. Preserve the current version and board identity before changing anything.
If the controller is already stable and exposes disks correctly, update only for a documented reason or supported target state. Keep a recovery method for the exact board.
Commission the HBA before trusting parity protection
Complete a controlled test: detect all disks, verify assignments, inspect SMART where supported, test spin-down, run sustained reads and a parity check, then reboot and confirm the layout returns cleanly.
Only after that should the controller be treated as part of the stable storage platform. Maintain independent backups because parity cannot protect against every controller, power or administrative failure.
Questions people ask
Unraid HBA Compatibility questions
Does Unraid recommend HBA mode?
Yes. Current deployment documentation explicitly says HBA mode rather than RAID mode, and its FAQ recommends non-RAID HBAs.
What should I save before swapping controllers?
Save every parity, array and pool disk serial assignment. Use serial identity rather than assuming controller port order will remain the same.
Why are my disks missing after installing an HBA?
Check controller mode, breakout-cable direction, connector family, power, firmware and whether the exact PCIe device is detected.
Does Unraid support SMART on SAS drives?
Current Unraid SMART documentation says SMART monitoring is not available for SAS drives, while SATA SMART monitoring is supported.
Should Unraid disks spin down behind an HBA?
They can, but behavior depends on the exact controller, disks, drivers and background workload. Test it if low idle power is a requirement.
Can I move disks between HBA ports?
Usually assignments are based on device identity rather than port number, but verify serial mappings before starting the array after any controller change.
Is SFF-8087 the same as SFF-8643?
No. They are different internal SAS connector families. Match the cable to the HBA and backplane.
Can I use a RAID controller if I create single-disk RAID0 volumes?
Unraid recommends direct HBA/non-RAID access. RAID virtual disks can hide health information and complicate maintenance.
How do I test a used HBA?
Verify model and firmware, run all disks under sustained I/O and parity load, inspect errors and temperatures, and reboot several times before production use.
Should I keep a spare HBA?
For a large array, a known replacement controller or documented replacement path can reduce downtime if one card provides connectivity to many disks.
Official references and methodology
Verify the exact controller, cable path and operating-system behavior
Compatibility guidance is based on current official Unraid deployment, FAQ and SMART documentation. It does not infer that every community-flashed card or chipset works identically. Marketplace firmware and model claims require verification on the delivered controller.
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.