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

x16a, 0x16b, 0x16c, 0x16d, 0x16e, 0x16f

Page 17 highlights

Event Number (dec/hex) Event Name Predictive Maintenance Implication Suspected Components Description Logged? Mfg Fail? 356/0x164 357/0x165 358/0x166 359/0x167 360/0x168 361/0x169 362/0x16a 363/0x16b 364/0x16c 365/0x16d 366/0x16e 367/0x16f 368/0x170 369/0x171 370/0x172 371/0x173 error appears in the first 4 bytes of the controller serial number field of this log record. The LUN appears in the fifth byte of the controller serial number, and the length of the affected area in 512 byte blocks appears in the last 3 bytes. The FRU field reports the FRU of the drive corrected. Local Controller Failed DRAM Y Ignore if DRAM SIMM, N This error code indicates that the DRAM SIMM on Address Decode Test recovered by Controller the local controller failed the DRAM address decode reset or power on test during the poweron process. Specifically, the DRAM SIMM on the primary controller failed the decode test. Remote Controller Failed Y Ignore if DRAM SIMM, N This error code indicates that the DRAM SIMM on DRAM Address Decode Test recovered by Controller the remote controller failed the DRAM address reset or power on decode test during the poweron process. Specifically, the DRAM SIMM on the secondary controller failed the decode test. Controller Failed Background Y Ignore if ROM, N This error code indicates that the ROM on the local ROM checksum test recovered by Controller controller failed the ROM checksum test done in the reset or power on background during idle time. The firmware stored in the ROM is corrupted. Scrub policy detected error Y Ignore - should Disk drive N This error code indicates that an error was returned be preceded by to the Scrub policy by a device read. It is logged to Drive errors provide information about the cause of the error. Additional information about the error from the device should precede this entry. New controller firmware was Y Ignore - Operator None N New controller firmware was successfully installed downloaded activity in all controllers present in the subsystem. Mode Parameters changed Y Ignore - Operator None N A mode select command was processed and it activity changed one or more changeable mode parameters in the subsystem. Shared memory recovered Y Ignore; other Controller N This error code indicates that some non-fatal error error errors will follow appeared in the shared-memory error queue. The if significant two words of this queue entry will be placed in the log entry extended info area. Shared-memory controller Y Ignore if Controller N This error code indicates that some fatal error error recovered by appeared in the shared-memory controller error reset or power queue. The two words of this error entry will be cycle placed in the event extended info area. After all entries in the queue have been processed, the subsystem will undergo a short reset. Shared-memory checksum Y > 1 in 6 mo. Controller, N This error code indicates that a fatal checksum error error SDRAM, appeared in the shared-memory controller error midplane, disks queue. The two words of this queue entry will be placed in the event extended info area. After all entries currently in the queue have been processed, the subsystem will undergo a reset. Flash failure resulting from Y N.A. Y This error code results if we get an error during the command sent to flash programming, erasing or reading flash. So if we get any error when commanding flash to perform a task that we interpret as Flash not responding correctly, we will log this error. DRAM Checksum failure Y N.A. N If during the download sequence of events we fail during download the checksum performed in DRAM this error will result. This event occurs before we try to copy to FLASH. Flash Checksum failure during Y N.A. Y If after copying the download image into the flash download part(s) the checksum of the image fails this error will result. Download Semaphore request Y N.A. N Only one download command from the host can be failed executed at a time. If a host request for download occurrs while one is already active the redunant requests will get this error. Download image failed Y N.A. N The download image sent from the host is validated validation by the Download Sequncer as to it validity. If the data received does not appear to be firmware image then this error will result. Family Image compare failed Y N.A. N If the firmware image to be downloaded has a different family image value then the currently running image and this is a online download, then this error will result. Download failed on slave Y N.A. Y In a dual controller environment the command to

  • 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
error appears in the first 4 bytes of the controller
serial number field of this log record.
The LUN
appears in the fifth byte of the controller serial
number, and the length of the affected area in 512
byte blocks appears in the last 3 bytes.
The FRU
field reports the FRU of the drive corrected.
356/0x164
Local Controller Failed DRAM
Address Decode Test
Y
Ignore if
recovered by
reset or power on
DRAM SIMM,
Controller
N
This error code indicates that the DRAM SIMM on
the local controller failed the DRAM address decode
test during the poweron process.
Specifically, the
DRAM SIMM on the primary controller failed the
decode test.
357/0x165
Remote Controller Failed
DRAM Address Decode Test
Y
Ignore if
recovered by
reset or power on
DRAM SIMM,
Controller
N
This error code indicates that the DRAM SIMM on
the remote controller failed the DRAM address
decode test during the poweron process.
Specifically, the DRAM SIMM on the secondary
controller failed the decode test.
358/0x166
Controller Failed Background
ROM checksum test
Y
Ignore if
recovered by
reset or power on
ROM,
Controller
N
This error code indicates that the ROM on the local
controller failed the ROM checksum test done in the
background during idle time.
The firmware stored
in the ROM is corrupted.
359/0x167
Scrub policy detected error
Y
Ignore - should
be preceded by
Drive errors
Disk drive
N
This error code indicates that an error was returned
to the Scrub policy by a device read.
It is logged to
provide information about the cause of the error.
Additional information about the error from the
device should precede this entry.
360/0x168
New controller firmware was
downloaded
Y
Ignore - Operator
activity
None
N
New controller firmware was successfully installed
in all controllers present in the subsystem.
361/0x169
Mode Parameters changed
Y
Ignore - Operator
activity
None
N
A mode select command was processed and it
changed one or more changeable mode parameters
in the subsystem.
362/0x16a
Shared memory recovered
error
Y
Ignore; other
errors will follow
if significant
Controller
N
This error code indicates that some non-fatal error
appeared in the shared-memory error queue. The
two words of this queue entry will be placed in the
log entry extended info area.
363/0x16b
Shared-memory controller
error
Y
Ignore if
recovered by
reset or power
cycle
Controller
N
This error code indicates that some fatal error
appeared in the shared-memory controller error
queue. The two words of this error entry will be
placed in the event extended info area. After all
entries in the queue have been processed, the
subsystem will undergo a short reset.
364/0x16c
Shared-memory checksum
error
Y
> 1 in 6 mo.
Controller,
SDRAM,
midplane, disks
N
This error code indicates that a fatal checksum error
appeared in the shared-memory controller error
queue. The two words of this queue entry will be
placed in the event extended info area. After all
entries currently in the queue have been processed,
the subsystem will undergo a reset.
365/0x16d
Flash failure resulting from
command sent to flash
Y
N.A.
Y
This error code results if we get an error during the
programming, erasing or reading flash. So if we get
any error when commanding flash to perform a task
that we interpret as Flash not responding correctly,
we will log this error.
366/0x16e
DRAM Checksum failure
during download
Y
N.A.
N
If during the download sequence of events we fail
the checksum performed in DRAM this error will
result. This event occurs before we try to copy to
FLASH.
367/0x16f
Flash Checksum failure during
download
Y
N.A.
Y
If after copying the download image into the flash
part(s) the checksum of the image fails this error
will result.
368/0x170
Download Semaphore request
failed
Y
N.A.
N
Only one download command from the host can be
executed at a time.
If a host request for download
occurrs while one is already active the redunant
requests will get this error.
369/0x171
Download image failed
validation
Y
N.A.
N
The download image sent from the host is validated
by the Download Sequncer as to it validity.
If the
data received does not appear to be firmware image
then this error will result.
370/0x172
Family Image compare failed
Y
N.A.
N
If the firmware image to be downloaded has a
different family image value then the currently
running image and this is a online download, then
this error will result.
371/0x173
Download failed on slave
Y
N.A.
Y
In a dual controller environment the command to