Home » Compaq Manuals » Servers » Compaq ProLiant 1000 » Manual Viewer

Compaq ProLiant 1000 ProLiant Server Troubleshooting Guide - Page 273

power the system on and look, controller is fully seated. Then

Get Compaq ProLiant 1000 PDF manuals and user guides

View all Compaq ProLiant 1000 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 273 highlights

ADU Error Messages Table D-1: Array Diagnostic Utility (ADU) Error Messages continued Message Description Recommended Action 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. 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. Use the same controller models for redundant controller configurations. This controller can't see the drives but the other controller can The other controller in the redundant controller configuration can recognize the drives, but this controller cannot. Resolve any other errors and then rerun ADU. This controller can see the drives but the other controller can't The other controller in the redundant controller configuration cannot recognize the drives, but this controller can. Resolve any other errors and then rerun ADU. Unable to communicate with drive on SCSI Port X, Drive ID Y The array controller cannot communicate with the drive. If the hard drive amber LED is on, replace the drive. 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. 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. 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 HP Servers Troubleshooting Guide D-23

Section	Page
HP Servers Troubleshooting Guide	1
Notice	2
Contents	3
About This Guide	11
Who Should Use This Guide	11
How to Use This Guide	12
Key Terms	12
Symbols in Text	13
Reader’s Comments	13
HP Resources	13
Chapter 1: Diagnosing the Problem	14
Developing a Troubleshooting Plan	15
Preparing to Troubleshoot the Server	16
Preparing the Server for Diagnosis	16
Using a Troubleshooting Methodology	16
Gathering Information	18
Preliminary Information	18
When the Server Does Not Start	19
When a ProLiant ML, ProLiant DL, TaskSmart, or Previously Released Server Does Not Start	19
When a ProLiant BL Server Does Not Start	22
When the Self-Tests Fail	25
When the Operating System Does Not Load	28
Locating Troubleshooting Information	31
Contacting HP	33
Contacting Technical Support or Authorized Reseller	33
Server Information You Need	34
Operating System Information You Need	35
Microsoft Operating Systems	36
Linux Operating Systems	37
Novell NetWare Operating Systems	38
Caldera and SCO Operating Systems	39
IBM OS/2 Operating Systems	40
Sun Solaris Operating Systems	41
Banyan VINES Operating Systems	42
SQL Server	42
Chapter 2: Hardware Problems	43
Important Safety Information	44
Symbols on Equipment	44
Rack Stability	46
Power Problems	47
Power Source	47
Power Supply	48
System Power Module	48
Uninterruptible Power Supply	49
System Short Circuit	50
Redundant Line Cord Switch	51
General Hardware Problems	52
Loose Connections	52
Cabling Order	52
New Hardware	53
General Devices	54
Third-Party Devices	54
Universal Serial Bus Devices	54
Testing the Device	54
Rack Environment	55
Internal System Problems	56
Processors	56
Processor Power Modules	58
PCI or PCI-X Hot Plug	59
Memory	59
Fans	62
General Fan Problems	62
Hot-Plug Fan Problems	63
Drive Problems	64
Diskette Drives	64
CD-ROM and DVD Drives	65
Hard Drives	66
General Hard Drives	66
SCSI Non-Hot-Plug Hard Drives	68
SCSI Hot-Plug Hard Drives	68
Predictive Failure Alert	72
Tape Drives	73
DLT Drives	73
DAT Drives	76
External Device Problems	77
Video	77
Audio	79
Printers	79
Mouse and Keyboard	80
Diagnostic Adapter	81
Integrated Management Display	82
Hot-Plug Management Module	82
Network and Modem Problems	83
Network Controllers	83
Modems	85
Chapter 3: Software Problems	89
Operating Systems	90
Operating System Problems	90
Operating System Updates	93
Restoring to a Backed-Up Version	93
When to Reconfigure or Reload Software	94
Application Software	96
Clustering Software	97
Remote ROM Flash Problems	97
Maintaining Current Drivers	100
Erasing the System	102
Chapter 4: Diagnostic Tools	104
Array Diagnostic Utility	105
Diagnostics	106
Enterprise Diagnostics LX32	106
Accessing Enterprise Diagnostics LX32	108
Running Tests	108
Saving Error Reports	108
Diagnostics on a 32-bit System	108
Running Diagnostics	109
Diagnostics on a 64-bit System	109
Running Diagnostics	109
Exiting Diagnostics	110
Server Management	111
Server Management on 64-bit Servers	111
Survey Utility	112
Running Survey Utility	112
Diagnostic Adapter	113
Diagnostic Station	113
Inspect Utility	113
Running Inspect on a 32-bit System	113
Running Inspect on a 64-bit System	114
Integrated Administrator	115
Integrated Lights-Out	115
Integrated Management Log	115
List of Events	116
Power-On Self-Test	121
BIOS Serial Console	121
Server Blade Health Driver	121
Chapter 5: Error Recovery	122
ROMPaq Disaster Recovery	123
Redundant ROM Image Recovery	125
Automatic Server Recovery-2	125
Unattended Recovery	126
Attended Recovery	127
Hardware Requirements	127
Health Driver	130
Initiating Diagnostics	131
Initiating the Operating System	135
ASR-2 Password Security	136
ASR-2 Integrated Management Log Messages	136
Automatic Revision Tracking	139
Storage Fault Recovery Tracking	140
Storage Automatic Reconstruction	140
Network Interface Fault Recovery Tracking	140
Memory Fault Recovery Tracking	140
Chapter 6: Error Prevention	141
Preparing for Changes	142
Minimizing the Impact of Changes by Using HP Too	143
Managing Updates Through Integration Servers	143
Installing Servers Consistently Through Replicate	144
Maintaining Server Software	144
Other Ways to Minimize the Impact of Changes	144
Version Control	144
Server Design	144
Minimizing Updates	145
Using a Methodology	145
Visually Checking Your Server	147
Recognizing Power Problems Caused by Acts of Nat	148
Preventing Power Management Problems	148
General Power Requirements	149
Power Consumption Considerations	149
Power Supply Considerations	149
Power Cord Considerations	149
Power Redundancy Considerations	150
Preventing Grounding Problems	150
Preventing Temperature Problems	150
Preventing Damage to Removable Drives	151
Preventing Electrostatic Damage	152
Preventing Cable Damage	152
Preventing Tape Drive Errors	153
Appendix A: HP Resources	154
Online Resources	155
Software and Option Resources	157
General Server Resources	162
ProLiant BL e-Class System Resources	165
Appendix B: Test Error Codes	166
100-199, Primary Processor Test Error Codes	167
200-299, Memory Test Error Codes	168
300-399, Keyboard Test Error Codes	170
400-499, Parallel Printer Test Error Codes	171
500599, Graphics Controller Unit Test Error Co	172
600-699, Diskette Drive Test Error Codes	173
1100-1199, Serial Test Error Codes	174
1200-1299, Modem Communications Test Error Code	175
6000-6099, Network Interface Controllers Test Er	176
6100-6199, Array Controller Test Error Codes	177
6500-6599, SCSI Hard Drive Test Error Codes	178
6600-6699, SCSI/IDE CD-ROM Drive Test Error Co	179
6700-6799, SCSI Tape Drive Test Error Codes	180
8600-8699, Pointing Device Interface Test Error Codes	180
Appendix C: POST Error Messages	181
Non-Numeric POST Error Messages or Beeps Only	182
100 Series POST Error Messages	187
200 Series POST Error Messages	194
300 Series POST Error Messages	205
400 Series POST Error Messages	207
500 Series POST Error Messages	207
600 Series POST Error Messages	208
800 Series POST Error Messages	210
900 Series POST Error Messages	216
1100 Series POST Error Messages	217
1600 Series POST Error Messages	218
1700 Series POST Error Messages	227
1800 Series POST Error Messages	250
Appendix D: ADU Error Messages	251

Match case Limit results 1 per page

ADU Error Messages

HP Servers Troubleshooting Guide

D-23

Table D-1:

Array Diagnostic Utility (ADU) Error Messages

continued

Message

Description

Recommended Action

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.

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.

Use the same controller

models for redundant

controller configurations.

This controller can’t see the

drives but the other controller

can

The other controller in the

redundant controller

configuration can recognize

the drives, but this controller

cannot.

Resolve any other errors and

then rerun ADU.

This controller can see the

drives but the other controller

can’t

The other controller in the

redundant controller

configuration cannot recognize

the drives, but this controller

can.

Resolve any other errors and

then rerun ADU.

Unable to communicate with

drive on SCSI Port

Drive ID

The array controller cannot

communicate with the drive.

If the hard drive amber LED is

on, replace the drive.

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.

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.

Power down the server.

Be sure that the controller

is fully seated.

Restart the server.

Resolve any error

messages displayed by

the controller.

If this does not solve the

problem, contact an authorized

service provider.

continued