HP StorageWorks 7100 Appendix A. Disk Array Controller Log - Page 16

FC-SCSI Interface SpecificationDescribes the IceCube SCSI interface. Targetted as part of OEM manual.Disk Array Con Error! No text of specified style in document. Event Number (dec/hex) Event Name Predictive Maintenance Implication Suspected Components Description Logged? Mfg Fail? 345/0x159 346/0x15a 347/0x15b 348/0x15c 349/0x15d 350/0x15e 351/0x15f 352/0x160 353/0x161 354/0x162 355/0x163 Bus A TWSI communication Y Controller, Y Either local controller or remote controller SRAM failure battery, power on two-wire serial bus A could not be accessed for supply, controller sync. Bus B SRAM will be used instead midplane (if Bus B SRAMs are also inaccessible, both controllers will reset and and try again; finally one controller will be disabled and the system will continue in single controller mode) Data Loss Detector entry Y Indicates Disk drive(s) N This error code indicates that the data loss detector multiple failure module was called because of multiple failures. A causing data loss data loss has occurred. Member Disk Drive Added Y Ignore - Operator None N This error code is a system change event indicating Back Into Disk Set or host activity that a member of a volume set that was either down, failed, or missing has been returned to the unrestricted use (aka ready) state. This can occur via the add physical drive command, or via hot plug insertion of the drive. Frontend Fibre Channel ABTS Y Ignore None N This error code indicates that the Host sent a Fibre Event Channel ABTS (Abort Sequence) BLS frame to the abort an IO. The array will log this event for informational and debug purposes only. It does not necessarily indicate a problem with the array. Cache Version Mismatch In Y See errors None N A firmware download has a new version of the RAM Image associated with cacheVersionNumber. This is OK if there are no shut down writes stuck in cache but it causes upload to fail with this error code if there are writes stuck in cache. To fix this it is necessary to revert to the old version of firmware and solve whatever problem was causing writes to be stuck in cache (probably one or more disks have failed). RAM Version Mismatch Y N.A. None N The upload routine was unable to upload part of the disk NVRAM image because the current firmware does not support that use of RAM. (Most likely an older version of firmware is trying to upload a disk image posted by some other firmware version.) Disk Format Version Mismatch Y N.A. None N The NVRAM format of the disks does not match the format used by the controller. This event is logged when an icicle controller attempts to use disks previously shutdown by an Ice controller or visa- versa. The controller cannot use an NVRAM image in the incorrect format. ShutDown Due To Power Y Single Power Supplies, N This error code indicates that the Background Supply Failure Occurrance Controller, Manager (BGM) has discovered that there are not Backplane enough good power supplies to run the system. The BGM is shutting down the subsystem to minimize system operation with inadequate power.The NVRAM is posted to disk. Recovery from battery backed Y Single Controller N This error code indicates that recovery from a RAM Loss Started Occurrance battery backed RAM loss has been initiated. Recovery from Battery Backed Y Ignore None N This error code indicates that recovery from a RAM Loss complete battery backed RAM loss completed with at least partial success. Maps were recovered. Multiple failures may or may not have occurred. Occurrance of multiple failures are reported in the log between the RECOV_STARTED and RECOV_DONE events. Redundancy corrected Y Suspect data if Disk Drive, N This error code indicates that the parity scan which followed by error Back End FC executes during recovery from RAM loss found an code 93 (0x5d) Link, Controller instance of incorrect redundant data. Data which was being updated when RAM was lost may produce this error in single failure scenarios. This error can also result from multiple failure conditions. Firmware differentiates the two scenarios by placing a limit on the number of these conditions which can occur before recovery is terminated due to multiple component failures. If this error is followed by error 93 (0x5d) then the contents of data blocks reported in this error should be considered suspect. The block address of the