Specifications

Diagnostic Tools 3-37
For use with Pentium II and Pentium III Xeon processor-based servers only
Table 3-21
ADU Diagnostic Messages
Message Description Recommended Action
Accelerator
board not
detected
Array controller did not detect a
configured array accelerator board.
Install the array accelerator board on the 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, you may need to
replace the array accelerator board.
Accelerator
parity read
errors: n
Number of times that read memory
parity errors were detected during
transfers from memory on array
accelerator board.
If there are many parity errors, you may need to
replace the array accelerator board.
Accelerator
parity write
errors: n
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, you may need to
replace the array accelerator board.
Accelerator
status: Cache
was
automatically
configured
during last
controller reset.
This 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 the 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, you may
need to replace the array accelerator.
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(s).
Resolve problem with drive(s). The controller
will be able to write dirty data to drives and then
posted write operations will be restored.
Accelerator
status: Dirty data
detected. Unable
to write dirty
data to drives
At least one cache line contains dirty
data that the controller has been
unable to flush (write) to the drives.
This problem usually occurs when
there is a problem with the drive(s).
Resolve the problem with drive(s), and then
controller will then be able to write dirty data to
drives.
continued