HP MSA2324sa HP 2000 G2 Modular Smart Array Controller Firmware M113R10 Releas - Page 5
A vdisk went offline after controller B was killed/unkilled.
View all HP MSA2324sa manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 5 highlights
• Improved processing on dual-ported drives. • After updating drive firmware, an email notification indicating that the update failed was generated, when the update actually completed successfully. • After replacing a failed chassis, cascaded drive enclosures were numbered incorrectly. (Single-controller systems only) • When a controller was in the process of booting up and that controller killed the partner controller, some vdisks were unnecessarily quarantined. • A power supply failure that coincided with drive removals or insertions was not reported in the Event logs. • When scrub failed on a RAID5 vdisk, an error message was not generated. An error message is now generated when a drive is removed or marked as down while any utility is in progress on a vdisk. • A master-to-standard volume conversion was rejected if a VolumeCopy operation was in progress and the snap-pool was not functioning or was not available. • When running a verify on a RAID1 vdisk and a drive was removed, an error message is now reported. • Reduced the possibility of losing the heartbeat between the controllers. • The controller crashed when deleting a snapshot at the same time I/O was being written to that snapshot. • When a dedicated spare was deleted from its vdisk, it was incorrectly classified as Leftover instead of Available. • Clearing metadata on a leftover drive caused a controller to crash. • When a RAID6 vdisk was in a critical state, multiple unresolvable medium errors on a drive caused the system controllers to crash. • The primary enclosure will now be assigned an ID of 0 and no other enclosure will be allowed to have an ID of 0, reducing the likelihood of a vdisk going down when a cable to a cascaded drive enclosure is inserted. • In a Fibre Channel system, the amber LEDs on all of the drives illuminated and SMI-S reported them as failed. • When a SAS cable was disconnected, the controller crashed. • A vdisk went offline after controller B was killed/unkilled. • The serial number of a power supply was reported inconsistently in the event logs. • An invalid error message was generated when the expand-snap-pool max command was issued on a vdisk with no remaining space available. • Prevent drive spin-down while rebooting the other controller during a firmware update. • If the array was power-cycled at approximately the same time as a drive was removed from a RAID6 vdisk, the controller crashed. • Controller crashed during a firmware update. • After updating controller firmware, dedicated spares were classified as Leftover. • When the vdisk owner was changed, the dedicated spare was classified as Leftover. • If the global spare for a critical RAID50 vdisk was not in the same enclosure as the vdisk, the reconstruction did not occur. • Enhanced backend error recovery for drives that do not respond to Task Management Functions. • Spare drives were not used correctly for RAID10 or RAID50 vdisks when they were not in the same enclosure as the failed drive. Enhancements and fixes 5