3-34 Compaq ProLiant ML570 Maintenance and Service Guide
Table 3-18
Array Diagnostic Utility (ADU) Error Messages
Message Description Recommended Action
Accelerator board
not detected
Array controller did not detect a
configured array accelerator board.
Install array accelerator board on array controller.
If an array accelerator board is installed, check
for proper seating on the array controller board.
Accelerator error log List of the last 32 parity errors on
transfers to or from memory on the
array accelerator board. Displays
starting memory address, transfer
count, and operation (read and
write).
If there are many parity errors, the array
accelerator board may need to be replaced.
Accelerator parity
read errors: X
Number of times that read memory
parity errors were detected during
transfers from memory on array
accelerator board.
If there are many parity errors, the array
accelerator board may need to be replaced.
Accelerator parity
write errors: X
Number of times that write memory
parity errors were detected during
transfers to memory on the array
accelerator board.
If there are many parity errors, the array
accelerator board may need to be replaced.
Accelerator status:
Cache was
automatically
configured during
last controller reset
Can occur when cache board is
replaced with one of a different
size.
Normal operations should continue.
Accelerator status:
Data in the cache
was lost due to
some reason other
than the battery
being discharged.
Data in cache was lost, but not
because of the battery being
discharged.
Check to be sure that the array accelerator is
properly seated. If the error continues, the array
accelerator may need to be replaced.
Accelerator status:
Dirty data detected
has reached limit.
Cache still enabled,
but writes no longer
being posted.
The number of cache lines
containing dirty data that cannot be
flushed (written) to the drives has
reached a preset limit. The cache is
still enabled, but writes are no
longer being posted. This problem
usually occurs when there is a
problem with the drive or drives.
Resolve the problem with the drive or drives, and
then the controller can write the dirty data to the
drives. Posted-writes operations are restored.
continued
To Next Page
Loading...
