Do I need an HBA for my NAS?

Not for most home builds. If your four to six chipset-native SATA ports cover your drives plus a spare bay, an HBA is a slot, a power draw and a heat source you do not need yet. The real trigger to buy one is running out of good chipset ports and wanting more drives, at which point an HBA is more reliable than chasing add-on SATA ports or a port multiplier.

What is IT mode and why does it matter for ZFS?

IT mode (initiator target) is the HBA firmware that strips out all RAID logic so the card becomes a pure pass-through, handing every disk straight to the operating system untouched. ZFS and Btrfs want to own the raw drives so they can verify their own checksums and self-heal, which is why OpenZFS recommends an HBA over a RAID controller. Cards often ship in IR (integrated RAID) mode and need reflashing to IT, or you buy one already flashed.

Can I use a SATA port multiplier instead of an HBA?

Avoid it for an array. A port multiplier fans one SATA port out to four or five drives that then share that single port's bandwidth, and OpenZFS notes that port-multiplier support is inconsistent across platforms. For a RAID or ZFS pool an HBA in IT mode, which gives each drive its own lane, is the far more reliable way to add ports.

How do I connect drives to an LSI HBA?

An 8-port card has two internal mini-SAS ports: SFF-8087 on the older 9200 series, SFF-8643 (mini-SAS HD) on the 9300 and newer. Each port drives four disks through a forward breakout cable that splits one mini-SAS plug into four SATA connectors. Match the connector to your card and buy the forward breakout direction, because a reverse breakout looks identical but will not work on an HBA.

Do HBAs need extra cooling?

Usually yes. These cards are designed for the forced airflow of a rack server, so in a quiet desktop case the controller chip can run hot enough to throttle or drop drives. Strapping a small fan over the heatsink is the single most common HBA fix, and it is worth doing from the start rather than after a drive disappears mid-rebuild.

HBA vs Onboard SATA: How to Add More Drives to Your NAS

Updated: 2026-07-23· Last verified July 2026

10 min read

Planning to fill all eight HBA ports?Drop in eight drives, compare RAID 6 against RAID 5 and see usable capacity before you buy the card.

Open calculator →

You have filled every SATA port on the motherboard, the array is healthy, and you want to add two more drives. That is the moment most DIY NAS builders meet the host bus adapter, or HBA, and it is also where a lot of them make a small mistake a checksumming filesystem will not forgive: they reach for a cheap add-on controller or a splitter instead of the card the whole homelab world already standardised on. This guide keeps things narrow and practical, walking through what an HBA actually is, whether you genuinely need one over your onboard ports, and how to cable, cool and scale it without any 1am surprises.

What an HBA actually is, and why it is not a RAID card

An HBA is a plain expansion card whose only job is to connect disks to the computer and pass each one through untouched, so the operating system sees the individual drives exactly as if they were plugged into the motherboard. A hardware RAID card looks almost identical and drops into the same PCIe slot, but it inserts itself between the disks and the OS, groups them into arrays and hides the raw drives behind its own firmware and cache. That difference is the whole point for a modern NAS, because the software wants the disks and the card wants to keep them.

ZFS and Btrfs are built to own the drives directly so they can read every sector, verify their own checksums and repair silent corruption, and a RAID card that hides the disks or buffers writes behind a battery takes exactly that control away. OpenZFS is blunt about this in its hardware guidance, which states that it is best to use an HBA instead of a RAID controller for both performance and reliability, and that hardware RAID controllers should not be used with ZFS at all. So the decision is not really "which card is faster", it is "which card gets out of the way", and for a checksumming pool you want the one that does the least. If the wider software-versus-hardware question is new to you, we lay it out in hardware RAID vs software RAID; the takeaway here is simply that a NAS wants an HBA that passes disks through, never a RAID card that takes them over.

The canonical card: an LSI/Broadcom SAS HBA in IT mode

When people say "just get an HBA", they almost always mean one specific family: the LSI SAS cards, now sold under Broadcom, in models like the 9211-8i, 9207-8i and the newer Broadcom 9300-8i. These are SAS controllers, and because a SAS port happily accepts SATA drives too, one card gives you eight extra drive connections from a single slot. They are everywhere in homelabs for two reasons: price, because enterprise servers retire by the thousand and used "enterprise pull" 9200 and 9300 cards flood the second-hand market cheaply, and support, because the mainline Linux kernel drives them with its built-in mpt2sas/mpt3sas driver so they are effectively plug and play on any Linux-based NAS OS.

The one phrase you have to understand before buying is IT mode. These cards ship in one of two firmwares: IR (integrated RAID), which still tries to build RAID volumes of its own, and IT (initiator target), which strips all of that out so the card becomes a pure pass-through that hands every disk straight to your NAS software. Many sellers already flash their cards to IT mode and say so in the listing; if not, reflashing is a well-documented one-time procedure. Buy an 8-port LSI or Broadcom SAS card, confirm it is running IT-mode firmware, and you have the connectivity that the entire DIY-NAS ecosystem is built around.

For the more technical crowd: the 9200 generation (9211-8i, 9207-8i) is a 6 Gbps SAS2 card while the 9300 is 12 Gbps SAS3, and for spinning drives the older SAS2 cards are almost always plenty, since even the fastest hard drives sustain only a couple of hundred megabytes per second and eight of them nowhere near saturate a SAS2 card's x8 uplink. The practical reason to pay more for a 9300 is a stack of SATA or SAS SSDs, where the extra bandwidth actually shows up. Whichever generation you land on, keep one consistent IT firmware on the card and let it match the driver your NAS ships, so a resilver never trips over a firmware-versus-driver mismatch.

Be honest first: do you even need one?

Before you buy anything, the honest answer for a lot of builds is no. Most consumer motherboards break out four to six chipset-native SATA ports, and a four- to six-bay home NAS running file shares and a bit of Plex fits inside that comfortably, so an HBA is a slot, a lane budget and a heat source you simply do not need yet. The trigger to add one is specific and worth naming: you have run out of good chipset ports and want more drives, full stop.

What you should not do is chase the two cheaper-looking shortcuts. The first is leaning on the extra SATA ports a board advertises beyond the chipset's own allotment, because those almost always ride on an add-on ASMedia or Marvell controller that sits further from the CPU and has a history of dropping drives under load, which an array reads as a failure and answers with a needless rebuild. The second, and worse, is a SATA port multiplier or "expander" that fans a single port out to four or five disks; the same OpenZFS hardware guidance warns that port-multiplier support is inconsistent across platforms, and sharing one port's bandwidth across five drives is a poor base for an array regardless. We cover the onboard side of this decision in the NAS motherboard guide, but the takeaway is short: stay on native ports while they last, and treat "I ran out of chipset SATA" as the actual reason to buy an HBA, not a splitter.

Cabling: SFF-8643, SFF-8087 and the breakout confusion

The cable is where first-time HBA buyers lose an afternoon, because the connectors have unhelpful names and the wrong cable does nothing at all. An 8-port card carries two internal mini-SAS ports, and which connector you have depends on the generation: the 9200-series cards use the older SFF-8087 connector, while the 9300 and newer use the smaller SFF-8643, usually called mini-SAS HD. Each of those ports carries four drives, so to reach four individual SATA disks you need a breakout cable, one mini-SAS plug on the card end fanning out to four SATA connectors at the drive end.

Here is the trap that catches almost everyone: these cables come in two directions that look identical in a product photo. A forward breakout runs from a mini-SAS host port to four SATA drives, which is what you want on an HBA; a reverse breakout runs the other way, from four SATA host ports into one mini-SAS device, and it will not work on your card no matter how right it looks. So match the connector to your card first (SFF-8087 for a 9200, SFF-8643 for a 9300), then confirm the listing says forward breakout before you order. The SAS connector families and their pinouts are documented on the Serial Attached SCSI reference if you want the detail; the practical rule is two cables per 8-port card, correct connector, forward direction, double-checked in the listing.

Going past eight drives: SAS expanders and backplanes

Eight ports covers most home builds, but if you are heading for a twelve- or twenty-four-bay chassis, a second HBA is not the only path and often not the tidy one. A SAS expander is a small board that works like a network switch for drives: it takes a few lanes from your HBA and multiplies them out to far more ports, so a single 8-port card can drive sixteen, twenty-four or more disks through one expander. In a proper server chassis this is usually invisible because the expander lives on the backplane, the board behind the drive bays that your disks slot straight into, so you run two cables from the HBA to the backplane and every hot-swap bay comes alive.

There is one hard rule worth stating plainly, because it is the classic way a big build goes wrong. The same OpenZFS hardware guidance warns that you should never put plain SATA disks behind a SAS expander without a SAS interposer, since SATA behind an expander is the configuration that works right up until it does not. For that reason the large multi-bay world is where enthusiasts often switch to actual SAS disks, or deliberately keep the drive count low enough to stay on direct-attached HBA ports. So for up to eight drives, direct-attach from one HBA and keep it simple; past that, a SAS expander or a backplane chassis scales cleanly, as long as you respect the SATA-behind-expander caveat and plan the chassis around it from the start.

The gotchas nobody warns you about

An HBA is a piece of datacentre hardware wearing a consumer-PC costume, and it behaves like one. None of the following are dealbreakers, but each has bitten someone who assumed the card would act like an ordinary expansion card, so it is worth reading them once before the parts arrive.

Heat and airflow. These cards are built for the forced airflow of a rack server, so in a quiet low-airflow desktop case the controller chip can run hot enough to throttle or drop drives; strapping a small 40 mm fan over the heatsink is the single most common HBA fix.
Power draw. An HBA adds a small but constant load, on the order of a spinning drive's worth of power, that runs whether the disks are idle or not, so fold it into your NAS power budget alongside the drives.
A real PCIe x8 slot. An 8-port card wants a physically and electrically x8 slot; drop it into an x4 or x1 slot and it may still work but can bottleneck, which loops straight back to the PCIe lane math in the motherboard guide.
Firmware matching. Keep one consistent IT-mode firmware on the card and match it to the driver your NAS ships, because a mismatch is the classic cause of drives that appear and vanish during a rebuild.

In short, give it a fan, a real x8 slot, a few watts in your power plan and one consistent firmware, and an HBA is as steady as the onboard ports it replaces. Remember too that adding the ports is only half the job: growing the pool onto the new disks is its own step, which we walk through in how to expand a RAID array.

Recommendation

For a small fixed-size home NAS of up to six drives, skip the HBA entirely: buy a board with enough chipset-native SATA ports and a free slot, and put the money toward drives instead. For a growing ZFS or Btrfs build that has outgrown its onboard ports, a used LSI or Broadcom 9211-8i or 9300-8i flashed to IT mode is the standard answer, wired with two forward breakout cables, given a small fan and a real x8 slot. For a large multi-bay build heading past eight or twelve drives, plan a backplane chassis with a SAS expander from the start, and lean toward SAS disks (or keep SATA on direct HBA ports) rather than hanging plain SATA drives off an expander. Across all three the rule that keeps a checksumming array happy is the same: pass the disks through raw on an HBA in IT mode, never a RAID card or a port multiplier. When you know your final drive count, size the array in the RAID calculator and check real disks in the NAS drives database, and if you are still choosing the board underneath it all, start with the ZFS hardware requirements deep dive.