Dennis HilkLinux diagnosticsDE

Storage controllers

LSI/Broadcom SAS3008

SAS3008 is a newer Fusion-MPT SAS3 controller identity handled by mpt3sas. SAS port capability, an expander’s topology and each drive’s negotiated link are separate pieces of evidence.

Editorial source review: Share public profileOpen in the identification tool
On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

1000:0097 maps to SAS3008 in the MPI configuration header. OEM boards can share this controller identity; subsystem IDs and board firmware are needed for a particular card.

Curated identifiers
pci 1000:0097

A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.

Driver & binding

The exact PCI table selects the SAS3008 path in mpt3sas. The same module supports multiple generations, so its module name alone cannot recover the controller family or negotiated SAS speed.

  • mpt3sas — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

Controller firmware, option ROM and drive firmware can be separate. The reviewed sources do not establish a host-loaded filename for this profile; firmware revision and update policy require the actual controller and OEM identity.

Inspect firmware packaging on your distribution

Read-only diagnostics

Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.

Check the PCI function and bound driver

lspci -nnk -s BDF

Replace BDF with the domain:bus:device.function address. Look for [1000:0097] and Kernel driver in use. mpt3sas in Kernel modules is only a candidate, not proof of binding.

Inspect visible block-device identities

lsblk -d -o NAME,MODEL,TRAN,HCTL

MODEL describes a block device or a controller-presented logical volume; it is not a PCI-controller identity. HCTL helps distinguish SCSI targets. TRAN can be absent, and this list does not establish the complete physical disk topology.

Read controller and transport messages

sudo journalctl -k -b --no-pager

Elevated access may be needed. Root reads the current boot kernel journal. Associate mpt3sas messages, port/host identifiers and timeout/reset timestamps with the actual controller. A reset message alone does not prove a bad disk or a firmware defect.

Limitations & related issues

A visible block device can be an individual disk or a firmware-presented volume, depending on configuration. The source ID does not prove drive health, redundancy or a safe firmware migration.

These guides are linked for relevant observations, not as known defects of every device in this family.

Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.