ProLiant ML530 Servers Maintenance and Service Guide
Table Of Contents
- Compaq ProLiant ML530 Servers Maintenance and Service Guide
- Notice Page
- Table of Contents
- About This Guide
- Chapter 1: Illustrated Parts List
- Chapter 2: Removal and Replacement Procedures
- Electrostatic Discharge Information
- Symbols on Equipment
- Preparation Procedures
- Tower Model Front Bezel Door
- RackMount Bezel
- Access Panel
- Fans
- Removable Media and Mass Storage Devices
- Cable Routing Diagrams
- System Board Tray
- System Board Components
- HotPlug Power Supplies
- Power Backplane Board
- Power On/Standby Switch
- Chapter 3: Diagnostics and Troubleshooting
- Diagnostic Tools Utility Overview
- Default Configuration
- Utilities Access
- PowerOn SelfTest
- Diagnostics Software
- Steps for Diagnostics
- 100–199, Primary Processor Test Error Codes
- 200–299, Memory Test Error Codes
- 300–399, Keyboard Test Error Codes
- 400–499, Parallel Printer Test Error Codes
- 500–599, Video Display Unit Test Error Codes
- 600–699, Diskette Drive Test Error Codes
- 800–899, Video Board Test Error Codes
- 1100–1199, Serial Test Error Codes
- 1200–1299, Modem Communications Test Error Codes
- 1700–1799, Hard Drive Test Error Codes
- 1900–1999, Tape Drive Test Error Codes
- 2400–2499, Advanced VGA Board Test Error Codes
- 6000–6099, Compaq NIC Boards Test Error Codes
- 6500–6599, SCSI Hard Drive Test Error Codes
- 6700–6799, SCSI Tape Drive Test Error Codes
- 8600–8699, Pointing Device Interface Test Error Codes
- Array Diagnostic Utility
- Integrated Management Log
- Rapid Error Recovery
- Remote Service Features
- ROMPaq Error Recovery Options
- Compaq Insight Manager
- Chapter 4: Connectors, Switches, Jumpers, and LED Indicators
- Chapter 5: Physical and Operating Specifications
- Index

3-46 Compaq ProLiant ML530 Servers Maintenance and Service Guide
Table 3-20
ADU Diagnostic Messages
continued
Message Description Recommended Action
Loose cable
detected –
logical drives
may be marked
FAILED until
corrected
Controller unable to communicate
with one or more physical drives,
probably because of a cabling
problem.
Logical drives may be in a FAILED
state until the condition is corrected,
preventing access to data on the
controller. If logical drives are
marked FAILED, those logical drives
will be unusable until problem
corrected.
Check all controllers and drive cable
connections.
Turn off the system. Check cables for tight
connection to logical drives. Restart the system.
If the same message recurs, cables may be
bad.
Mirror data
miscompare
Data was found at reinitialization in
the posted write memory; however,
the mirror data compare test failed
resulting in data being marked as
invalid. Data loss is possible.
Replace the array accelerator board.
No configuration
for accelerator
board
The array accelerator board has not
been configured.
If the array accelerator board is present, run the
Array Configuration Utility (ACU) to configure the
board.
NVRAM
configuration
present,
controller not
detected
EISA nonvolatile RAM has a
configuration for an array controller,
but there is no board in this slot.
Either a board has been removed
from the system or a board has been
placed in the wrong slot.
Place the array controller in the proper slot or
run the System Configuration Utility to
reconfigure nonvolatile RAM to reflect the
removal or new position.
One or more
drives is unable
to support
redundant
controller
operation
At least one drive in use does not
support redundant controller
operation.
Replace the drive that does not support
redundant controller operation.
Other controller
indicates
different
hardware model
The other controller in the redundant
controller configuration is a different
hardware model.
Make sure both controllers are fully seated and
using the same hardware model.
Other controller
indicates
different
firmware version
The other controller in the redundant
controller configuration is using a
different firmware version.
Make sure both controllers are using the same
firmware revision.
Other controller
indicates
different cache
size
The other controller in the redundant
controller configuration has a
different size array accelerator.
Make sure both controllers are using the same
capacity array accelerator.
continued










