HP ProLiant Gen9 User manual

HP ProLiant Gen9
Troubleshooting Guide
Volume II: Error Messages
Abstract
This guide provides a list of error messages associated with HP ProLiant servers, HP Integrated Lights-Out, HP Smart Array storage, HP Onboard
Administrator, HP Virtual Connect,
ROM, and Configuration Replication Utility. This document is intended for the person who installs, administers,
and troubleshoots servers or server blades. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazar
ds
in products with hazardous energy levels.
Part Number: 795673-001
September 2014
Edition: 1

© Copyright 2014 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Microsoft®, Windows®, and Windows Server® are U.S. registered trademarks of the Microsoft group of companies.
Intel®, Pentium®, and Itanium® are trademarks of Intel Corporation in the U.S. and other countries.
UNIX® is a registered trademark of The Open Group.

Contents 3
Contents
Introduction.................................................................................................................................. 8
Overview ....................................................................................................................................................8
Troubleshooting resources ...................................................................................................................8
HP ProLiant server errors................................................................................................................ 9
ADU error messages.....................................................................................................................................9
Introduction to ADU error messages .....................................................................................................9
ADU version 8.0 through 8.28 error messages ...................................................................................29
POST error messages and beep codes .........................................................................................................39
Introduction to POST error messages ..................................................................................................39
Non-numeric messages or beeps only.................................................................................................39
100 Series ......................................................................................................................................49
200 Series ......................................................................................................................................51
300 Series ......................................................................................................................................63
400 Series ......................................................................................................................................65
600 Series ......................................................................................................................................65
1100 Series ....................................................................................................................................66
1500 Series ....................................................................................................................................66
1600 Series ....................................................................................................................................67
1700 Series ....................................................................................................................................71
1800 Series ....................................................................................................................................90
Event list error messages .............................................................................................................................94
Introduction to event list error messages..............................................................................................94
A CPU Power Module (System Board, Socket X)..................................................................................94
ASR Lockup Detected: Cause.............................................................................................................94
Automatic operating system shutdown initiated due to fan failure..........................................................95
Automatic Operating System Shutdown Initiated Due to Overheat Condition..........................................95
Blue Screen Trap: Cause [NT]... ........................................................................................................95
Corrected Memory Error Threshold Passed (Slot X, Memory Module Y)..................................................95
EISA Expansion Bus Master Timeout (Slot X)........................................................................................95
PCI Bus Error (Slot X, Bus Y, Device Z, Function X) ...............................................................................95
Processor Correctable Error Threshold Passed (Slot X, Socket Y)............................................................96
Processor Uncorrectable Internal Error (Slot X, Socket Y).......................................................................96
Real-Time Clock Battery Failing..........................................................................................................96
System AC Power Overload (Power Supply X).....................................................................................96
System AC Power Problem (Power Supply X).......................................................................................96
System Fan Failure (Fan X, Location) ..................................................................................................96
System Fans Not Redundant..............................................................................................................97
System Overheating (Zone X, Location) ..............................................................................................97
System Power Supplies Not Redundant...............................................................................................97
System Power Supply Failure (Power Supply X)....................................................................................97
Unrecoverable Host Bus Data Parity Error... ........................................................................................97
Uncorrectable Memory Error (Slot X, Memory Module Y)......................................................................97
Windows® Event Log processor error codes .................................................................................................97
Message ID: 4137...........................................................................................................................97
Message ID: 4140...........................................................................................................................98
Message ID: 4141...........................................................................................................................98

Contents 4
Message ID: 4169...........................................................................................................................98
Message ID: 4190...........................................................................................................................98
HP ProLiant Gen9 power fault LEDs............................................................................................. 100
Power fault LEDs.......................................................................................................................................100
HP Smart Array errors ............................................................................................................... 101
Controller runtime LEDs.............................................................................................................................101
P440ar controller LEDs ...................................................................................................................101
P440 controller LEDs ......................................................................................................................102
P441 controller LEDs ......................................................................................................................103
P840 controller LEDs ......................................................................................................................104
Cache module LEDs..................................................................................................................................105
Smart Array Windows Event Log messages.................................................................................................106
Message identifiers 24578-24599 ..................................................................................................106
Message identifiers 24600-24624 ..................................................................................................115
Message identifiers 24625-24649 ..................................................................................................120
Message identifiers 24650-24674 ..................................................................................................123
Message identifiers 24675-24699 ..................................................................................................127
Message identifiers 24700-24724 ..................................................................................................131
Message identifiers 24725-24749 ..................................................................................................139
Message identifiers 24750-24774 ..................................................................................................144
Message identifiers 24775-24799 ..................................................................................................149
Message identifiers 24800-24808 ..................................................................................................156
Smart Array Windows driver errors............................................................................................................157
HP Onboard Administrator errors ............................................................................................... 159
Onboard Administrator error messages......................................................................................................159
SysLog messages .....................................................................................................................................175
Alertmail log messages ...................................................................................................................175
Authentication and startup log messages ..........................................................................................175
CGI log messages..........................................................................................................................176
CLI log messages ...........................................................................................................................176
Interconnect bay log messages ........................................................................................................176
DHCP log messages .......................................................................................................................177
Enclosure-Link log messages ............................................................................................................178
Non-volatile configuration log messages...........................................................................................179
Firmware flash log messages...........................................................................................................181
Flash certificate, configuration, and storage log messages..................................................................181
DNS network configuration log messages.........................................................................................183
LCD log messages..........................................................................................................................184
Operational log messages ..............................................................................................................185
Linux log messages.........................................................................................................................193
Management log messages.............................................................................................................193
OA internal log messages...............................................................................................................200
LDAP log messages ........................................................................................................................201
Redundancy log messages ..............................................................................................................201
SSO log messages .........................................................................................................................202
Two-factor log messages.................................................................................................................203
FIPS log messages..........................................................................................................................203
VLAN log messages .......................................................................................................................204
Onboard Administrator SNMP traps ..........................................................................................................204
Enclosure event notifications......................................................................................................................205
Command line event notifications...............................................................................................................205

Contents 5
HP Virtual Connect errors........................................................................................................... 208
SNMP overview.......................................................................................................................................208
SNMP traps...................................................................................................................................209
Virtual Connect Manager SysLog events .....................................................................................................216
Domain events (1000-1999) ...........................................................................................................217
Enclosure events (2000-2999).........................................................................................................219
Ethernet Module events (3000-3999) ...............................................................................................221
FC Module events (4000-4999).......................................................................................................224
Server events (5000-5999) .............................................................................................................225
Profile events (6000-6999) .............................................................................................................227
Ethernet Network events (7000-7999)..............................................................................................229
FC Fabric events (8000-8999) ........................................................................................................229
Unknown Module events (9000-9999).............................................................................................230
Enet uplinkset events (17000-17999)...............................................................................................231
HPRCU errors........................................................................................................................... 232
HPRCU return codes .................................................................................................................................232
CONREP errors ........................................................................................................................ 233
Using CONREP........................................................................................................................................233
CONREP return codes ..............................................................................................................................233
CONREP screen output.............................................................................................................................234
HP iLO errors ........................................................................................................................... 235
iLO overview ...........................................................................................................................................235
iLO POST LED indicators...........................................................................................................................235
Event log entries.......................................................................................................................................235
RIBCL messages .......................................................................................................................................238
Hardware and software link-related issues ..................................................................................................243
Login issues .............................................................................................................................................243
Login name and password not accepted...........................................................................................243
Directory user premature logout.......................................................................................................243
iLO Management Port not accessible by name ..................................................................................244
iLO RBSU unavailable after iLO and server reset................................................................................244
Unable to access the login page......................................................................................................244
Unable to return to login page after an iLO flash or reset ...................................................................244
Unable to access virtual media or graphical remote console...............................................................245
Unable to connect to iLO after changing network settings...................................................................245
Unable to connect to the iLO processor through the NIC ....................................................................245
Unable to log in to iLO after installing the iLO certificate ....................................................................245
Unable to connect to the iLO IP address............................................................................................246
Blocked iLO ports...........................................................................................................................246
Troubleshooting alert and trap issues..........................................................................................................246
Unable to receive HP SIM alarms (SNMP Traps) from iLO ..................................................................246
Unable to login with emergency access............................................................................................246
Incorrect authentication code...........................................................................................................247
Troubleshooting directory issues.................................................................................................................247
ActiveX controls are enabled and I see a prompt, but the domain/name login format does not work ......247
User contexts do not appear to work................................................................................................247
Directory user does not logout after the directory timeout has expired..................................................247
Troubleshooting Remote Console issues ......................................................................................................248
Remote Console applet has a red X when running Linux client browser................................................248
Unable to navigate the single cursor of the Remote Console to corners of the Remote............................248
Remote Console text window not updating properly...........................................................................248

Contents 6
Monitor problems in IRC or Java Remote Console..............................................................................249
Mouse/keyboard not working in IRC or Java Remote Console ............................................................249
IRC sends characters continuously after switching windows ................................................................249
Java Remote Console does not display the correct floppy and USB-key device......................................249
Caps Lock goes out of synch between iLO and a Java Remote Console session ....................................251
Num Lock goes out of synch between iLO and a multi-user IRC session................................................251
Session leader does not receive connection request when IRC is in replay mode...................................251
Keyboard LED does not display correctly ..........................................................................................252
Inactive IRC ...................................................................................................................................252
IRC failed to connect to server error message....................................................................................252
Troubleshooting SSH issues .......................................................................................................................252
Initial PuTTY input slow ...................................................................................................................253
PuTTY client unresponsive with Shared Network Port..........................................................................253
SSH text support from a Remote Console session...............................................................................253
Troubleshooting video and monitor issues...................................................................................................253
User interface does not display correctly...........................................................................................253
Troubleshooting Virtual Media issues..........................................................................................................253
Virtual Floppy media applet is unresponsive......................................................................................253
Troubleshooting Remote Text Console issues ...............................................................................................254
Unable to view the Linux installer in the text console ..........................................................................254
Unable to pass data through an SSH terminal ...................................................................................254
Troubleshooting miscellaneous issues .........................................................................................................254
Cookie sharing between browser instances and iLO..........................................................................254
Unable to get SNMP information from HP SIM ..................................................................................256
Unable to upgrade iLO firmware .....................................................................................................256
iLO network failed flash recovery.....................................................................................................257
Issues generating a keytab using ktpass.exe......................................................................................258
Testing SSL ....................................................................................................................................258
File not present after copy through IRC virtual drives to USB key..........................................................259
Resetting iLO .................................................................................................................................259
Server name still present after ERASE utility is executed ......................................................................260
Troubleshooting a remote host.........................................................................................................260
Microsoft Windows Event ID and SNMP traps.............................................................................. 261
Event log messages associated with SNMP traps.........................................................................................261
Windows NT® event log format ................................................................................................................261
Agent descriptions....................................................................................................................................261
Foundation agents....................................................................................................................................262
Event Identifiers 1105-1808............................................................................................................262
Event Identifiers 2048-2359............................................................................................................271
Event Identifiers 3072-3876............................................................................................................274
Event Identifiers 4352-4626............................................................................................................278
Storage agents ........................................................................................................................................281
Event Identifiers 256-774................................................................................................................281
Event Identifiers 1061-1098............................................................................................................284
Event Identifiers 1101-1199............................................................................................................291
Event Identifiers 1200-1294............................................................................................................317
Event Identifiers 1343-4613............................................................................................................335
Server agents...........................................................................................................................................339
Event Identifiers 256-1024..............................................................................................................339
Event Identifiers 1025-1092............................................................................................................342
Event Identifiers 1103-1183............................................................................................................351
Event Identifiers 1539-3352............................................................................................................385
Event Identifiers 5632-5684............................................................................................................387

Contents 7
NIC agents..............................................................................................................................................389
Event Identifiers 256-299................................................................................................................389
Event Identifiers 300-1293..............................................................................................................393
Support and other resources ...................................................................................................... 399
Before you contact HP ..............................................................................................................................399
HP contact information..............................................................................................................................399
Acronyms and abbreviations...................................................................................................... 400
Documentation feedback ........................................................................................................... 404
Index....................................................................................................................................... 405

Introduction 8
Introduction
Overview
This guide is part of a two volume set. Volume I, the HP ProLiant Gen9 Troubleshooting Guide, Volume I:
Troubleshooting provides procedures for resolving common problems. This guide, Volume II: Error
Messages, provides a list of error messages and information to assist with interpreting and resolving error
messages on ProLiant servers and server blades. Use these messages to troubleshoot and optimize the
operation of your HP equipment.
Troubleshooting resources
The HP ProLiant Gen9 Troubleshooting Guide, Volume I: Troubleshooting provides procedures for resolving
common problems and comprehensive courses of action for fault isolation and identification, issue resolution,
and software maintenance on ProLiant servers and server blades. To view the guide, select a language:
•English (http://www.hp.com/support/Gen9_TSG_en)
•French (http://www.hp.com/support/Gen9_TSG_fr)
•Spanish (http://www.hp.com/support/Gen9_TSG_es)
•German (http://www.hp.com/support/Gen9_TSG_de)
•Japanese (http://www.hp.com/support/Gen9_TSG_ja)
•Simplified Chinese (http://www.hp.com/support/Gen9_TSG_zh_cn)

HP ProLiant server errors 9
HP ProLiant server errors
ADU error messages
Introduction to ADU error messages
This section contains a complete alphabetical list of all ADU error messages for ADU version 7.85.16.0 and
earlier.
IMPORTANT: This guide provides information for multiple servers. Some information may not
apply to the server you are troubleshooting. Refer to the server documentation for information on
procedures, hardware options, software tools, and operating systems supported by the server.
WARNING: To avoid potential problems, ALWAYS read the warnings and cautionary
information in the server documentation before removing, replacing, reseating, or modifying
system components.
Accelerator Board not Detected
Description: Array controller did not detect a configured array accelerator board.
Action: Install an array accelerator board on an array controller. If an array accelerator board is installed,
check for proper seating on the array controller board.
Accelerator Error Log
Description: List of the last 32 parity errors on transfers to or from the memory on the array accelerator board.
Displays starting memory address, transfer count, and operation (read and write).
Action: If many parity errors are listed, you may need to replace the array accelerator board.
Accelerator Parity Read Errors: X
Description: Number of times that read memory parity errors were detected during transfers from memory on
the array accelerator board.
Action: If many parity errors occurred, you may need to replace the array accelerator board.
Accelerator Parity Write Errors: X
Description: Number of times that write memory parity errors were detected during transfers to memory on
the array accelerator board.
Action: If many parity errors occurred, you may need to replace the array accelerator board.

HP ProLiant server errors 10
Accelerator Status: Cache was Automatically Configured During Last Controller
Reset
Description: Cache board was replaced with one of a different size.
Action: No action is required.
Accelerator Status: Data in the Cache was Lost...
...due to some reason other than the battery being discharged.
Description: Data in cache was lost, but not because of the battery being discharged.
Action: Be sure the array accelerator is properly seated. If the error persists, you may need to replace the
array accelerator.
Accelerator Status: Dirty Data Detected has Reached Limit...
...Cache still enabled, but writes no longer being posted.
Description: Number of cache lines containing dirty data that cannot be flushed (written) to the drives has
reached a preset limit. The cache is still enabled, but writes are no longer being posted. This problem usually
occurs when a problem with the drive or drives occurs.
Action: Resolve the problem with the drive or drives. The controller can then write the dirty data to the drives.
Posted-writes operations are restored.
Accelerator Status: Dirty Data Detected...
...Unable to write dirty data to drives
Description: At least one cache line contains dirty data that the controller has been unable to flush (write) to
the drives. This problem usually occurs when a problem with the drive or drives occurs.
Action: Resolve the problem with the drive or drives. The controller can then write the dirty data to the drives.
Accelerator Status: Excessive ECC Errors Detected in at Least One Cache Line...
...As a result, at least one cache line is no longer in use.
Description: At least one line in the cache is no longer in use due to excessive ECC errors detected during use
of the memory associated with that cache line.
Action: Consider replacing the cache. If cache replacement is not done, the remaining cache lines generally
continue to operate properly.
Accelerator Status: Excessive ECC Errors Detected in Multiple Cache Lines...
...As a result, the cache is no longer in use.
Description: The number of cache lines experiencing excessive ECC errors has reached a preset limit.
Therefore, the cache has been shut down.
Action:
1. Reseat the cache to the controller.
2. If the problem persists, replace the cache.

HP ProLiant server errors 11
Accelerator Status: Obsolete Data Detected
Description: During reset initialization, obsolete data was found in the cache due to the drives being moved
and written to by another controller.
Action: No action is required. The controller either writes the data to the drives or discards the data
completely.
Accelerator Status: Obsolete Data was Discarded
Description: During reset initialization, obsolete data was found in the cache, and was discarded (not written
to the drives).
Action: No action is required.
Accelerator Status: Obsolete Data was Flushed (Written) to Drives
Description: During reset initialization, obsolete data was found in the cache. The obsolete data was written
to the drives, but newer data may have been overwritten.
Action: If newer data was overwritten, you may need to restore newer data; otherwise, normal operation
should continue.
Accelerator Status: Permanently Disabled
Description: Array accelerator board has been permanently disabled. It will remain disabled until it is
reinitialized using HP SSA.
Action: Check the Disable Code field. Run HP SSA to reinitialize the array accelerator board.
Accelerator Status: Possible Data Loss in Cache
Description: Possible data loss was 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.
Action: No way exists to determine if dirty or bad data was in the cache and is now lost.
Accelerator Status: Temporarily Disabled
Description: Array accelerator board has been temporarily disabled.
Action: Check the Disable Code field.
Accelerator Status: Unrecognized Status
Description: A status was returned from the array accelerator board that ADU does not recognize.
Action: Obtain the latest version of ADU.
Accelerator Status: Valid Data Found at Reset
Description: Valid data was found in posted-write memory at reinitialization. Data will be flushed to disk.
Action: No error or data loss condition exists. No action is required.

HP ProLiant server errors 12
Accelerator Status: Warranty Alert
Description: Catastrophic problem exists with array accelerator board. Refer to other messages on
Diagnostics screen for exact meaning of this message.
Action: Replace the array accelerator board.
Adapter/NVRAM ID Mismatch
Description: EISA NVRAM has an ID for a different controller from the one physically present in the slot.
Action: Run the server setup utility.
Array Accelerator Battery Pack X not Fully Charged
Description: Battery is not fully charged.
Action: If 75% of the batteries present are fully charged, the array accelerator is fully operational. If more
than 75% of the batteries are notfully charged, allow 36 hours to recharge them.
Array Accelerator Battery Pack X Below Reference Voltage (Recharging)
Description: Battery pack on the array accelerator is below the required voltage levels.
Action: Replace the array accelerator board if the batteries do not recharge within 36 powered-on hours.
Board in Use by Expand Operation
Description: Array accelerator memory is in use by a capacity expansion or RAID migration.
Action: The array accelerator is automatically re-enabled for caching when the capacity expansion or RAID
operation completes.
Board not Attached
Description: An array controller is configured for use with array accelerator board, but one is not connected.
Action: Connect array accelerator board to array controller.
Cache Has Been Disabled Because ADG Enabler Dongle is Broken or Missing
Description: The cache has been disabled because RAID ADG volume is configured but the ADG Enabler
Dongle is broken or missing.
Action: Check the ADG Enabler Dongle. Replace if needed.
Cache Has Been Disabled; Likely Caused By a Loose Pin on One of the RAM Chips
Description: Cache has been disabled due to a large number of ECC errors detected while testing the cache
during POST. This is probably caused by a loose pin on one of the RAM chips.
Action: Try reseating the cache to the controller. If that does not work, replace the cache.

HP ProLiant server errors 13
Configuration Signature is Zero
Description: ADU detected that NVRAM contains a configuration signature of zero. Old versions of the server
setup utility could cause this.
Action: Run the latest version of server setup utility to configure the controller and NVRAM.
Configuration Signature Mismatch
Description: The array accelerator board is configured for a different array controller board. The
configuration signature on the array accelerator board does not match the one stored on the array controller
board.
Action: To recognize the array accelerator board, run HP SSA.
Controller Communication Failure Occurred
Description: Controller communication failure occurred. ADU was unable to successfully issue commands to
the controller in this slot.
Action:
1. Be sure all cables are properly connected and working.
2. Be sure the controller is working, and replace if needed.
Controller Detected. NVRAM Configuration not Present
Description: EISA NVRAM does not contain a configuration for this controller.
Action: Run the server setup utility to configure the NVRAM.
Controller Firmware Needs Upgrading
Description: Controller firmware is below the latest recommended version.
Action: Update the controller to the latest firmware version.
Controller is Located in Special "Video" Slot
Description: Controller is installed in the slot for special video control signals. If the controller is used in this
slot, LED indicators on the front panel may not function properly.
Action: Install the controller into a different slot, and run the server setup utility to configure NVRAM. Then, run
HP SSA to configure the controller.
Controller Is Not Configured
Description: Controller is not configured. If the controller was previously configured and you change drive
locations, a problem might exist with the placement of the drives. ADU examines each physical drive and
looks for drives that have been moved to a different drive bay.
Action: Look for messages indicating which drives have been moved. If no messages are displayed and drive
swapping did not occur, run HP SSA to configure the controller and run the server setup utility to configure
NVRAM. Do not run either utility if you believe drive swapping has occurred.

HP ProLiant server errors 14
Controller Reported POST Error. Error Code: X
Description: The controller returned an error from its internal POST.
Action: Replace the controller.
Controller Restarted with a Signature of Zero
Description: ADU did not find a valid configuration signature to use to get the data. NVRAM may not be
present (unconfigured) or the signature present in NVRAM may not match the signature on the controller.
Action: Run the server setup utility to configure the controller and NVRAM.
Disable Command Issued
Description: The issuing of the Accelerator Disable command has disabled posted-writes. This occurred
because of an operating system device driver.
Action: Restart the system. Run HP SSA to reinitialize the array accelerator board.
Drive (Bay) X Firmware Needs Upgrading
Description: Firmware on this physical drive is below the latest recommended version.
Action: Update the drive to the latest firmware version.
Drive (Bay) X has Insufficient Capacity for its Configuration
Description: Drive has insufficient capacity to be used in this logical drive configuration.
Action: Replace this drive with a larger capacity drive.
Drive (Bay) X has Invalid M&P Stamp
Description: Physical drive has invalid monitor and performance data.
Action: Run the server setup utility to properly initialize this drive.
Drive (Bay) X Has Loose Cable
Description: The array controller could not communicate with this drive at power-up. This drive has not
previously failed.
Action:
1. Be sure all cables are properly connected and working.
2. Power down the system and attempt to reconnect data/power cable to the drive.
3. Power up the system.
4. If the problem persists, power down the system and replace the cable.
5. If the problem persists, power down the system and replace the drive.

HP ProLiant server errors 15
Drive (Bay) X is a Replacement Drive
Description: This drive has been replaced. This message is displayed if a drive is replaced in a fault-tolerant
logical volume.
Action: If the replacement was intentional, allow the drive to rebuild.
Drive (Bay) X is a Replacement Drive Marked OK
Description: The drive has been replaced and marked OK by the firmware, in one of three possible
scenarios: the drive was replaced in a non-fault-tolerant configuration; more drives were replaced than the
configured fault-tolerant-configuration mode could sustain; or the storage enclosure was powered down
before the server, preventing the drive from being rebuilt. The drive may contain incorrect data.
Action: Verify data on the drives. Always power down the server before powering down any external drive
enclosures.
Drive (Bay) X is Failed
Description: The indicated physical drive has failed.
Action:
1. Check for loose cable connections.
2. If cable connectors are secure, replace the drive.
Drive (Bay) X is Undergoing Drive Recovery
Description: This drive is being rebuilt from the corresponding mirror or parity data.
Action: No action is required.
Drive (Bay) X Upload Code Not Readable
Description: An error occurred while ADU was trying to read the upload code information from this drive.
Action: If multiple errors occur, the drive may need to be replaced.
Drive (Bay) X Was Inadvertently Replaced
Description: The physical drive was incorrectly replaced after another drive failed.
Action:
CAUTION: Do not run the server setup utility and try to reconfigure, or data will be lost.
1. Power down the server.
2. Replace the drive that was incorrectly replaced.
3. Replace the original drive that failed.

HP ProLiant server errors 16
Drive Monitoring Features Are Unobtainable
Description: ADU is unable to get monitor and performance data due to a fatal command problem (such as
drive time-out), or is unable to get data due to these features not being supported on the controller.
Action: Check for other errors such as time-outs. If no other errors occur, upgrade the firmware to a version
that supports monitor and performance, if desired.
Drive Monitoring is NOT Enabled for SCSI Port X Drive ID Y
Description: The monitor and performance features have not been enabled on this drive.
Action: Run the server setup utility to initialize the monitor and performance features.
Drive Time-Out Occurred on Physical Drive Bay X
Description: ADU issued a command to a physical drive and the command was never acknowledged.
Action: The drive or cable may be bad. Check the other error messages on the Diagnostics screen to
determine resolution.
Drive X Indicates Position Y
Description: Message indicates a designated physical drive, which seems to be scrambled or in a drive bay
other than the one for which it was originally configured.
Action:
1. Examine the graphical drive representation on ADU to determine proper drive locations.
2. Power down the server.
3. Remove drive X and place it in drive position Y.
4. Rearrange the drives according to the ADU instructions.
Duplicate Write Memory Error
Description: Data cannot be written to the array accelerator board in duplicate due to the detection of parity
errors. This is not a data-loss situation.
Action: Replace the array accelerator board.
Error Occurred Reading RIS Copy from SCSI Port X Drive ID
Description: An error occurred while ADU was trying to read the RIS from this drive.
Action: HP stores the hard drive configuration information in the RIS. If multiple errors occur, the drive may
need to be replaced.
FYI: Drive (Bay) X is Third-Party Supplied
Description: Third-party supplied the installed drive.
Action: If problems exist with this drive, replace it with a supported drive.

HP ProLiant server errors 17
Identify Logical Drive Data did not Match with NVRAM
Description: The identify unit data from the array controller does not match with the information stored in
NVRAM. This can occur if new, previously configured drives have been placed in a system that has also been
previously configured.
Action: Run the server setup utility to configure the controller and NVRAM.
Insufficient adapter resources
Description: The adapter does not have sufficient resources to perform posted-write operations to the array
accelerator board. Drive rebuild may be occurring.
Action: Operate the system without the array accelerator board until the drive rebuild completes.
Inter-Controller Link Connection Could Not Be Established
Description: Unable to communicate over the link connecting the redundant controllers.
Action: Be sure both controllers are using the same hardware and firmware revisions. If one controller failed,
replace it.
Less Than 75% Batteries at Sufficient Voltage
Description: The operation of the array accelerator board has been disabled due to less than 75% of the
battery packs being at the sufficient voltage level.
Action: Replace the array accelerator board if the batteries do not recharge within 36 powered-on hours.
Less Than 75% of Batteries at Sufficient Voltage Battery Pack X Below Reference
Voltage
Description: Battery pack on the array accelerator is below the required voltage levels.
Action: Replace the array accelerator board if the batteries do not recharge within 36 powered-on hours.
Logical Drive X Failed Due to Cache Error
Description: This logical drive failed due to a catastrophic cache error.
Action: Replace the array accelerator board and reconfigure it using HP SSA.
Logical Drive X Status = Failed
Description: This status could be issued for several reasons:
•Logical drive is configured for No Fault Tolerance, and one or more drives failed.
•Mirroring is enabled, and any two mirrored drives failed.
•Data Guarding is enabled, and two or more drives failed.
•Another configured logical drive is in the WRONG DRIVE REPLACED or LOOSE CABLE DETECTED
state.
Action: Check for drive failures, wrong drive replaced, or loose cable messages. If a drive failure occurred,
replace the failed drive or drives, and then restore the data for this logical drive from the tape backup.

HP ProLiant server errors 18
Otherwise, follow the procedures for correcting problems when an incorrect drive is replaced or a loose
cable is detected.
Logical Drive X Status = Interim Recovery (Volume Functional, but not Fault Tolerant)
Description: A physical drive in this logical drive has failed. The logical drive is operational, but the loss of
an additional drive may cause permanent data loss.
Action: Replace the failed drive as soon as possible.
Logical Drive X Status = Loose Cable Detected...
...SOLUTION: Turn the system off and attempt to reattach any loose connections. If this does not work, replace the
cable(s) and connection(s).
Description: At power up, the system does not detect a configured physical drive or an external storage unit
that was previously detected before the last system shutdown. This event can occur if the user removes one or
more drives after the system is powered down or if a loose cable or malfunction prevents the drives from
spinning up.
Action:
If a drive or enclosure has been removed or disconnected, do the following:
1. Power down the server.
2. Check cabling.
3. Power up the server and storage enclosure at the same time.
If drives are failed or purposely removed while the system is off:
1. Reboot the server.
2. When prompted during POST, press F2 to fail the missing drives.
Logical Drive X Status = Overheated
Description: The temperature of the Intelligent Array Expansion System drives is beyond safe operating levels
and has shut down to avoid damage.
Action: Check the fans and the operating environment.
Logical Drive X Status = Overheating
Description: The temperature of the Intelligent Array Expansion System drives is beyond safe operating levels.
Action: Check the fans and the operating environment.
Logical Drive X Status = Recovering (rebuilding data on a replaced drive)
Description: A physical drive in this logical drive has failed and has now been replaced. The replaced drive
is rebuilding from the mirror drive or the parity data.
Action: No action is required. Normal operations can occur; however, performance will be less than optimal
until after the rebuild process completes.

HP ProLiant server errors 19
Logical Drive X Status = Wrong Drive Replaced
Description: A physical drive in this logical drive has failed. The incorrect drive was replaced.
Action:
1. Power down the server.
2. Replace the drive that was incorrectly replaced.
3. Replace the original drive that failed with a new drive.
CAUTION: Do not run the server setup utility and try to reconfigure, or data will be lost.
Loose Cable Detected - Logical Drives May Be Marked FAILED Until Corrected
Description: At power up, the system does not detect a configured physical drive or an external storage unit
that was previously detected before the last system shutdown. This event can occur if the user removes one or
more drives after the system is powered down or if a loose cable or malfunction prevents the drives from
spinning up.
Action: If a drive or enclosure has been removed or disconnected, do the following:
1. Power down the server.
2. Check cabling.
3. Power up the server and storage enclosure at the same time.
If drives are failed or purposely removed while the system is off:
1. Reboot the server.
2. When prompted during POST, press F2 to fail the missing drives.
Mirror Data Miscompare
Description: Data was found at reset initialization in the posted-write memory; however, the mirror data
compare test failed resulting in that data being marked as invalid. Data loss is possible.
Action: Replace the array accelerator board.
No Configuration for Array Accelerator Board
Description: The array accelerator board has not been configured.
Action: If the array accelerator board is present, run HP SSA to configure the board.
One or More Drives is Unable to Support Redundant Controller Operation
Description: At least one drive in use does not support redundant controller operation.
Action: Replace the drive that does not support redundant controller operation.

HP ProLiant server errors 20
Other Controller Indicates Different Hardware Model
Description: The other controller in the redundant controller configuration is a different hardware model.
Action: Be sure both controllers are using the same hardware model. If they are, make sure the controllers are
fully seated in their slots.
Other Controller Indicates Different Firmware Version
Description: The other controller in the redundant controller configuration is using a different firmware
version.
Action: Be sure both controllers are using the same firmware revision.
Other Controller Indicates Different Cache Size
Description: The other controller in the redundant controller configuration has a different size array
accelerator.
Action: Be sure both controllers are using the same capacity array accelerator.
Processor Reduced Power Mode Enabled in RBSU
Description: Processors clocked down
Action: If you select the reduced power mode in RBSU, the processor are displayed as their reduced speed
during POST. This message indicates that the RBSU reduced power mode has been enabled and also
indicates the maximum speed for the installed processors.
Processor Not Started (Processor Stalled)
Description: If processor fails to launch or fails after being launched but before completing its initialization,
the processor is not started and this message is displayed. This is likely a defective processor.
Processor Not Started (Stepping Does Not Match)
Description: If a processor has a stepping different than the bootstrap processor, the processor is not started,
and this message is displayed.
Processor Not Started (Unsupported Processor Stepping)
Description: If a processor has an unsupported stepping, it is not started, and this message is displayed.
Processor Not Supported (Unsupported Core Speed)
Description: If a processor has a core speed that is incompatible with the other installed processors, the
processor is not started, and this message is displayed.