LSI 9207-8i HBA: IT Mode, Cables and What You Give Up
The LSI 9207-8i is an eight-port internal SAS host bus adapter, and it is bought almost entirely for one reason: it does not do RAID. That is the feature rather than a limitation.
Why anyone wants a controller without RAID
Counterintuitive until you know what it is for.
Software-defined storage systems — ZFS, Storage Spaces, Ceph and similar — manage redundancy themselves. They want to see the physical drives directly, with unfiltered access to health data and full control over how writes are handled.
A RAID controller sits in the way of all of that. It presents virtual disks rather than physical drives, it filters some health information, and its cache behaviour can conflict with what the storage layer expects.
So the requirement is an adapter that connects drives and gets out of the way. That is what IT mode firmware does on this card — every drive appears individually to the operating system, exactly as it is.
Our RAID versus HBA guide covers the distinction properly, and it is the reason this card family became the default choice for software storage builds.
IT mode and IR mode
The same hardware ships with different firmware, and this is worth checking before buying.
IT mode — initiator target — is pure pass-through. No RAID, no virtual disks, drives presented individually.
IR mode — integrated RAID — adds basic array capability, which is not what a software storage build wants.
Cards are sold in either state, and the firmware can generally be changed. Two practical points: ask which firmware is loaded rather than assuming, and note that cross-flashing firmware is a procedure with some risk, so buying the card in the mode you need is simpler.
The same silicon also appears under server vendor part numbers with vendor firmware, which may behave differently. Our OEM guide covers why the part number rather than the chip tells you what you are getting.
What is not included
The most common omission in an order for this card.
Cables are separate. The card has internal ports that need cables to reach either a backplane or individual drives, and those cables come in different types — a cable that connects to a backplane is different from one that fans out to individual drives.
Connector generations also differ and do not physically mate across them. Our cabling guide covers the families, and the reliable approach is to establish what your backplane presents before ordering.
The bracket may not match. 1U servers take low-profile cards, and check what ships in the box — our PCIe guide covers this along with lane requirements.
What you give up
Being honest about the trade.
No hardware RAID. If you want the controller to manage arrays, this is the wrong card — you want something like our PERC guide describes.
No write cache. A RAID controller's battery-backed cache absorbs writes and acknowledges them immediately, which is a real performance mechanism. An HBA has none, so write performance comes entirely from the drives and the software layer.
Booting needs thought. Without hardware RAID there is no redundant boot volume from the controller. Most builds use a separate boot device — our boot devices guide covers the options, and mirrored M.2 is the common answer.
None of these are drawbacks in a software storage build. They are drawbacks if you bought the card expecting a RAID controller.
Drive compatibility
Simpler than with a RAID controller, and that is part of the appeal.
Because the card does not validate drive firmware the way Smart Array or PERC controllers do, bare manufacturer drives work without the vendor coding question. That makes it a natural pairing with drives sold under Seagate, Western Digital or Toshiba part numbers rather than server vendor ones — our enterprise drive guide covers that distinction.
One thing still applies: use enterprise or NAS class drives rather than desktop ones. Desktop drives retry errors for too long and lack vibration tolerance for a populated chassis, and while a plain HBA is more forgiving than a RAID controller about the timing, the underlying drive is still the wrong class for continuous multi-drive duty.
Practical points
Two worth knowing.
These cards run hot. They were designed for server chassis with strong front-to-back airflow, and in a quieter or lower-airflow build they need attention — a card overheating produces intermittent faults that look like drive or cable problems.
Record the firmware version. Where you build a system on a specific firmware level, note it, because a replacement card at a different level may behave differently. Our firmware guide covers why consistency matters more than being current.
Before you order
Your chassis and how drives connect — backplane or individual. What connector type your backplane presents, and what cables you need. Whether you need IT or IR firmware. Slot availability, electrical width and bracket height. And what storage software you are running, since that is the reason for choosing this card at all.
Common questions
Why buy a controller that does not do RAID?
Because software-defined storage systems manage redundancy themselves and want to see physical drives directly, with unfiltered health data. A RAID controller presents virtual disks and filters some of that information, which is exactly what those systems do not want.
What is the difference between IT and IR mode?
IT mode is pure pass-through with drives presented individually. IR mode adds basic RAID capability, which is not what a software storage build wants. Cards ship in either state, so ask which firmware is loaded rather than assuming.
Are cables included?
No, and they are the most common omission. Cable type depends on whether you are connecting to a backplane or to individual drives, and connector generations differ and do not physically mate. Establish what your backplane presents before ordering.
How do I boot without hardware RAID?
Most builds use a separate boot device, and mirrored M.2 on a carrier card is the common answer. There is no redundant boot volume from the controller itself, so plan it rather than discovering it during the build.
Can I use desktop drives behind an HBA?
A plain HBA is more forgiving than a RAID controller about error recovery timing, but the drive is still the wrong class — desktop drives lack vibration tolerance for a populated chassis and are not rated for continuous multi-drive duty. Use enterprise or NAS class drives.
Tell us your chassis, how drives connect and what storage software you are running, and we will confirm the card, firmware mode and cables together.
