IBM Support

MegaRAID Storage Manager cannot find controllers using inbox Linux storage driver - IBM SAS HBA

Troubleshooting


Problem

When starting MegaRAID Storage Manager (MSM), any version, with one of the affected Linux Operating Systems (OSes) that uses the inbox Serial Attached SCSI (SAS) controller driver, the application is unable to scan and find any supported SAS controllers.

Resolving The Problem

Source

RETAIN tip: H197306

Symptom

When starting MegaRAID Storage Manager (MSM), any version, with one of the affected Linux Operating Systems (OSes) that uses the inbox Serial Attached SCSI (SAS) controller driver, the application is unable to scan and find any supported SAS controllers.

Affected configurations

The system is configured with at least one of the following:

  • LSI Logic MegaRAID Storage Manager, any version
  • Red Hat Enterprise Linux 4, any update
  • Red Hat Enterprise Linux 5, any update
  • SUSE Linux Enterprise Server 10, any service pack
  • SUSE Linux Enterprise Server 10 for AMD64/EM64T, any service pack
  • SUSE Linux Enterprise Server 11, any service pack

The system is configured with one or more of the following IBM Options:

  • IBM 3 Gigabit SAS HBA v2, Option part number 44E8700, replacement part number (FRU) 44E8701
  • IBM SAS HBA Controller, Option part number 25R8060, replacement part number (FRU) 25R8071
  • Paddle board with LSI 1064E SAS Controller, any replacement part number (FRU)

This tip is not system specific.

Note: This does not imply that the network operating system will work under all combinations of hardware and software.

Please see the compatibility page for more information: http://www.ibm.com/servers/eserver/serverproven/compat/us/

Solution

Download and install the IBM-provided Linux driver.

The referenced file will be available from the "Disk controller and RAID software matrix" at the following URL:

Workaround

Manually add the driver "mptctl" to the drivers that get loaded during the Linux boot process. Refer to the Operating System (OS) documentation for information on how to do this.

After manually installing the "mptctl" module by "modprobe mptctl", restart the framework:

  /etc/init.d/vivaldframework restart

and mrmonitor:

  /etc/rc.d/mrmonitor restart

Additional information

The issue happens if the "mptctl" module is not loaded into the kernel during system boot.

This issue occurs even if users have manually installed the "mptctl" module by "modprobe mptctl" because the framework needs to be restarted.

When installing the supported IBM Linux driver, the mptctl module is configured to load first during a system reboot allowing MSM to work properly.

Document Location

Worldwide

Operating System

System x Hardware Options:Red Hat Enterprise Linux 4

System x Hardware Options:Red Hat Enterprise Linux 5

System x Hardware Options:SUSE Linux Enterprise Server 10

System x Hardware Options:SUSE Linux Enterprise Server 10 x86-64

System x Hardware Options:SUSE Linux Enterprise Server 11

[{"Type":"HW","Business Unit":{"code":"BU016","label":"Multiple Vendor Support"},"Product":{"code":"QU02DJC","label":"System x Hardware Options->SAS\/SATA Controller->Host Bus Adapter->25R8060"},"Platform":[{"code":"PF042","label":"Caldera"},{"code":"PF047","label":"SurePOS"}],"Line of Business":{"code":"","label":""}},{"Type":"HW","Business Unit":{"code":"BU016","label":"Multiple Vendor Support"},"Product":{"code":"QU03VYS","label":"System x Hardware Options->SAS\/SATA Controller->Host Bus Adapter->44E8700"},"Platform":[{"code":"PF042","label":"Caldera"},{"code":"PF047","label":"SurePOS"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 January 2019

UID

ibm1MIGR-5085190

Page Feedback