HP StorageWorks 2012sa Modular Smart Array firmware release notes Version J300P10-01 (508849-001, November 2008)

6. Select your Windows Server 2003 o perating system.
7. In the Operating System — Enhancements and QFEs section, select the KB940467 QFE.
• I/O may not resume to SUSE and Red Hat Linux hosts upon cable reinsertion.
The likelihood of this issue occurring increases with the number of LUNs configured on the storage
array and load. The failover/failback process is working correctly at the multipath driver level. At
the multipath application level, multipath maps are not getting updated. To update the maps at
application level, run the command multipath -v0. This command may take a few ninutes
with heavy I/O running on the system.
• Windows Ser ver 2003 host may hang af ter failure of a vdisk.
The start menu bar goes away, applications may become slow to close, and the system will not
reboot (shuts down all progra m s and closes network connections but hangs at gray screen with
mouse cursor still active) . Microsoft is working on a QFE hotfix. Power cycling the host corrects
the issue.
• Installing the latest driver in RHEL5.2 with HP Device Mapper (HPDM) and Boot from Storage
configuration may stop the OS from booting.
After installing the 4 .00.13.04-2 driver in a b oot from storage configuration with HPDM enabled,
the RHEL 5.2 host may no longer boot into the operating system. HP is working on the issue.
Changing to the previous driver (for example, older INITRD) allows the host to boot from storage.
• After a cable move, LSI Logic MPT SAS BIOS loads incorrectly, showing initialization twice on
the server.
After moving SAS cables to a different SAS host bus adapter (HBA) on the server, the MPT SAS
BIOS may incorrectly load and initialize SAS HBA cards, after which the MSA2012sa stops
accepting I/O requests from the server. Use the SMU to reset the host port interface on both
MSA2012sa storage controllers. Log into the SMU and navigate to the MANAGE > UTILITIES >
host utilities > reset host channel page and click the ResetHostPortbutton to initiate the action.
Although the web page will return imm ediately with a response, it may take up to 1 minute for
the MSA2012sa storage controller to process the request and m ake the host por ts ready for
initialization by the SAS H BA card. A reboot of the server is not required.
• An unanticipated path change may occur on Red Hat Linux 4 Update 6 hosts using HPDM
Multipath software.
In a multi-path configuration using HPDM software during periods of heavy I/O load, Linux Red
Hat 4.6 hosts may experience unanticipated path change due to a SCSI I/O tim eout. This issue
does not occur for single path configurations. To reduce the likelihood of occurrence, ensure the
storage array is pr operly configured and has a balanced I/O load.
• Drives may not be seen by the LSI Logic MPT SAS BIOS when more than one SAS HBA card is
installed on some servers.
After making some con figurationchanges,theMPTSASBIOSmaynotlistallavailabledrives
for boot during startup. This message may appear during startup: Adapter configuration
may have changed, reconfiguration is suggested. The MPT SAS BIOS setup utility,
accessed by pressing F8 during boot-up and selecting the SAS Configuration Tool, can be used to
add the HBA back to the boot list. A reboot of the server is required.
• A newly created snapshot volume on a single controller array presented a nd mapped to a
Windows host may not be detected by the Windows operating system.
Use the Rescan Disks command in Windows Disk Management to force detection of the
newly created snap shot volume. Rescanning disks can take several minutes, depending on the
number of hardware devices installed.
• The SMU may hang after drive failures.
If this cond ition o ccurs, access the array using the command line interface (CLI) and restart
the management controller (MC) using the command: restart mc a (single controller) or
restart mc both (dual controller).
• Issuing the CLI command set cache-parameters read-ahead maximum does not change
the setting although the message indicates success.
Some cases, where the number of volumes is large or for some reason the available read cache
is small, may result in the setting of "maximum" to display a smaller value than expected. The
maximum read-ahead cache is calculated by dividing the available read cache by the number
of volumes presented.
• An NTP server IP address change on one controller does not propagate to the other controller.
HP StorageWorks 2012sa Modular Smart Array firmware release notes
5