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

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? 260/0x104 261/0x105 262/0x106 263/0x107 264/0x108 No Quorum For Disk Set Attachment No Quorum Due To Broadcast Failure No Address Table No Disk Drives Found During Initialization Insufficient Space During Rebuild accompanying errors Y Ignore - Operator None activity or accompanying errors Y Ignore - See None accompanying errors Y Ignore - Operator None activity or accompanying errors Y Ignore - Operator None activity Y Ignore - See None accompanying errors. 265/0x109 Rebuild Started Y Ignore - See None accompanying errors. 266/0x10a 267/0x10b 268/0x10c Rebuild Complete Insufficient Space To Start Rebuild Rebuild Failed 269/0x10d 270/0x10e Cancel Rebuild Complete Disk Drive Table Overflow Y Ignore None Y Ignore - See None accompanying errors Y Ignore - See None accompanying errors Y Ignore - Operator None or Host Activity Y Ignore - Operator None activity 271/0x10f Duplicate Disk Drive Identifier Y Single Occurrance Controller or Erroneous Operator Activity 272/0x110 Disk Drive Installed Y Ignore - Operator None Activity Since volume set partitioning is not allowed the system cannot attach to this VS. N During startup (with VS related NVRAM invalid) we were unable to find a VS with a quorum of its members present. N During startup (with VS related NVRAM invalid) we were unable to invalidate the NVRAM image on a quorum of the members of the VS we tried to attach to. N During startup (with VS related NVRAM invalid) we were unable to to find a VS present that had a valid shutdown image on any of the members present. N During startup no disks were present so a new volume set with no members was created. N here is insufficient disk space for migrating data. This is a controllererror, although the subsystem may still support some I/Os without adding disks.his message follows the message, if the error isdiscovered during rebuild. N ebuild has been started either automatically or by command. Unless there wasa reset during rebuild, at least two more messages follow this , ,, ,, or . The messageindicates that a format subsystem was issued through the front panel or byhost command, eliminating the need for a rebuild. If there was a resetduring rebuild, you will see the message repeated. N ebuild has completed successfully. This message follows the message. N here is insufficient disk space for rebuild to execute. This message followsthe message and may follow the REBUILD message. N ebuild has failed to complete due to multiple disk failures or a controllerfailure. Previous messages in the log should indicate whether or not therehave been multiple disk failures. This message follows the message. N ebuild cancellation has completed. This message always follows the message. N The controller is capable of retaining information about 16 drives. Since only 12 can be inserted at a time the remaining 4 would have to be missing drives on which the controller still depends. If the total number of missing drives and present drives ever exceeds this limit, the TOO_MANY_DRIVES condition is logged. At this point the controller cannot recognise any additional inserted drives. The system always reports data unavailable before this condition is reached. N As part of its stamp, each drive indicates its logical position in the volume set to which it is attached. This error is logged whenever the controller encounters two drives which claim to be in the same position of the same volume set. The most likely source of this error is the erroneous assignment of duplicate volume set ID's. This would generally originate with incorrect controller serial number assignment, and/or loss of NVRAM. This error would also occur if a user made an image copy of a drive. N This error code indicates the system state change consisting of a hot plug insertion. This event occurs regardless of the disposition of the drive toward the volume set. The device number of the drive added appears in this change record. A device number consisting of the controller serial number followed