Dennis HilkLinux diagnosticsDE

Storage controllers

LSI/Broadcom MegaRAID Fusion function (005b)

This is the MegaRAID Fusion identity in megaraid_sas. RAID firmware can expose logical volumes whose block-device model strings do not identify the underlying physical disks.

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

The exact constant is named LSI_FUSION and resolves to 005b. The profile keeps that checked family wording instead of claiming a specific controller chip or an OEM card model from an unverified label.

Curated identifiers
pci 1000:005b

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

megaraid_sas has the exact Fusion table entry and separate handling of physical and logical disk lists. Source support is not proof that all array members are healthy or exposed directly to Linux.

  • megaraid_sas — 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:005b] and Kernel driver in use. megaraid_sas 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 megaraid_sas 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

lsblk alone is insufficient for a full RAID inventory. Controller firmware, cache state and member health need appropriate read-only controller evidence; this profile does not offer array creation, initialization or repair commands.

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.