HBA - LSI SAS HBA Firmware Issue, SAS Devices Not Being Seen by Server

Asset ID:	1-72-1350564.1
Update Date:	2012-04-30
Keywords:

Solution Type Problem Resolution Sure

Solution 1350564.1 : HBA - LSI SAS HBA Firmware Issue, SAS Devices Not Being Seen by Server

Applies to:

Sun Storage 3Gb SAS PCI-X HBA - Version Not Applicable and later
Sun StorageTek SL24 Tape Autoloader - Version Not Applicable and later
Sun StorageTek SL48 Tape Library - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms

LSI SAS HBA Firmware Issue.
SAS attached drive not seen by server.
SAS attached library not seem by server.
System is aware the SAS HBA is there, but is not aware of the drives/library.

There is an issue with the LSI SAS1 (3GB) HBA with a firmware level of 1.26.00 and below where the HBA will not see any SAS devices connected to it.

NOTES:
This pertains to any Sun Storage 3Gb SAS HBA.
This can effect any OS or Application running.
This is strictly an HBA firmware issue.

Changes

Installing a SAS attached library and drives.

Cause

Down level SAS HBA firmware.

Solution

Upgrade SAS HBA firmware to level 1.29.06 or higher to resolve drives and library not being seen.

To find the level of firmware running on the HBA on a Windows or Solaris x86 host you would have to watch for the BIOS of the HBA while the server is booting up. In that BIOS message it will state what firmware version the HBA is currently running.

To find the level of firmware running on the HBA on a Solaris SPARC host, you have to first look in the prtdiag (explorer) output to see what model the LSI SAS HBA is and then you can do a find for that model in the prtpicl (explorer) output and find the firmware version of that HBA.

Below is an example from a LSI SAS HBA running the bad 1.1a.00 firmware (the code is listed in hexidecimal in the prtpicl output).

The latest firmware from the following LSI/Oracle website fixes this issue:
http://www.lsi.com/sep/Pages/oracle/sg_xpci8sas_e_sRoHS.aspx

If the customer has issues upgrading the firmware then the Midgrange disk team who supports the SAS HBA's should engaged to assist the customer.

There is also a workaround where you can unplug the device and then plug it back in while the HBA is up and running (hot plug the device) and usually the device will be seen by the HBA. But as soon as you reboot with the device connected it will not be seen by the HBA anymore.

Example:

:model LSI,1068E
:compatible (b700001174TBL)
| pci13e9,58 |
| pciex1000,58 |
| pci1000,58 |
| AAPL,MPT |
:assigned-addresses
81 11 00 10 00 00 00 00 00 00 a0 00 00 00 00 00 00 00 01 00
82 11 00 14 00 00 00 00 01 60 00 00 00 00 00 00 00 00 40 00
82 11 00 1c 00 00 00 00 01 61 00 00 00 00 00 00 00 01 00 00
82 11 00 30 00 00 00 00 01 80 00 00 00 00 00 00 00 20 00 00
:ddi-intr-weight 0xa
:scsi-enumeration 0
:scsi-options 0x107ff8
:scsi-reset-delay 0xbb8
:scsi-watchdog-tick 0xa
:scsi-selection-timeout 0xfa
:scsi-tag-age-limit 0x2
:scsi-initiator-id 0x7
:initiator-interconnect-type SATA
:disable-sata-mpxio yes
:mpxio-disable yes
:ddi-vhci-class scsi_vhci
:fm-ereport-capable
:fm-errcb-capable
:fm-dmachk-capable
:fm-accchk-capable
:pm-components (b70000115eTBL)
| NAME=mpt2 |
| 0=Off (PCI D3 State) |
| 3=On (PCI D0 State) |
:firmware-version 1.1a.0.0 <----------------- HBA Firmware Version
:nvdata-version-default 0x2d03
:nvdata-version-persistent 0x2d03
:num-phys 0x8
:initiator-port 500605b00115e770
:devfs-path /pci@400/pci@2/pci@0/pci@c/LSILogic,sas@0
:driver-name mpt
:binding-name pciex1000,58
:bus-addr 0
:instance 2
:_class scsi-2
:name LSILogic,sas

Provided by Ryan Lucas

Attachments

This solution has no attachment