Page 1: Troubleshooting Guide
HP ProLiant Servers Troubleshooting Guide Part Number 375445-009 June 2010 (Ninth Edition)
Page 2 © Copyright 2004, 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Page 3: Table Of Contents
Contents Introduction ..........................8 What's new ..............................8 Revision history ............................8 375445-xx8 (July 2009) ........................8 375445-xx7 (November 2008) ......................9 375445-xx6 (September 2007)......................10 375445-xx5 (June 2006) ........................10 375445-xx4 (May 2006) ......................... 10 375445-xx3 (September 2005)......................11 Getting started ..........................
Page 4 Problems with new hardware ......................39 Unknown problem ..........................40 Third-party device problems ......................40 Internal system problems ..........................41 Battery pack problems ........................41 CD-ROM and DVD drive problems ..................... 41 Diskette drive problems ........................42 Drive problems (hard drives and solid state drives) ................43 SD card problems ..........................
Page 5 ROMPaq utility ..........................72 Remote Insight Lights-Out Edition II ..................... 73 iLO and iLO 2 technology ......................... 73 Integrated Lights-Out 3 technology ..................... 73 Erase Utility ............................. 74 Redundant ROM support ........................74 USB support ............................ 74 Diagnostic tools ............................75 HP Insight Diagnostics ........................
Page 6 Device driver information ........................88 DDR3 memory configuration......................89 Operating System Version Support ..................... 89 Operating system installation and configuration information (for factory-installed operating systems) ..89 Server configuration information ......................89 Installation and configuration information for the server setup software ..........89 Software installation and configuration of the server ................
Page 7 Processor-related port 85 codes ....................... 166 Memory-related port 85 codes......................167 Expansion board-related port 85 codes .................... 167 Miscellaneous port 85 codes ......................168 Windows® Event Log processor error codes ....................169 Message ID: 4137 ......................... 169 Message ID: 4140 ......................... 169 Message ID: 4141 .........................
Page 8: Introduction
Introduction What's new The ninth edition of the HP ProLiant Servers Troubleshooting Guide, part number 375445-xx9, includes the following additions and updates: • Added new section to Getting started (on page 12): Breaking the server down to the minimum hardware configuration (on page 17) •...
Page 9: 375445-Xx7 (November 2008)
• Added information to the introduction for the server power-on problems flowchart (on page 27). • Added new steps to Power problems (on page 37). • Added a new section to Fan problems (on page 46): All fans in an HP ProLiant G6 server are not spinning or are not spinning at the same speed (on page 47) •...
Page 10: 375445-Xx6 (September 2007)
375445-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 preventing electrostatic discharge (on page 15). • Added new DIMM handling guidelines (on page 19). •...
Page 11: 375445-Xx3 (September 2005)
375445-xx3 (September 2005) The third edition of the HP ProLiant Servers Troubleshooting Guide, part number 375445-xx3, included the following changes: • Updated SCSI hard drive guidelines • Added hot-plug SCSI hard drive LED combinations (on page 20) • Updated diagnostic flowcharts (on page 23) •...
Page 12: Getting Started
Getting started HP ProLiant 100 Series Server troubleshooting information For HP ProLiant 100 Series Server troubleshooting information, see the respective server user guides. How to use this guide NOTE: For common troubleshooting procedures, the term "server" is used to mean servers and server blades.
Page 13: Pre-Diagnostic Steps
ADU error messages (on page 91) POST error messages and beep codes (on page 115) Event list error messages (on page 157) HP BladeSystem infrastructure error codes ("HP BladeSystem p-Class infrastructure error codes" on page 161) Port 85 codes and iLO messages (on page 165) Pre-diagnostic steps WARNING: To avoid potential problems, ALWAYS read the warnings and cautionary...
Page 14: Warnings And Cautions
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 receptacle. This symbol indicates the presence of a hot surface or hot component. If this surface is contacted, the potential for injury exists.
Page 15: Electrostatic Discharge
WARNING: To reduce the risk of personal injury or damage to the equipment: • Observe local occupation health and safety requirements and guidelines for weight in kg manual handling. weight in lb Obtain adequate assistance to lift and stabilize the chassis during installation or •...
Page 16: Symptom Information
For more information on static electricity or assistance with product installation, contact an authorized reseller. Symptom 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? •...
Page 17: Breaking The Server Down To The Minimum Hardware Configuration
Breaking the server down to the minimum hardware configuration During the troubleshooting process, you may be asked to break the server down to the minimum hardware configuration. A minimum configuration consists of only the components needed to boot the server and successfully pass POST. When requested to break the server down to the minimum configuration, uninstall the following components, if installed: •...
Page 18: Common Problem Resolution
Common problem resolution Loose 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.
Page 19: Dimm Handling Guidelines
DIMM 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 15). • Always hold DIMMs by the side edges only. •...
Page 20: Hard Drive Led Combinations
• Drives must be the same capacity to provide the greatest storage space efficiency when drives are grouped together into the same drive array. Hard drive LED combinations Hot-plug SCSI hard drive LED combinations Activity Online Fault Interpretation LED (1) LED (2) LED (3) On, off,...
Page 21: Server Updates With An Hp Trusted Platform Module And Bitlocker™ Enabled
Interpretation Online/activity Fault/UID LED LED (green) (amber/blue) On, off, or Alternating amber The drive has failed, or a predictive failure alert has been flashing and blue received for this drive; it also has been selected by a management application. Steadily blue On, off, or The drive is operating normally, and it has been selected by a flashing...
Page 22 • Moving a BitLocker™-protected drive to another server • Adding an optional PCI device, such as a storage controller or network adapter Common problem resolution 22...
Page 23: Diagnostic Flowcharts
Diagnostic flowcharts Troubleshooting flowcharts To effectively troubleshoot a problem, HP recommends that you start with the first flowchart in this section, "Start diagnosis flowchart (on page 25)," 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 25)."...
Page 24 Under Product support, select the product. Select Manuals (guides, supplements, addendums, etc). Under Service and maintenance information, locate the link for the maintenance and service guide. 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.
Page 25: Start Diagnosis Flowchart
Start diagnosis flowchart Use the following flowchart to start the diagnostic process. General diagnosis flowchart Diagnostic flowcharts 25...
Page 26 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 26...
Page 27: Power-On Problems Flowchart
Power-on problems flowchart Server 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.
Page 28 Diagnostic flowcharts 28...
Page 29 p-Class server blade power-on problems flowchart c-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). Symptoms: • The server does not power on. Diagnostic flowcharts 29...
Page 30: Post Problems Flowchart
• 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 POST problems flowchart Symptoms: •...
Page 31 NOTE: The server has completed POST when the system attempts to access the boot device. • Server completes POST with errors Possible problems: • Improperly seated or faulty internal component • Faulty KVM device • Faulty video device Server and p-Class server blade POST problems flowchart Diagnostic flowcharts 31...
Page 32: Operating System Boot Problems Flowchart
c-Class server blade POST problems flowchart Operating 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 • Incorrect boot order setting in RBSU Diagnostic flowcharts 32...
Page 33: Server Fault Indications Flowchart
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 blade. Server fault indications flowchart Symptoms: •...
Page 34 • 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 •...
Page 35 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 35...
Page 36 c-Class server blade fault indications flowchart Diagnostic flowcharts 36...
Page 37: Hardware Problems
Hardware problems Procedures 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. Power problems Power source problems Action: Press the Power On/Standby button to be sure it is on.
Page 38: Ups Problems
UPS problems UPS is not working properly Action: Be sure the UPS batteries are charged to the proper level for operation. See the UPS documentation for details. Be sure the UPS power switch is in the On position. See the UPS documentation for the location of the switch.
Page 39: General Hardware Problems
General hardware problems Problems 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.
Page 40: Unknown Problem
Be sure all boards are properly installed in the server. To see if the utility recognizes and tests the device, run HP Insight Diagnostics (on page 75). Uninstall the new hardware. Unknown problem Action: Disconnect power to the server. Following the guidelines and cautionary information in the server documentation, strip the server to its most basic configuration by removing every card or device that is not necessary to start the server.
Page 41: Internal System Problems
To a different slot on the same bus (not applicable for PCI Express) To a PCI, PCI-X, or PCI Express slot on a different bus To the same slot in another working server of the same or similar design If the board works in any of these slots, either the original slot is bad or the board was not properly seated.
Page 42: Diskette Drive Problems
Refer to the operating system and server documentation to be sure both support booting from a USB CD-ROM drive. Be sure legacy support for a USB CD-ROM drive is enabled in RBSU. Data read from the drive is inconsistent, or drive cannot read data Action: Clean the drive and media.
Page 43: Drive Problems (Hard Drives And Solid State Drives)
Drive is not found Action: Be sure no loose connections (on page 18) exist with the drive. Non-system disk message is displayed Action: Remove the non-system diskette from the drive. Check for and disconnect any non-bootable USB devices. Diskette drive cannot write to a diskette Action: If the diskette is not formatted, format the diskette.
Page 44 • If the drive fault LED is illuminated, see the drive LED combination tables in "Hard drive LED combinations (on page 20)." • If the drive fault LED is flashing, replace the hard drive. See the server maintenance and service guide.
Page 45 Action: Check the hard drive LEDs to be sure they indicate normal function. For information on hard drive LEDs, see hard drive LED combinations (on page 20). 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 18) exist.
Page 46: Sd Card Problems
SD card problems System does not boot from the drive Action: Be sure the drive boot order in RBSU is set so that the server boots from the SD card. Reseat the SD card. USB drive key problems System does not boot from the drive Action: Be sure that USB is enabled in RBSU.
Page 47: Hp Trusted Platform Module Problems
Check the LEDs to be sure the hot-plug fans are working. Refer to the server documentation for LED information. NOTE: For servers with redundant fans, backup fans may spin up periodically to test functionality. This is part of normal redundant fan operation. Be sure no POST error messages ("POST error messages and beep codes"...
Page 48: Memory Problems
• HP is not liable for blocked data access caused by improper TPM use. For operating instructions, see the encryption technology feature documentation provided by the operating system. Memory problems General memory problems are occurring Action: • Isolate and minimize the memory configuration. Use care when handling DIMMs ("DIMM handling guidelines"...
Page 49 Server fails to recognize existing memory Action: Reseat the memory. Use care when handling DIMMs ("DIMM handling guidelines" on page 19). Be sure the memory is configured properly. See the server documentation. Be sure a memory count error did not occur ("Memory count error exists"...
Page 50: Ppm Problems
If the system is configured with HP iLO 2 Firmware version 1.77 or later, the IML message reports the following message: Memory Configuration Error: System boot halted For more information, see the server documentation on the HP website (http://www.hp.com/support). PPM problems Action: If the PPMs are not integrated on the system board: CAUTION: Do not operate the server for long periods with the access panel open or...
Page 51: Tape Drive Problems
processor and its associated PPM (if applicable) one by one, restarting each time, to find the faulty processor or processors. At each step, be sure the server supports the processor configurations. Tape drive problems The following sections include the most common tape drive issues. Actions are listed in the order that they should be tried.
Page 52: Graphics And Video Adapter Problems
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.
Page 53: System Open Circuits And Short Circuits
• Be sure the adapter is seated properly. System 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.
Page 54: Mouse And Keyboard Problems
Be sure the video driver is current. Refer to the third-party video adapter documentation for driver requirements. Be sure a video expansion board, such as a RILOE board, has not been added to replace onboard video, making it seem like the video is not working. Disconnect the video cable from the onboard video, and then reconnect it to the video jack on the expansion board.
Page 55: Audio Problems
Replace the device with a known working equivalent device (another similar mouse or keyboard). If the problem still occurs with the new mouse or keyboard, the connector port on the system I/O board is defective. Replace the board. If the problem no longer occurs, the original input device is defective. Replace the device. Be sure the keyboard or mouse is connected to the correct port.
Page 56: Modem Problems
Modem problems No dial tone exists Action: 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.
Page 57 Modem does not connect to another modem Action: Be sure a dial tone exists. Be sure the line is not in use at another extension before using it. Be sure you are dialing the correct telephone number. Be sure the modem on the other end is working. Modem disconnects while online Action: Be sure no loose connections (on page 18) exist.
Page 58: Network Controller Problems
You are unable to connect at 56 Kbps Action: Find out the maximum baud rate at which the ISP connects, and change the settings to reflect this. Reattempt to connect at a lower baud rate. Be sure no line interference exists. Retry the connection by dialing the number several times. If conditions remain poor, contact the telephone company to have the line tested.
Page 59: Expansion Board Problems
Network controller stopped working when an expansion board was added Action: Be sure no loose connections (on page 18) exist. Be sure the server and operating system support the controller. Refer to the server and operating system documentation. Be sure the new expansion board has not changed the server configuration, requiring reinstallation of the network driver.
Page 60: Software Problems
Software 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 configuration. Other useful resources include HP Insight Diagnostics (on page 75) and HP SIM. Use either utility to gather critical system hardware and software information and to help with problem diagnosis.
Page 61: Operating System Updates
Errors are displayed in the error log Action: Follow the information provided in the error log, and then refer to the operating system documentation. Problems occur after the installation of a service pack Action: Follow the instructions for updating the operating system ("Operating system updates"...
Page 62: Restoring To A Backed-Up Version
If you decide to apply an operating system update: Perform a full system backup. Apply the operating system update, using the instructions 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).
Page 63: Linux Operating Systems
using the NSS/PoolVerify command followed by the NSS/PoolRebuild command, if necessary. Refer to the NetWare documentation for more information. Caldera UnixWare and SCO OpenServer from Caldera—Emergency boot diskette. Refer to the Caldera UnixWare or SCO OpenServer from Caldera documentation for more information. Sun Solaris—Device Configuration Assistant boot diskette.
Page 64: Rom Problems
• 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. ROM problems Remote ROM flash problems General remote ROM flash problems are occurring Action: Be sure you follow these requirements for using the Remote ROM flash utility: •...
Page 65: Boot Problems
Network connection fails on remote communication Because network connectivity cannot be guaranteed, it is possible for the administrative client to become disconnected from the target server during the ROM flash preparation. If any remote connectivity procedure fails during the ROM flash online preparation, the ROM flash does not occur for the target system.
Page 66 • The server fails to boot after a SYSROM update using ROMPaq. Action: Servers (non-blades) If the system ROM is corrupted, the system 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.
Page 67: Software Tools And Solutions
Software tools and solutions Configuration tools SmartStart software SmartStart is a collection of software that optimizes single-server setup, providing a simple and consistent way to deploy server configuration. SmartStart has been tested on many ProLiant server products, resulting in proven, reliable configurations. SmartStart assists the deployment process by performing a wide range of configuration activities, including: •...
Page 68: Using Rbsu
• Configuring system devices and installed options • Enabling and disabling system features • Displaying system information • Selecting the primary boot controller • Configuring memory options • Language selection For more information on RBSU, see the HP ROM-Based Setup Utility User Guide on the Documentation CD or the HP website (http://www.hp.com/support/smartstart/documentation).
Page 69: Boot Options
To change any ORCA default settings and override the auto-configuration process, press the F8 key when prompted. By default, the auto-configuration process configures the system for the English language. To change any default settings in the auto-configuration process (such as the settings for language, operating system, and primary boot controller), execute RBSU by pressing the F9 key when prompted.
Page 70: Array Configuration Utility
Array 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 •...
Page 71: Option Rom Configuration For Arrays
• Partition types, sizes, or layout • Software RAID information • Operating system device names or mount points Option 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.
Page 72: Management Tools
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 the manufacturing process and should NOT be modified. This option should only be used by qualified service personnel. This value should always match the serial number sticker located on the chassis.
Page 73: Remote Insight Lights-Out Edition Ii
For example: http://www.hp.com/support/dl360g6 Remote Insight Lights-Out Edition II RILOE II enables browser access to servers through a hardware-based, OS-independent graphical remote console. Some of the features include virtual diskette drive and power button, server management through any standard browser, dedicated LAN connectivity, automatic network configuration, external power backup, group administration, and functions available with the Remote Insight Board.
Page 74: Erase Utility
• 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).
Page 75: Diagnostic Tools
• Diagnostics • • Operating environments which do not provide native USB support Diagnostic tools HP 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 problems, and perform repair validation.
Page 76: Integrated Management Log
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.com/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...
Page 77: Remote Support And Analysis Tools
Remote support and analysis tools HP Insight Remote Support software HP Insight Remote Support software delivers secure remote support for your HP Servers and Storage, 24 X 7, so you can spend less time solving problems and more time focused on your business. You can have your systems remotely monitored for hardware failure using secure technology that has been proven at thousands of companies around the world.
Page 78: Version Control
If you do not use the SmartStart CD to install an OS, drivers for some 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 drivers for a particular server, enter the following web address into the browser: http://www.hp.com/support/<servername>...
Page 79: Hp Smart Update Manager
HP Smart Update Manager The HP Smart Update Manager provides intelligent and flexible firmware and software deployment. This technology assists in reducing the complexity of provisioning and updating HP ProLiant Servers, options, and Blades within the datacenter. HP SUM is delivered on The Smart Update Firmware DVD, ProLiant Support Packs, and Easy Set-up CDs.
Page 80: Subscriber's Choice
Subscriber's choice HP's Subscriber's Choice is a customizable 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).
Page 81: Automatic Backup
A system reboot is required 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 Recovery 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.
Page 82: Verifying Firmware Versions
• HP Onboard Administrator for HP c-Class BladeSystem NOTE: The Onboard Administrator and NIC firmware are only supported in online deployments. Verifying firmware versions To locate and verify the most current firmware versions, use the following tools: • Insight Diagnostics Online Edition ("HP Insight Diagnostics"...
Page 83: System Rompaq Firmware Upgrade Utility
This procedure is most effective when flashing the ROM on a small number of servers located in close proximity. 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).
Page 84: Offline Deployment
Offline deployment To deploy components in an offline manner: Boot the server from the Firmware Maintenance CD or a USB drive key. At the prompt, select a language and keyboard. Click Continue. Read the End-User License Agreement. If you agree to the terms of the license agreement, click Agree to continue.
Page 85: Unsupported Processor Stepping With Intel® Processors
Unsupported processor stepping with Intel® 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®...
Page 86: Hp Resources For Troubleshooting
HP resources for troubleshooting Online resources HP Technical Support website Troubleshooting tools and information, as well as the latest drivers and flash ROM images, are available on the HP website (http://www.hp.com/support). HP Guided Troubleshooting website HP Guided Troubleshooting is available for many products and components on the HP website (http://www.hp.com/support/gts).
Page 87: Hp Care Pack Services
To create a profile 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).
Page 88: Teardown Procedures, Part Numbers, Specifications
Teardown 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) Technical topics Refer to white papers on one of the following: •...
Page 89: Ddr3 Memory Configuration
DDR3 memory configuration See the DDR3 Memory Configuration Tool on the HP website (http://www.hp.com/go/ddr3memory- configurator). Operating System Version Support For information about specific versions of a supported operating system, refer to the operating system support matrix (http://www.hp.com/go/supportos). Operating system installation and configuration information (for factory-installed operating systems) Refer to the factory-installed operating system installation documentation that ships with the server.
Page 90: Installation And Configuration Information For The Server Management System
Installation and configuration information for the server management system Refer to the HP Systems Insight Manager Installation and User Guide on the Management CD or the HP website (http://www.hp.com/go/hpsim). Fault tolerance, security, care and maintenance, configuration and setup Refer to the server documentation available in the following locations: •...
Page 91: Error Messages
Error messages ADU error messages Introduction to ADU error messages This section contains a complete alphabetical list of all ADU ("Array diagnostic software" on page 76) 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.
Page 92 Accelerator Status: Cache was Automatically Configured During Last Controller Reset Description: Cache board was replaced with one of a different size. Action: No action is required. Accelerator Status: Data in the Cache was Lost..due to some reason other than the battery being discharged. Description: Data in cache was lost, but not because of the battery being discharged.
Page 93 Accelerator Status: Obsolete Data Detected Description: During reset initialization, obsolete data was found in the cache due to the drives being moved and written to by another controller. Action: No action is required. The controller either writes the data to the drives or discards the data completely.
Page 94: Array Accelerator Battery Pack X Not Fully Charged
Accelerator Status: Warranty Alert Description: Catastrophic problem exists with array accelerator board. Refer to other messages on Diagnostics screen for exact meaning of this message. Action: Replace the array accelerator board. Adapter/NVRAM ID Mismatch Description: EISA NVRAM has an ID for a different controller from the one physically present in the slot. Action: Run the server setup utility.
Page 95: Configuration Signature Is Zero
Configuration Signature is Zero Description: ADU ("Array diagnostic software" on page 76) detected that NVRAM contains a configuration signature of zero. Old versions of the server setup utility could cause this. Action: Run the latest version of server setup utility to configure the controller and NVRAM. Configuration Signature Mismatch Description: The array accelerator board is configured for a different array controller board.
Page 96: Controller Restarted With A Signature Of Zero
Controller Reported POST Error. Error Code: X Description: The controller returned an error from its internal POST. Action: Replace the controller. Controller Restarted with a Signature of Zero Description: ADU ("Array diagnostic software" on page 76) did not find a valid configuration signature to use to get the data.
Page 97 Drive (Bay) X is a Replacement Drive Description: This drive has been replaced. This message is displayed if a drive is replaced in a fault- tolerant logical volume. Action: If the replacement was intentional, allow the drive to rebuild. Drive (Bay) X is a Replacement Drive Marked OK Description: The drive has been replaced and marked OK by the firmware, in one of three possible scenarios: the drive was replaced in a non-fault-tolerant configuration;...
Page 98: Drive Monitoring Features Are Unobtainable
Drive Monitoring Features Are Unobtainable Description: ADU ("Array diagnostic software" on page 76) 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.
Page 99: Identify Logical Drive Data Did Not Match With Nvram
Identify Logical Drive Data did not Match with NVRAM Description: The identify unit data from the array controller does not match with the information stored in NVRAM. This can occur if new, previously configured drives have been placed in a system that has also been previously configured.
Page 100 Action: Check for drive failures, wrong drive replaced, or loose cable messages. If a drive failure occurred, replace the failed drive or drives, and then restore the data for this logical drive from the tape backup. Otherwise, follow the procedures for correcting problems when an incorrect drive is replaced or a loose cable is detected.
Page 101: Mirror Data Miscompare
Logical Drive X Status = Recovering (rebuilding data on a replaced drive) Description: A physical drive in this logical drive has failed and has now been replaced. The replaced drive is rebuilding from the mirror drive or the parity data. Action: No action is required.
Page 102: One Or More Drives Is Unable To Support Redundant Controller Operation
One or More Drives is Unable to Support Redundant Controller Operation Description: At least one drive in use does not support redundant controller operation. Action: Replace the drive that does not support redundant controller operation. Other Controller Indicates Different Hardware Model Description: The other controller in the redundant controller configuration is a different hardware model.
Page 103: Ris Copies Between Drives Do Not Match
RIS Copies Between Drives Do Not Match Description: The drives on this controller contain copies of the RIS that do not match. The hard drives in the array do not have matching configuration information. Action: Resolve all other errors encountered. Obtain the latest version of ADU, and then rerun ADU ("Array diagnostic software"...
Page 104: Set Configuration Command Issued
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. SCSI Port X, Drive ID Y RIS Copies Within This Drive Do Not Match Description: The copies of RIS on the drive do not match.
Page 105: Soft Firmware Upgrade Required
Soft firmware upgrade required Description: ADU ("Array diagnostic software" on page 76) 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"...
Page 106: Storage Enclosure On Scsi Bus X Indicated That The Fan Is Degraded
Description: The cooling fan located in the external storage unit has failed. Action: Replace the fan. Storage Enclosure on SCSI Bus X Indicated that the Fan is Degraded..SOLUTION: this condition usually occurs on enclosures with multiple fans and one of those fans has failed. Replace any fans not operating properly.
Page 107 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. Swapped Cables or Configuration Error Detected. An Unsupported Drive Arrangement Was Attempted..SOLUTION: Power down system then move drives back to their original location.
Page 108: System Board Is Unable To Identify Which Slots The Controllers Are In
Description: More logical drives were created than are supported on this controller, causing lost logical drive volumes. Action: 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. System Board is Unable to Identify which Slots the Controllers are in Description: The slot indicator on the system board is not working correctly.
Page 109: Unknown Disable Code
Unable 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. Unable to Retrieve Identify Controller Data. Controller May be Disabled or Failed ...SOLUTION: Power down the system.
Page 110 WARNING - 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.
Page 111: Adu Version 8.0 Through 8.28 Error Messages
Write 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 incomplete connection between the cache and the controller. This is not a data loss circumstance. Action: Power down the system and be sure that the cache board is fully connected to the controller.
Page 112 Array Accelerator: This controller has been set up to be a part of a redundant pair of controllers..but the array accelerator cache sizes are different on the two controllers. Make certain that both controllers are using array accelerators with the same amount of cache memory installed. Action: Adjust the memory installed in the array accelerators to matching sizes.
Page 113 Drive 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 70). Drive Offline due to Erase Operation: The physical drive is offline from having an erase in progress.
Page 114 Logical 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. Logical drive state: The logical drive is queued for expansion. Action: No action is required.
Page 115: Post Error Messages And Beep Codes
Action: No action is required. Redundancy State: This controller has been setup to be part of a redundant pair of controllers..but redundancy is disabled. Redundancy is disabled for an unknown reason. Action: Contact HP support ("Contacting HP" on page 173). Redundant Path Failure: Multi-domain path failure Action: Check the storage device I/O module and cables to restore redundant paths.
Page 116: Non-Numeric Messages Or Beeps Only
Non-numeric messages or beeps only Advanced Memory Protection mode: Advanced ECC Audible Beeps: None Possible Cause: Advanced ECC support is enabled. Action: None. Advanced Memory Protection mode: Advanced ECC with hot-add support Audible Beeps: None Possible Cause: Advanced ECC with Hot-Add support is enabled. Action: None.
Page 117: Fatal Dma Error
Critical Error Occurred Prior to this Power-Up Audible Beeps: None Possible Cause: A catastrophic system error, which caused the server to crash, has been logged. Action: Run Insight Diagnostics ("HP Insight Diagnostics" on page 75) and replace failed components as indicated.
Page 118: Fatal Global Protocol Error
Fatal 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 75) and replace failed components as indicated. Fatal Hub Link Error Audible Beeps: None Possible Cause: The hub link interface has experienced a critical failure that caused an NMI.
Page 119: Ilo Generated Nmi
iLO Generated NMI Audible Beeps: None Possible Cause: The iLO controller generated an NMI. Action: Check the iLO logs for details of the event. Internal CPU Check - Processor Audible Beeps: None Possible Cause: A processor has experienced an internal error. Action: Run Insight Diagnostics ("HP Insight Diagnostics"...
Page 120: Network Server Mode Active And No Keyboard Attached
Mismatched 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.
Page 121: No Floppy Drive Present
No 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 drive exists. No Keyboard Present Audible Beeps: None Possible Cause: A keyboard is not connected to the server or a keyboard failure has occurred.
Page 122: Power Supply Solution Not Fully Redundant
Power 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. Processor X Unsupported Wattage.
Page 123: This Dimm Does Not Support Thermal Monitoring
Temperature violation detected - system Shutting Down in X seconds Audible Beeps: 1 long, 1 short Possible Cause: The system has reached a cautionary temperature level and is shutting down in X seconds. Action: Adjust the ambient temperature, install fans, or replace any failed fans. There must be a first DIMM in pair if second DIMM in pair is populated.
Page 124 Unsupported power supply detected in bay X Audible Beeps: 1 long, 1 short Possible Cause: The power supply in bay X is not supported by the server. Action: Install a supported power supply in bay X. For supported power supplies, see the server documentation on the HP website (http://www.hp.com/support).
Page 125: 100 Series
Audible Beeps: 2 short Possible Cause: Only Type 0 and Type 1 Header PCI Devices are configured by the system ROM. The device will not work unless the OS or device driver properly configure the card. Typically this message only occurs when PCI cards with a PCI to PCMCIA bridge are installed. Action: Refer to the operating system documentation or the device driver information that ships with the Type 2 PCI device.
Page 126: Rom Error
101-ROM Error Audible Beeps: 1 long, 1 short Possible Cause: System ROM checksum. Action: Run Insight Diagnostics ("HP Insight Diagnostics" on page 75) and replace failed components as indicated. 101-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.
Page 127: Asr Timer Failure
102-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"...
Page 128: 200 Series
180-Log Reinitialized Audible Beeps: None Possible Cause: The IML ("Integrated Management Log" on page 76) has been reinitialized due to corruption of the log. Action: Event message, no action is required. 200 Series 201-Memory Error Audible Beeps: None Possible Cause: Memory failure detected. Action: Run Insight Diagnostics ("HP Insight Diagnostics"...
Page 129 207-Invalid Memory Configuration - DIMM Size Parameters Not Supported. Audible Beeps: 1 long, 1 short Possible Cause: Installed memory module is an unsupported size. Action: Install a memory module of a supported size. 207-Invalid Memory Configuration - Incomplete Bank Detected in Bank X Audible Beeps: 1 long, 1 short Possible Cause: Bank is missing one or more DIMMs.
Page 130: Invalid Lockstep Memory Configuration
207-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 long, 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.
Page 131 209-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 in a mirrored configuration does not match. Action: Install or reinstall DIMMs to support mirrored mode. 209-RAID 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 in a RAID does not match.
Page 132: 300 Series
300 Series 301-Keyboard Error Audible Beeps: None Possible Cause: 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. 301-Keyboard Error or Test Fixture Installed Audible Beeps: None Possible Cause: Keyboard failure occurred.
Page 133: 400 Series
Run Insight Diagnostics ("HP Insight Diagnostics" on page 75) and replace failed components as indicated. 400 Series 40X-Parallel Port X Address Assignment Conflict Audible Beeps: 2 short Possible Cause: Both external and internal ports are assigned to parallel port X. Action: Run the server setup utility and correct the configuration.
Page 134: 1100 Series
Replace the diskette in the drive. Reformat the diskette. 605-Diskette Drive Type Error. Audible Beeps: 2 short Possible Cause: Mismatch in drive type occurred. Action: Run the server setup utility to set the diskette drive type correctly. 611-Primary Floppy Port Address Assignment Conflict Audible Beeps: 2 short Possible Cause: A hardware conflict in the system is preventing the diskette drive from operating properly.
Page 135 Audible Beeps: None Possible Cause: Real-time clock system battery has lost power. The system will lose its configuration every time AC power is removed (when the system is unplugged from AC power source) and this message displays 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.
Page 136 Audible Beeps: None Possible Cause: Required fan is not spinning. Action: Replace the failed fan to provide redundancy, if applicable. 1611-Fan Failure Detected Audible Beeps: 2 short Possible Cause: Required fan is not installed or spinning. Action: Check the fans to be sure they are working. Be sure each fan cable is properly connected and each fan is properly seated.
Page 137 1611-Fan x Not Present (Fan Zone I/O) Audible Beeps: 2 short Possible Cause: Required fan is not installed or spinning. Action: Check the fans to be sure they are working. Be sure each fan cable is properly connected, if applicable, and each fan is properly seated. If the problem persists, replace the failed fans.
Page 138: 1700 Series
1615-Power Supply Configuration Error 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. 1615-Power Supply Configuration Error - A working power supply must be installed in Bay 1 for proper cooling.
Page 139 Audible Beeps: None Possible Cause: An application has overwritten memory reserved by the Smart Array controller. Action: If this occurs when a particular application is loaded, check for an updated version of that application. 1707 - Slot X Drive Array Controller - Bootstrap NVRAM checksum failed The second line of the message includes one of the following lines of text: (unrecoverable error) (no suitable backup found)
Page 140 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 70). 1712-Slot X Drive Array - RAID 5 logical drive(s) configured with 56 Drives, but Array Accelerator size <= 32 MB...
Page 141 Audible Beeps: 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 system when this block address is read. Action: Backup and restore the data on the drive.
Page 142 1720-S.M.A.R.T. Hard Drive Detects Imminent Failure 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 configured as a non-RAID 0 array, replace the failing or failed drive. Refer to the server documentation.
Page 143 Audible Beeps: None Possible Cause: The array accelerator configuration has been updated automatically due to replacement of the array accelerator (or controller) with one having different cache memory size. Action: Run the ACU ("Array Configuration Utility" on page 70) to change the default cache read/write allocation ratio.
Page 144 1733-Slot X Drive Array - Storage Enclosure Firmware Upgrade Problem Detected..Port x box y: Enclosure firmware upgrade needed - run Flash Components. Port x box y: Unable to read firmware version of one or more components Audible Beeps: None Possible Cause: An incorrect enclosure firmware version is installed, or an enclosure firmware upgrade is needed.
Page 145 • HP is not liable for blocked data access caused by improper TPM use. For operating instructions, see the encryption technology feature documentation provided by the operating system. 1737-Slot X Drive Array - Redundant Cabling Configuration has excess Device Paths..Redundant I/O paths to some devices attached to the controller are exceeding per device limit by firmware.
Page 146 Audible Beeps: None Possible Cause: The system detects that the drives are still present during POST and that the user previously requested the drives to be removed from the controller configuration information. Action: Do one of the following: • If the drives will be removed at a later time, press F1 to continue ignoring the physical drives. •...
Page 147 Audible Beeps: None Possible Cause: The controller or firmware version does not support the attached drive enclosure. Action: Upgrade the controller, or detach the expander-based storage connections. 1747-Slot X Drive Array - Unsupported Array Configuration Detected..Followed by one of many possible reasons, including the following: More logical drives are configured than this controller can support when the memory module is detached.
Page 148 1754-Slot X Drive Array - RAID ADG configured but ADG is not supported on this controller model. Audible Beeps: None Possible Cause: RAID ADG configured by ADG is not supported on this controller model. Action: Replace the controller with a model that supports RAID ADG. 1754-Slot X Drive Array - One or more RAID levels are configured...
Page 149 Expansion will resume when Array Accelerator battery reaches full charge. Expansion will resume when automatic data recovery has been completed. Audible Beeps: None Possible Cause: The capacity expansion process has been temporarily disabled. Action: Follow the action that is displayed onscreen to resume the capacity expansion process. 1768-Slot X Drive Array - Resuming Logical Drive Expansion Process Audible Beeps: None Possible Cause: Power was lost while a logical expansion operation was performed.
Page 150 1774-Slot X Drive Array - Obsolete Data Found in Array Accelerator Audible Beeps: None Possible Cause: Drives were used on another controller and reconnected to the original controller while data was in the original controller cache. Data found in the array accelerator is older than data found on the drives and has been automatically discarded.
Page 151 1776-Slot X Drive Array - Shared SAS Port Connection Conflict Detected - Ports 1I, 1E: Storage connections detected on both shared internal and external ports..Controller selects internal port until connection is removed from one of the ports. Audible Beeps: None Action: For cable configuration information, refer to the controller documentation.
Page 152: Drive Array Resuming Automatic Data Recovery Process
• Check the LEDs. If the ProLiant Storage System power LED is amber instead of green, this indicates a redundant power supply failure. • If the message indicates to check SCSI cables, do the following: Compare the cabling against the diagrams in the HP Smart Array Controller User Guide. If the routing is correct, replace cables on the specified port until the POST error message is eliminated.
Page 153 1784-Slot X Drive Array Drive Failure. The Following SCSI Drive(s) Should Be Replaced: SCSI Port Y: SCSI ID Z Audible Beeps: None Possible Cause: Defective drive or SCSI cables detected. Action: Be sure all cables are connected properly and securely. Be sure all drives are fully seated.
Page 154: Drive Array Operating In Interim Recovery Mode
Audible Beeps: None Possible Cause: A failed or replacement drive has not yet been rebuilt. Action: • Perform one of the following actions: Press the F1 key to continue with recovery of data to the drive. Data will be automatically restored to drive X when a failed drive has been replaced, or to the original drive if it is working again without errors.
Page 155: Slot X Drive Array Reports Incorrect Drive Replacement
Replace drive X. (depending on the fault-tolerance level, all data may be lost if another drive fails). 1788-Slot X Drive Array Reports Incorrect Drive Replacement..The following SCSI drive(s) should have been replaced: SCSI Port Y: SCSI ID Z. The following SCSI drive(s) were incorrectly replaced: SCSI Port y: SCSI ID z. Select F1 to continue –...
Page 156 • When powering down the system, the server must be powered down before external storage systems. 1792-Drive Array Reports Valid Data Found in Array Accelerator..Data will automatically be 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.
Page 157: Event List 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.
Page 158: A Cpu Power Module (System Board, Socket X)
03/19/2002 12:54 PM FAN INSERTED Main System Location: System Board Fan ID: 03 **END OF EVENT** WARNING: To avoid potential problems, ALWAYS read the warnings and cautionary information in the server documentation before removing, replacing, reseating, or modifying system components. IMPORTANT: This guide provides information for multiple servers.
Page 159: Blue Screen Trap: Cause [Nt]
Blue Screen Trap: Cause [NT]..Kernel Panic: Cause [UNIX] Abnormal Program Termination: Cause [NetWare] Event Type: System lockup Action: Refer to the operating system documentation. Corrected Memory Error Threshold Passed (Slot X, Memory Module Y)..Corrected Memory Error Threshold Passed (System Memory) Corrected Memory Error Threshold Passed (Memory Module Unknown) Event Type: Correctable error threshold exceeded Action: Continue normal operation, and then replace the memory module during the next scheduled...
Page 160: System Ac Power Overload (Power Supply X)
System AC Power Overload (Power Supply X) Event Type: Power supply overload Action: Switch the voltage 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. System AC Power Problem (Power Supply X) Event Type: AC voltage problem Action: Check for any power source problems.
Page 161: Uncorrectable Memory Error (Slot X, Memory Module Y)
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 173) before proceeding. Action: Replace the board on which the processor is installed. Uncorrectable Memory Error (Slot X, Memory Module Y)...
Page 162 Location: Server blade management module Action: Perform the following steps to resolve the problem. Stop when the problem is resolved. Press the server blade management module reset button. Replace the server blade management module. Server blade management module signal backplane error codes LED code: 10-1, 10-2, or 10-3 Location: Server blade management backplane Action: Perform the following steps to resolve the problem.
Page 163 For more information, refer to the HP BladeSystem Maintenance and Service Guide on the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info). Replace the interconnect device. For more information, refer to the HP BladeSystem Maintenance and Service Guide on the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info). Interconnect B Error Code LED code: 14-1, 14-2, 14-3, or 14-4 Location: Interconnect device - side B Action: Perform the following steps to resolve the problem.
Page 164: Power Management Module Error Codes
For more information, refer to the HP BladeSystem Maintenance and Service Guide on the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info). Interconnect Module B (10-Connector) Error Code LED code: 16-1 or 16-2 Location: Interconnect module - side B (10-connector) Action: Perform the following steps to resolve the problem. Stop when the problem is resolved. Press the server blade management module reset button.
Page 165: Port 85 Codes And Ilo Messages
Location LED codes Power Supply - Slot 2 2-1 or 2-2 Power Supply - Slot 3 3-1 or 3-2 Power Supply - Slot 4 4-1 or 4-2 Power Supply - Slot 5 5-1 or 5-2 Power Supply - Slot 6 6-1 or 6-2 Action: Perform the following steps to resolve the problem.
Page 166: Processor-Related Port 85 Codes
IMPORTANT: Be sure the port 84/85 switch is set to display port 85 codes. Locate the code in the following table. For example, if the port 85 code displays "31h," see "Processor-related port 85 codes (on page 166)" for more information. Port 85 code Description Port 85 codes in this format indicate processor-related errors.
Page 167: Memory-Related Port 85 Codes
Replace the processor board, if applicable. Replace the system board. IMPORTANT: If replacing the system board or clearing NVRAM, you must re-enter the server serial number through RBSU ("Re-entering the serial number and product ID" on page 71). Memory-related port 85 codes Memory-related port 85 codes display in the format 4xh.
Page 168: Miscellaneous Port 85 Codes
Expansion boards Processors, except the processor installed in socket 1 IMPORTANT: Processor socket 1 and PPM slot 1 must be populated at all times or the server does not function properly. PPMs, except the PPM installed in slot 1 DIMMs, except the first bank Hard drives Peripheral devices Install the expansion boards one at a time, rebooting between each installation to isolate the failed...
Page 169: Windows® Event Log Processor Error Codes
Windows® Event Log processor error codes Message ID: 4137 Severity: Error Description: The processor in slot X, socket X has corrected an excessive number of internal errors. The system will continue to operate. Action: Replace the processor. Message ID: 4140 Severity: Warning Description: The system is operating with a heterogeneous processor environment.
Page 170: Msg_Cpu_Rr_2
• Ensure proper ventilation and cooling for the server. • Ensure the processor heatsinks are attached correctly (do not remove them). • Check diagnostics and the Integrated Management Log for heat-related events. • Upgrade to the latest versions of system BIOS and Insight Diagnostics. •...
Page 171: Msg_Cpu_Rr_8
MSG_CPU_RR_8 Event type: Unable to update the CMOS time. Action: Replace the board that CMOS is on. MSG_CPU_RR_9 Event type: MMX hardware is not present. Action: Replace the processor. MSG_CPU_RR_10 Event type: MMX add instruction has failed. Action: Replace the processor. MSG_CPU_RR_11 Event type: MMX subtraction instruction has failed.
Page 172: Msg_Cpu_Rr_17
MSG_CPU_RR_17 Event type: Stress integer math test has failed. Action: • Ensure proper ventilation and cooling for the server. • Ensure the processor heatsinks are attached correctly (do not remove them). • Check diagnostics and the Integrated Management Log for heat-related events. •...
Page 173: Contacting Hp
Contacting HP Contacting HP technical support or an authorized reseller Before 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 173) and operating system information ("Operating system information you need"...
Page 174: Operating System Information You Need
• Explanation of the issue, the first occurrence, and frequency • Any changes in hardware or software configuration before the issue surfaced • Third-party hardware information: Product name, model, and version Company name • Specific hardware configuration: Product name, model, and serial number Number of processors and speed Number of DIMMs and their size and speed List of controllers and NICs...
Page 175: Linux Operating Systems
• An updated Emergency Repair Diskette • If HP drivers are installed: Version of the PSP used 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 •...
Page 176: Novell Netware Operating Systems
• A list of each third-party hardware component installed, with the firmware revisions • A list of each third-party software component installed, with the versions • A detailed description of the problem and any associated error messages Novell NetWare operating systems Collect the following information: •...
Page 177: Ibm Os/2 Operating Systems
/etc/conf/cf.d/sdevice /etc/inittab /etc/conf/cf.d/stune /etc/conf/cf.d/config.h /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) •...
Page 178: Sun Solaris Operating Systems
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 revisions • A list of each third-party software component installed, with the versions •...
Page 179: Acronyms And Abbreviations
Acronyms and abbreviations ABEND abnormal end ACPI Advanced Configuration and Power Interface Array Configuration Utility Advanced Data Guarding (also known as RAID 6) Array Diagnostics Utility Advanced Memory Protection Automatic Server Recovery baseboard management controller CCITT International Telegraph and Telephone Consultative Committee CMOS complementary metal-oxide semiconductor central processing unit...
Page 180 direct memory access driver update error checking and correcting Extended Feature Supplement EISA Extended Industry Standard Architecture electrostatic discharge FBDIMM fully buffered DIMM Firmware Deployment Tool HP SIM HP Systems Insight Manager integrated device electronics Integrated Lights-Out iLO 2 Integrated Lights-Out 2 iLO 3 Integrated Lights-Out 3 Integrated Management Display...
Page 181 Integrated Management Log interrupt request keyboard, video, and mouse low-voltage differential multimedia extensions non-maskable interrupt NVRAM non-volatile memory OBDR One Button Disaster Recovery ORCA Option ROM Configuration for Arrays PCI-X peripheral component interconnect extended POST Power-On Self Test processor power module ProLiant Support Pack Preboot Execution Environment Acronyms and abbreviations 181...
Page 182 RBSU ROM-Based Setup Utility RILOE Remote Insight Lights-Out Edition RILOE II Remote Insight Lights-Out Edition II reserve information sector Red Hat Package Manager storage area network serial attached SCSI SATA serial ATA Systems Insight Manager SIMM single inline memory module Service Pack 1 support software diskette trusted platform module...
Page 183 universal serial bus Version Control Agent VCRM Version Control Repository Manager video graphics array Acronyms and abbreviations 183...
Page 184: Index
Index backup, restoring 62 batteries, insufficient warning when low 38 batteries, replacing 41 120PCI.HAM 61 battery 38, 41, 99, 111, 134 battery pack, array accelerator 143 beep codes 115 BIOS Serial Console 69 accelerator error log 91 blank screen 53 accelerator status 92, 93, 94 blue screen event 159 ACPI support 61...
Page 185 controller state 112 controllers, array 102, 108, 140, 147, 148 ECC errors 92 critical error 117 EISA expansion bus master timeout 159 CSR (customer self repair) 173 electrostatic discharge 15 customer self repair (CSR) 173 end user license agreement (EULA) 84 energy saver features 54 erase operation 112, 113 data loss 42, 157...
Page 186 global protocol error 118 Important Safety Information document 13 graphics adapter problems 52 incorrect drive replacement 155 graphics card option 52 information required 173, 174 guided troubleshooting 86 infrastructure error codes 161 guidelines, cabling 19 Insight Diagnostics 75, 77, 157, 169, 170, 171, Insight Diagnostics processor error codes 169, 170, 171, 172 hard drive guidelines 19...
Page 187 media issue, tape drive 52 operating systems supported 78, 89 MEGA4 XX.HAM 61 option ROM 81 memory 48, 88, 119, 127, 128, 129, 130, 159 Option ROM Configuration for Arrays (ORCA) 71 memory boards 131 ORCA (Option ROM Configuration for Arrays) 71 OS boot problems flowchart 32 memory count error 48, 49 memory error 128, 138, 161...
Page 188 power supplies 37, 120, 122, 124, 137, 138, redundant ROM 65, 74, 81, 122, 140 registering the server 87 powering down 116 reloading software 62 powering on problems 116 Remote Insight Lights-Out Edition II (RILOE II) 61, 73 remote ROM flash 64, 65 powering up 68 power-on problems flowchart 27, 29 remote ROM flash problems 64...
Page 189 system power supplies not redundant 160 server setup 89, 94 service notifications 18, 86 system power supply failure 160 Service Packs 61 system ROM 80, 85 shared ports 151 System ROMPaq Firmware Upgrade Utility 83 shared SAS port connection conflict 151 short circuits 53 SIMM failure detected 142 tape drives 51...
Page 190 warnings 14, 87 website, HP 86, 87 websites, reference 23, 86 what's new 8 when to reconfigure or reload software 62 white papers 86, 88 Windows Event Log processor error codes 169 Index 190...

This manual is also suitable for:

Proliant Proliant 100 series

HP ProLiant BL620c - G7 Server Troubleshooting Manual

Introduction

Getting Started

Common Problem Resolution

Diagnostic Flowcharts

Hardware Problems

Software Problems

Software Tools and Solutions

O

HP Resources for Troubleshooting

Error Messages

Quick Links

Troubleshooting Guide

Troubleshooting

Related Manuals for HP ProLiant BL620c - G7 Server

Summary of Contents for HP ProLiant BL620c - G7 Server

This manual is also suitable for:

Table of Contents