ZimaOS LSI 9207 SAS Detection: What Fixed This Case

Bottom Line: This LSI SAS Case Was Fixed by a ZimaOS Driver Update

The controller and two SAS SSDs worked in CasaOS but were invisible in ZimaOS. IceWhale added the requested driver for the 1.4.2 beta, and the same hardware was then detected successfully. That is stronger evidence than a generic “LSI should work” assumption.

ZimaOS storage screen showing two SAS SSDs detected through an LSI controller as a RAID1 array — After the driver change, both 7.68 TB SAS SSDs appeared in ZimaOS and were shown as a protected RAID1 storage set.

Verify the Controller Before Blaming the Disks

lspci -nn
dmesg | grep -i -E 'mpt|sas|scsi'
lsblk

If lspci sees the HBA but no disks appear, the problem is different from a controller that never binds to a driver. The Linux kernel's SCSI documentation and the SCSI driver reference provide the upstream model.

Do Not Generalize One 9207/9211-Class Success to Every SAS Card

Firmware mode, PCI IDs, expander topology and disk type matter. The thread mentions LSI 9207/9211/9240-family naming inconsistently, so record the exact PCI ID and firmware mode before comparing your card with this case.

Once the Disks Appear, Treat Storage Setup as a Separate Step

Driver detection only proves ZimaOS can see the hardware. RAID creation, filesystem setup and data import are separate decisions. The ZimaOS RAID recovery guide is useful if the disks already contain an array, while the ZimaCube 2 multi-drive storage page provides current hardware context.

If a Current ZimaOS Release Still Misses the HBA

Capture lspci -nn, dmesg, exact HBA model/firmware and ZimaOS version. Driver support that worked for one adapter in 1.4.2 does not guarantee every later card revision or OEM firmware variant.