HP ProLiant Servers Troubleshooting Guide Abstract This document describes common procedures and solutions for the many levels of troubleshooting for HP ProLiant G7 ...
Text Previews (text result may be not accurate)
HP ProLiant Servers
Troubleshooting Guide
Abstract
This document describes common procedures and solutions for the many levels of troubleshooting for HP ProLiant G7 and earlier
servers. 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 hazards in products with hazardous energy levels.
Part Number: 375445
403
October 2011
Edition: 12
© Copyright 20
04, 2011 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 se
t forth in the express
warranty statements accompanying such products and servic
es. 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 Microsoft Corpor
ation.
Intel and Pentium are trademarks of Intel Corporation in the United States and other countries.
AMD is a trademark of Advanced Micro Devices, Inc.
Contents
Contents
Introduction
What's new
Revision history
402 (April 2011)
401 (January 2011)
xx9 (June 2010)
xx8 (July 2009)
xx7 (November 2008)
xx6 (September 2007)
xx5 (June 2006)
xx4 (May 2006)
xx3 (September 2005)
Getting started
13
HP ProLiant 100 Series Server troubleshooting information
How to use this guide
Pre
diagnostic steps
Important safety information
Symptom information
Prepare the server for diagnosis
Common problem resolution
20
Loose connections
Service notifications
Firmware updates
DIMM handling guidelines
Hard drive guidelines
SAS and SATA hard drive guidelines
SCSI hard drive guidelines
Hard drive LED combinations
plug SCSI hard drive LED combinations
SAS and SATA hard drive LED combinations
Server updates with an HP Trusted Platform Module and
BitLocker™ enabled
Diagnostic flowcharts
24
Troubleshooting flowc
harts
Troubleshooting flowchart reference websites
Start
diagnosis flowchart
General diagnosis flowchart
Power
on proble
ms flowchart
POST problems flowchart
Operating system boot probl
ems flowchart
Server fault indications flowchart
Hardware
problems
39
Procedures for all ProLiant servers
Power problems
Power source problems
Contents
Power supply problems
System open circuits and short circuits
UPS problems
General hardware problems
Problems with new hardware
Unknown problem
Third
party device problems
Internal system problems
Battery pack problems
CD
ROM and DVD drive problems
Remote ROM flash problems
Boot problems
Software tools and solutions
69
Configuration tools
SmartStart software
HP ROM
Contents
entering the serial number and product ID
Management tools
Automatic Server Recovery
ROMPaq utility
iLO and iLO 2 technology
iLO 3 technology
Erase Utility
Redundant ROM support
USB support
Diagnostic tools
HP Insight Diagnostics
HP Insight Diagnostics survey functionality
Integrated Management Log
Array diagnostic software
Remote support and analysis tools
HP Insight Remote Support software
Keeping the system current
Drivers
Version control
ProLiant Support Packs
Operating system version support
Firmware
HP Smart Update Manager
System Online ROM flash component utility
Subscriber's choice
Care Pack
Firmware maintenance
Types of ROM
Verifying firmware versions
Updating firmware
HP Smart Update Manager deployment
ROM Update Utility
Unsupported processor stepping with Intel® processors
Unsupported processor stepping with AMD processors
HP resources for troubleshooting
88
Online resources
HP Technical Support website
HP Guided Troubleshooting website
Server documentation
White papers
Service notifications, advisories, and notices
Subscription services
HP Care Pack Services
Product information resources
Additional product information
Registering the server
Overview of server features and installation instructions
Key features, option part numbers
Server and option specifications, symbols, installation warni
ngs, and notices
Teardown procedures, part numbers, specifications
Technical topics
Product installation resources
Contents
System AC Power Problem (Power Supply X)
System Fan Failure (Fan X, Location)
System Fans Not Redundant
System Overheating (Zone X, Location)
System Power Supplies Not Redundant
System Power Supply Failure (Power Supply X)
Unrecoverable Host Bus Data Parity Error...
Contents
Uncorrectable Memory Error (Slot X, Memory Module Y)...
HP BladeS
ystem
Class
infrastructure error codes
Server blade management module error codes
Power management module error codes
Port 85 codes and iLO messages
Troubleshooting the system using port 85 codes
Processor
related port 85 codes
Memory
related port 85 codes
Expansion board
related port 85 codes
Miscellaneous port 85 codes
Windows® Event Log processor error codes
Message ID: 4137
Message ID: 4140
Message ID: 4141
Message ID: 4169
Message ID: 4190
Contacting HP
187
Contacting HP technical support or an authorized reseller
Customer self repair
Server information you need
Operating system information you need
Microsoft® operating systems
Linux operating systems
Introduction
ntroduction
hat's new
The twelfth edition of the
HP ProLiant Servers Troubleshooting
Guide
, part number 375445
403, includes the
following additions and updates:
Updated
Power source problems
(on page
Updated
HP SIM reports a drive fault on a hard drive
managed by an HP Smart Array controller
(on
page
Updated
The fault LED is illuminated on a hard drive managed by an HP Smart Array controller
(on
page
Updated
No hard drives are recognized
(on page
Updated
General graphics and video adapter problems are o
ccurring
(on page
Updated
Screen is blank for more than 60 seconds after you power up the server
(on page
Updated
During installation of Oracle Solaris, the system locks up or a panic error occurs
(on page
Updated
hen to Reconfigure or Reload Software
(on page
Updated
Array Configuration Utility
(on page
Updated
Option ROM Configuration for Arrays
(on page
Updated
Automatic Server Recovery
(on page
Updated the following section in
HP Smart Update Manager deployment
(on page
Online deployment
(on page
Added or updated multiple messages in
Error messages
(on page
ADU version 8.0 through 8.28 error messages
(on page
POST error messages and beep codes
(on page
Non
numeric messages or beeps only
(on page
200 series
(on page
1700 series
(on page
147
1800 series
(on page
172
Updated
Linux operating systems
(on page
Updated
Oracle Solaris operating systems
(on page
Introduction
Revision history
375445
402 (April 2011)
The eleventh edition of the
HP ProLiant Servers Troubleshooting Guide
, part number 375445
402, included
the following additions and updates:
Updated the
HP ProLiant 100 Series Server troubleshooting information
(on page
) section to provide
troubleshooting information for the HP ProLiant ML110 G7 Server and HP ProLiant DL12
0 G7 Server.
Updated the following sections to include the HP Smart Update Firmware DVD:
Firmware updates
(on page
HP Smart Update Manager deployment
(on page
ROM Update Utility
(on page
375445
401 (January 2011)
The tenth edition of the
HP ProLiant Servers Troubleshooting Guide
, part number 375445
401, included the
following additions and updates:
Added a new section to
Getting started
(on
page
Performing processor procedures in the troubleshooting process
(on page
Updated
Breaking the server down to t
he minimum hardware configuration
(on page
Updated the introduction and sections in
Hardware problems
(on page
Unknown problem
(on page
Processor problems
(on page
Updated multiple messages in
Error messages
(on page
POST error messages and beep codes
(on page
Event List Error Messages
(on page
Port 85 codes and iLO messages
(on page
181
Windows® Event Log processor error codes
(on page
Insight Diagnostics processor error codes
375445
xx9 (June 2010)
The
ninth edition of the
HP ProLiant Servers Troubleshooting Guide
, part number 375445
xx9, included the
following additions and updates:
Added new section to
Getting started
(on page
Breaking the server down to the minimum hardware configuration
(on page
Updated
Diagnostic flowcharts
(on page
General diagnosis flowchart
(on page
Server power
on problems flowchart
(on page
Server and
Class
server blade POST problems flowchart
(on page
Introduction
Class server blade POST problems flowchart
(on page
Server and
Class
server blade fault indications flowchart
(on page
Added and updated sections in
Software tools and solutions
(on page
Integrated Lights
Out 3 technology
iLO 3 technology
" on page
Firmware
(on page
HP Smart Update Manager
(on page
Added new sections to
Hardware problems
(on page
Battery pack problems
(on page
Cable problems
(on page
Added a new section to
Software problems
(on page
ROM problems
(on page
Updated a section in
Online resources
(on page
Server documentation
(on page
Updated
Firmware maintenance
(on page
Added new error messages:
ADU error messages
(on page
POST error messages and beep codes
(on page
75445
xx8 (July 2009)
The eighth edition of the
HP ProLiant Servers Troubleshooting Guide
, part number 375445
xx8, included the
following additions and updates:
Added info
rmation to the introduction for the
server power
on problems flowchart
(on page
Added new steps to
Power problems
(on page
Added a new section to
Fan problems
(on page
All fans in an HP ProLiant G6 server are not spinning or are not
spinning at the same speed
(on page
Added a new section to
Memory problems
(on page
Server fails to boot, all DIMM LEDs illuminate amber, ....
(on page
Updated the content for
Tape drive proble
(on page
Added new sections to
Software tools and solutions
(on page
Diagnostics
tasks
(on page
HP Insight Server Migration software for ProLiant
Array diagnostic software
(on page
HP Insight Remote Support software
(on page
Added new content to
HP Resources for Troubleshooting
(on page
HP Guided Troubleshooting website
(on page
DDR3 memory configuration
(on page
Power capacity
(on page
Introduction
Added new error messages:
ADU Error Messages
(on page
POST error messages and beep codes
(on page
75445
xx7 (November 2008)
The seventh editi
on of the
HP ProLiant Servers Troubleshooting Guide
, part number 375445
xx7, included
the following additions and updates:
Added new information about
Server updates with an HP Trusted Platform Module and BitLocker™
enabled
(on page
) to
Common problem resolution
(on page
Added TPM information to
Drive problems (hard drives and solid state drive
(on page
Added information about HP BladeSystem c
Class enclosure fan problems to
Fan problems
(on page
Added
HP Trusted Platform Module problems
(on page
) to
Hardware problems
(on page
Added
SD card problems
(on page
) to
Hardware problems
(on page
Added
USB drive key problems
(on page
) to
Hardware problems
(on page
Added TPM information to
Remote ROM flash problems
(on page
Added Service Essentials Remote Support Pack to
Software tools and solutions
(on page
Added TPM information to
Firmware maintenance
(on page
Updated the
ADU error messages
(on page
) section to reflect the supported versions for the
messages in this document
Updated and added new
POST error messages and beep codes
(on page
75445
xx6 (September 2007)
The sixth edition of the
HP ProLiant Servers Troubleshooting Guide
, part number 375445
xx6, included the
following additions and updates:
Added new information about preventi
ng
electrostatic discharge
(on page
Added new
DIMM handling guidelines
(on page
Added new procedures for troubleshooting
drive problems (hard drives and solid state drives)
(on page
Added inf
ormation on new software tools and solutions:
HP Insight Control Environment Suites
HP Smart Update Manager
(on page
Improved
firmware maintenance
(on page
Added new technology
Expanded existing information
Added new firmware update procedures for unsupported processor stepping
Introduction
75445
xx5 (June 2006)
The fifth edition of the
HP ProLiant Servers Troubleshooting Guide
, part number 375445
xx5, included the
following additions:
Added three new c
Class server blade flowcharts:
Class server blade power
on problems flowchart
(on page
Class server blade POST problems flowchart
(on page
Class server blade fault indications flowchart
(on page
Added new processor error codes:
Windows® Event Log processor error codes
(on page
Insight Diagnostics processor error codes
75445
xx4 (May 2006)
The fourth edition of the
HP ProLiant Servers Troubleshooting Guide
, part number 375445
xx4, included the
following additions:
Hot
plug
SAS and SATA hard drive
LED combinations
(on page
Operating system issues with Intel® dual
core processors (Hyper
Threading enabled)
(on page
Tape drive problems
(on page
New error messages in
ADU error messages
(on page
) and
POST error messages and beep codes
(on page
75445
xx3 (September 2005)
The third edition of the
HP ProLiant Servers Troubleshooting Guide
, part number 375445
xx3, included the
following changes:
Updated SCSI hard d
rive guidelines
Added
hot
plug SCSI hard drive LED combinations
(on page
Updated
diagnostic flowcharts
(on page
Added
operating system problems
(on page
Added
Port 85 codes and iLO messages
(on page
181
Added new error messages to ADU error messages and POST error mess
ages and beep codes
Updated contacting HP:
Contacting HP technical support or an authorized reseller
Server information you need
Getting
started
etting started
P ProLiant 100 Series Server troubleshooting
information
Use this guide for troubleshooting information on the HP ProLiant ML110 G7 Server and the HP ProLiant
DL120 G7 Server.
For troublesh
ooting information on HP ProLiant 100 Series Servers other than the HP ProLiant ML110 G7
Server and HP ProLiant DL120 G7 Server, see the respective server user guides.
ow to use this guide
NOTE:
For
common troubleshooting procedures, the term "server" is used to mean servers and
server blades.
This guide provides common procedures and solutions for the many levels of troubleshooting a ProLiant
server
from the most basic connector issues to complex
software configuration problems.
To understand the sections of this guide and to identify the best starting point for a problem, use the following
descriptions:
Common problem resolution
(on page
Many server problems are caused by loose connections, outdated firmware, and other issues. Use this
section to perform basic troubleshooting for common problems.
Diagnostic flowcharts
(on page
When a server exhibits symptoms that do not immediately pinpoint the problem, use this section to
begin troubleshooting. The section contains a series of flowcharts that provide a common
troublesh
ooting process for ProLiant servers. The flowcharts identify a diagnostic tool or a process to
help solve the problem.
Hardware problems
(on page
When the symptoms point to
a specific component, use this section to find solutions for problems with
power, general components, system boards, system open circuits and short circuits, and external
devices.
Software problems
(on page
When you have a known, specific software problem, use this section to identify a solution to the
problem.
Software tools and solutions
(on page
Use this section as a reference for software tools and utilities.
HP resources for troubleshooting
(on page
Getting
started
When additional information becomes necessary, use this section to identify websites and
supplemental documents that contain troubleshooting information.
Error messages
(on page
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.
Review the
important safety information
(on page
Gather
symptom information
(on page
Prepare the server for diagnosis
(on page
Use the
Start diagnosis flowchart
(on page
) to begin the diagnostic process.
mportant safety information
Familiarize yourself with the safety information in the following sections before troubleshooting the server.
Getting
started
This symbol indicates the presence of electric shock hazards. The area contains no user
or field serviceable parts. Do not open for any reason.
WARNING:
To reduce the risk of injury from electric shock hazards, do not open
this
enclosure.
This symbol on an RJ
45 receptacle indicates a network interface connection.
WARNING:
To reduce the risk of electric shock, fire, or damage to the equipment, do
not plug telephone or telecommunications connectors into this recepta
cle.
This symbol indicates the presence of a hot surface or hot component. If this surface is
contacted, the potential for injury exists.
WARNING:
To reduce the risk of injury from a hot component, allow the surface to
cool before touching.
weight in kg
weight in lb
This symbol indicates that the component exceeds the recommended weight for one
individual to handle safely.
WARNING:
To reduce the risk of personal injury or damage to the equipment,
observe local occupational health and saf
ety requirements and guidelines for manual
material handling.
These symbols, on power supplies or systems, indicate that the equipment is supplied
by multiple sources of power.
WARNING:
To reduce the risk of injury from electric shock, remove all
power cords
arnings and cautions
WARNING:
Only authorized technicians trained by HP should attempt to repair
this equipment.
All troubleshooting and repair procedures are detailed to allow only subassembly/module
level
repair. Because of the complexity of the individual boards and subassemblies, no one should
attempt to make repairs at the component level or to m
ake modifications to any printed wiring
board. Improper repairs can create a safety hazard.
WARNING:
To reduce the risk of personal injury or damage to the equipment, be sure that:
WARNING:
To reduce the risk of electric shock or damage to the equipment:
Do not disable the power cord grounding plug. The grounding plug is an important safety
feature.
Plug the power cord into a
grounded (earthed) electrical outlet that is easily accessible at all
times.
Unplug the power cord from the power supply to disconnect power to the equipment.
Do not route the power cord where it can be walked on or pinched by items placed against it.
Pay
particular attention to the plug, electrical outlet, and the point where the cord extends from
the server.
Getting
started
weight in kg
weight in lb
WARNING:
To reduce the risk of personal injury or damage to the equipment:
Observe local occupation health and
removal.
The server is unstable when not fastened to the rails.
When mounting the server in a rack, remove the power
supplies and any other
removable module to reduce the overall weight of the product.
CAUTION:
To properly ventilate the system, you must provide at least 7.6 cm (3.0 in) of
clearance at the front and back of the server.
CAUTION:
The server is designed to be electrically grounded (earthed). To ensure proper
operation, plug the AC power cord into a properly grounded AC outlet only.
lectrostatic discharge
reventing electrostatic discharge
Getting
started
ymptom information
Before troubleshooting a server problem, collect the following information:
What events preceded the failure? After which steps does the problem occur?
What has been changed since the time the server was working?
Did
you recently add or remove hardware or software? If so, did you remember to change the
Getting
started
erforming processor procedures in the troubleshooting process
Because this document supports multiple generations of HP ProLiant server models, it al
so covers processes
that include troubleshooting of various models and types of processors.
Before performing any troubleshooting steps that involve processors, review the following guidelines:
Be sure that only authorized personnel perform the troubleshoo
ting steps that involve installation,
removal, or replacement of a processor.
Always locate the documentation for your processor model before performing
any
steps that require
installing, removing, or replacing a processor. If you cannot locate the hard co
py of the instructions,
locate your server user guide or maintenance and service guide on the
HP website
http://www.hp.com/support/manuals
Some processor models require the use of a processor installation
tool, and specific steps are
documented to ensure that you do not damage the processor or processor socket on the system board.
Getting
started
lways use the recommended minimum configuration above before removing any processors. If you are
unable to isolate the issue with the configuration above, you will then remove all but one of the additional
processors.
CAUTION:
Before removing or repla
cing any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
Common problem
resolution
ommon problem resolution
oose connections
Action
Be sure all power cords are securely connected.
Be sure all cables are properly aligned and securely connected for all external and internal
components.
Remove and check all data and power cables for damage. Be sure no
cables have bent pins or
damaged connectors.
If a fixed cable tray is available for the server, be sure the cords and cables connected to the server are
routed correctly through the tray.
Be sure each device is properly seated. Avoid bending or flexing cir
cuit boards when reseating
components.
Common problem
resolution
IMM handling guidelines
CAUTION:
Failure to properly handle DIMMs can cause damage to DIMM
components and the
system board connector.
When handling a DIMM, observe the following guidelines:
Avoid
electrostatic discharge
(on page
Always hold DIMMs by the side edges only.
Avoid touching the connectors on the bottom of the DIMM.
Never wrap your fingers around a DIMM.
Avoid touching the components on the sides of the DIMM.
ever bend or flex the DIMM.
When installing a DIMM, observe the following guidelines:
Before seating the DIMM, align the DIMM with the slot.
To align and seat the DIMM, use two fingers to hold the DIMM along the side edges.
To seat the DIMM, use two finger
s to apply gentle pressure along the top of the DIMM.
For more information, see the
HP website
http://h20000.www2.hp.com/biz
support/TechSupport/Document.jsp?lang=en&cc=us&objectID=c008
68283&jumpid=reg_R1002_USEN
ard drive guidelines
AS and SATA hard drive guidelines
When adding hard drives to the server, observe the following general guidelines:
The system
automatically sets all drive numbers.
If only one hard drive is used, install it in the bay with the lowest drive number.
Drives must be the same capacity to provide the greatest storage space efficiency when drives are
grouped together into the same drive
array.
Drives in the same logical volume must be of the same type:
ACU does not support mixing SAS and SATA drives in the same logical volume.
ACU does not support mixing traditional drives and solid state drives (SSD) in the same logical
volume.
CSI hard drive guidelines
Each SCSI drive must have a unique ID.
Common problem
resolution
Drives must be the same capacity to provide the greatest storage space efficiency when drives are
grouped together into the same drive array.
ard drive LED combinations
plug SCSI hard drive LED combinations
Activity
LED (1)
Online
LED (2)
Fault LED
(3)
Interpretation
On, off, or
flashing
On or off
Flashing
A predictive failure alert has been received for this drive.
Replace the drive as soon as possible.
On, off, or
flashing
Off
The drive is online and is configured as part of an array.
If the array is configured for fault tolerance and all other drives in the
array are online, and a predictive failure alert is
received or a drive
capacity upgrade is in progress, you may replace the drive online.
On or
flashing
Flashing
Off
Do not remove the drive. Removing a drive may terminate the current
operation and cause data loss.
The drive is rebuilding or undergoing cap
acity expansion.
Off
Off
Do not remove the drive.
The drive is being accessed, but (1) it is not configured as part of an
array; (2) it is a replacement drive and rebuild has not yet started; or
(3) it is spinning up during the POST sequence.
Flashing
Flashing
Flashing
Do not remove the drive. Removing a drive may cause data loss in
non
fault
tolerant configurations.
One or more of the following conditions may exist:
The drive is part of an array being selected by an array
configuration utility
Drive I
dentification has been selected in HP
The drive firmware is being updated
Off
Off
The drive has been placed offline due to hard disk drive failure or
subsystem communication failure.
You may need to replace the drive.
Off
Off
Off
One or more of
the following conditions may exist:
The drive is not configured as part of an array
The drive is configured as part of an array, but it is a replacement
The drive is configured as an online spare
If the
drive is connected to an array controller, you may replace the
drive online.
AS and SATA hard drive LED combinations
NOTE:
Predictive failure alerts can occur only when the server is connected to a Smart Array
controller.
Common problem
resolution
Online/activity
LED (green)
Fault/UID LED
(amber/blue)
Interpretation
On, off, or flashing
Alternating amber
and blue
The drive has failed, or a predictive failure alert has been received
for this drive; it also has been selected by a management
application.
On, off, or flashing
Steadily blue
The drive is operating normally, and it has been selected by a
management application.
Amber, flashing
regularly (1 Hz)
A predictive failure alert has been received for this drive.
Replace the drive as soon as possible.
Off
The drive is online, but
it is not active currently.
Flashing regularly
(1 Hz)
Amber, flashing
regularly (1 Hz)
Do not remove the drive. Removing a drive may terminate the
current operation and cause data loss.
The drive is part of an array that is undergoing capacity expansion
or stripe migration, but a predictive failure alert has been received
for this drive. To minimize the risk of data loss, do not replace the
drive until the expansion or migration is complete.
Flashing regularly
(1 Hz)
Off
Do not remove the drive. Removing
a drive may terminate the
current operation and cause data loss.
The drive is rebuilding, erasing, or it is part of an array that is
undergoing capacity expansion or stripe migration.
Flashing irregularly
Amber, flashing
regularly (1 Hz)
The drive is
active, but a predictive failure alert has been received
for this drive. Replace the drive as soon as possible.
Flashing irregularly
Off
The drive is active, and it is operating normally.
Off
Steadily amber
A critical fault condition has been identified
for this drive, and the
controller has placed it offline. Replace the drive as soon as
possible.
Off
Amber, flashing
regularly (1 Hz)
A predictive failure alert has been received for this drive. Replace
the drive as soon as possible.
Off
Off
The drive is
offline, a spare, or not configured as part of an array.
erver updates with an HP Trusted Platform Module
and BitLocker™ enabled
When a TPM is installed and enabled in RBSU, and w
hen the Microsoft® Windows® BitLocker™ Drive
Encryption feature is enabled, always disable BitLocker™ before performing any of the following
procedures:
Restarting the computer for maintenance without a PIN or startup key
Updating firmware
(on page
Upgrading critical early boot components
Upgrading the system board to replace or remove the TPM
Disabling or clearing the TPM
Moving a BitLocker™
protected drive to another ser
ver
Adding an optional PCI device, such as a storage controller or network adapter
Diagnostic flowcharts
Diagnostic flowcharts
roubleshooting flowcharts
To effectively troubleshoot a problem, HP recommends that you start with the first flowchart in this section,
Start diagnosis flowchart
(on page
)," and follow the appropriate diagnostic path. If the other flowcharts
do not provide a troubleshooting solution, follow the diagnostic steps in "
General diagnosis flowchart
(on
page
)." The General diagnosis flowchart is a generic troubleshooting process to be used when the
problem is not server
specific or is not easily categorized into the other flowcharts.
The av
ailable flowcharts include:
Start diagnosis flowchart
(on page
General diagnosis flowchart
(on page
Power
on problems
Server power
on problems flowchart
(on page
Class
server blade power
on problems flowchart
(on page
Class server blade power
on problems flowchart
(on p
age
POST problems flowchart
(on page
Server and
Class
server blade POST problems flowchart
(on page
Class server blade POST problems flowchart
(on page
Operating system boot problems flowchart
(on page
Server fault indications flowchart
Server and
Class
server blade fault indications flowchart
(on page
Cla
ss server blade fault indications flowchart
(on page
roubleshooting flowchart reference websites
Each flowchart contains references to external websites. The following websites correspond to the numbered
websites in each flowchart:
HP Technical Support
http://www.hp.com/support
Select your country and then follow the instructions to locate software, firmware, and drivers.
HP ProLiant maintenance and service guides:
Business Support Center
http://www.hp.com/
go/bizsupport
Select
Manuals
. Under Servers, select
ProLiant and tc series servers
. Select the product, and then
locate the link for the maintenance and service guide.
HP BladeSystem
Class
Support and Documents
http://www.hp.com/products/servers/proliant
bl/p
class/info
Under Product support, select the product. Select
Manuals (guides, supplements, addendums, etc)
Under Service and maintenance information, locate the link for th
e maintenance and service guide.
Diagnostic flowcharts
HP BladeSystem c
Class Technical Documentation
http://www.hp.com/go/bladesystem/documentation
Select
Support, Drivers and Manuals
, and then select the product. Select
Manuals
, and then locate
the link for the maintenance and service guide.
HP BladeSystem
Class
Support and Documents
http://www.hp.com/product
s/servers/proliant
bl/p
class/info
To locate the
HP BladeSystem
Class
System Maintenance and Service Guide
, select the product.
Select
Manuals (guides, supplements, addendums, etc)
. Under Service and maintenance information,
locate the link for the docu
ment.
HP BladeSystem Power Sizer
http://www.hp.com/go/bladesystem/powercalculator
Diagnostic flowcharts
tart diagnosis flowchart
Use the following flowchart to start the diagnostic process.
eneral diagnosis flowchart
Diagnostic flowcharts
The General diagnosis flowchart provides a generic approach to troubleshooting. If you are unsure of the
problem, or if the other flowcharts do not fix the problem, use the following flowchart.
Diagnostic flowcharts
ower
on problems flowchart
erver power
on problems flowchart
Some servers have an internal health LED and an external health LED, while other servers have a single
system health LED.
The system health LED provides the same functionality as the two separate internal and
external health LEDs. Depending on the model, the internal health LED and external health LED may either
appear solid or they may flash. Both conditions represent the sa
me symptom.
For the location of server LEDs and information on their statuses, see the server documentation on the
HP
website
http://www.hp.com/support
Symptoms:
The server does not power on.
The system power LED
is off or amber.
The external health LED is red, flashing red, amber, or flashing amber.
The internal health LED is red, flashing red, amber, or flashing amber.
The system health LED is red, flashing red, amber, or flashing amber.
Possible causes:
Improper
ly seated or faulty power supply
Loose or faulty power cord
Power source problem
Improperly seated component or interlock problem
Diagnostic flowc
harts
Diagnostic flowcharts
Class server blade power
on problems flowchart
Class server blade power
on problems flowchart
For the location of server LEDs and information on their statuses, see the server documentation on the
HP
website
http://www.hp.com/support
Diagnostic flowcharts
Symptoms:
The server does
not power on.
The system power LED is off or amber.
The health LED is red or amber.
Possible causes:
Improperly seated or faulty power supply
Loose or faulty power cord
Power source problem
Improperly seated component or interlock problem
Diagnostic flowcharts
OST problems flowchart
Symptoms:
Diagnostic flowcharts
erver and
Class
server blade POST problems flowchart
Diagnostic flowcharts
Class server blade POST problems flowchart
perating system boot problems flowchart
Symptoms:
Server does not boot a previously installed OS
Server does not boot SmartStart
Possible causes:
Corrupted OS
Hard drive subsystem problem
Diagnostic flowcharts
Incorrect boot order setting in RBSU
There are two ways
to use SmartStart when diagnosing OS boot problems on a server blade:
Use iLO to remotely attach virtual devices to mount the SmartStart CD onto the server blade.
Use a local I/O cable and drive to connect to the server blade, and then restart the server b
lade.
Diagnostic flowcharts
erver fault indications flowchart
Symptoms:
Server boots, but a fault event is reported by Insight Management Agents
Server boots, but the internal health LED, external health LED, or component health LED
is red or amber
NOTE:
For the location of server LEDs and information on their statuses, refer to the server
documentation.
Possible causes:
Improperly seated or faulty internal or external component
Unsupported component installed
Redundancy
failure
System overtemperature condition
erver and
Class
server blade fault indications flowchart
Some servers have an internal health LED and an external health LED, while other servers have a single
system hea
lth LED. The system health LED provides the same functionality as the two separate internal and
external health LEDs. Depending on the model, the internal health LED and external health LED may either
appear solid or they may flash. Both conditions represe
nt the same symptom.
Diagnostic flowcharts
For the location of server LEDs and information on their statuses, see the server documentation on the
HP
website
http://www.hp.com/support
Diagnostic flowcharts
Class
server blade fault indications flowchart
Hardware problems
ardware problems
rocedures for all ProLiant servers
The procedures in this section are comprehensive and include steps about or references to hardware features
that may not be supported by the server you are
troubleshooting.
CAUTION:
Before removing or replacing any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
ower problems
ower source problems
Action
Press the Power On/Standby button to be sure it is on. If the server has a Power On/Standby button that
Hardware problems
If the power supplies have LEDs, be sure they indicate that each power supply is working properly. If
the LEDs indicate a problem with a power supply, replace the power supply. For more informat
ion, see
the server documentation on the
HP website
http://www.hp.com/support
Be sure the system has enough power, particularly if you recently added hardware, such as hard drives.
Additional power supplies may be
required. Check the system information from the IML.
For product
specific information, see the server documentation on the
HP website
http://www.hp.com/support
For more information, see the HP Power Advisor on t
he
HP website
http://www.hp.com/go/hppoweradvisor
If running a redundant configuration, be sure that all of the power supplies in the system are the same.
For a list of supported power supplies, see the
server documentation on the
HP website
http://www.hp.com/support
ystem open circuits and short circuits
Action
CAUTION:
Do not operate the server
for long periods with the access panel open or removed.
Operating the server in this manner results in improper airflow and improper cooling that can
lead to thermal damage.
Check the server LEDs to see if any statuses indicate the source of the proble
m. For LED information,
refer to the server documentation.
Remove all power sources to the server.
Be sure no
loose connections
(on page
) exist in the area.
Be sure each component in the area is working. Refer to the section for each component in this guide.
If you cannot determine the problem by checking the specific area, perform
each of the following actions.
Restart the server after each action to see if the problem has been corrected.
Reseat all I/O expansion boards.
Be sure no
loose connections
(on page
) exist in the rest of the server, particularly with the cables that
connect to the system board.
Hardware problems
Be sure the power cord is the corr
ect type for the UPS and the country in which the server is located. See
the UPS reference guide for specifications.
Be sure the line cord is connected.
Be sure each circuit breaker is in the On position, or replace the fuse if needed. If this occurs repea
tedly,
contact an authorized service provider.
Check the UPS LEDs to be sure a battery or site wiring problem has not occurred. See the UPS
documentation.
If the UPS sleep mode is initiated, disable sleep mode for proper operation. The UPS sleep mode can
e turned off through the configuration mode on the front panel.
Change the battery to be sure damage was not caused by excessive heat, particularly if a recent air
conditioning outage has occurred.
NOTE:
The optimal operating temperature for UPS batteries is 25°C (77°F). For approximately
every 8°C to 10°C (16°F to 18°F) average increase in ambient temperature above the optimal
temperature, battery life is reduced by 50 percent.
ow battery warning is displayed
Action
Plug the UPS into an AC grounded outlet for at least 24 hours to charge the batteries, and then test the
batteries. Replace the batter
ies if necessary.
Be sure the alarm is set appropriately by changing the amount of time given before a low battery
warning. Refer to the UPS documentation for instructions.
ne or more LEDs on the UPS is
red
Action
: Refer to the UPS documentation for instructions regarding the specific LED to determine the cause of
the error.
eneral hardware problems
roblems with new hardware
Action
Be sure the hardware being installed is a supported option on the server. For information on supported
hardware, see the server documentation.
If necessary, remove unsupported hardware.
To be sure the problem is not caused by a change to the hardware release, see the release notes
included with the hardware. If no documentation is available, see the
HP support website
http://www.hp.com/support
Hardware problems
Install
ation of a SCSI device without termination or without proper ID settings
Hardware problems
CAUTION:
Before removing or replacing any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Failu
re to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
If the system fails in this minimum configuration, one of the primary components has failed. If you
have already verified that the p
rocessor, PPM, power supply, and memory are working before
getting to this point, replace the system board. If not, be sure each of those components is working.
If the system boots and video is working, add each component back to the server one at a time,
restarting the server after each component is added to determine if that component is the cause of
the problem. When adding each component back to the server, be sure to disconnect power to the
server and follow the guidelines and cautionary information in
the server documentation.
hird
party device problems
Action
Refer to the server and operating system documentation to be sure the server and operating system
support the device.
Be sure the latest device drivers are installed.
Refer to the device documentation to be sure the device is properly installed. For example, a third
party
PCI or PCI
X board may be required to be installed on the primary PCI or PCI
X bus, respectively.
esting the device
Action
Uninstall the device.
If the server works with the device removed and uninstalled, a problem exists with the device, the server
does not support the device, or a conflict exists with another d
evice.
If the device is the only device on a bus, be sure the bus works by installing a different device on the bus.
Clearing NVRAM can resolve various problems. Clear the NVRAM, but do not use t
he backup .SCI file
if prompted. Have available any .CFG, .OVL, or .PCF files that are required.
Hardware problems
nternal system problems
attery pack problems
he battery stops charging or begins to swell
The batteries in BBWC battery packs are a consumable material. After 3 years of service, batteries may not
provide predictable data retention times. If a battery fails completely, the HP Smart Array
controller detects
this condition and automatically restricts write cache functions to protect user data. To help ensure
uninterrupted performance levels, HP recommends replacing battery packs at 3
year intervals.
In NiMH batteries, the charging and discha
rging processes create and recombine inert gases, which can
cause the button cell to swell in size by as much as 20%. Battery packs are designed to stop charging before
excess swelling occurs.
However, if excess swelling does occur, a pressure mechanism wi
thin the button cell releases these non
toxic,
non
corrosive gases before the cell incurs physical damage. If this pressure release occurs, the battery no
longer charges properly, and the storage solution reports a failed battery.
ROM and DVD drive problems
ystem does not boot from the drive
Action
Be sure the drive boot
Hardware problems
Hardware problems
Hardware problems
Be sure no
loose connections
(on page
) exist.
Be sure no device conflict exists.
Be sure the hard drive is cabled properly and terminated if necessary.
Be sure
the hard drive data cable is working by replacing it with a known functional cable.
Be sure the access panel is installed properly when the server is operating. Drives may overheat and
cause sluggish response or drive failure.
Run
Insight Diagnostics
HP Insight Diagnostics
" on page
) and replace failed components as
indicated.
Run
RBSU
HP ROM
Based Setup Utility
" on page
) to verify that the boot controller order is set
properly.
o hard drives are recognized
Action
Be sure no
power problems
(on page
) exist.
Check for
loose connections
(on page
Be sure that the controller supports the hard drives being installed.
Be sure the controller has the most recent firmware.
If the controller supports license keys and the configuration is dual do
main, be sure the license key is
installed.
ard drive is not recognized by the server
Action
Check the hard drive LEDs to be sure they indicate normal function. For information on ha
rd drive LEDs,
hard drive LED combinations
(on page
). For server
specific hard drive LED information, see the
server documentation or the
HP website
http://www.hp.com
Be sure no
loose connections
(on page
) exist.
Be sure the correct drive controller drivers are installed.
Be sure the hard drive is configured properly:
To determine the proper configuration, see the hard drive documentat
ion.
Remove the hard drive and be sure the configuration jumpers are set properly.
For a non
hot
plug hard drive, be sure a conflict does not exist with another hard drive. Check for
SCSI ID conflicts.
When using an array controller, be sure the hard drive
is configured in an array. Run
ACU
Array
Configuration Utility
" on page
new hard drive is not recognized
Action
Hardware problems
Be sure the drive bay is not defective by installing the hard drive in another bay.
Run
HP Insight Diagnostics
(on page
). Then, replace failed components as indicated.
When the drive is a replacement drive on an array controller, be sure that the drive is the same type and
of the same or larger capacity than the original drive.
ata is inaccessible
Action
Be sure the files are not corrupt. Run the repair utility for the operating system.
Be sure no viruses exist on t
he server. Run a current version of a virus scan utility.
When a TPM is installed and is being used with BitLocker™, be sure the TPM is enabled in
RBSU
HP
ROM
Based Setup Utility
" on page
). See the TPM replacement recovery procedure in the operating
system documentation.
When migrating encrypted data to a new server, be sure to follow the recovery procedures in the
operating system documentation.
erver response time is slower than usual
Action
Be sure the hard drive is not full. If needed, increase the amount of free space on the hard drive. HP
recommends that hard drives have a minimum of 15 percent
free space.
Review information about the operating system encryption technology, which can cause a decrease in
server performance. For more information, see the operating system documentation.
D card problems
ystem does not
boot from the drive
Action
Hardware problems
an problems
eneral fan problems are occurring
Acti
Be sure the fans are properly seated and working.
Follow the procedures and warnings in the server documentation for removing the access panels
and accessing and replacing fans.
Unseat, and then reseat, each fan according to the proper procedures.
Repl
ace the access panels, and then attempt to restart the server.
Be sure no
POST error messages
POST error messages and beep codes
" on page
123
) are displayed.
Be sure hot
Hardware problems
ll fans in an HP ProLiant G6 server are not spinning or are not spinning at the same
speed
Action:
For all servers, access the IML. If no error messages are listed, then the fans are operating as designed. If an
error message is listed in the IML, then perform the suggested procedure to correct the error.
For all server blades, access more information from the Onboard Administrator or iLO 3.
P Trusted Platform Module problems
Action
: If the TPM fails and is no longer detected by RBSU, request a new system board and TPM board from
an
HP authorized service provider
Contacting HP technical support or an authorized res
eller
" on page
).
CAUTION:
Any attempt to remove an installed TPM from the system board breaks or disfigures
the TPM security rivet. Upon locating a broken or disfigu
red rivet on an installed TPM,
administrators should consider the system compromised and take appropriate measures to ensure
the integrity of the system data.
When installing or replacing a TPM, observe the following guidelines:
Do not remove an
installed TPM. Once installed, the TPM becomes a permanent part of the system
board.
When installing or replacing hardware, HP service providers cannot enable the TPM or the encryption
technology. For security reasons, only the customer can enable these fe
atures.
Hardware problems
If you are unsure which DIMM has failed, test each bank of DIMMs by removing all other DIMMs.
Then, isolate the failed DIMM by switching each DIMM in a bank with a known working DIMM.
Remove any third
party memo
ry.
To test the memory, run
HP Insight Diagnostics
(on page
erver is out of memory
Action
Be sure the memory is configured properly. Refer to the application documentation to determine the
memory configura
tion requirements.
Be sure no operating system errors are indicated.
Be sure a
memory count error
Memory count error exists
" on page
) did not occur. Refer to the
message displaying memory count during POST.
emory count error exists
Possible Cause
: The memory modules are not installed correctly.
Action
Be sure the memory modules are supported by the server. See the server documentation.
Be sure the memory modules have been installed correctly in a supported configuration. See the server
documentation.
Be sure the memory modules are seated properly
DIMM handling guidelines
" on page
Be sure no operating system errors are indicated.
Restart the server and check to see if the error message is still
displayed.
Run
HP Insight Diagnostics
(on page
). Then, replace failed components as indicated.
erver fails to
recognize existing memory
Action
Reseat the memory.
Use care when handling DIMMs
DIMM handling guidelines
" on page
Be sure the memory is configu
red properly. See the server documentation.
Be sure a memory count error did not occur
Memory count error exists
" on page
). See the message
displaying memory count during POST.
erver fails to recognize new memory
Action
Be sure the memory is the correct type for the server and is install
ed according to the server
requirements. See the server documentation or
HP website
http://www.hp.com
Be sure you have not exceeded the memory limits of the server or operating system. See the server
documentation.
Be sur
e no Event List error messages are displayed in the
IML
Integrated Management Log
" on page
Be sure the memory is seated properly
DIMM handling guidelines
" on page
Be sure no conflicts are occurring with existing memory. Run the server setup utility.
Hardware problems
Test the memory by installing the memory into a known working server. Be s
If applicable, check the PPM
LEDs to identify if a PPM failure occurred. For information on LEDs, refer to
the server documentation.
Reseat each PPM, and then restart the server.
If reseating the PPMs is not effective, remove all but one PPM, restart the server to see if the PPM is
working, and then install each PPM individually, cycling power each time. Follow the warnings and
cautionary information in the server documentation.
Hardware problems
rocessor problems
Action
If applicable, check the processor LEDs to identify if a PPM failure occurred. For LED information, see the
server
documentation.
Be sure each processor is supported by the server and is installed properly. For processor requirements,
see the server documentation.
Be sure the server ROM is current.
CAUTION:
Before removing or replacing any processors, be sure to follow the guidelines
provided in "
Performing processor procedures
in the troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
If the server has only one processor installed, replace it with a known functional processor. If the
problem is resolved after you restart the server, the original processor failed.
CAUTION:
Before removing or replacing any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Failu
re to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
If the server has multiple processors installed, test each processor:
Remove all but one processor from the server. Replace each wit
h a processor terminator board or
blank, if applicable to the server.
If the server includes PPMs that are not integrated on the system board, remove all PPMs from the
server except for the PPM associated with the remaining processor.
Replace the remaining
processor with a known functional processor. If the problem is resolved after
you restart the server, a fault exists with one or more of the original processors. Install each
processor and its associated PPM (if applicable) one by one, restarting each tim
e, to find the faulty
processor or processors. At each step, be sure the server supports the processor configurations.
ape drive problems
The following sections include the most common tape drive issues.
Actions are listed in the order that they
Hardware
problems
To download HP StorageWorks Library and Tape Tools, see the
HP website
http://www.hp.com/support/tapetools
For more information about common tasks, see the
HP website
http://www.hp.com/support/lttfaq
tuck tape issue
Action:
Manually press the Eject button. Allow up to 10 minutes for the tape t
o rewind and eject.
Perform a forced eject:
Press and hold the Eject button for at least 10 seconds.
Allow up to 10 minutes for the tape to rewind and eject. The green Ready LED should flash.
Power cycle the drive. Allow up to 10 minutes for the drive to b
ecome ready again.
Check for conflicts in backup software services.
Check the SCSI/HBA/Driver configuration of the drive.
Inspect media and cables, and discard any that are faulty or damaged.
Contact HP support
Contacting HP tec
hnical support or an authorized reseller
" on page
187
ead/write issue
Action:
Run the Drive Assessment Test in HP StorageWorks Library
and Tape Tools.
CAUTION:
Running the Drive Assessment Test overwrites the tape. If it is not possible to overwrite
the tape, run the logs
based Device Analysis Test instead.
Run the Media Assessment Test in HP StorageWorks Library and Tape Tools.
This is a read
only test.
ackup issue
Action:
Run the Drive Assessment Test in HP StorageWorks Library and Tape Tools.
CAUTION:
Running the Drive Assessment Test overwrites the tape. If it is not possible to overwrite
the tape, run the logs
based Device Analysis Test instead.
Check the backup logs.
Verify that a supported configuration is being used.
Check for media damage:
Incorrect label placement
Broken, missing, or loose leader pin
Damaged cartridge seam
Usage in
incorrect environment
Check for software issues:
Check the backup software.
Check that virus scanning software is not scheduled to run at the same time as the back
up.
Verify that a tape can be formatted.
Hardware problems
edia issue
Action:
Verify that the correct media part number is being used.
Pull a support ticket using HP StorageWorks Library and Tape Tools.
Look for issues in the cartridge health section.
Look for issues in the drive health section.
Run the Media Assessment Test in HP
StorageWorks Library and Tape Tools.
Check for media damage:
Incorrect label placement
Broken, missing, or loose leader pin
Damaged cartridge seam
Usage in incorrect environment
Check if the Tape Error LED is flashing:
Reload the suspect tape. If the Tape
Error LED stops flashing, the problem has cleared.
Load a new or known good tape. If the Tape Error LED stops flashing, the problem has cleared.
Reload the suspect tape. If the Tape Error LED flashes, discard the suspect media as faulty.
Discard any media
that has been used at temperatures greater than 45°C (113ºF) or less than 5ºC
(41ºF).
raphics and video adapter problems
eneral graphics and video adapter problems are occurring
Action:
Use only cards listed as a supported option for the server. For a complete list of supported options, see
the server documentation on the
HP website
http://www.hp.com/support
Be sure that the power supplies installed in the server provide adequate power to support the server
configuration. Some high
power graphics adapters require specific cabling, fans, or auxiliary power.
For more information about adapter power requirements, see the documentation that ships with the
graphics option or see the vendor website. For more infor
mation about server power capabilities, see
the server documentation on the
HP website
http://www.hp.com/support
Be sure the adapter is seated properly.
xternal device problems
ideo problems
creen is blank for more than 60 seconds after you power up the server
Action
Hardware problems
Be sure the monitor power cord is plugged into a working grounded
(earthed) AC outlet.
Power up the monitor and be sure the monitor light is on, indicating that the monitor is receiving power.
Be sure the monitor is cabled to the intended server or KVM connection.
Be sure no
loose connections
(on page
) exist.
For rack
Press any
key, or enter the password, and wait a few moments for the screen to activate to be sure the
power
on password feature is not in effect. You can also tell if the power
on password is enabled if a
Hardware problems
ouse and keyboard problems
Action
Be sure no
loose connections
(on page
) exist. If a KVM switching device is in use, be sure the server
is properly connected to the switch.
For rack
mounted servers, check the cables to the switch box and be sure
Hardware problems
able
problems
Action
: If the local I/O cable does not have hot
plug functionality, be sure you are not using a PS/2 keyboard
or mouse. With a PS/2 keyboard or mouse, the local I/O cable cannot be connected as a hot
plug device.
Connect the local I/O cable before booting the server, or switch to USB devices (if supported) to use the local
I/O cable hot
plug functionality.
odem problems
o dial tone exists
Actio
Be sure the cables are plugged in as specified in the modem documentation.
Connect a working telephone directly to the wall jack, and then test the line for a dial tone.
If no dial tone is detected, the phone line is not working. Contact the local
telephone company and
arrange to correct the problem.
o response occurs when you type AT commands
Action
: Reconfigure the COM port address for the modem.
Hardware problems
Hardware problems
Hardware problems
Software problems
oftware problems
The best sources of information for software problems are the operating system and application software
documentation, which may also point to fault detection tools that report errors and preserve the system
con
figuration.
Other useful resources include
HP Insight Diagnostics
(on page
) and HP SIM. Use either utility to gather
critical system hardware and software information and to
help with problem diagnosis.
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.
Refer to "
Software tools and solutions
(on page
)" for more information.
perating
system problems and resolutions
perating system problems
perating system locks up
Action
: Scan for viruses with an updated virus scan utility.
eneral protection fault occurs
A general protection fault, or general protection error, occurs when the Microsoft operating system
terminates suddenly with an error, including but not limited to:
Miscalculating the amount of RAM needed for an
allocation
Transferring execution to a segment that is not executable
Writing to a read
only or a code segment
Loading a bad value into a segment register
Using a null pointer
A GPF is immediately identifiable by a blue screen with white text, and the text
may contain information that
identifies the problem.
Action
Remove any newly installed software or hardware to verify that they are not the cause.
Boot the server in Safe Mode or Last Known Good Configuration.
If neither of these actions resolve the pro
blem,
contact an authorized service provider
Contacting HP
technical support or an authorized reseller
" on page
187
). For more information about d
ebugging tools or
specific GPF messages, refer to the
Microsoft website
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
Software problems
rrors are displayed in the error log
Action
: Follow the information provided in the error log, and then refer to the operating system
documentation.
roblems occur after the installation of
a service pack
Action
: Follow the
instructions for updating the operating system
Operating system updates
" on page
uring installation of Oracle Solaris, the system locks up or a panic error occurs
Action
: Disable ACPI support in Oracle Solaris. For more information on how to disable ACPI, see the
Oracle
website
http://www.oracle.com
perating system issues with Intel® dual
core processors (Hyper
Threading enabled)
Some versions of Microsoft® Windows® and distributions of Linux may hang during OS
installation, fail to
complete OS installation, or fail to boot after installation on servers with either three or four Intel® dual
core
processors installed.
Action:
Microsoft® Windows Server™ 2003
based media
System may hang during installation or durin
g boot. Windows Server™ 2003 SP1 Slipstream does not
exhibit this issue.
If SP1 Slipstream media is not available, the base media installation can be performed using one of the
following methods:
Install the OS with only one or two processor(s)
Disable
Hyper
Threading in RBSU, then apply SP1 before adding the additional processor(s) and
enabling Hyper
Threading
Linux distributions
Additional information and the appropriate solutions for the Linux distributions (if any) can be found at
the
HP website
http://h18004.www1.hp.com/products/servers/linux/processor
notes.html
perating system updates
Use care when applying operating system updates (Service Packs, hotfixes, and patches). Before updating
the operating system, read the release notes for each update. If you do not require sp
ecific fixes from the
update, it is recommended that you do
not
apply the updates. Some updates overwrite files specific to HP.
If you decide to apply an operating system update:
Perform a full system backup.
Apply the operating system update, using the in
structions provided.
Install the current drivers.
If you apply the update and have problems, locate files to correct the problems on the
HP website
http://www.hp.com/support
Software problems
estoring to a backed
up version
If you recently upgraded the operating system or software and cannot resolve the problem, you can try
restoring a previously saved version of the system. Before restoring the backup, make a backup of the current
Be sure the server has adequate resources (processor speed, hard drive space, and memory) for the
software.
Be sure the server ROM is current and the configuration is correct.
Be sur
e you have printed records of all troubleshooting information you have collected to this point.
Be sure you have two good backups before you start. Test the backups using a backup utility.
Check the operating system and application software resources to be
sure you have the latest
information.
If the last
known functioning configuration does not work, try to recover the system with operating
system recovery software:
Microsoft® operating systems:
Windows Server® 2003
Software problems
IBM OS/2
Power u
from the server setup utility and manually set the software switches. Refer to the application
documentation, the vendor website, or both.
Check for overwritten files. Refer to the application documentation to find out which files are
added by
the application.
Reinstall the application.
Be sure you have the most current drivers.
Software problems
OM problems
emote ROM flash problems
eneral remote ROM flash problems are occurring
Action
: Be sure you follow these requirements for using the Remote ROM flash utility:
A local administrative client system that is running the Microsoft® Windows NT® 4.0,
Windows®
2000, o
r Windows
Server™ 2003 operating system
One or more remote servers with system ROMs requiring upgrade
An administrative user account on each target system. The administrative account must have the same
username and password as the local administrative clie
nt system.
for the target comput
er, and then restart the process. Be sure the remote registry service is running on a
Windows®
based system.
nvalid or incorrect command
Software problems
ailure occurs during ROM flash
Software problems
Remove the access panel.
Change positions 1, 5, and 6 of the system maintenance switch to on.
Install the access panel.
Install the server into the rack.
Power up the server.
After the system
beeps, repeat steps 1 through 3.
Change positions 1, 5, and 6 of system maintenance switch to off.
Repeat steps 5 and 6.
If both the current and backup versions of the ROM are corrupt, return the system board for a service
replacement.
To switch to the bac
kup ROM when the System ROM is not corrupt, use
RBSU
HP ROM
Based Setup Utility
on page
).
Server blades
If the system ROM is corrupted, the syst
em automatically switches to the redundant ROM in most cases. If the
system does not automatically switch to the redundant ROM, perform the following steps:
Power down the server.
Remove the server.
Remove the access panel.
Change positions 1, 5, and 6 of
the system maintenance switch to on.
Install the access panel.
Install the server in the enclosure and power up the server.
After the system beeps, repeat steps 1 through 3.
Change positions 1, 5, and 6 of system maintenance switch to off.
Repeat steps 5
and 6.
If both the current and backup versions of the ROM are corrupt, return the system board for a service
replacement.
To switch to the backup ROM when the System ROM is not corrupt, use
RBSU
HP ROM
Based Setup Utility
on pag
).
Software tools
and solutions
oftware tools and solutions
onfiguration tools
martStart software
Sma
rtStart is a collection of software that optimizes single
Software tools
and solutions
Displaying system information
Selecting the primary boot controller
Configuring memory options
Language selection
For more information on RBSU, see the
HP R
OM
Based Setup Utility User Guide
on the Documentation CD or
the
HP website
http://www.hp.com/support/smartstart/documentation
sing RBSU
To use
RBSU, use the following keys:
To access RBSU, press the
key during power
up when prompted.
To navigate the menu system, use the arrow keys.
To make selections, press the
Enter
key.
To access Help for a highlighted configuration option, press the
key
IMPORTANT:
Default configuration settings are applied to the server at one of the following times:
Upon the first system power
After defaults have been restored
Default configuration settings are sufficient for proper typical server operation, but
configuration settings can
be modified using RBSU. The system will prompt you for access to RBSU with each power
up.
uto
configuration process
The auto
configuration process automatically runs when you boot the server for
the first time. During the
power
up sequence, the system ROM automatically configures the entire system without needing any
intervention. During this process, the ORCA utility, in most cases, automatically configures the array to a
default setting based o
n the number of drives connected to the server.
NOTE:
The server may not support all the following examples.
NOTE:
If the boot drive is not empty or has been written to in the past, ORCA does not
automatically configure the array. You must run ORCA to configure the array settings.
Drives installed
Drives used
RAID level
RAID 0
RAID 1
3, 4, 5, or 6
3, 4, 5, or 6
RAID 5
More than 6
None
To change any ORCA default settings and override the auto
configuration process, press the
key when
prompted.
Software tools
and solutions
By default, the auto
configuration process configures the system for the English language. To change any
default settings in the auto
Software tools
and solutions
rray Configuration Utility
ACU is a browser
based utility with the following features:
Runs as a local application or remote service
Supports
online array capacity expansion, logical drive extension, assignment of online spares, and
RAID or stripe size migration
Suggests the optimum configuration for an unconfigured system
Provides different operating modes, enabling faster configuration or grea
ter control over the
configuration options
Remains available any time that the server is on
Displays on
screen tips for individual steps of a configuration procedure
Beginning with ACU version 8.28.13.0, provides diagnostic functionality on the Diagnostics
(formerly known as Array Diagnostics Utility).
For optimum performance, the minimum display settings are 1024 × 768 resolution and 16
bit color. Servers
running Microsoft® operating systems require one of the following supported browsers:
Internet
Explorer 6.0 or later
Mozilla Firefox 2.0 or later
For Linux servers, see the README.TXT file for additional browser and support information.
For more information about the controller and its features, see the
HP Smart Array Controllers for HP ProLiant
Ser
vers User Guide
on the
HP website
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01608507/c01608507.pdf
). To
configure arrays, see the
nfiguring Arrays on HP Smart Array Controllers Reference Guide
on the
HP
website
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c00729
544/c00729544.pdf
iagnostics tasks
The ACU Diagnostics feature replaces the Array Diagnostic Utility supported by SmartStart v8.20 and
earlier. For each controller, or for all of them, you can selec
t the following tasks:
View Diagnostic Report
ACU generates and displays the diagnostic report.
Generate Diagnostic Report
ACU generates a report without the graphical display.
For either task, you can save the report. In the SmartStart environment, you ca
n save the report to a formatted
diskette or USB device. In online and offline environments, ACU saves the diagnostic report to a compressed
folder, which contains an XML report, a plain text report, and a viewer file so you can display and navigate
the re
port through a web browser.
Each ACU Diagnostics report contains a consolidated view of any error or warning conditions encountered.
It also provides detailed information for every storage device, including the following:
Device status
Configuration flags
Firmware version numbers
Physical drive error logs
Software tools
and solutions
ACU Diagnostics never collects information about the data content of logical drives. The diagnostic report
does not collect or include the following:
File system types, contents, or status
Partition types,
sizes, or layout
Software RAID information
Operating system device names or mount points
ption ROM Configuration for Arrays
Before installing an operating
system, you can use the ORCA utility to create the first logical drive, assign
RAID levels, and establish online spare configurations.
The utility also provides support for the following functions:
Reconfiguring one or more logical drives
Viewing the curre
nt logical drive configuration
Deleting a logical drive configuration
Setting the controller to be the boot controller
Selecting the boot volume
If you do not use the utility, ORCA will default to the standard configuration.
For more information regarding the default configurations that ORCA uses, see the
HP ROM
Based Setup
Utility User Guide
on the Documentation CD.
For more information about the controller and its features, see the
HP Smart Array Controllers for HP ProLiant
Servers User Guide
on the
HP website
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01608507/c01608507.pdf
). To
configure arrays, see th
Configuring Arrays on HP Smart Array Controllers Reference Guide
on the
HP
website
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c00729
544/c00729544.pdf
entering the serial number and product ID
When re
entering the serial number and product ID on an HP ProLiant G4 or G5 server, use the
following procedure:
After you replace the system board, you must re
enter th
e server serial number and the product ID.
During the server startup sequence, press the
F9
key to access RBSU.
Select the
System Options
menu.
Select
Serial Number
. The following warning is displayed:
WARNING! WARNING! WARNING! The serial number is loaded
into the system during
the manufacturing process and should NOT be modified. This option should only
be used by qualified service personnel. This value should always match the
Press the
Enter
key to clear the
warning.
Enter the serial number and press the
Enter
key.
Select
Product ID
Software tools
and solutions
Enter the product ID and press the
Enter
key.
Press the
Esc
key to close the menu.
Press the
Esc
key to exit RBSU.
Press the
F10
key to confirm exiting RBSU. The server will autom
atically reboot.
When re
entering the serial number and product ID on an HP ProLiant G6 server or later, use the
following procedure:
After you replace the system board, you must re
enter the server serial number and the product ID.
During the server
startup sequence, press the
F9
key to access RBSU.
Select the
Advanced Options
menu.
Select
Service Options
Select
Serial Number
. The following warnings appear:
WARNING! WARNING! WARNING! The serial number is loaded into the system during
manufacturing process and should NOT be modified. This option should only
be used by qualified service personnel. This value should always match the
Warning: The serial number should ONLY be modified by qualifi
ed personnel.
Press the
Enter
key to clear the warning.
Enter the serial number and press the
Enter
key.
Select
Product ID
. The following warning appears:
Warning: The Product ID shou
ld ONLY be modified by qualified personnel. This
Enter the product ID and press the
Enter
key.
Press the
Esc
key to close the menu.
Press the
Esc
key to exit RBSU.
Press the
F10
key to confirm exitin
g RBSU. The server automatically reboots.
anagement tools
utomatic Server Recovery
ASR is a feature that causes
the system to restart when a catastrophic operating system error occurs, such as
a blue screen, ABEND (does not apply to HP ProLiant DL980 Servers), or panic. A system fail
safe timer, the
ASR timer, starts when the System Management driver, also known as
the Health Driver, is loaded. When the
Software tools
and solutions
OMPaq utility
The ROMPaq utility enables you to upgrade the system firmware (BIOS). To upgrade the firmware, insert a
ROMPaq USB Key into an available USB port and boot the system. In addition to ROMPa
q, Online Flash
Components for Windows and Linux operating systems are available for updating the system firmware.
The ROMPaq utility checks the system and provides a choice (if more than one exists) of available firmware
revisions.
For more information, see the Download drivers and software page for the server. To access the
server
specific page, enter the following web address into the browser:
http://www.hp.com/support/
servernameser;&#x-15v;Nr-;n-3;
-2m;&#x-4e-;ሀ
For example:
http://www.hp.com/support/dl360g6
LO and iLO 2 technology
The iLO subsystem is a standard component of selected ProLiant servers that provides server health and
remote server manageability. The iLO or iLO 2 subsystem inclu
des an intelligent microprocessor, secure
Software tools
and solutio
ns
Use the shared iLO 3 Remote Co
nsole to collaborate with up to six server administrators.
Remotely mount high
performance Virtual Media devices to the server.
Securely and remotely control the power state of the managed server.
Send alerts from iLO 3 regardless of the state of the host
server.
Access advanced troubleshooting features through the iLO 3 interface.
For more information about iLO 3 features (which may require an iLO Advanced Pack or iLO Advanced for
BladeSystem license), see the iLO 3 documentation on the Documentation CD or
on the
HP website
http://www.hp.com/go/ilo
rase Utility
CAUTION:
Perform a backup before running the System Erase Utility. The utility sets the system
to its original factory state, deletes the current hardware configuration information, including
array setup and disk partitioning, and erases all connected hard drives
Run the Erase Utility if you must erase the system for the following reasons:
You want to install a new operating system on a server with an existing operating system.
You encounter an error
when completing the steps of a factory
installed operating system installation.
To access the Erase Utility, use the System Erase button on the home screen of the
SmartStart CD
SmartStart
software
" on page
edundant ROM support
The server
enables you to upgrade or configure the ROM safely with redundant ROM support. The server has
a single ROM that acts as two separate ROM images. In the standard implementation, one side of the ROM
contains the current ROM program version, while the other
side of the ROM contains a backup version.
NOTE:
The server ships with the same version programmed on each side of the ROM.
Software tools
and solutions
POST
RBSU
Diagnostics
DOS
Operating environments which do not provide native USB support
iagnostic tools
P Insight
Diagnostics
HP Insight Diagnostics is a proactive server management tool, available in both offline and online versions,
that provides diagnostics and troubleshooting capabilities to assist IT administrators who verify server
installations, troubleshoot pr
oblems, and perform repair validation.
HP Insight Diagnostics Offline Edition performs various in
depth system and component testing while the OS
is not running. To run this utility, launch the SmartStart CD.
HP Insight Diagnostics Online Edition is a web
based application that captures system configuration and
other related data needed for effective server management. Available in Microsoft® Windows® and Linux
versions, the utility helps to ensure proper system operation.
For more information or to downloa
d the utility, refer to the
HP website
http://www.hp.com/servers/diags
mart Array SCSI Diagnosis feature
NOTE:
This feature is only available in HP Insight Diagnostics Online Edition.
The
HP Insight Diagnostics Online Edition
HP Insight
Diagnostics
" on page
) provides the capability to
use non
intrusive system level checks to diagnose Smart Array SCSI hard drives. Diagnosis supports SCSI,
SATA, and SAS hard d
rives that are attached to a Smart Array controller and configured as part of a logical
volume. Diagnosis is
not
component testing, but is a combination of drive history and controller error status.
Diagnosis assists in confirming hardware status and is fa
ster than offline testing. Using the diagnosis feature
reduces downtime and provides information on one pass.
The diagnosis feature should be used:
To troubleshoot why a hard drive is in a particular state.
When HP SIM reports a hard drive pre
failure or
that a hard drive has failed.
When data corruption or storage problems occur, but no physical indications are evident.
When conflicting errors exist.
When repeated failures occur.
P Insight Diagnostics survey functionality
HP Insight Diagnostics
(on page
) provides survey functionality that gathers critical hardware and s
oftware
information on ProLiant servers.
Software tools
and solutions
This functionality supports operating systems that may not be supported by the server. For operating systems
supported by the server, see the
HP website
http://www.hp.co
m/go/supportos
If a significant change occurs between data
gathering intervals, the survey function marks the previous
information and overwrites the survey data files to reflect the latest changes in the configuration.
Survey functionality is installed
with every SmartStart
assisted HP Insight Diagnostics installation, or it can be
installed through the
HP PSP
ProLiant Support Packs
" on page
NOTE:
The current version of SmartStart provides the memory spare part numbers for the server.
To download the latest version, see the
HP website
http://www.hp.com/support
ntegrated Management Log
The IML records hundreds of events and stores them in an easy
view form. The IML timestamps each event
with 1
minute gr
anularity.
You can view recorded events in the IML in several ways, including the following:
From within HP SIM
From within Survey Utility
From within operating system
specific IML viewers
Software tools
and solutions
emote support and analysis tools
P Insight Remote Support software
HP strongly recommends that you install HP Insight Remote Support software to complete the installation or
upgrade of your product and to enable enhanced delivery of your HP Warranty, HP Care Pac
k Service, or
HP contractual support agreement. HP Insight Remote Support supplements your monitoring 24 x 7 to ensure
maximum system availability by providing intelligent event diagnosis, and automatic, secure submission of
hardware event notifications to
HP, which will initiate a fast and accurate resolution, based on your product’s
service level. Notifications may be sent to your authorized HP Channel Partner for on
site service, if
configured and available in your country. The software is available in t
wo variants:
HP Insight Remote Support Standard: This software supports server and storage devices and is
optimized for environments with 1
50 servers. Ideal for customers who can benefit from proactive
notification but do not need proactive service delive
ry and integration with a management platform.
HP Insight Remote Support Advanced: This software provides comprehensive remote monitoring and
proactive service support for nearly all HP servers, storage, network, and SAN environments, plus
selected non
HP
servers that have a support obligation with HP. It is integrated with HP Systems Insight
Manager. A dedicated server is recommended to host both HP Systems Insight Manager and HP Insight
Remote Support Advanced.
Details for both versions are available on t
he
HP website
http://www.hp.com/go/insightremotesupport
To download the software, go to
Software Depot
http://www.software.hp.com
Select
Insight Remote S
upport
from the menu on the right.
eeping the system current
rivers
IMPORTANT:
Always perform a backup before installing or updating device drivers.
The server
includes new hardware that may not have driver support on all OS installation media.
If you are installing a SmartStart
supported OS, use the
SmartStart software
(on page
and its Assisted
Path feature to install the OS and latest driver support.
If you are installing drivers from the SmartStart CD, be sure that you are using the latest SmartStart version
that your server supports. To verify that your server is using the la
test supported version, see the
HP website
http://www.hp.com/support
). For more information, see the documentation provided with the SmartStart
CD.
If you do not use the SmartStart CD to install an OS, drivers for s
ome of the new hardware are required.
These drivers, as well as other option drivers, ROM images, and value
add software can be downloaded
from the
HP website
http://www.hp.com/support
To directly locate the OS dr
ivers for a particular server, enter the following web address into the browser:
http://www.hp.com/support/
servername
In place of
servernamser;&#x-3v4;r-3;&#xn-3a;&#x-2m-;一e
, enter the server name.
Software tools
and solutions
For example:
http://www.hp.com/support/dl360g6
http://www.hp.com/support/dl360g6
ersion control
The VCRM and VCA are Web
enabled Insight Management Agents tools that HP SIM uses to facilitate and
schedule
software update tasks to the entire enterprise.
VCRM manages the repository for Windows and Linux PSPs as well as online firmware. Administrators
can browse a graphical view of the PSPs or configure VCRM to automatically update the repository with
Internet
downloads of the latest software from HP.
VCA compares installed software versions and available updates. Administrators can configure VCA to
point to a repository managed by VCRM.
For more information about version control tools, see the
HP Systems Insig
ht Manager Help Guide
and the
Version Control User Guide
on the
HP Systems Insight Manager website
http://www.hp.com/go/hpsim
roLiant Support Packs
PSPs re
present operating system
specific bundles of ProLiant optimized drivers, utilities, and management
agents. Refer to the
PSP website
http://h18000.www1.hp.com/products/servers/man
agement/psp.html
perating system version support
Refer to the
operating system support matrix
http://www.hp.com/go/supportos
irmware
The Smart Update Firmware DVD is an organized firmware coll
ection for ProLiant servers and options
powered by
HP Smart Update Manager
(on page
). The Smart Update Firmware DVD combines the
following resources on a single DVD:
Firmwa
re Maintenance CD
HP BladeSystem Firmware Deployment Tool (FDT)
The HP BladeSystem online firmware bundles
Software tools
and solutions
Enables GUI and a command
line, scriptable interface
Enables scriptable, command
line deployment
Requires no agent for remote installations
Enables
dependency checking, which ensures appropriate install order and dependency checking
Integrates with other software maintenance, deployment, and operating system tools
Automatically checks for hardware, firmware, and operating system dependencies, and installs only
the correct ROM
upgrades required by each target server
To download the tool and for more information, see the
HP website
http://www.hp.com/support
ubscriber's choice
HP's Subscriber's Choice is a cust
omizable subscription sign
up service that customers use to receive
personalized email product tips, feature articles, driver and support alerts, or other notifications.
To create a profile and select notifications, refer to the
HP website
http://www.hp.com/go/subscriberschoice
Software tools
and solutions
hange control and proactive notification
HP offers Change Control and Proactive Notification to notify customers 30 to 60
days in advance of
upcoming
hardware and software changes on HP commercial products.
For more information, refer to the
HP website
http://www.hp.com/go/pcn
are Pack
HP Care Pack Services offer upgraded service levels to extend and expand bundled services with
easy
buy, easy
use support packages that help you make the most of your server investments. For more
information, see the
HP website
http://www.hp.com/services/carepack
irmware maintenance
HP has developed technologies to help ensure that HP servers provide maximum uptime with minimal
intenance. Many of these technologies also reduce server management efforts, enabling administrators to
work on issues and resolve problems without taking servers offline.
The process of updating system or option firmware is referred to as a flash process
or
flashing the ROM
. A
firmware or ROM flash removes the existing version of firmware from the ROM and replaces it with a more
recent version.
Update the firmware to do the following:
Support new hardware, such as a processor revision
Support new features
Correct problems in a previous firmware version
Without the correct firmware version, the server and hardware options may not function properly.
ypes of ROM
Types of ROMs include:
System ROM
(on page
Option ROMs
(on page
ystem ROM
All ProLiant servers have a system ROM.
A system reboot is requ
ired for a ROM upgrade to take effect. For disaster recovery or ROM downgrade
purposes, backups of the most current ROM image are available in either redundant ROM or a ROM
backup.
ProLiant servers support either the redundant ROM feature or the Disaster R
ecovery feature. Both assist with
the management of system ROM revisions and ensure the proper operation of the platform if a failure occurs
during the firmware upgrade process.
Software tools
and solutions
edundant ROM support
The server enables you to upgrade o
r configure the ROM safely with redundant ROM support. The server has
an 8
MB ROM that acts as two, separate 4
MB ROMs. In the standard implementation, one side of the ROM
contains the current ROM program version, while the other side of the ROM contains a
backup version.
NOTE:
The server ships with the same version programmed on each side of the ROM.
When you flash the system ROM, ROMPaq writes over the backup ROM and saves the current ROM as a
backup, enabling you to switch easily to the alternate
ROM version if the new ROM becomes corrupted for
any reason. This feature protects the existing ROM version, even if you experience a power failure while
flashing the ROM.
You can choose which ROM to use in
RBSU
HP ROM
Based
Setup Utility
" on page
isaster recovery support
The Disaster Recovery feature is supported on servers that do not s
upport Redundant ROM. When a ROM
flash fails or the system ROM becomes corrupted, disaster recovery enables administrators to update the
Software tools
and solutions
erifying firmware versions
To locate and verify the most current firmware versions, use the following tools:
Insight
Diagnostics Online Edition
HP Insight Diagnostics
" on page
Access this tool from the System Management Homepage.
VCA
Version control
" on page
Access this tool from the System Management Homepage.
HP SIM
VCRM
Version control
" on page
Subscriber's Choice
(on page
pdating firmware
To update the firmware:
Check the
firmware version on the device
Verifying firmware versions
" on page
Software too
and solutions
To flash the ROM using ROMPaq:
Download the system ROMPaq utility diskette or USB drive key for each target server. ROMPaq
downloads are available on the
HP website
http://www.hp.com/support
Shut down each target server, and then reboot using the correct ROMPaq diskette or USB drive key for
that server.
Follow the interactive session in the ROMPaq utility, and then select the devices to be flashed.
After the ROMPaq utility flashes the ROM for
the selected devices, cycle power manually to reboot the
system back into the operating system.
Option ROMPaqs have been retired as an upgrade delivery method for storage options. Firmware upgrades
for storage options are now delivered using Smart Componen
ts and Smart Component deployment utilities.
For additional information about the ROMPaq utility, see the server documentation or the
HP website
http://www.hp.com/support
ystem ROMPaq Firmware Upgrade Utility
The Systems ROMPaq Firmware Upgrade Utility for ProLiant servers is available as a SoftPaq download from
the
HP website
http://www.hp.com/support
). The Enhanced SoftPaq dow
nload contains utilities to restore
or upgrade the System ROM on ProLiant servers:
ROMPaq Diskette
A Windows
based utility to create a bootable 1.44
MB diskette that can be used to restore or update
the System ROM locally.
ROMPaq USB Key
A Windows
based u
tility to partition, format, and copy files locally to a USB flash media device, such
as an HP drive key.
ROMPaq USB Key diskette format
A Windows
based utility to partition, format, and copy files locally to a USB flash media device, such
as an HP drive k
ey. The formatted USB key simulates a diskette in capacity and is usable on the
following servers:
Servers that exhibit an
Unsupported processor state
Software tools
and solutions
If using the Smart Update Firmware DVD, at the menu, select either
Automatic Mode
(default) or
Interactive Mode
If
Automatic Mode
is selected or the 30 second default timer runs out, the latest firmware available
on the DVD is installed. The server automatically reboots when it finishes updating. Log files are not
availa
ble in this method of installation.
If
Interactive Mode
Software tools
and solutions
HP SmartStart CD 6.x
HP Firmware Maintenance CD 7.0 or later
HP Smart Update Firmware DVD
Select the
Maintenance
nsupported processor stepping with I
ntel® processors
For systems based on Intel® processors, you must update the system ROM to support new steppings
(revisions) of processors. System ROM for HP servers contains the Intel® microcode, also called processor
support code, that the system uses to
initialize the processor and ensure proper operation of the platform.
New steppings of Intel® processors tend to be functionally equivalent to previous steppings. HP ProLiant
servers fully support mixing steppings when other parameters are identical: proc
essor speed, cache size,
number of cores, and processor wattage. To maintain support and uptime, HP provides updated system
ROM before shipping new stepping processors.
A new or replacement processor may be a newer stepping. At boot, the server indicates i
f the current system
ROM does not support the new stepping processor. The following message is displayed:
HP resources for
troubleshooting
P resources for troubleshooting
nline resources
P Technical Support website
Troubleshooti
ng tools and information, as well as the latest drivers and flash ROM images, are available on
the
HP website
http://www.hp.com/support
P Guid
ed Troubleshooting website
HP Guided Troubleshooting is available for many products and components on the
HP website
http://www.hp.com/support/gts
erver
documentation
HP resources for
troubleshooting
To create a pro
file and select notifications, refer to the
HP website
http://www.hp.com/go/subscriberschoice
Change control and proactive notification
HP offers Change Control and Proactive Notification to notify
customers 30 to 60
days in advance of
upcoming hardware and software changes on HP commercial products.
For more information, refer to the
HP website
http://www.hp.com/go/pcn
P Care Pack Services
HP Care Pack Services offer upgraded service levels to extend and expand bundled services with
easy
buy, easy
use support packages that help you make the most of your server investments. For more
information, see the
HP we
bsite
http://www.hp.com/services/carepack
roduct information resources
dditional product information
Refer to product information on the
HP Servers website
http://www.hp.com/country/us/eng/prodserv/servers.html
egistering the server
To register the server, refer to the
HP Registration website
http://register.hp.com
verview of server features and
installation instructions
Refer to the server user guide on the Documentation CD or on the
HP Business Support Center website
http://www.hp.com/go/bizsupport
ey features, option part numbers
Refer to the QuickSpecs on the
HP website
http://www.hp.com
erver and option specifications, symbols, installation warnings,
and notices
Refer to the server documentation and printed notices. Printed notices are available in the Reference
Information pack
. Server documentation is available in the following locations:
Documentation CD that ships with the server
HP Business Support Center website
http://www.hp.com/go/bizsupport
HP Technical Documentation websit
http://www.docs.hp.com
HP resources for
troubleshooting
eardown procedures, part numbers, specifications
Refer to the server maintenance
and service guide, available in the following locations:
Documentation CD that ships with the server
HP Business Support Center website
http://www.hp.com/go/bizsupport
HP Technical Documentation website
http://www.docs.hp.com
echnical topics
Refer to white papers on one of the following:
HP Business Support Center
http://www.hp.com
/go/bizsupport
HP Industry Standard Server Technology Papers
http://h18004.www1.hp.com/products/servers/technology/whitepapers/index.html
roduct installation resources
witch settings, LED functions, drive, memory, expansion board
and processor install
ation instructions, and board layouts
Refer to the hood labels and the server user guide. The hood labels are inside the access panels of the server,
and the server user guide is available in the following locations:
Documentation CD that ships with the se
rver
HP Business Support Center website
http://www.hp.com/go/bizsupport
HP Technical Documentation website
http://www.docs.hp.com
xternal cabling information
Refer to cabling information on the
HP website
http://www.hp.com/support
ower capacity
For all HP ProLiant ML and DL servers,
see the HP Power Advisor on the
HP website
http://www.hp.com/go/hppoweradvisor
For all HP ProLiant BL server blades, see the HP BladeSystem Power Sizer on the
HP website
http://www.hp.com/go/bladesystem/powercalculator
roduct configuration resources
evice driver information
Refer to driver information on the
HP S
oftware and Drivers website
http://www.hp.com/support
HP resources for
troubleshooting
DR3 memory configuration
See the DDR3 Memory Configuration Tool on the
HP website
http://www.hp.com/go/ddr3memory
configurator
perating System Ver
sion Support
For information about specific versions of a supported operating system, refer to the
operating system
support matrix
http://www.hp.com/go/supportos
perating system
installation and configuration information (for
factory
installed operating systems)
Refer to the factory
installed operating system installation documentation that ships with the server.
erver configuration information
Refe
r to the server user guide on the Documentation CD, the server installation poster shipped with the server,
and the SmartStart installation poster (if the server supports SmartStart) in the HP ProLiant Essentials
Foundation Pack.
nstallation and configuration information for the server setup
software
Refer to the server user guide on the Documentation CD, the server installation poster ship
ped with the server,
and the SmartStart installation poster (if the server supports SmartStart) in the HP ProLiant Essentials
Foundation Pack.
oftware install
ation and configuration of the server
If the server supports SmartStart, refer to the SmartStart installation poster in the HP ProLiant Essentials
Foundation Pack.
LO information
Refer to the
HP Integrated Lights
Out User Guide
on the Documentation CD or the
Remote Management
website
http://www.hp.com/servers/lights
out
anagement of the server
Refer to the
HP Systems Insight Manager Help Guide
on the Management CD or DVD, or the
HP website
http://www.hp.com/go/hpsim
HP resources for
troubleshooting
nstallation and configuration information for the server
management system
Refer to the
HP Systems Insight Manager Installation and User Guide
on the Management CD or DVD, or the
HP website
http://www.hp.com/go/hpsim
ault tolerance, security, care and maintenance, configuration
Error messages
Error messages
DU error messages
ntroduction to ADU error messages
This section contains a complete alphabetical list of all
ADU
Array diagnostic software
" on page
) 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. R
efer 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.
Error messages
ccelerator Status: Cache was Automatically Configured During Last C
ontroller
Error messages
ADU
Array diagnostic software
" on page
ccelerator 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 err
or or data loss condition exists. No action is required.
Error messages
ccelerator 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.
dapter/NVRAM ID Mismatch
Description
: EISA NVRAM has an ID for a different controller from the one physically present in the slot.
Action
Error messages
onfiguration Signature is Zero
Description
ADU
Array diagnostic software
" on page
) detected that NVRAM contains a configuration
Error messages
ontroller Reported POST Error. Error Code: X
Description
: The controller returned an error from its internal POST.
Action
: Replace the
controller.
ontroller Restarted with a Signature of Zero
Description
ADU
Array diagnostic software
" on page
) 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 NVRA
isable 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
ACU
Array Configuration Utility
" on page
) to reinitialize the array
accelerator board.
rive (Bay) X Firmware Needs Upgrading
Description
: Firmware on this physical drive is below the latest recommended version.
Acti
Update the drive to the latest firmware version
Firmware maintenance
" on page
rive (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.
rive (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.
rive (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
Be sure all cables are properly connected and working.
Power down the system and attempt to reconnect data/power cable to the drive.
Power up the system.
If the problem persists, power down the system and replace the cab
le.
If the problem persists, power down the system and replace the drive.
Error messages
rive (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 volum
Action
: If the replacement was intentional, allow the drive to rebuild.
rive (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 dr
ive 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.
rive (Bay) X is Failed
Description
: The indicated physical drive has failed.
Action
Check for
loose cable connections
Loose connections
" on page
If cable connectors are secure, replace the drive.
rive (Bay) X is Undergoing Drive Recovery
Description
: This drive is being rebuilt from the corresponding mirror or parity
Action
: No action is required.
rive (Bay) X Upload Code Not Readable
Description
: An error occurred while
ADU
Array diagnostic software
" on page
) was trying to read the
upload code information from this drive.
Action
: If multiple errors occur, the drive may need to be replaced.
rive (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.
Power down the server.
Replace the drive that was incorrectly
replaced.
Replace the original drive that failed.
Error messages
rive Monitoring Features Are Unobtainable
Description
ADU
Array diagnostic software
" on page
) 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.
rive Monitoring is NOT Enabled for SCSI Port X Drive ID Y
Descri
ption
: 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.
rive Time
Out Occurred on P
hysical 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
Error messages
dentify Logical Drive Da
ta 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 co
nfigured.
Action
: Run the server setup utility to configure the controller and NVRAM.
nsufficient adapter resources
Description
: The adapter does not have sufficient resources to perform posted
write op
erations to the array
accelerator board. Drive rebuild may be occurring.
Action
: Operate the system without the array accelerator board until the drive rebuild completes.
nter
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.
ess 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.
ess 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.
ogical Drive X Failed Due to Cache Error
Description
: This logical drive failed due to a ca
tastrophic cache error.
Action
: Replace the array accelerator board and reconfigure using
ACU
Array Configuration Utility
" on
page
ogical 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.
Error messages
Action
: Check for drive failures, wrong drive replaced, or loose cable messages. If a drive fail
ure occurred,
replace the failed drive or drives, and then restore the data for this logical drive from the tape backup.
Otherwise, follow the procedures for correcting problems when an incorrect drive is replaced or a loose
cable is detected.
ogical 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 perma
nent data loss.
Action
: Replace the failed drive as soon as possible.
Error messages
ogical Drive X Status = Wrong Drive Replaced
Description
: A physical drive in this logical drive has failed. The incorrect
drive was replaced.
Action
Power down the server.
Replace the drive that was incorrectly replaced.
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.
Error messages
ther Controller Indicates Different Hardware Model
Description
: The other controller in the redundant co
ntroller 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.
ther 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.
ther 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.
rocessor
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 e
nabled and also
indicates the maximum speed for the installed processors.
rocessor 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.
rocessor 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.
rocessor Not Started (Unsupported Processor Stepping)
Description
: If a processor has an unsupported stepping, it is not started, and this message is displayed.
rocessor 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.
Error messages
Error messages
Description
: SMART is unable to communicate with the drive, because the cable is not securely connected, or
the drive cage connection has failed.
Action
Power down the system.
Reconnect the cable securely.
Restart the system.
If the problem
persists, replace the cables and connectors as needed.
CSI Port X, Drive ID Y RIS Copies Within This Drive Do Not Match
Description
: The copies of RIS on the drive do not match.
Action
: Check
for other errors. The drive may need to be replaced.
CSI Port X, Drive ID Y...S.M.A.R.T. Predictive Failure Errors Have Been Detected in
the Factory Monitor and Performance D
ata...
...SOLUTION: Please replace this drive when conditions permit.
Description
: A predictive failure warning for this hard drive has been generated, indicating that a drive
failure is imminent.
Action
: Replace this drive at the earliest opportunity. Ref
er to the server documentation for drive replacement
information before performing this operation.
CSI Port X, Drive ID Y...S.M.A.R.T. Predictive Failure Errors Have Been
Detected in
the Power Monitor and Performance Data...
...SOLUTION: Please replace this drive when conditions permit.
Description
: A predictive failure warning for this hard drive has been generated, indicating a drive failure is
imminent.
Action
: Replace t
his drive at the earliest opportunity. Refer to the server documentation for drive replacement
information before performing this operation.
CSI Port X, Drive ID Y Was Replaced On a Good Volume:
(failure message)
Description
ADU
Array diagnostic software
" on page
) found that this drive was replaced, even though
no problem occurred wit
h the volume.
Action
: No action is required.
Error messages
oft firmware upgrade required
Description
ADU
Array diagnostic software
" on page
) has determined that the controller is running
firmware that has been soft upgraded by the Upgrade Utility. However, the firmware running is not present
on all drives. This could be caused by the addition of new drives
in the system.
Action
Update all drives to the latest firmware version
Firmware maintenance
" on page
torage
Enclosure on SCSI Bus X has a Cabling Error (Bus Disabled)...
...SOLUTION: The SCSI controller has an internal and external cable attached to the same bus. Please disconnect the
internal or external cable from the controller. If this controller supports mu
ltiple buses, the cable disconnected can be
reattached to an available bus.
Description
: The current cabling configuration is not supported.
Action
: Refer to the server documentation for cabling guidelines, and reconfigure as indicated.
torage Enclosure on SCSI Bus X Indicated a Door Alert...
...SOLUTION: Be sure that the storage enclosure door is closed or the side panel is properly installed.
Description
: The side panel of the external storage unit is open.
Action
: Be sure the
side panel of the storage unit is securely closed.
torage Enclosure on SCSI Bus X Indicated a Power Supply Failure...
...SOLUTION: Replace the power supply.
Description
: A power supply in the external storage unit has failed.
Acti
: Replace the power supply.
torage Enclosure on SCSI Bus X Indicated an Overheated Condition...
...SOLUTION: Make sure all cooling fans are operating properly. Also be sure the operating environment of storage
enclosure is withi
n temperature specifications.
Description
: The external storage unit is generating a temperature alert.
Action
Be sure all fans are connected and operating properly.
Be sure the operating environment of the storage unit is within specifications.
For
better airflow, remove any dust buildup from fans or other areas.
Check the server documentation for allowable temperature specifications and additional tips.
If the problem persists, replace the fan.
torage enclosure on SCSI Bus
X is unsupported with its current firmware version...
...SOLUTION: Upgrade the firmware version on the storage enclosure.
Description
: The firmware version of the external storage unit is not supported.
Action
Update the storage device to the latest
firmware version
Firmware maintenance
" on page
torage Enclosure on SCSI Bus X Indicated that the Fan Failed...
...SOLU
TION: Replace the fan.
Error me
ssages
Description
: The cooling fan located in the external storage unit has failed.
Action
: Replace the fan.
torage Enclosure on SCSI Bus X Indicated that the Fan is Degraded...
...SOLUTION: this condition usuall
y occurs on enclosures with multiple fans and one of those fans has failed. Replace
any fans not operating properly.
Description
: One or more fans in the external storage unit have failed.
Action
: Replace the failed fans.
torage
Enclosure on SCSI Bus X Indicated that the Fan Module is Unplugged...
...SOLUTION: Make sure the fan module is properly connected.
Description
: A fan in the external storage unit is not connected properly.
Action
: Check and reseat all fan connections
securely.
torage Enclosure on SCSI Bus X
Wide SCSI Transfer Failed...
...SOLUTION: This may indicate a bad SCSI cable on bus
X. Try replacing the cable.
Description
: A cable on bus
X has failed.
Action
Replace the failed
cable.
If the problem persists, contact an authorized service provider.
Error messages
Place the drives
in their original locations.
Restart the server, and then complete the expand operation.
Move the drives to their new locations after the expand operation is completed.
Error messages
Description
: More logical drives were created than are supported on this controller, causing lost logical drive
volumes.
ction
: Identify the drives containing lost volumes, and then move them to another controller so the lost
volumes can be recreated.
CAUTION:
Removing a drive that contains valid volume data causes all valid data to be lost.
ystem Board is Unable to Identify which Slots the Controllers are in
Description
: The slot indicator on the system board is not working correctly. Firmware recognizes both
controllers as being installed in the same slot.
Action
Be sure bot
h controllers are fully seated in their slots.
If the problem persists, this might indicate a controller problem or a system board problem.
CAUTION:
Only authorized technicians trained by HP should attempt to remove the system
board. If you believe th
e system board requires replacement, contact
HP Technical Support
Contacting HP
" on page
) before proceeding.
Remove one of the controllers in the configuration and see if the remaining controller generates a POST
message.
Move the remaining controller to the other slot to see if it
still generates a POST message.
Repeat these steps with the other controller.
If both controllers give POST messages in one slot but not the other, it is a system board problem. If one of the
controllers gives POST messages and the other controller does no
t, replace the controller that is giving the
POST messages. Contact an authorized service provider for any warranty replacements.
he 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.
Description
: ADU detected two different controller models installed in a redundant controller configura
tion.
This is not supported and one or both controllers may not be operating properly.
Action
: Use the same controller models for redundant controller configurations.
his Controller Can See the Drives but the Other Controller Can
Description
: The other controller in the redundant controller configuration cannot recognize the drives, but
this controller can.
Action
: Resolve any other errors and then rerun
ADU
Array diagnostic software
" on page
his Controller Can't See the Drives but the Other Controller Can
Description
: The other controller in the redundant controller configuration can recogn
ize the drives, but this
controller cannot.
Action
: Resolve any other errors and then rerun
ADU
Array diagnostic software
" on page
Error messages
nable to Communicate with Drive on SCSI Port X, Drive ID Y
Description
: The array controller cannot communicate with the drive.
Action
: If the hard drive amber LED is on, replace the drive.
failed.
Action
Power down the server.
Be sure 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 HP authorized service provider
Contacting HP technical
support or an authorized reseller
" on page
nknown Disable Code
Description
: A code was returned from the array accelerator board that ADU does not recognize.
Action
: Obtain the latest version of
ADU
Array dia
gnostic software
" on page
nrecoverable Read Error
Description
: Read parity errors were detected when an attempt to read the same data
from both sides of the
mirrored memory was made. Data loss will occur.
Action
: Replace the array accelerator board.
nsupported Processor Configuration (Processor Required in Slot #1)
Description
: Processor requir
ed in slot 1.
Action:
If you do not install a supported processor in slot 1, this message is displayed, and the system halts.
Error messages
ARNING
Drive Write Cache is Enabled on X
Description
: Drive has its
internal write cache enabled. The drive may be a third
party drive, or the operating
parameters of the drive may have been altered. Condition can cause data corruption if power to the drive is
interrupted.
Action
: Replace the drive with a supported drive
or restore the operating parameter of the drive.
ARNING
Error messages
rite Memory Error
Description
: Data cannot be written to the cache memory. This typically means that a parity error was
detected while writing data to the cache. This can be caused by an
Error messages
Error messages
Array status: The array currently has a drive erase operation queued, running,
Error messages
Controller State: The array controller is connected to an expander card or an external
enclosure…
…and is
operating without a memory board. If there are physical drives attached to the expander card or external
enclosure, and those drives contain any logical drives, then making any configuration change will lead to potential
data loss on those logical drives.
Action:
Install a cache memory module.
Controller State: The array controller is operating without a memory board…
…and contains one or more logical drives with a RAID level that is not supported in the current configuration. Any
configuration command
(e.g. logical drive creation, array expansion, etc.) or modification to the controller will result
in the loss of all existing data on the disabled volume(s).
Action:
Install a cache memory module.
Controller State: The array controller is operating witho
ut a memory board and has
a bad volume position…
…Any configuration command (e.g. logical drive creation, array expansion, etc.) or modification to the controller will
result in the loss of all existing data on the disabled volume(s).
Action:
Install a cac
he memory module.
Controller State: The array controller is operating without a memory board and
contains more logical drives than are supported in the current configuration…
…Any configuration command (e.g. logical drive creation, array expansion, etc.)
or modification to the controller will
result in the loss of all existing data on the disabled volume(s).
Action:
Install a cache memory module.
Controller State: The array controller is operating without a memory board and has
an invalid physical drive c
onnection…
…Any configuration command (e.g. logical drive creation, array expansion, etc.) or modification to the controller will
result in the loss of all existing data on the disabled volume(s).
Action:
Install a cache memory module.
Controller State: T
he array controller has a configuration that requires more physical
drives than are currently supported…
…You may reconfigure the controller, but the existing configuration and data will be overwritten and potentially lost.
Action:
Do one of the following:
If this message is observed after moving a configured array of drives from another controller, then
upgrade the firmware on this controller. Also, check if the cache module is installed. Install the cache
module if not present. If this doesn't solve the p
roblem, power down the server and move the drives back
to the original controller.
If this message is observed without any drive movement, check if the cache module has failed and
replace it if required. If the problem persists,
contact HP support
Contacting HP
" on page
Error messages
Controller State: The array controller has an unknown disabled configuration status
message…
…Any configuration command (e.g.
logical drive creation, array expansion, etc.) or modification to the controller will
result in the loss of all existing data on the disabled volume(s).
Action:
Contact HP support
Contacting HP
" on page
Controller State: The array controller has an unsupported configuration…
…You may reconfigure the controller, but the existing configuration and data will be overwritten and potentially lost.
Action:
Do one of the following:
If this message is observed after moving a configured array of drives from another controller, then
upgrade the firmware on this controller. Also, check if the cache module is installed. Install the cache
module if not pres
ent. If this doesn't solve the problem, power down the server and move the drives back
to the original controller.
If this message is observed without any drive movement, check if the cache module has failed and
replace it if required. If the problem persi
sts,
contact HP support
Contacting HP
" on page
Controller State: The controller cannot be configured. CACHE STATUS PROBLEM
DETECTED:...
…The
cache on this controller has a problem. To prevent data loss, configuration changes to this controller are not
allowed. Please replace the cache to be able to continue to configure this controller.
Action
: Replace the cache module.
ontroller State: A logical drive is configured with a newer version of the Array
Configuration tools than is currently running.
...Please obtain a newer version of the Array Configuration tools to configure or diagnose this controller.
Action
: Obtain the
latest version of ACU.
ontroller State: The HBA does not have an access ID...
...External SCSI array controllers that support SSP require HBAs to have an access ID.
Action
: Upgrade the HBA. If the problem persists,
contact HP suppo
Contacting HP
" on page
rive Offline due to Erase Operation: The logical
drive is offline from having an
erase in progress.
Action
: No action is required. The logical drive will be offline temporarily. Logical drive migrate and extend
operations are not possible while the erase operation is in progress.
rive Offline due to Erase Operation: The physical drive is currently queued for
erase.
Action
: No action is required. The logical drive containing this physical drive cannot be migrated or
extended while the erase
operation is in progress.
Error messages
rive Offline due to Erase Operation: The physical drive is offline and currently being
erased.
Action
: No action is required. The logical drive containing this ph
ysical drive cannot be migrated or
extended while the erase operation is in progress.
rive
Offline due to Erase Operation: The physical drive is offline and the erase
process has been failed...
...The drive may now be brought online through the re
enable erased drive command in ACU.
Action
: Re
enable the physical drive using the
Array Configura
tion Utility
(on page
rive Offline due to Erase Operation: The physical drive is offline and the erase
process has completed...
...The drive may now be brought online through the re
enable erased drive command in ACU.
Action
: Re
enable the physical drive using the
Array Configuration Utility
(on page
rive Offline due to Erase Operation: The physical drive is offline from having an
erase in progress.
Action
: No action is required. The logical drive containin
g this physical drive cannot be migrated or
extended while the erase operation is in progress.
Failed Array Controller: code:lockup Codl7o;-1k;u10;&#xp-2 ;ুo;훠e : Restart the server and run a
diagnostic report…
…Install the latest version of controller firmware. If the condit
ion persists, the controller may need to be replaced or
require service.
Action:
Take the appropriate action as indicated in the message. If the condition persists, replace the
controller or
contact HP support
Contacting HP
" on page
ogical drive state: A logical drive is configured with a newer version of
Storage/Config Mod than is currently running.
Action
: Obtai
n the latest version of ACU.
ogical drive state: Background parity initialization is currently queued...
...or in progress on this logical drive. If background parity initialization is queued, it will start when I/O is performe
on the drive. When background parity initialization completes, the performance of the logical drive will improve.
Action
: No action is required.
ogical drive state: The current array controller is performing capacity expansio
n,...
...extension, or migration on this logical drive.
Action
: No action is required. Further configuration is disabled until the process completes.
Error messages
ogical drive state: The logical drive is disabled from a SCSI ID conflict.
Action
: Check all SCSI components to make sure they all have a unique SCSI ID.
ogical drive state: The logical drive is not configured.
Action
: Refresh the system using the
Array Configuration Utility
(on page
ogical drive state: The logical drive is not yet available.
Action
: No action is required. This logical drive will remain in this state until all expand/shrin
k or move
operations on this array are completed. All I/O requests sent to the logical drive in this state will be rejected.
ogical drive state: The logical drive is offline from being ejected.
Action
: Reinstall the removed ph
ysical drives.
ogical drive state: The logical drive is queued for erase.
Action
: No action is required. Logical drive migrate and extend operations are not possible while the erase
operation is in progress.
ogical drive state: The logical drive is queued for expansion.
Action
: No action is required.
ogical drive state: The logical drive is queued for rebuilding.
Action
: No action is required. Normal operations can occur; ho
wever, performance will be less than optimal
during the rebuild process.
ogical drive state: This logical drive has a high physical drive count...
...as well as a high stripe size value such that a controller lock up could occur
. It is recommended that the stripe size be
migrated to a lower value.
Action
: Migrate the stripe size to a lower value using the
Array Configuration Utility
(on page
VRAM Error: Board ID could not be read...
...(Read
Only Table failed checksum test). Unrecoverable error.
Action
Contact HP support
Contacting HP
" on page
VRAM Error: Bootstrap NVRAM image failed checksum test,...
...but a backup image was found and successfully restored. A system restart is nee
ded.
Action
: Restart the server.
VRAM Error: Bootstrap NVRAM image failed checksum test...
...and could not be restored. This error may or may not be recoverable. A firmware update might be able to correct the
error.
Error messages
Action
: Update the controller firmware. If the update fails,
contact HP support
Contacting HP
" on page
).
hysical Drive Sta
te: The data on the physical drive is being rebuilt.
Action
: No action is required. Normal operations can occur; however, performance will be less than optimal
during the rebuild process.
Physical Drive State: Predictive failure. This physical drive is pr
edicted to fail soon.
Action
: If this drive is part of a non
fault
tolerant configuration, do the following:
Back up all data on the drive.
Replace the drive.
Restore all data to the new drive.
If this drive is part of a fault
tolerant configuration, do no
t replace this drive unless all other drives in the array
are online.
hysical Drive State: This drive is not supported for configuration...
...and should be disconnected from this controller.
Action
: Replace the physical drive
with a drive supported by the controller.
Physical Drive State: SATA drives are not supported for configuration and should be
disconnected from this controller.
Action
: Replace the physical drive with a drive supported by the controller.
Physical Drive
State: Single
ported drives are not supported for configuration and
should be disconnected from this controller.
Action
: Replace the physical drive with a drive supported by the controller.
Physical Drive State: This drive contains unsupported configurati
on data...
...It cannot be used for configuration and should be disconnected from this controller.
Action
: Replace the physical drive with a drive supported by the controller.
Physical Drive State: This drive is not supported for configuration by this ver
sion of
controller firmware.
Action
: Replace the physical drive with a drive supported by the controller.
Physical Drive State: This drive is smaller in size than the drive it is replacing...
...It is not supported for configuration and should be disconne
cted from this controller.
Action
: Replace the physical drive with a larger drive supported by the controller.
Physical Drive State: This drive is unrecognizable...
...It is not supported for configuration and should be disconnected from this controller.
Error messages
Action
: Replace the physical drive with a drive supported by the controller.
Physical Drive State: This physical drive is part of a logical drive that is not supported
by the current configuration...
… Any configuration command (e.g. logical drive creatio
n, array expansion, etc.) or modification to the controller will
result in the loss of all existing data on the disabled logical drive(s).
Action:
Do one of the following:
If this message is observed after moving a configured array of drives from another c
ontroller, then
upgrade the firmware on this controller. Also, check if the cache module is installed. Install the cache
module if not present. If this doesn't solve the problem, power down the server and move the drives back
to the original controller.
this message is observed without any drive movement, check if the cache module has failed and
replace it if required. If the problem persists,
contact HP support
Contacting HP
" on page
Error messages
Smart SSD State: SSD has less than 2% of usage remaining before wearout.
Action:
Monitor the drive frequently and replace the drive before wearout.
Smart SSD State
: SSD has less than 2% of usage remaining before wearout…
…It has less than an estimated 56 days before it reaches the maximum usage limit and should be replaced as soon as
possible.
Action:
Replace the SSD as soon as possible.
Smart SSD State: SSD has
less than 5% of usage remaining before wearout.
Action:
Monitor the drive frequently and replace the drive before wearout.
Smart SSD State: SSD has less than 5% of usage remaining before wearout…
…It has less than an estimated 56 days before it reaches th
e maximum usage limit and should be replaced as soon as
possible.
Action:
Replace the SSD as soon as possible.
Smart SSD State: SSD has less than an estimated 56 days before it reaches the
maximum usage limit for writes (wearout)...
...and should be repla
ced as soon as possible.
Action:
Replace the SSD as soon as possible.
Smart SSD State: SSD has reached the maximum rated usage limit for writes
(wearout) and should be replaced immediately.
Action:
Replace the SSD immediately.
Smart SSD State: The SmartS
SD Wear Gauge log is full…
...Wear Gauge parameters are not available.
Action:
SSD wearout cannot be monitored. If wearout needs to be monitored, replace the drive.
Storage Enclosure: The enclosure is reporting a critical temperature status
condition...
...Power off the enclosure immediately.
Action: Power off the enclosure immediately. Be sure that all the fans are connected and operating properly.
Replace any defective fans. For better airflow remove any dust buildup from fans or other areas. If the
pro
blem persists,
contact HP support
Contacting HP
" on page
Storage Enclosure: One or more fans have failed.
Action:
Replace the failed fan.
Error mes
sages
Stor
age Enclosure: Warning: The enclosure is reporting a high temperature status.
Action:
Be sure that all
fans are connected and operating properly. Replace any defective fans.
For better
airflow, remove any dust buildup from fans or other areas. If the problem persists,
contact HP support
Contacting HP
" on page
Stor
age Enclosure: Warning: One or more redundant power supplies in this
enclosure has failed or is not plugged in correctly.
Action:
Reseat the power supply firmly and check the power cable. If the problem persists, check the power
supply.
OST error messages and beep codes
ntroduction to POST error messages
The error messages and codes in this section include all me
ssages generated by ProLiant servers. Some
messages are informational only and do not indicate any error. A server generates only the codes that are
applicable to its configuration and options.
HP ProLiant
Class
server blades do not have speakers and thu
s do not support audio output. Disregard the
audible beeps information if the server falls into this category.
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.
numeric messages or beeps only
dvanced Memory Protection mode: Advanced ECC
Audible Beeps
: None
Possible Cause
: Advanced ECC support is enabled.
Action
: None.
dvanced Memory Protection mode: Advanced ECC with hot
add
support
Audible Beeps
: None
Possible Cause
: Advanced ECC with Hot
Add support is enabled.
Action
: None.
dvanced Memory Protection mode: Online spare with Advanced
ECC
...Xxxx MB System memory and xxxx MB memory reserved for Online Spare.
Error messages
Audible Beeps
: None
Possible Cause
: This message indicates Online Spare Memory is enabled and indicates the amount of
memory reserved for this feature.
Action
: None.
dvanced Memory Protection mode: Multi
board mirrored memory with Advanced
ECC
...Xxxx MB System memory and xxxx MB memory reserved for Mirroring.
Audible Beeps
: None
Possible Cause
: This message indicates Mi
rrored Memory is enabled and indicates the amount of memory
reserved for this feature.
Action
: None.
dvanced Memory Protection mode: RAID memory with Advanced ECC
...Xxxx MB System memory and xxxx
MB memory reserved for RAID.
Audible Beeps
: None
Possible Cause
: This message indicates RAID Memory is enabled and indicates the amount of memory
reserved for this feature.
Action
: None.
n Unexpected Shutdow
n occurred prior to this power
Audible Beeps
: None
Possible Cause
: The server shut down because of an unexpected event on the previous boot.
Action
Error messages
an Solution Not Sufficient
Audible Beeps
Possible Cause
: The minimum number of required f
ans is missing or failed.
Action
: Install fans or replace any failed fans.
atal DMA Error
Audible Beeps
: None
Possible Cause
: The DMA controller has experienced a critical error that has caused an NMI.
Action
: Run
Insight
Diagnostics
HP Insight Diagnostics
" on page
) and replace failed components as
indicated.
atal Express Po
rt Error
Audible Beeps
: None
Possible Cause
: A PCI Express port has experienced a fatal error that caused an NMI.
Action
: Run
Insight Diagnostics
HP Insight Diagnostics
" on page
) and replace the failed PCI Express
boards or reseat loose PCI Express boards.
atal Front Side Bus Error
Audible Beeps
: None
Possible Cause
: The processor front
side
bus experienced a fatal error.
Action
Run
Insight Diagnostics
HP Insight Diagnostics
" on page
CAUTION:
Before replacing or reseating any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Fai
lure to follow the recommended guidelines can cause damage to the system board requiring
replacement of the system board.
Replace any failed processors or reseat any loose processors.
atal Global Protocol
Error
Audible Beeps
: None
Possible Cause
: The system experienced a critical error that caused an NMI.
Action
: Run
Insight Diagnostics
HP Insight Diagnostics
" on page
) and replace failed components as
indicated.
Error messages
atal Hub Link Error
Audible Beeps
: None
Possible Cause
: The hub link interface has experienced a critical failure
that caused an NMI.
Action
: Run
Insight Diagnostics
HP Insight Diagnostics
" on page
) and replace failed components as
indicated.
ATAL ROM ERROR: The System ROM is not Properly Programmed.
Audible Beeps
long, 1
short
Possible Cause
: The System ROM is not properly programmed.
Action
: Replace the physical ROM part.
ibre Channel
Mezzanine/Balcony Not Supported.
Audible Beeps
: 2 short
Description
: The Fibre Channel adapter is not supported on the server.
Action:
Install the supported Fibre Channel adapter.
igh Temperature Condition detected by Proces
sor X
Audible Beeps
: None
Possible Cause
: Ambient temperature exceeds recommended levels, fan solution is insufficient, or fans have
failed.
Action
: Adjust the ambient temperature, install fans, or replace the failed fans.
llegal Opcode
System Halted
Audible Beeps
: None
Possible Cause
: The server has entered the Illegal Operator Handler because of an unexpected event. This
error is often software
related and does not necessarily indicate a hardw
are issue.
Action
: Run
Insight Diagnostics
HP Insight Diagnostics
" on page
) and replace any failed components as
indicated. Be sure that all software is installed properly.
LO Generated NMI
Audible Beeps
: None
Possible Cause
: The iLO controller generated
an NMI.
Action
Error messages
nternal CPU Check
Processor
Audible Beeps
: None
Possible Cause
: A processor has experienced an internal error.
tion
Run
Insight Diagnostics
HP Insight Diagnostics
" on page
CAUTION:
Before removing or replacing any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
Replace any failed components as indicated, including
processors and PPMs.
nvalid memory types were found on the same node. Please check DIMM
compatibility.
Some DIMMs may not be used
Description
To use the installed DIMMs, install a processor in the
Error messages
ismatched power supplies not supported
Audible Beeps
: 1 long, 1 short
Possible Cause
: The power supplies installed in the server are not supported in the current configuration. The
server
does not support installing more than one type of power supply.
Action
: Install supported power supplies in a supported configuration.
For supported power supply configurations, see the server documentation on the
HP website
http://www.hp.com/support
Error messages
o Floppy Drive Present
Audible Beeps
: None
Possible Cause
: No diskette drive is installed or a diskette drive failure has occurred.
Action
Power down the server.
Replace a failed diskette drive.
Be sure a diskette drive is cabled properly, if a diskette d
rive exists.
o Keyboard Present
Audible Beeps
: None
Possible Cause
: A keyboard is not connected to the server or a keyboard failure has occurred.
Action
Power down the server, and then reconnect the keyboard.
Be su
re no keys are depressed or stuck.
If the failure reoccurs, replace the keyboard.
arity Check 2
System DIMM Memory
Audible Beeps
: None
Possible Cause
: An uncorrectable error memory event occurred in a memory DIMM.
Action
: Run
Insight Diagnostics
HP Insight Diagnostics
" on page
) to identify failed DIMMs. Then, use the
DIMM LEDs to identify failed DIMMs and replace t
he DIMMs.
CI Bus Parity Error, PCI Slot X
Audible Beeps
: None
Possible Cause
: A PCI device has generated a parity error on the PCI bus.
Action
: For plug
in PCI cards, remove the card. For embedded PCI
devices, run Insight Diagnostics and
replace any failed components as indicated.
Error messages
ower Supply Solution Not Fully Redundant
Audible beeps
: None
Possible cause
: The minimum power supply requirement is installed, but a redundant power
supply is missing
or failed.
Action
: Do one of the following:
Install a power supply.
Replace failed power supplies to complete redundancy.
rocessor X Unsupported Wattage.
Audible beeps
: 1 long, 1 short
Possibl
e cause
: Processor not supported by current server.
Action
CAUTION:
Before removing or replacing any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
See the server
documentation for supported processors. If the processor is supported, remove the processor,
update the system to latest ROM, and then reinstall the processor.
edundant ROM Detected
This system contains a valid backup system ROM.
udible Beeps
: None
Possible Cause
: The system recognizes both the system ROM and redundant ROM as valid. This is not an
error.
Action
: None
EDUNDANT ROM ERROR: Backup ROM Invalid.
...run ROMPAQ to correct error c
ondition.
Audible Beeps
: None
Possible Cause
: The backup system ROM is corrupted. The primary ROM is valid.
Action
: Run ROMPaq Utility to flash the system so that the primary and backup ROMs are valid.
EDUNDANT ROM ERR
OR: Bootblock Invalid.
...contact HP Representative.
Audible Beeps
: None
Possible Cause
: ROM bootblock is corrupt.
Action
: Contact an authorized service provider.
EDUNDANT ROM ERROR: Primary ROM invalid. Booting
Backup ROM.
...run ROMPAQ to correct error condition
Error messages
Audible Beeps
: None
Possible Cause
: The primary system ROM is corrupt. The system is booting from the redundant ROM.
Action
: Run ROMPaq Utility to restore the system ROM to the correct version.
Correct the processor configuration.
Error messages
Trusted Execution Error fo
und: 0X
Audible beeps
: None
Possible cause
: Intel Trusted Execution Technology has indicated an error during the previous attempt at
trusted boot.
Action
: Check the error code in the Intel documentation. For more information, see the
Intel website
http://www.intel.com
nsupported DIMM(s) found in system.
DIMM(s) may not be used
Description
: Unsupported memory types found in system.
Action:
Refer to the applicable server user guide memory requirements
and replace with supported DIMMs.
nsupported PCI Card Detected Remove PCI Card from Slot
Audible beeps
: 2 short
Possible cause
: The PCI card installed in the slot referenced in the message is strictly not supported on this
system.
Actio
: Remove the card from the slot reported in the message.
Error messages
Audible Beeps
: None
Possible
Cause
: A USB tape device that supports One Button Disaster Recovery (OBDR) is installed in the
system.
Action
Press 1 or 2.
Pressing 2 exits the configuration.
Pressing 1 starts the configuration. The following message appears
Observe the configuration progress. The following error may appear:
Follow the onscreen directions:
The following message should
appear:
Error messages
CAUTION:
Before removing or replacing any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the
troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
Correct the processor configuration.
ARNING: ProLiant Demand Based Power Management cannot be supported
with the following processor configuration. The system will run in Full Performance
mode.
Audible Beeps
: None
Possible Cause
: The system is configured for HP Static Low mode and the current processor cannot support
this mode.
Action
: For more information about the Power Regulator for ProLiant option, see the
HP ROM
Based Setup
Utility User Guide
on the Documentati
on CD or the
HP website
http://www.hp.com/support/smartstart/documentation
00 Series
I/O ROM Error
Audible Beeps
: None
Possible
Cause
: Options ROM on a PCI, PCI
X, or PCI Express device is corrupt.
Action
: If the device is removable, remove the device and verify that the message disappears. Update Option
ROM for a failed device.
ROM Error
Audible Beeps
: 1 long,
1 short
Possible Cause
: System ROM checksum.
Action
: Run
Insight Diagnostics
HP Insight Diagnostics
" on page
) and replace failed components as
ind
icated.
Option ROM Checksum Error...
...An add
in card in your system is not working correctly. If you have recently added new hardware, remove it and see
if the problem remains. If this message goes away after you remove your new
hardware, there may be a problem with
the add
in card.
Audible Beeps
long, 1
short
Possible Cause
: An expansion board in the system is not working correctly.
Action
: If you have recently added new hardware, remove it and see if the problem persists. If
this message
goes away after you remove the new hardware, there may be a problem with the expansion board. Review
the expansion board documentation, and then try reinstalling the board.
Error messages
System Board Failur
Audible Beeps
: None
Possible Cause
: 8237 DMA controllers, 8254
timers, and similar devices.
CAUTION:
Only authorized technicians trained by HP should attempt to remove the system
board. If you believe the system board requires replacement, contact
P Technical Support
Contacting HP
" on page
) before proceeding.
Action
Action
: Contact an authorized service provider for system board replacement.
System Board Failure, DMA Test Failed
Audible Beeps
: None
Possible Cause
: 8237 DMA controllers, 8254
timers, and similar
devices.
CAUTION:
Only authorized technicians trained by HP should attempt to remove the system
board. If you believe the system board requires replacement, contact
HP Technical Support
Contacting HP
" on page
) before proceeding.
Action
: Contact an authorized service provider for system board replacement.
System Board Failure, Timer Test
Failed
Audible Beeps
: None
Possible Cause
: 8237 DMA controllers, 8254
timers, and similar devices.
CAUTION:
Only authorized technicians trained by HP should attempt to remove the system
board. If you believe the system board requires replacement, contact
HP Technical Support
Contacting HP
" on page
) before proceeding.
Action
: Contact an authorized service provider for a system board replacement.
ASR Timer Failure
Audible Beeps
: None
Possible Cause
: System board failure.
CAUTION:
Only authorized technicians trained by HP should attempt to remove the system
board. If you believe the system board requires replacement, contact
HP Technical Support
Contacting HP
" on page
) before proceeding.
Error messages
Action
: Run
Insight Diagnostics
HP Insight Diagnostics
" on page
) and replace failed components as
indicated.
Error messages
Memory Address Error
Audible Beeps
: None
Possible Cause
Error messages
Invalid Memory Configuration
Insufficient Timings on DIMM
Audible Beeps
: 1 long, 1 short
Possible Cause
: The installed memory module is not supported.
Action
: Install a memory module of a supported type.
Inva
lid Memory Configuration
Mismatched DIMMs within DIMM Bank
Audible Beeps
: 1 long, 1 short
Possible Cause
: Installed DIMMs in the same bank are of different sizes.
Action
: Install correctly matched DIMMs.
Invalid
Memory Configuration
Mismatched DIMMs within DIMM Bank...
...Memory in Bank X Not Utilized.
Audible Beeps
: 1 long, 1 short
Possible Cause
: Installed DIMMs in the same bank are of different sizes.
Action
: Install correctly matched DIMMs.
Invalid Memory Configuration
Mismatched DIMMs within DIMM Bank...
...Memory in Board X Bank X Not Utilized.
Audible Beeps
: 1 long, 1 short
Possible Cause
: Installed DIMMs in the same bank are of different sizes.
Action
: Install correctly matched DIMMs
Invalid Memory Configuration
Unsupported DIMM in Bank X
Audible Beeps
: 1 long, 1 short
Possible Cause
: One of the DIMMs in bank X is of an unsupported type.
Action
: Install supported DIMMs to fill the bank.
Invalid Memory Configuration
Single channel memory...
...mode supports a single DIMM installed in DIMM socket 1. Please remove all other DIMMs or install memory in valid
pairs. System Halted.
Audible Beeps
: 1 lon
g, 1 short
Possible Cause
: DIMMs are installed in pairs, but the server is in single channel memory mode.
Action
: Remove all other DIMMs or install memory in valid pairs and change the memory mode.
Invalid Memory
Configuration
Error messages
Memory Configuration Warning
DIM
Error messages
Mirror Memory Configuration
Memory Sizes on boards X and Y do not match
Audible Beeps
: 1 long, 1 short
Possible Cause
: The overall size of two boards participating i
n a mirrored configuration does not match.
Action
: Install or reinstall DIMMs to support mirrored mode.
RAID Memory Configuration
Memory Sizes on boards X and Y do not match
Audible Beeps
: 1 long, 1 short
Possible Cause
: The over
all size of two boards participating in a RAID does not match.
Action
: Install or reinstall DIMMs to support RAID mode.
Memory Board Power Fault on board X
Audible Beeps
: 1 long, 1 short
Possible Cause
: A problem exists with a mem
ory board powering up properly.
Action
Replace failed components as indicated.
Processor PPM Failed, Module X
Audible Beeps
: None
Possible Cause
: Indicated PPM failed.
Action
: Run
Insight Diagnostics
HP Insight Diagnostics
" on page
) and replace failed components as
indicated.
Error messages
00 Series
Keyboard Error
Audible Beeps
: None
Possible Cause
: Keyboard failure occurr
ed.
Action
Power down the server, and then reconnect the keyboard.
Be sure no keys are depressed or stuck.
If the failure reoccurs, replace the keyboard.
Keyboard Error or Test Fixture Installed
Audible Beeps
: None
Possible Ca
use
: Keyboard failure occurred.
Action
Power down the server, and then reconnect the keyboard.
Be sure no keys are depressed or stuck.
If the failure reoccurs, replace the keyboard.
Keyboard Controller Error
Audible Beeps
: Non
Possible Cause
: System board, keyboard, or mouse controller failure occurred.
Action
Be sure the keyboard and mouse are connected.
CAUTION:
Only authorized technicians trained by HP should attempt to remove the system
board. If you believe the system board requires replacement, contact
HP Technical Support
Contacting HP
" on page
) before proceeding.
Run
Insight Diagnostics
HP Insight Diagnostics
" on page
) and replace failed c
omponents as
indicated.
Keyboard or System Unit Error
Audible Beeps
: None
Possible Cause
: Keyboard, keyboard cable, mouse controller, or system board failure.
Action
Be sure the keyboard and mouse are connected.
CAUTION:
Only authorized technicians trained by HP should attempt to remove the system
board. If you believe the system board requires replacement, contact
HP Technical Support
Contacting HP
" on page
) before proceeding.
Error messages
Run
Insight Diagnostics
HP Insight Diagnostics
" on page
) and replace failed components as
indicated.
00 Series
Parallel Port X Address Assignment Conflict
Audible Beeps
: 2 short
Possible
Cause
: Both external and internal ports are assigned to parallel port
Action
: Run the server setup utility and correct the configuration.
Parallel Port Address Conflict Detected...
...A hardware conflict in your system is keepin
g some system components from working correctly. If you have recently
Error messages
Reformat the diskette.
Diskette Drive Type Error.
Audible Beeps
: 2 short
Possible Cause
: Mismatch in
drive type occurred.
Action
Error messages
again if a battery
failure has occurred. However, the system will function and retain configuration settings if
the system is connected to the AC power source.
Action
: Replace battery (or add external battery).
Error messages
Error messages
Be sure each fan cable is properly connected, if applicable, and each fan is properly seated.
If the problem persists, replace the failed fans.
Power Supply Zone Fan Assembly Failure
Error messages
Power Supply Configuration Error
Audible Beeps
: None
ssible Cause
: The server configuration requires an additional power supply. A moving bar is displayed,
indicating that the system is waiting for another power supply to be installed.
Action
: Install the additional power supply.
ower Supply Configuration Error
A working power supply must be installed in Bay 1 for proper cooling.
System Halted!
Audible Beeps
: None
Possible Cause
: The server configuration requires an additional power supply. A moving bar is displayed,
indicating
that the system is waiting for another power supply to be installed.
Action
: Install the additional power supply.
Power Supply Failure, Power Supply Unplugged, or Power Supply Fan Failure
in Bay X
Audible Beeps
: None
Possible Ca
use
: The power supply has failed, or it is installed but not connected to the system board or AC
power source.
Action
: Reseat the power supply firmly and check the power cable or replace power supply.
Power Supply Configuration F
ailure
A working power supply must be installed in Bay 1 for proper cooling.
System Halted!
Audible Beeps
: None
Possible Cause
: Power supply is improperly configured.
Action
: Run the server setup utility and correct the configuration.
700 Series
Slot X Drive Array
Please replace Array Accelerator Battery...
...The Array Accelerator Cache will be enabled once the battery has been replaced and charged.
Audible Beeps
: None
Possible Cause
: The battery needs to
be replaced and charged.
Action
: Replace and charge the Array Accelerator battery.
Slot X Drive Array
Please install Array Accelerator Battery...
...The Array Accelerator Cache will be enabled once the battery is installed and charged.
Error messages
Audible Bee
: None
Possible Cause
: The battery needs to be installed and charged.
Action
: Install and charge the Array Accelerator battery.
Error messages
Audible Beeps
: None
Possible Cause
: The Bootstrap NVRAM on the specified Smart Array controller is corrupt or invalid.
Action
:
Update the controller with t
he latest firmware version.
If the problem still exists, replace the controller.
Slot X Drive Array Controller
Bootstrap NVRAM restored from backup.
System restart required
Audible Beeps
: None
Possible Cause
: The spe
cified Smart Array controller Bootstrap NVRAM was restored in one of the following
ways:
It was detected as corrupt, and the backup copy was restored.
It was automatically updated because a newer version was available.
Action
:
Reboot the server.
If the
problem still exists, update the controller to the latest firmware version.
Slot X Drive Array
Non
Error messages
Audible Beeps
: None
Possible Cause
: This configuration is not recommended because of controller memory requirements.
Action
: Perform RAID migration to lower stripe size using the
Array Configuration Utility
(on page
Slot X Drive Array
RAID 5 logical drive(s) configured with 56 Drives, but Array
Accelerator size = 32 MB...
...This configuration is not recommended. Consider migrating logical drive(s) to RAID 0 or 1, reducing the number of
drives in the array, or upgrading the Array Accelerator module.
Audible Beeps
: None
Possible Cause
: Upgrade the Array Accelerator module to
a larger size.
Action
: Migrate logical drives to RAID 0 or 1, reduce the number of drives in the array, or upgrade to a
larger
size array accelerator module.
Slot X Drive Array
Redundant ROM Reprogramming Failure...
...Replace the controller if
this error persists after restarting system.
Audible Beeps
: None
Possible Cause
: Flash ROM is failing. The controller detects a checksum failure, but is unable to reprogram
the backup ROM.
Action
Update the controller to the latest firmware version
Firmware maintenance
" on page
If the problem persists, replace the controller.
Slot X Drive Array
Redundant Checksum Error...
...Backup ROM
has automatically been activated; check firmware version.
Audible Beeps
: None
Possible Cause
: The controller flash operation is interrupted by a power cycle, or flash ROM is failing. The
controller detects a ROM checksum error and automatically switches to
the backup ROM image.
Action
: If this backup ROM image is a lower version than the originally running image, update the controller
to the latest firmware version.
Slot X Drive Array Controller
Memory Error(s) Occurred...
...Warning: Corrected Memo
ry Error(s) were detected during controller memory self
test. Please replace the controller
if this error persists.
Audible Beeps
: None
Possible Cause
: The memory is beginning to fail.
Action
: If this error persists, replace the controller.
Slot X Drive Array
Unrecoverable Media Errors Detected on Drives during
previous Rebuild or Background Surface Analysis (ARM) scan...
...Errors will be fixed automatically when the sector(s) are overwritten. Backup and restore recommended.
Error messages
Audible B
eeps
: None
Possible Cause
: A media error is detected on a drive and cannot be corrected because of degraded fault
tolerance or a media error at the same location on another drive in the same array. An unrecoverable read
error is returned to the operating s
ystem when this block address is read.
Action
: Backup and restore the data on the drive. Sequential write operations to the affected blocks should
resolve the media errors.
Slot X Drive Array
Disk Drive(s) Reporting OVERHEATED Condition: Port X
Box
Y Bay(s) Z
Audible Beeps
: None
Possible Cause
: The drives listed in this message are currently in an overheated state.
Action
: Check the fans and be sure the air flows over the drive. Install the access panel, if removed.
Slot X Drive Array Device
discovery found more devices attached to this
controller than firmware currently supports...
...Some devices are ignored.
Audible Beeps
: None
Possible Cause
: The firmware does not support the number of devices currently attached to the controller.
Action
If release notes indicate that support for additional devices has been added, upgrade to the latest
version of controller firmware.
Remove some of the devices attached to the controller.
Slot X Drive Array
A controller fai
lure event occurred prior to this power
up
(previous lock
up code = 0x####)
Audible Beeps
: None
Possible Cause
: A controller failure event occurred before the server powered up.
Action
: Install the latest version of controller firmware. If the condition pe
rsists, then replace the controller.
Slot X Drive Array
S.M.A.R.T. Hard Drive(s) Detect imminent failure: Port X
Box Y Bay(s) Z...
Do not replace drive unless all other drives in the array are online! Back up data before replacing drive(s) if u
sing
RAID 0.
Audible Beeps
: None
Possible Cause
: A hard drive SMART predictive failure condition is detected. It may fail at some time in the
future.
Action
If this drive is part of a non
fault
tolerant configuration, back up all data before replacing the
drive and
restore all data afterward.
Error messages
If this drive is part of a fault
tolerant configuration, do not replace this drive unless all other drives in the
array are online.
Slot X Drive Array
rror messages
Audible Beeps
: None
Possible Cause
: The controller has detected an additional array of drives that was connected when the power
was off. The logical drive configuration information has been updated to add
the new logical drives. The
maximum number of logical drives supported is 32. Additional logical drives will not be added to the
configuration.
Action
: No action is required.
Slot X New (or Previously Failed) Logical Drive(s) Attached...
Error messages
Fixed Disk 0 Does Not Support DMA Mode
Audible Beeps
: None
Possible Cause
Error messages
HP Trusted Platform Module Error
Audible Beeps
: 2 short
Possible Cause
: A TPM is installed, but the System ROM is unab
le to communicate with the TPM.
Action
: Request a new system board and TPM board from an
HP authorized service provider
Contacting HP
technical support or an authorized reseller
" on page
187
When installing or replacing a TPM, observe the following guidelines:
Do not remove an installed TPM. Once installed, the TPM becomes a permanent part of the system
board.
When installing or replacing hardware,
HP service providers cannot enable the TPM or the encryption
technology. For security reasons, only the customer can enable these features.
Error messages
Audible Beeps
: None
Possible Cause
: A problem exists with the storage enclosure redundant cabling. A single path was foun
d to
drives that were previously connected redundantly.
Action
Check the storage box I/O module and cable to restore redundant paths to the drives, then do one of the
following:
If the redundant cables/paths were not purposefully removed, press
to disp
lay this message on
reboot until the problem is resolved. The drives should be accessible through the remaining path.
If the redundant paths were purposefully removed, press
to disable this message on all subsequent
reboots.
Slot X Drive Array
edundant Cabling is not as recommended...
(followed by one or more of the following:)
...* Storage box has multiple paths from same controller port
* I/O modules are not cabled for good fault tolerance
* Redundant I/O paths exist due to direct loopback
of controller ports
* Redundant I/O module supported and unsupported storage boxes are cabled together.
* Refer to product user guide
Audible Beeps
: None
Possible Cause
: Incorrect redundant cabling configuration
Action
: For information on how to cable
the device in a supported manner for dual
domain redundant path
support, see the product user guide.
Fixed Disk 0 failed Set Block Mode
Audible Beeps
: None
Possible Cause
Abort the erase
process using
ACU
Array Configuration Utility
" on page
Error messages
Slot X Drive Array
Logical Drive Erase Operation(s) are Queued...
...Logical drives will temporarily go offline while being erased.
Audible Beeps
: None
Possible Cause
: The drives being e
rased are offline.
Action
: Do one of the following:
Abort the erase process using
ACU
Array Configuration Utility
" on page
Slot X Drive Array
Drive Erase Operation In Progress (or Queued)...
...The following disk drive(s) will be blank upon completion: (followed by a list of drives)
Audible
Beeps
: None
Possible Cause
: A drive erase operation was previously initiated by the user and is in progress or is
scheduled for all drives in the list.
Action
: None required
Slot X Drive Array
Drive Erase Operation Com
pleted...
...The following disk drive(s) have been erased and will remain offline until hot
replaced or re
enabled by the Array
Configuration Utility:
(followed by a list of drives)
Audible Beeps
: None
Possible Cause
: The drive erase operation was successf
ully completed, and the drives are being held in an
offline state to ensure that the drives remain blank until re
enabled by the user.
Action
: Replace each drive in the list or re
enable each drive in the list using one of the following methods:
Use the
ray Configuration Utility
(on page
) (all drive types).
Perform hot
plug removal and reinstallation (hot
plug hard drives only).
Slot X Drive Array
Unsupported
Error messages
* Configuration information indicates one or more hard drive(s) are located in drive bays that
are inaccessible when
Error messages
Fixed Disk 0 failed ID command
Audible Beeps
: None
Possible Cause
If the problem persists, replace the system board.
Error messages
Slot X Array Accelerator module Incompatible with this controller...
...Please replace
Array Accelerator module.
Audible Beeps
: None
Possible Cause
: The current Array Accelerator is not supported.
Action
: Replace the Array Accelerator module with the correct model for this controller. If this occurs after
upgrading to a larger module, updat
e the controller firmware before attaching the new module.
Drive Array
Replace the system board.
Fixed Disk 0 does not support Block Mode
Audible Beeps
: None
Possible Cause
Error messages
Audible Beeps
: None
Possible Cause
: The current controller firmware does not support the attached Array Accelerator module
type.
Action
: Upgrade the con
troller firmware, or replace the Array Accelerator module.
Slot X Drive Array
Array Accelerator daughtercard critical error; please
replace...
...(Controller is disabled until this problem is resolved)
Audible Beeps
: None
Possible Cause
: Array acce
lerator module is loose, missing, or defective.
Action
: Replace the array accelerator module.
Slot X Drive Array
Error messages
* Expansion Aborted due to Unrecoverable
Drive Errors.
* Expansion Aborted due to Array Accelerator Errors.
Select "F1" to continue with logical drives disabled
Select "F2" to accept data loss and to re
enable logical drives
Audible Beeps
: None
Possible Cause
: Data was lost while the array was e
xpanded; therefore, the drives have been temporarily
disabled. Capacity expansion failed due to:
Array accelerator or hard drive failed or was removed; expansion progress data lost
Expansion progress data could not be read from array accelerator
Expansion
aborted due to unrecoverable drive errors
Expansion aborted due to array accelerator errors
Action
Press the
key to continue with the logical drives disabled. Or, press the
key to accept the data loss
and re
enable the logical drives.
Restore data
from backup.
Replace drive or array accelerator, as appropriate.
Slot X Drive Array
Disk Drive Firmware Update Recommended
...Please upgrade firmware on the following drive model(s) using ROM Flash Components (download from
www.hp.com/support
/proliantstorage): Model XYZ (minimum version = ####)
Audible Beeps
: None
Possible Cause
: Drive firmware update needed.
Action
: The indicated drives are running firmware that is known to cause intermittent problems.
Update all
drives to the latest firmware
version
Firmware maintenance
" on page
Primary Disk port Address conflict
Audible Beeps
: None
Possible Cause
: Internal and external hard drive controllers are both assigned to the primary address.
Action
Error messages
Primary Fixed Disk port Address conflict
Audible Beeps
: None
Possible Cause
Error messages
Drive Array Reports Improper SCSI Port 1 Cabling
Audible Beeps
: None
Possible Cause
The integrated
array enabler board failed.
The I/O board, drive backplane fan board, or drive backplane failed.
Action
Replace the integrated array enabler board.
Update the integrated Smart Array option to the latest firmware version
Firmware
maintenance
" on
page
CAUTION:
Only authorized technicians trained by HP should attempt to remove the I/O board.
If you believe the I/O board requires replacement, co
ntact
HP Technical Support
Contacting
" on page
) before proceeding.
Reboot the server after replacing each item:
Drive backplane fan board
Drive backplane
I/O board
Slot X Drive Array
Error messages
IMPORTANT:
This error message applies to systems that use SCSI controllers. For systems that
use SAS controllers, see
error message 1777 for SAS
1777
Slot X Drive Array
Storage
Slot X Drive Array
Slot X Drive Array resuming Automatic Data Recovery (Rebuild) process
Audible Beeps
: None
Possible Cause
: A controller reset or power cycle occurred while
Automatic Data Recovery was in progress.
Action
: No action is required.
Slot X Drive Array
Replacement drive(s) detected OR previously failed drive(s)
now appear to be operational:...
...Port X Box Y Bay(s) Z
Restore data from backup if replacement
drive(s) have been installed.
Error messages
Audible Beeps
: None
Possible Cause
: More drives failed (or were replaced) than the fault
tolerance level allows. The array cannot
be rebuilt. If drives have not been replaced, this message indicates an intermittent drive fail
ure.
Action
: Be sure the system is always powered up and down correctly:
When powering up the system, all external storage systems must be powered up before (or at the same
time as) the server.
When powering down the system, the server must be powered dow
n before powering down any
external storage systems.
Slot X Drive Array
Logical drive(s) previously failed...
...Select "F1" to continue with logical drives disabled
Select "F2" to accept data loss and to re
enable logical drives
(followed by one
of the following:)
* Logical drive(s) disabled due to possible data loss.
* Logical drive(s) reenabled.
Restore data from backup if replacement drive(s) have been installed
Audible Beeps
: None
Possible Cause
: Previously failed logical drives are attached
to the controller.
Action
: Do one of the following:
To continue with logical drives disabled, select
To accept data loss and to re
enable the logical drives, select
Disk 0 Failure
Audible Beeps
: None
Possible Cause
: Hard drive or format erro
r detected. The drive is not installed correctly or has failed.
Action
Error messages
Disk Controller Failure
Audible Beeps
: None
Possible Cause
: Hard drive circuitry error detected.
Action
: Run
Insight Diagnostics
HP Insight Diagnostics
" on page
) and replace failed components as
indicated.
Slot X Drive Array Controller Failure...
followed by one of the foll
owing:)
...* [Board ID not programmed (replace ROMs or replace controller)]
* [I2C read error]
* [Image checksum error]
* [Inconsistent volume count]
* [Inconsistent volume count (B)]
* [Unexpected hardware revision
hardware rework needed]
* [Unsu
pported Flash ROM type installed]
* [iLO communication mechanism self
test error]
* [PROGRAM BUG! Insufficient padding bytes (cmd=##h)]
* [Incorrect EEPROM type]
* [Init failure (cmd=##h, err=##h)]
* [Command failure (cmd=##h, err=##h)]
* [Self
test
failure (ErrCode=####h)]
* [I2C NVRAM reconfiguration failure]
* [PCI bridge missing]
* [PCI bridge disabled; check System ROM version]
* [PDPI not found]
* [PDPI disabled; check System ROM version]
* [Board ID not programmed]
Audible Beeps
: None
Possible Cause
: The controller failed.
Action
Reseat the array accelerator module.
Reseat the controller in the PCI slot.
Update the controller to the latest firmware version
Firmware maintenance
" on page
If the problem persists, replace the controller.
Slot X Drive Array
Drive Failure...
...The following disk drive(s) should be replaced:
Port X Box Y Bay(s) Z
Audible Beeps
: None
Possible
Cause
ror messages
Replace defective cables, drive
, or both.
Slot X Drive Array
Logical Drive Failure
Audible Beeps
: None
Possible Cause
Error messages
Press the
key to continue with recovery of data to the drive. Data will be automatically restored
to drive
when a failed drive has been replaced, or to the original drive if it is working again
without errors.
Press the
key to co
ntinue without recovery of data to the drive. The failed drive will not be rebuilt
and the system will continue to operate in a failed state of Interim Data Recovery Mode.
Replace the failed drive and press the
key to rebuild the array. If the drive reb
uild is not successful or
is aborted because the system rebooted before the rebuild of the drive completed, another version of the
1786 POST error message will be displayed.
Slot X Drive Array Operating in Interim Recovery (Degraded) Mode...
(followe
d by one or more of the following:)
...* The following disk drive(s) are failed and should be replaced
* The following disk drive(s) are insufficient size and should be replaced
* The following disk drive(s) are mismatched type and should be replaced
*
The following disk drive(s) are unsupported type and should be replaced
* The following disk drive(s) are offline due to the erase process
(additionally be one of the following if a spare drive is activated:)
* On
Line Spare Drive is being Activated
*
On
Line Spare Drive Active
* On
Line Spare Drive Failed
Audible Beeps
: None
Possible Cause
: Hard drive
failed or cable is loose or defective. Following a system restart, this message
notes that drive
is defective and fault tolerance is being used.
Action
Be sure all cables are connected properly and securely.
Test and replace defective cables.
Replace drive
. (depending on the fault
tolerance level, all data may be lost if another drive fails).
Slot
X Drive Array Reports Incorrect Drive
Replacement...
...The following drive(s) should have been replaced: Port x Box y Bay(s) z
The following drive(s) were incorrectly replaced: Port x Box y Bay(s) z
Select "F1" to continue
drive array will remain disabled.
Select "F2" to reset configuration
all data will be lost.
Audible Beeps
: None
Possible Cause
Replacement drives may have been installed in the wrong drive bays.
A bad power cable connection to the drive, noise on the data cable, or defective SCSI cable exists.
Action
If replacement dr
ives are installed in the wrong bays, properly reinstall the drives as indicated and then
do one of the following:
Press the
key to restart the server with the drive array disabled.
Press the
key to use the drives as configured and lose all the data
on them.
If a bad power cable connection exists:
Error messages
Repair the connection and press the
key.
If the problem persists, run
ADU
Array diagnostic software
" on page
) to resolve.
Be sure the cable is routed properly.
Slot X Drive Array Disk Drive(s) Not Responding...
...Check cables or replace the following drive(s): Port x Box y Bay(s) z
Select "F1" to
continue
drive array will remain disabled
Select "F2" to fail drive(s) that are not responding
Interim Recovery Mode will be enabled if configured for fault
tolerance.
Audible Beeps
: None
Possible Cause
: Drives that were working when the system was
last used are now missing or are not starting
up. A possible drive problem or loose cable exists.
Action
Power down the system.
Be sure all cables are properly connected.
Be sure all drives are fully seated.
Power cycle any external enclosures while the
system is off.
Power up the server to see if the problem still exists.
If configured for fault
tolerant operation and the RAID level can sustain failure of all indicated drives:
Press the
key to fail the drives that are not responding
Replace the failed
drives.
Press the
key to start the system with all logical drives on the controller disabled.
Be sure the system is always powered up and down correctly.
When powering up the system, all external storage systems must be powered up before the server.
Wh
en powering down the system, the server must be powered down before external storage systems.
Disk 0 Configuration Error
Audible Beeps
: None
Possible Cause
: Hard drive error or wrong drive type detected.
Action
Run the server setup utility and
correct the configuration.
If the problem persists, run
Insight Diagnostics
HP Insight Diagnostics
" on page
) and replace the
failed assembly as ind
icated.
Disk 1 Error
Audible Beeps
: None
Possible Cause
: Hard drive error or wrong drive type detected.
Action
Run the server setup utility and correct the configuration.
Error messages
If the problem persists, run
Insight Diagnostics
Insight Diagnostics
" on page
) and replace the
failed assembly as indicated.
Slot X Drive Array
Valid Data Found in Array Accelerator...
...Data will automatically b
e written to drive array.
Audible Beeps
: None
Possible Cause
: Power was interrupted while data was in the array accelerator memory. Power was then
restored within several days, and the data in the array accelerator was flushed to the drive array.
Action
: No action is required. No data has been lost. Perform orderly system shutdowns to avoid leaving
data in the array accelerator.
Drive Array
Data in Array Accelerator has been Lost...
(plus one of the following:)
...* Array Accelerator Battery Dep
Error messages
Audible Beeps
: None
Possible Cause
: Array
accelerator is defective or is missing. Depending on the array controller model, the
cache may be disabled or the controller might not be usable until this problem is corrected.
Action
Reseat the array accelerator daughter board if the connector is loose.
If the problem persists, replace the board.
Slot X Drive Array
Array Accelerator Read Error Occurred...
...Data in Array Accelerator has been lost.
Array Accelerator is disabled.
Audible Beeps
: None
Possible Cause
: Hard parity error detected while
reading data from posted
writes memory.
Action
: Replace the array accelerator daughter board.
Slot X Drive Array
Array Accelerator Self
Test Error Occurred...
...Array Accelerator is disabled.
Audible Beeps
: None
Possible Cause
: Array accelerator
failed self
test. Depending on the array controller model, the cache may be
disabled or the controller might not be usable until this problem is corrected.
Action
: Replace the array accelerator daughter board.
Slot X Drive Array
Drive(s) Disabled d
ue to Array Accelerator Data Loss...
...Select “F1” to continue with logical drives disabled.
Select “F2” to accept data loss and to re
enable logical drives.
Audible Beeps
: None
Possible Cause
: One or more logical drives failed due to loss of data in post
writes memory.
Action
Press the
key to continue with the logical drives disabled.
Press the
key to accept data loss and re
enable logical drives. After pressing the
key, check the
integrity of the file system and restore lost data from backup.
1800 Series
Slot X Drive Array
Array Accelerator Super
Cap is charging...
...The Array Accelerator Cache will be enabled once Super
Cap has been charged. No action is r
equired.
Audible Beeps
: None
Possible Cause
: The Array Accelerator Super
Cap is charging.
Action
: No action is required.
Error messages
Slot X Drive Array
Please install Array Accelerator Super
Cap...
...The Array Accelerator Cache will be enabled once Super
Cap
is installed and charged.
Audible Beeps
: None
Possible Cause
: The Array Accelerator Super
Cap needs to be installed.
Action
: Install the Array Accelerator Super
Cap.
ve
nt list error messages
ntroduction to event list
error messages
This section contains event list error messages recorded in the
IML
Integrated Management Log
" on page
), which can be viewed through different tools.
The format of the list is different when viewed through different tools. An example of the format of an event
as displayed on the IMD follows:
WARNING:
To avoid potential problems, ALWAYS read the warnings and cautionary
information in the server documentation before removi
ng, replacing, reseating, or modifying
system components.
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.
NOTE:
The error messages in this section may be worded slightly different than as displayed by
the server.
Error messages
or the
SmartStart Support and Documents website
http://www.hp.com/s
upport/smartstart/documentation
utomatic operating system shutdown initiated due to fan failure
Event Type
: Fan failure
Action
: Replace the fan.
utomatic Operating System
Shutdown Initiated Due to Overheat
Condition...
...Fatal Exception (Number
X, Cause)
Event Type
: Overheating condition
Action
Error messages
Replace the processor.
rocessor Uncorrectable Internal Error (Slot X, Socket Y)
Event
Type
: Uncorrectable error
Action
CAUTION:
Before removing or replacing any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
Replace the processor.
eal
Time Clock Battery Failing
Event Type
: System configuration battery low
Action
: Replace the system configuration battery.
ystem AC Power Overload (Power Supply X)
Event Type
: Power supply overload
Action
Switch the vol
tage from 110
V to 220
V or add an additional power supply (if applicable to the
system).
If the problem persists, remove some of the installed options.
ystem AC Power Problem (Power Supply X)
Event Type
: AC voltage problem
Action
: Check for any power source problems.
ystem Fan Failure (Fan X, Location)
Event Type
: Fan failure
Action
: Replace the fan.
Error messages
ystem Fans Not Redundant
Event Type
: Fans not redundant
Action
: Add a fan or replace the failed fan.
ystem Overheating (Zone X, Location)
Event Type
: Overheating condition
Action
: Check fans.
ystem Power Supplies Not Redundant
Event Type
: Power supply not redundant
Action
: Add a power supply or replace the failed power supply.
ystem Power Supply Failure (Power Sup
ply X)
Event Type
: Power supply failure
Action
: Replace the power supply.
nrecoverable Host Bus Data Parity Error...
...Unrecoverable Host Bus Address Parity Error
Event Type
: Host bus error
CAUTION:
On
ly authorized technicians trained by HP should attempt to remove the system
board. If you believe the system board requires replacement, contact
HP Technical Support
Contacting HP
" on page
) before proceeding.
Action
: Replace the board on which the processor is installed.
ncorrectable Memory Error (Slot X, Memory Module Y)...
...Uncorrectable Memory Error (System Memory)
Uncorrectable Memory Error (Memory Module Unknown)
Event Type
: Uncorrectable error
Action
: Replace the memory module. If the problem persists, replace the memory board.
P BladeSystem
Class
infrastructure error codes
The server blade management modules and power management modules contain service ports
that enable
service personnel to gather fault information.
To gather the fault information:
Connect to the service port. For more information, refer to the
BladeSystem Maintenance and
Service Guide
on the
HP website
http://www.hp.com/products/servers/proliant
bl/p
class/info
Error messages
Access the diagnostics. For more information, refer to the
BladeSystem Maintenance and Service
Guide
on the
HP website
http://www.hp.com/products/servers/proliant
bl/p
class/info
erver blade management module error codes
erver blade error codes
Location
LED codes
Server Blade
Slot 1
1 or 1
Server Blade
Slot 2
1 or 2
Server Blade
Slot 3
1 or 3
Server Blade
Slot 4
1 or 4
Server Blade
Slot 5
1 or 5
Server Blade
Slot 6
1 or 6
Server Blade
Slot 7
1 or 7
Server Blade
Slot 8
1 or 8
Action:
Perform the following steps to resolve the problem. Stop when the problem is resolved.
Reseat the server.
Refer to server documentation on the
HP website
http://www.hp.com/products/servers/proliant
bl/p
class/info
erver blade management module board error codes
LED code:
1, 9
2, 9
4, 9
5, 9
6, 9
7, 9
8, 9
9, 9
10, 9
11, or 9
Location:
Server blade management module
Action:
Perform the following steps to resolve the problem. Stop when the problem is resolved.
Error messages
Error messages
Location:
Interconnect module
side A (10
connector)
Action:
Perform the following steps to resolve the problem. Stop when the problem is resolved.
Press
Error messages
For more information, refer to the
BladeSystem Maintenance and Service Guide
n the
HP website
http://www.hp.com/products/servers/proliant
bl/p
class/info
Replace the interconnect module.
For more information, refer to the
BladeSystem Maintenance and Ser
vice Guide
on the
HP website
http://www.hp.com/products/servers/proliant
bl/p
class/info
nknown server blade management module e
rror code
LED code:
Location:
Unknown
Action:
Perform the following steps to resolve the problem. Stop when the problem is resolved.
Power Supply
Slot 1
1 or 1
Power Supply
Slot 2
1 or 2
Power Supply
Slot 3
1 or 3
Power Supply
Slot 4
1 or 4
Power Supply
Slot 5
1 or 5
Power Supply
Slot 6
1 or 6
Action:
Perform the following steps to resolve the problem. Stop when the problem is resolved.
Reseat the power supply.
For more information, refer to the
BladeSystem Maintenance and Service Guide
on the
HP website
http://www.hp.com/products/servers/proliant
bl/p
class/in
Reseat the power management module.
Replace the power supply.
ower management module board error codes
LED code:
1, 7
2, 7
3, 7
4, 7
5, 7
6, 7
7, 7
8, 7
9, 7
10, 7
11, 7
12, or 7
Location:
Power
management board
Action:
Perform the following steps to resolve the problem. Stop when the problem is resolved.
Reseat the power management module.
Replace the power management module.
ower management module backplane error codes
LED code:
1, 8
2, 8
3, 8
4, 8
5, 8
6, 8
7, or 8
Location:
Power management backplane
Error messages
Action:
Perform the following steps to resolve the problem. Stop when the problem is resolved.
Press the power managemen
t module reset button.
nknown power management module error code
LED code:
Location:
Unknown
Action:
Perform the following steps to resolve the problem. Stop when the problem is reso
lved.
Locate the code in the following table.
For example, if the port 85 code displays "31h," see "
Processor
related port 85 codes
(on page
)"
for more information.
Port 85 code
Description
3xh
Port 85 codes in this format indicate processor
related errors. See "
Processor
related
port 85 codes
(on page
181
)" for more information.
4xh
Port 85 codes in this format indicate memory
related errors. See "
Memory
related
port 85 codes
(on page
182
)" for more information.
6xh
Port 85 codes in this format indicate expansion board
related errors. See "
Expansion
board
related port 85 codes
(on page
)" for more information.
All other codes,
including 00h, 01h,
and 5xh
Port 85 codes in this range cover several areas. See the section "
Miscellaneous port
85 codes
(on page
)" for more information.
Reference the designated section in this guide for the appropriate troubleshooting steps.
ocessor
related port 85 codes
Processor
related port 85 codes display in the format 3xh.
IMPORTANT:
Reboot the server after completing each numbered step. If the error condition
continues, proceed with the next step.
To troubleshoot
processor
related error codes:
Bring the server to base configuration by removing all components that are not required by the server
to complete POST. For more information, see "
Breaking the server down to the minimum hardware
configuration
(on page
)." This process can include removing all:
Expansion boards
DIMMs, except the first bank
Error messages
Hard drives
Peripheral devices
IMPORTANT:
CAUTION:
Before removing or replacing any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
Remove all processors and PPMs, except t
he processor installed in socket 1 and the corresponding
PPM.
CAUTION:
Before replacing or reseating any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system board requiring
replacement of the system board.
Reseat the remaining processors, rebooting after each installation to identify any failed processors.
IMPORTANT:
Populate the
processors in the following order: 1, 2, 4, 3.
IMPORTANT:
Always install a PPM when you install a processor. The system fails to boot if the
PPM is missing.
emory
related port 85 codes
Memory
related port 85 codes display in the format 4xh.
IMPORTANT:
Reboot the server after completing each numbered step. If the error condition
continues, proceed with the next step.
To troubleshoot memory
related error codes:
Check the memory LEDs for any identified errors or failed DIMMs, and take corrective actio
Err
or messages
Bring the server to base configuration by removing all components that are not required by the server
to complete POST. For more information, see "
Breaking the server down to the minimum hardware
configuration
(on page
)." This process can include removing all:
Expansion boards
DIMMs, except the first bank
Hard drives
Peripheral devices
IMPORTANT:
Processor socket 1 and PPM slot 1 must be populated at all times or the server does
not function properly.
CAUTION:
Before removing or replacing any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the
troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
Remove
xpansion board
related port 85 codes
Expansion
board
related port 85 codes display in the format 6xh.
IMPORTANT:
Reboot the server after completing each numbered step. If the error condition
continues, proceed with the next step.
To troubleshoot expansion board
related error codes:
Reseat all
expansion boards.
Bring the server to base configuration by removing all components that are not required by the server
to complete POST. For more information, see "
Breaking the server down to the minimum hardware
configuration
(on page
)." This process can include removing all:
Expansion boards
DIMMs, except the first bank
Hard drives
Peripheral devices
IMPORTANT:
Processor socket 1 and PPM slot 1 must be populated at
all times or the server does
not function properly.
Error messages
CAUTION:
Before removing or replacing any processors, be sure to follow the guidelines
provided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
Remove all processors and PPMs, except the processor installed i
n socket 1 and the corresponding
PPM.
Install the expansion boards one at a time, rebooting between each installation to isolate the failed
expansion board.
Replace the failed expansion board, if applicable.
Replace the PCI riser board, if applicable.
Repl
ace the system board.
IMPORTANT:
If replacing the system board or clearing NVRAM, you must
enter the server
serial number through RBSU
entering the serial number and product ID
" on page
iscellaneous port 85 codes
To troubleshoot all other port 85 codes:
IMPORTANT:
Reboot the server after completing each numbered step. If the error condition
continues, proceed with the next step.
Bring the server to base configuration by removing all components that are not required by the server
to complete POST. For more infor
mation, see "
Breaking the server down to the minimum hardware
configuration
(on page
)." This process can include removing all:
Expansion boards
DIMMs, except the first
bank
Hard drives
Peripheral devices
IMPORTANT:
Processor socket 1 and PPM slot 1 must be populated at all times or the server does
not function properly.
CAUTION:
Before removing or replacing any processors, be sure to follow the guidelines
ovided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system board, requiring
replacement of the system board.
Remove all processors and PPMs, except the processor installed i
n socket 1 and the corresponding
PPM.
Install each remaining system component, rebooting between each installation to isolate any failed
components.
Clear the system NVRAM.
Replace the system board.
IMPORTANT:
If replacing the system board or clearing NVRAM, you must
enter the server
serial number through RBSU
entering the serial number and product ID
" on page
Error messages
indows® Event Log processor error codes
essage ID: 4137
Severity
: Error
Description
: The processor in slot
Replace the processor.
essage ID: 4140
Severity
: Warning
Description
: The system is
operating with a heterogeneous processor environment.
Action
: None
essage ID: 4141
Severity
: Warning
Description
: Only
out of the
installed processors have been started by the operating system. The system
will continue to operate.
Action
: Confirm that the license agreement in use supports all of the installed processors.
essage ID: 4169
verity
: Warning
Description
: The processor in slot
Replace the processor.
essage ID: 4190
Severity
: Error
Error messages
Description
: The system encountered an NMI prior to this boot. The NMI source was "Uncorrectable cache
memory error."
Action
CAUTION:
Before removing or replacing any processors, be sure to follow the gui
delines
provided in "
Performing processor procedures in the troubleshooting process
(on page
)."
Failure to follow the recommended guidelines can cause damage to the system
board, requiring
replacement of the system board.
Replace the processor.
Contacting HP
ontacting HP
ontacting HP technical support or an authorized
reseller
efore contacting HP, always attempt to resolve problems by completing the procedures in this guide.
IMPORTANT:
Collect the appropriate
server information
Server information you need
" on
page
) and
operating system information
Operating system information you need
" on page
) befo
re contacting HP for support.
For United States and worldwide contact information, see the
Contact HP website
http://www.hp.com/go/assistance
In the United States:
To contact HP by phone, call
334
5144. For continuous quality improvement, calls may be
recorded or monitored.
If you have purchased a Care Pack (service upgrade), see the
Support & Drivers website
http://www8.hp.com/u
s/en/support
drivers.html
). If the problem cannot be resolved at the website,
call 1
3600. For more information about Care Packs, see the
HP website
http://pro
sama.houston.hp.com/services/cache/10950
225
121.html
ustomer self repair
What is customer self repair?
HP's customer self
repair program offers you the fastest service
under either warranty or contract. It enables
HP to ship replacement parts directly to you so that you can replace them. Using this program, you can
replace parts at your own convenience.
A convenient, easy
use program:
An HP support specialist will di
Contacting HP
Product name, model, and version
Company name
Specific hardware configurat
ion:
Product name, model, and serial number
Number of processors and speed
Number of DIMMs and their size and speed
List of controllers and NICs
List of connected peripheral devices
List of any other optional HP or Compaq hardware
Network configuration
Specific software information:
Operating system information
Operating system information you need
" on page
List of third
party, HP, and Compaq software installed
PCAnywhere information, if installed
Verification of latest drivers installed
Verification of latest ROM/BIOS
Verification of latest firmware
on array controllers and drives
Results from attempts to clear NVRAM
perating system information you need
Depending on the problem, you may be asked for ce
rtain pieces of information. Be prepared to access the
information listed in the following sections, based on operating system used.
icrosoft® operating systems
Collect the following information:
Whether the operating sy
stem was factory installed
Operating system version number
A current copy of the following files:
WinMSD (Msinfo32.exe on Microsoft® Windows® 2000 systems)
Boot.ini
Memory.dmp
Event logs
Dr. Watson log (drwtsn32.log) if a user mode application, such as the
Insight Agents, is having a
problem
IRQ and I/O address information in text format
An updated Emergency Repair Diskette
If HP drivers are installed:
Version of the PSP used
Contacting HP
List of drivers from the PSP
The drive subsystem and file system information:
Number and size of partitions and logical drives
File system on each logical drive
Current level of Microsoft® Windows® Service Packs and Hotfixes installed
A list of each third
party hardware component installed, with the firmware revision
A list of each
third
party software component installed, with the version
A detailed description of the problem and any associated error messages
inux operating systems
Collect the following information:
Operating system distribution and version
Look for a
Contacting HP
Contacting HP
/etc/conf/cf.d/sdevice
/var/adm/messages (if PANIC messages are displayed)
If HP drivers are installed:
Version of the EFS used
List of drivers from the EFS
If
management agents are installed, version number of the agents
System dumps, if they can be obtained (in case of panics)
A list of each third
party hardware component installed, with the firmware revisions
A list of each third
party software component insta
lled, with the versions
A detailed description of the problem and any associated error messages
BM OS/2 operating systems
Collect the following information:
Operating system version number and printouts or electronic copies (to e
mail to a
support technician)
of:
IBMLAN.INI
PROTOCOL.INI
CONFIG.SYS
STARTUP.CMD
SYSLEVEL information in detail
TRAPDUMP information (if a TRAP error occurs)
A directory listing of:
OS2
OS2
BOOT
HPFS386.INI (for Advanced or Advanced with SMP)
If HP driver
s are installed:
Version of the SSD used
List of drivers from the SSD
Versions of the OS/2 Management Insight Agents, CPQB32.SYS, and OS/2 Health Driver use
The drive subsystem and file system information:
Number and size of partitions and logical drives
File system on each logical drive
Warp Server version used and:
Whether Entry, Advanced, Advanced with SMP, or e
Business
All services running at the time the problem occurred
A list of each third
party hardware component installed, with the firmware revis
ions
A list of each third
party software component installed, with the versions
Contacting HP
A detailed description of the problem and any associated error messages
racle Solaris operating systems
Collect the following information:
Operating syst
em version number
Type of installation selected: Interactive, WebStart, or Customer JumpStart
Which software group selected for installation: End User Support, Entire Distribution, Developer System
Support, or Core System Support
If HP drivers are installe
d with a DU:
DU number
Acronyms and
abbreviations
Acronyms and abbreviations
ABEND
abnormal end
ACPI
Advanced Configuration and Power Interface
ACU
Array Configura
tion Utility
ADG
Advanced Data Guarding (also known as RAID 6)
ADU
Array Diagnostics Utility
AMP
Advanced Memory Protection
Automatic Server Recovery
BMC
baseboard management controller
CCITT
International Telegraph and Telephone Consultative
Committee
CMOS
complementary metal
oxide semiconductor
CPU
central processing unit
cable select
Acronyms and
abbreviations
DMA
direct memory access
driver update
ECC
error checking and correcting
EFS
Extended Feature Supplement
EISA
Extended Industry Standard
Architecture
ESD
electrostatic discharge
FBDIMM
fully buffered DIMM
Firmware Deployment Tool
HP SIM
HP Systems Insight Manager
IDE
integrated device electronics
iLO
Integrated Lights
Out
iLO 2
Integrated Lights
Out 2
iLO 3
Integrated Lights
Out
IMD
Integrated Management Display
Acronyms and
abbreviations
IML
Integrated Management Log
IRQ
interrupt request
KVM
keyboard, video, and mouse
LVD
low
voltage differential
multimedia extensions
NMI
non
maskable interrupt
NVRAM
non
volatile memory
OBDR
One Button
Disaster Recovery
ORCA
Option ROM Configuration for Arrays
PCI
peripheral component interconnect extended
POST
Power
On Self Test
processor power module
PSP
ProLiant Support Pack
PXE
Preboot Execution Environment
Acronyms and
abbreviations
RBSU
ROM
Based Setup Utility
RIS
reserve information sector
RPM
Red Hat Package Manager
Acronyms and
abbreviations
VCRM
Version Control Repository Manager
VGA
video graphics array
Index
accelerator error log
accelerator status
93, 94, 95
ACPI support
ACU (Array Configuration Utility)
adapters
95, 100
additional
information
ADG enabler dongle is broken or missing
ADU (Array Diagnostic Utility)
ADU error messages
92, 112
Advanced ECC support
Advanced Memory Protection (AMP)
122, 123
advisories
application software problems
array
accelerator
112
array accelerator battery pack
170
array accelerator board
92, 93, 95, 99, 100,
102, 110, 112, 148, 149, 151, 170
array accelerator memory size change
command syntax
command
line syntax error
common problem resolution
common problems
configuration errors
107, 108, 135
configuration of system
68, 90
configuration signature
configuration
tools
connection errors
58, 59
connection problems
20, 57
contacting authorized reseller
contacting HP
186, 187
contacting technical support
186
controller
109, 110, 112
controller failure
96, 150
controller state
116
Index
Index
controllers,
array
96, 97, 103, 109, 158, 159
critical error
CSR (customer self repair)
186
customer self repair (CSR)
186
data loss
data recovery
43, 47
DDR3 memory configuration
deployment, offline
deployment, online
device driver
information
diagnose tab, HP Insight Diagnostics
diagnosing problems
diagnostic tools
73, 74, 76
diagnostics
Diagnostics tasks
diagnostics utility
dial tone
DIMM installation guidelines
DIMMs
21, 126, 128, 130,
131, 136, 137, 138
dirty data
disable command issued
disaster recovery
diskette drive
diskette drive problems
44, 141, 142
DMA error
124
documentation
drive array controller
147, 148
drive erase operation
156
drive errors
44, 57, 97, 98, 99, 102, 105, 110,
128, 141, 142
drive failure
57, 104
drive failure, detecting
drive LEDs
22, 44
drive monitoring not enabled
drive not found
44, 46
drive not responding
drive not stamped for monitoring
104
drive
offline due to erase operation
116, 117
drive problems
43, 44, 45, 104, 105
drive replaced, no problem found
105
drive time
out occurred
drivers
78, 89
drives, troubleshooting
DVD
ROM drive
ECC errors
EISA expansion bus master
timeout
173
electrostatic discharge
end user license agreement (EULA)
84, 85
energy saver features
erase operation
116, 117
Erase Utility
error codes, HP BladeSystem p
Class
infrastructure
error codes, processor
error code
s, Windows Event Log processor
184
error log
error messages
62, 65, 92, 112, 122, 172, 175
error messages, ADU
error messages, event list
error messages, POST
122
EULA (end user license agreement)
84, 85
event list error messages
expansion board
60, 89
expansion board problems
expansion board
related port 85 codes
express port error
124
external device problems
fan assembly
143, 145
fan LED
fan problems
48, 49, 123, 124
fans
48, 49, 123, 124, 12
5, 144, 145, 173
fault
tolerance methods
FBDIMMs
21, 49
features
8, 88
Fibre Channel adapters
firmware
66, 79, 89, 96, 106
firmware maintenance
Firmware Maintenance CD
79, 84, 85
firmware, updating
20, 66, 81, 83
firmware,
upgrading
20, 66, 83, 104, 159
firmware, version
flash ROM
66, 81
flowcharts
front side bus error
general diagnosis flowchart
general protection fault
getting started
global protocol error
graphics adapter problem
graphics card option
Index
guided troubleshooting
guidelines, cabling
hard drive guidelines
hard drive LED combinations
hard drive LEDs
22, 45
hard drive problems, diagnosing
hard drive, failure of
hard drives
21,
22, 45
hard drives, determining status of
hard drives, moving
46, 47
hardware features
hardware problems
38, 40
hardware supported
hardware troubleshooting
38, 40, 41, 43, 54
health driver
health LEDs
hotfixes
hot
plug P
CI slot, power fault
128
how to use this guide
HP BladeSystem infrastructure error codes
175
HP Care Pack Services
81, 88
HP Enterprise Configurator
HP Guided Troubleshooting website
HP Insight Diagnostics
76, 172
HP Insight
Diagnostics survey functionality
HP Insight Remote Support software
HP ProLiant Essentials Foundation Pack
HP Smart Update Manager overview
HP Smart Update Manager, deployment
HP Systems Insight Manager overview
45, 90, 91
HP tec
hnical support
186
HP troubleshooting resources
HP website
hub link error
IBM OS/2
190
illegal opcode
125
illegal operator handler
iLO (Integrated Lights
Out)
74, 90, 132
iLO messages
IMD (Integrated Management
Display)
172
IML (Integrated Management Log)
51, 77, 135,
Important Safety Information document
information required
186, 187
infrastructure error codes
Insight Diagnostics
76, 78, 172
installation and configuration
installation
instructions
88, 89
insufficient adapter resources
Integrated Lights
Out (iLO)
74, 90, 132
Integrated Management Log (IML)
77, 172
inter
controller link connection
100
internal health LED
internal system problems
invalid password
126
keyboard
56, 127, 128
keyboard problems
56, 127, 128, 140
KVM
55, 56
LED combinations, hard drive
LED combinations, SAS hard drive
LED combinations, SATA hard drive
LED combinations, SCSI hard drive
LEDs
LEDs, hard
drive
LEDs, PPM failure
51, 52
LEDs, processor failure
LEDs, troubleshooting
Linux
64, 188
local I/O cable
logical drive
100, 151
logical drive attachment detected
logical drive expansion process
160
logical drive
state
117, 118
logical drive, failure of
100, 101, 102, 148, 151
logical drive, migrating
148, 149
loose connections
20, 104
maintenance and service guide
Management CD
90, 91
management tools
media issue, tape drive
memory
89, 126, 135, 136, 137, 138, 173
memory boards
139
memory count error
memory error
112, 135, 136, 175
memory not recognized
memory problems
49, 50
memory requirements
memory, configuring
90, 136, 137, 138
Index
memory, interleaving
memory, mirrored
70, 71, 139
memory, RAID
70, 139
memory
related port 85 codes
181
Microsoft operating systems
187
Mini SAS cable
minimum hardware configuration
mirror data miscompare
mirrored memory
70, 71, 123
miscellaneous port
85 codes
modem problems
modems
57, 58
monitor
54, 55
mouse
mouse problems
network connection problems
network controller problems
network controllers
59, 60
network interconnect blades
new hardware
NMI
event
124, 125, 127
no dial tone
non
system disk message
notices
Novell NetWare
189
NVRAM error
offline deployment
One Button Disaster Recovery
131
online deployment
Online ROM Flash Component Utility
online
spare memory
70, 122, 138
online troubleshooting resources
operating system crash
operating system problems
61, 62, 173
operating system updates
operating system version support
79, 90
operating systems
61, 62, 64, 79, 90, 187
operat
ing systems supported
79, 90
option ROM
Option ROM Configuration for Arrays (ORCA)
Oracle Solaris
62, 191
ORCA (Option ROM Configuration for Arrays)
OS boot problems flowchart
overheating
panic error
parallel port
141
parameters
parity errors
92, 99, 128
part numbers
88, 89
passwords
patches
PCI boards
PCI bus error
PCI device
131, 132
PCI expansion slots
128
PCI slot, power fault
128
performance optimization scan
152
performance
threshold violated for the drive
104,
phone numbers
186
physical drive state
port 85 code, expansion board
related
182
port 85 code, list
port 85 code, memory
related
port 85 code, miscellaneous
port 85 code,
processor
related
180
port 85 code, troubleshooting
port 85 code, viewing
180
POST error messages
103, 111, 122
POST error messages, 100 series
133
POST error messages, 1100 series
142
POST error messages, 1600 series
142
POST error messa
ges, 1700 series
146
POST error messages, 200 series
135
POST error messages, 300 series
140
POST error messages, 400 series
141
POST error messages, 600 series
141
POST error messages, non
numeric
122
POST problems flowchart
31, 32, 33
power
calculator
power cord
power fault
128
power management module error codes
179, 180
power module
172
power problems
38, 39
power regulator
power source
power supplies
38, 127, 129, 131, 145, 146,
175, 179
power supply failure
errors
179
powering down
123
powering on problems
123
powering up
Index
power
on problems flowchart
28, 30
PPM (processor power module)
51, 52, 126
PPM failure LEDs
51, 52
PPM problems
51, 139
PPM slots
pre
diagnostic steps
prediciv
ROM
Based Setup Utility (RBSU)
43, 68
ROMPaq Disaster Recovery
66, 82
ROMPaq utility
74, 75, 83
safety considerations
safety information
SAS and SATA hard drive guidelines
SAS drives
21, 22
SAS hard drive guidelines
SAS hard drive LEDs
SAS/SATA LED combinations
SATA hard drive
21, 22, 46
SATA hard drive
guidelines
SATA hard drive LEDs
SCO
scripted installation
SCSI bus termination error
162
SCSI hard drive
21, 45, 46
SCSI hard drive guidelines
SCSI port cabling
163
SD card
serial number
server blade management mod
ule error
codes
176, 177, 178, 179
server documentation
87, 88, 89, 90
server does not boot
server fault indications flowchart
34, 35, 37
server features and options
server management
90, 91
server response time
Index
22, 38
troubleshooting flowcharts
troubleshooting
procedures, processor
troubleshooting resources
13, 24, 87
Trusted Platform Module (TPM)
23, 47, 49, 60, 66,
uncorrectable memory error
175
unknown disable code
110
unknown error code
180
unknown problem
unrecoverable host bus
data parity error
175
unrecoverable read error
unsupported array accelerator battery
attached
unsupported processor configuration
110
unsupported processor stepping
unsupported wattage
updating the firmware
83, 86
updating the
operating system
updating the system ROM
75, 86
UPS (uninterruptible power supply)
39, 40
USB drive key
47, 83, 84, 85
USB support
using this guide
utilities
utilities, deployment
Version Control Repository Manager (VCRM)
video adapter problems
video colors
video problems
54, 55
Index
warning messages
110, 111
warnings
15, 88
website, HP
87, 88
websites, reference
24, 87
what's new
when to reconfigure or reload software
white papers
87, 89
Windows Event Log processor error codes
184
HP ProLiant Servers Troubleshooting Guide