HP 1850R - ProLiant - 128 MB RAM Troubleshooting Manual page 273
Proliant server troubleshooting guide
Hide thumbs
Also See for 1850R - ProLiant - 128 MB RAM:
- Reference manual (138 pages) ,
- Implementation manual (35 pages) ,
- Overview (20 pages)
Table of Contents
Table D-1: Array Diagnostic Utility (ADU) Error Messages
Message
The redundant controllers
installed are not the same
model.
SOLUTION: Power down the
system and verify that the
redundant controllers are
different models. If they are
different models, replace the
other controller with the same
model as this one.
This controller can't see the
drives but the other controller
can
This controller can see the
drives but the other controller
can't
Unable to communicate with
drive on SCSI Port X,
Drive ID Y
Unable to retrieve identify
controller data. Controller may
be disabled or failed.
SOLUTION: Power down the
system. Verify that the
controller is fully seated. Then
power the system on and look
for helpful error messages
displayed by the controller. If
this doesn't help, contact your
COMPAQ service provider.
HP Servers Troubleshooting Guide
Description
ADU detected two different
controller models installed in a
redundant controller
configuration. This is not
supported, and one or both
controllers may not be
operating properly.
The other controller in the
redundant controller
configuration can recognize
the drives, but this controller
cannot.
The other controller in the
redundant controller
configuration cannot recognize
the drives, but this controller
can.
The array controller cannot
communicate with the drive.
ADU requested the identify
controller data from the
controller but was unable to
obtain it. This usually indicates
that the controller is not seated
properly, or has failed.
ADU Error Messages
continued
Recommended Action
Use the same controller
models for redundant
controller configurations.
Resolve any other errors and
then rerun ADU.
Resolve any other errors and
then rerun ADU.
If the hard drive amber LED is
on, replace the drive.
1.
Power down the server.
2.
Be sure that the controller
is fully seated.
3.
Restart the server.
4.
Resolve any error
messages displayed by
the controller.
If this does not solve the
problem, contact an authorized
service provider.
continued
D-23
Table of Contents
Troubleshooting
