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

x12a, 0x12b, 0x12c, 0x12d, 0x12e, 0x12f

Page 13 highlights

Event Number (dec/hex) Event Name Predictive Maintenance Implication Suspected Components Description Logged? Mfg Fail? Problem Unsupported Disk 298/0x12a Disk Reassign Completed 299/0x12b Disk Reassign Cancelled Y See disk drive Disk vendor's reassign rate spec. Y Ignore None 300/0x12c No Error On Disk Media After Y Medium Error Ingore unless medium error recurs Disk Drive 301/0x12d Incompatible RAM Image Revision Y Ignore - Operator None Error 302/0x12e Controller Presence Detect Faulted Off Y Single Controller, Occurrance Midplane 303/0x12f No Interrupts From Other Controller Y Single Controller, Occurrance Backplane 304/0x130 305/0x131 306/0x132 307/0x133 308/0x134 Disk Interface Disconnect Disk Downed Data Unavailable Y Ignore - Disk Disk Drive compatibility problem Y Ignore - Operator None or Host activity Y Ignore - See None accompanying errors Insufficient Optimal Space For Y Rebuild Ingore - See accompanying errors None Rebuild Restarted Y Ignore None 309/0x135 310/0x136 311/0x137 Rebuild Executing Rebuild Preempted Cancel Rebuild Started Y N.A. None Y N.A. None Y Ingore - Operator None or Host activity 312/0x138 Rebuild IO Priority Changed 313/0x139 Non-Member Drive Removed Y Ignore - Host None activity Y Ignore - Operator None activity data transfer phase. This will cause disconnects to be disabled for the entire on the interface, thus causing degraded drive performance. This event may also indicate that the firmware could not enable queueing on this drive, which also causes disconnects to be disabled on the interface. The reported FRU is the slot number. (See the "Disk Interface Queuing Disabled" event.) N This event indicates that the array firmware successfully completed a data reassignment (sparing) operation. The reported FRU is the slot number. This is informational only, not an error condition. N This event indicates that a data-reassign (sparing) operation was cancelled by the array firmware. The most likely reason is that the firmware detected that the disk was reset and in need of reconfiguration. The reported FRU is the slot number. This is informational only, not an error. N This event indicates that the PDD's media test has determined that media for which a drive had reported a MEDIUM ERROR is actually OK. The data stored at the affected LBA may or may not have been recovered. The reported FRU is the slot number. N This event indicates that the NVRAM image stored on the volume set when it was shutdown is not compatible with the current version of firmware. The image cannot be uploaded and the resulting system state is NO_MAPS for this volume set. Y he presence detect bit for the other controller is not working. This controller does not "see" another controller in the enclosure, yet it can communicate successfully with the Trifid on the other controller. This error is logged only once per power on. N he "other controller" interrupt seems to be broken. The timer interrupt fired multiple times with new communication messages but no "other controller" interrupts were present. This error is logged only once per power on. N An attached disk unexpectedly disconnected during a disk data transfer. This is informational, not an error. N A device was successfully transitioned to the down state in response to user request. N The data unavailable condition was triggered. This is due to multiple failed, down, or missing drive(s). The condition persists as a warning until less than 2 drives and down, failed, or missing. N here is insufficient disk space for rebuild to execute. This may be due tothe mix of disk sizes on the subsystem. This message follows the message and may follow the REBUILD message. N ebuild has been automatically restarted due to disk failure or removal. Thismessage follows the message. N ab Instrumentation Only. N ab Instrumentation Only. N ebuild has been cancelled either automatically or by command. The subsystemautomatically cancels rebuild if it needs to restart rebuild due to a diskaddition, a LUN deletion, or a LUN format. This message follows the message and may be followed by another message. N host command has changed rebuild I/O priority relative to host I/Os. Thismessage follows the message. N This error code indicates the system state change consisting of a hot plug removal. This event occurs for drives that are not volume set members when they are removed. The device number field is not

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27

Event
Number
(dec/hex)
Event
Name
Logged?
Predictive
Maintenance
Implication
Suspected
Components
Mfg Fail?
Description
Problem -
Unsupported
Disk
data transfer phase.
This will cause disconnects to
be disabled for the entire on the interface, thus
causing degraded drive performance.
This event
may also indicate that the firmware could not enable
queueing on this drive, which also causes
disconnects to be disabled on the interface.
The
reported FRU is the slot number.
(See the "Disk
Interface Queuing Disabled" event.)
298/0x12a
Disk Reassign Completed
Y
See disk drive
vendor’s reassign
rate spec.
Disk
N
This event indicates that the array firmware
successfully completed a data reassignment
(sparing) operation.
The reported FRU is the slot
number.
This is informational only, not an error
condition.
299/0x12b
Disk Reassign Cancelled
Y
Ignore
None
N
This event indicates that a data-reassign (sparing)
operation was cancelled by the array firmware.
The
most likely reason is that the firmware detected that
the disk was reset and in need of reconfiguration.
The reported FRU is the slot number.
This is
informational only, not an error.
300/0x12c
No Error On Disk Media After
Medium Error
Y
Ingore unless
medium error
recurs
Disk Drive
N
This event indicates that the PDD’s media test has
determined that media for which a drive had
reported a MEDIUM ERROR is actually OK.
The
data stored at the affected LBA may or may not
have been recovered.
The reported FRU is the slot
number.
301/0x12d
Incompatible RAM Image
Revision
Y
Ignore - Operator
Error
None
N
This event indicates that the NVRAM image stored
on the volume set when it was shutdown is not
compatible with the current version of firmware.
The image cannot be uploaded and the resulting
system state is NO_MAPS for this volume set.
302/0x12e
Controller Presence Detect
Faulted Off
Y
Single
Occurrance
Controller,
Midplane
Y
he presence detect bit for the other controller is not
working.
This controller does not "see" another
controller in the enclosure, yet it can communicate
successfully with the Trifid on the other controller.
This error is logged only once per power on.
303/0x12f
No Interrupts From Other
Controller
Y
Single
Occurrance
Controller,
Backplane
N
he "other controller" interrupt seems to be broken.
The timer interrupt fired multiple times with new
communication messages but no "other controller"
interrupts were present.
This error is logged only
once per power on.
304/0x130
Disk Interface Disconnect
Y
Ignore - Disk
compatibility
problem
Disk Drive
N
An attached disk unexpectedly disconnected during
a disk data transfer.
This is informational, not an
error.
305/0x131
Disk Downed
Y
Ignore - Operator
or Host activity
None
N
A device was successfully transitioned to the down
state in response to user request.
306/0x132
Data Unavailable
Y
Ignore - See
accompanying
errors
None
N
The data unavailable condition was triggered.
This
is due to multiple failed, down, or missing drive(s).
The condition persists as a warning until less than 2
drives and down, failed, or missing.
307/0x133
Insufficient Optimal Space For
Rebuild
Y
Ingore - See
accompanying
errors
None
N
here is insufficient disk space for rebuild to execute.
This may be due tothe mix of disk sizes on the
subsystem. This message follows the message and
may follow the REBUILD message.
308/0x134
Rebuild Restarted
Y
Ignore
None
N
ebuild has been automatically restarted due to disk
failure or removal. Thismessage follows the
message.
309/0x135
Rebuild Executing
Y
N.A.
None
N
ab Instrumentation Only.
310/0x136
Rebuild Preempted
Y
N.A.
None
N
ab Instrumentation Only.
311/0x137
Cancel Rebuild Started
Y
Ingore - Operator
or Host activity
None
N
ebuild has been cancelled either automatically or by
command. The subsystemautomatically cancels
rebuild if it needs to restart rebuild due to a
diskaddition, a LUN deletion, or a LUN format.
This message follows the message and may be
followed by another message.
312/0x138
Rebuild IO Priority Changed
Y
Ignore - Host
activity
None
N
host command has changed rebuild I/O priority
relative to host I/Os. Thismessage follows the
message.
313/0x139
Non-Member Drive Removed
Y
Ignore - Operator
activity
None
N
This error code indicates the system state change
consisting of a hot plug removal.
This event occurs
for drives that are not volume set members when
they are removed. The device number field is not