SerialSCSI-00 (sasd) B.11.31.1103 Mass Storage Driver Release Notes

Table 5 HP-UX 11i v3 March 2009 Fixes — SerialSCSI-00 B.11.31.0903

DescriptionSR Number

Potential system hang issue during abort for an I/O.QXCR1000865554

System panics while posting an ABORT request when chip is in transient state.QXCR1000837729

Table 6 HP-UX 11i v3 December 2008 Fixes — SerialSCSI-00 B.11.31.0812

DescriptionSR Number

Unmapped WSIO Memory causes MCA.QXCR1000878007

Table 7 HP-UX 11i v3 September 2008 Fixes — SerialSCSI-00 B.11.31.0809

DescriptionSR Number

System panic when Scatter/Gather elements exceed the limit.QXCR1000806108

4 Known problems and limitations

This section provides a list of problems and limitations known to HP when these release notes were

published. If workarounds are available, they are included.

4.1 HP 8 Internal Port SAS Controller and HP Multi-Port Internal SAS Controller

• Updating the adapter firmware to version 1.23.33 or later might change the target ID of disk

devices.

This occurs on HP Integrity rx2660, rx3600, and rx6600 servers when an Integrated RAID

volume is configured on the controller and you perform one of the following actions:

◦ Update the adapter firmware offline using sasflash.efi.

◦ Boot to an HP-UX or Ignite-UX disk containing the sasd driver from one of the following

releases, which download firmware version 1.23.33 to the adapter during boot:

– B.11.23.0712

– B.11.31.0712

Changing the target ID might cause physical disks, including the OS boot disk, to become

inaccessible. If some of the disks from the IR volume are inaccessible, the volume can become

degraded or fail.

NOTE: The target ID change does not occur on systems without a RAID-1 volume. It also

does not occur on Bl860c servers with the HP Multiport SAS Controller.

For detailed information on how to avoid or correct this problem, see Updating Internal SAS

Controller Firmware to Version 1.23.33 Or Later at:

http://www.hp.com/go/sas-hba-docs

Click the link for your HP-UX version. The document is listed alphabetically in the “Setup and

install - general” section.

• Before replacing a failed disk, note its Device Special File (DSF) information.

If you shut down a server to replace a failed disk offline, the DSF of the failed disk is not visible

in the ioscan utility when the server restarts. The DSF is required by the replace_tgt

command to rebuild the array with the new disk.

Corrective Action: Before you shut down the server, run the ioscan utility and note the DSF

information for the failed disk.