Compaq ProLiant 6000 Maintenance And Service Manual page 66

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . .
Accelerator board
not detected
Accelerator error
log
Accelerator parity
read errors: n
Accelerator parity
write errors: n
Accelerator status:
Permanently
disabled
Accelerator status:
Possible data loss
in cache
Accelerator status:
Temporarily
DAAD Diagnostic Messages
Message
Array controller did not detect a
configured array accelerator
board.
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).
Number of times that read
memory parity errors were
detected during transfers from
memory on array accelerator
board.
Number of times that write
memory parity errors were
detected during transfers to
memory on the array accelerator
board.
Array accelerator board has
been permanently disabled. It
will remain disabled until it is
reinitialized using the System
Configuration Utility.
Possible data loss detected
during power-up due to all
batteries being below sufficient
voltage level and no presence of
the identification signatures on
the array accelerator board.
Array accelerator board has
been temporarily disabled.
Table 3-20
Description
Compaq ProLiant 6000 Servers Maintenance and Service Guide
Recommended Action
Install array accelerator board
on array controller. If an array
accelerator board is installed,
check for proper seating on
the array controller board.
You may need to run the
System Configuration Utility
and disable the array
accelerator board to get this
message off the screen.
If there are many parity
errors, you may need to
replace the array accelerator
board.
If there are many parity
errors, you may need to
replace the array accelerator
board.
If there are many parity
errors, you may need to
replace the array accelerator
board.
Check the Disable Code field.
Run the System
Configuration Utility to
reinitialize the array
accelerator board.
There is no way to determine
if dirty or bad data was in the
cache and is now lost.
Check the Disable Code field.
3-49