HP 2000 Modular Smart Array Controller Firmware J202P01, J212P01, and J302P01 Release Notes (537811-008, December 2012)

• Scrub log entries did not properly display the parity error count after a failover event.
• In both the SMU and CLI, metadata was not cleared from all of the selected drives when
commanded to do so.
• The controller stalled when a vdisk with snapshot and replication volumes was deleted.
• A duplicate vdisk was reported after a halted controller recovered.
• LUNs were not properly re-mapped after changing vdisk ownership.
• The wrong drive was marked as “down”.
• Improved management of cache flushing.
• Added ability to allow flow control on iSCSI ports.
• Removed unused debug agent component.
• RAID data logs were not flushed after an extended power off or when a controller was restarted
but failover did not occur.
• RAID 50 error reporting did not report errors during verify.
• Improved performance on RAID 10 vdisks.
• When a controller was removed and I/O was in process, the transaction was held in the cache.
• Scrubbing message was unclear when vdisk is owned by the other controller.
• After extensive run time and I/Os, the system may stall during a shutdown procedure.
• Background vdisk scrub stopped with no warning.
• If a controller was restarting or failing over at the same time that a snapshot was being deleted,
there was a possibility of the snapshot becoming inconsistent.
• Disk loss during an expansion controller upgrade.
• A power supply module failure event was not included in the system event logs.
• Vdisk scrub failed ungracefully on disk URE.
• Reduced the I/O delay when a has failed and data needs to be reconstructed by the RAID engine.
• There was a disk channel error when using SATA drives.
• The event log did not properly report when both controllers were restarted.
• LEDs of all drives in enclosure 1 were amber and SMI-S reported them as failed.
• Management controller hung after recovery.
• Disconnecting a back end cable caused a controller to halt.
• Volume was not accessible after converting it from a Master volume to a Standard volume.
• An unknown setting was reported set on one disk in a system.
• False under-run errors were written to the event logs.
• A controller halt reported Double IOB to same Nexus in the event logs.
• The power supply module was incorrectly identified in the event logs.
• Incorrectly reported the components were in a degraded state.
• Could not collect a complete set of logs from an array.
CLI-specific fixes and enhancements incorporated into J202R10, J212R10, and J302R10:
• trust command: Updated CLI help example.
• trust vdisk command: When run on a vdisk that was online, it reported success when it
should have reported failure.
6 Fixes and enhancements