3-40
Diagnostic Tools
DAAD Diagnostic Messages
Continued
Message
Description
Recommended Action
Controller needs
replacing (DAAD
Error 104)
The Intelligent Array Expansion System
firmware is less than version 1.14.
Replace the controller as soon as possible.
Controller
reported POST
error.
Error Code: x
The controller returned an error from its
internal Power-On Self Tests.
Replace the controller.
Controller
restarted with a
signature of zero
DAAD did not find a valid configuration
signature to use to get the data.
Nonvolatile RAM may not be present
(unconfigured) or the signature present
in nonvolatile RAM may not match the
signature on the controller.
Run the System Configuration Utility to configure the
controller and nonvolatile RAM.
DAAD recorded
errors attempting
to access: X
DAAD found errors while attempting to
access physical drive X, believed to be
operational. Message followed by
specific information about the error.
Replace the drive, or correct the condition that caused
the error.
Disable command
issued
Posted-writes have been disabled by
the issuing of the Accelerator Disable
command. This occurred because of an
operating system device driver.
Restart the system. Run the System Configuration Utility
to reinitialize the array accelerator board.
Drive (bay) X
needs replacing
(DAAD Error 102)
The 210-megabyte hard drive has
firmware version 2.30 or 2.31.
Replace the drive.
Drive Monitoring
features are
unobtainable
DAAD unable to get monitor and
performance data due to fatal
command problem such as drive time-
out, or unable to get data due to these
features not supported on the
controller.
Check for other errors (time-outs, and so on). If no other
errors occur, upgrade the firmware to a version that
supports monitor and performance, if desired.
Drive Monitoring
is NOT enabled
for drive bay X
The monitor and performance features
have not been enabled.
Run the System Configuration Utility to initialize the
monitor and performance features.
Drive time-out
occurred on
physical drive
bay X
DAAD issued a command to a physical
drive and the command was never
acknowledged.
The drive or cable may be bad. Check the other error
messages on the Diagnostics screen to determine
resolution.
Continued