HP StorageWorks 2000fc - G2 Modular Smart Array Firmware Release Notes page 4

• Improved ability to communicate with a controller after it has been shut down, to improve restart
behavior.
• Enhanced the SNMP community string to support strings that contain dash and underscore char-
acters.
• Improved the SNMP Notification page in internationalized systems that uses non-ASCI characters,
such as Japanese.
Fixes
• Fixed a problem detecting the number of disk drive bays in an expansion enclosure.
• Fixed the issue that all drives spun up concurrently when a single power supply was in use. If only
a single power supply is functioning, disk drives now spin up in a staggered manner.
• Fixed a situation where a SATA disk drive may be dropped from a vdisk during a firmware up-
grade.
• Fixed a problem where user credentials were reset to default values when controller A was replaced.
• Fixed an issue where the vdisk number was mis-reported.
• Fixed an issue where a firmware upgrade did not error out when an invalid package was used.
• Fixed an issue that allowed a user to set the independent cache mode to an unsupported config-
uration.
• Fixed an issue that a reconstructing vdisk would report as completed when just beginning the re-
build.
• Fixed an issue where a failed disk drive might cause a controller to stall.
• Fixed an issue where correctable ECC errors caused a scrub failure.
• Fixed a problem where a scrub error was reported when, in fact, the background scrub was
manually stopped.
• Fixed an issue where an offline vdisk might not be appropriately quarantined when an array is
powered up.
• Fixed an issue where the array did not correctly report all supported persistent reservation types.
• Fixed an issue where deleting a vdisk failed.
• Fixed an issue that, while deleting a snapshot, could lead to an error and cause the snapshot to
not be deleted.
• Fixed an issue where a quarantine event caused a scrub error.
• Fixed an issue where media errors were not leading to a disk drive being removed from service.
• Fixed a situation where IO requests during a failover would fail out with the following error message:
"Request not supported".
• Fixed a problem where failover did not occur, even when a component failed.
• Fixed a situation where reconstruction progress stuck at 0%.
• Fixed a rare timing issue that lead to a drive enclosure not being discovered on a reboot.
• Fixed an issue that lead to drive enclosure firmware update failure.
• Fixed a problem where a LUN reset did not clear same sector reads.
• Fixed an issue where a controller failover lead to IP settings being lost.
• Fixed an issue where a Windows OS might see a volume that does not exist at LUN 0.
• Fixed an issue where both storage controllers became unresponsive when a disk issue caused a
general protection fault to be delivered to both controllers.
• Fixed an issue that could cause a storage controller to crash while I/O is being written to a RAID
6 vdisk that is in a critical state.
• Fixed a timing issue that lead to a controller becoming unresponsive.
4