Page 1: Troubleshooting Guide
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.
Page 2 © Copyright 2004, 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 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 ............................9 375445-402 (April 2011) ........................9 375445-401 (January 2011) ......................9 375445-xx9 (June 2010) ........................9 375445-xx8 (July 2009) ........................10 375445-xx7 (November 2008) ......................11 375445-xx6 (September 2007)......................11 375445-xx5 (June 2006) ........................
Page 4 Power supply problems ........................39 System open circuits and short circuits ....................40 UPS problems ..........................40 General hardware problems ........................41 Problems with new hardware ......................41 Unknown problem ..........................42 Third-party device problems ......................43 Internal system problems ..........................44 Battery pack problems ........................
Page 5 Re-entering the serial number and product ID ..................73 Management tools............................74 Automatic Server Recovery ........................ 74 ROMPaq utility ..........................75 iLO and iLO 2 technology ......................... 75 iLO 3 technology ..........................75 Erase Utility ............................. 76 Redundant ROM support ........................76 USB support ............................
Page 6 Switch settings, LED functions, drive, memory, expansion board and processor installation instructions, and board layouts ..........................90 External cabling information ......................90 Power capacity ..........................90 Product configuration resources ........................90 Device driver information ........................90 DDR3 memory configuration......................91 Operating System Version Support .....................
Page 7 Uncorrectable Memory Error (Slot X, Memory Module Y)..............176 HP BladeSystem p-Class infrastructure error codes ..................176 Server blade management module error codes .................. 177 Power management module error codes ................... 180 Port 85 codes and iLO messages ....................... 181 Troubleshooting the system using port 85 codes ................
Page 8: Introduction
Introduction What'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 39) • Updated HP SIM reports a drive fault on a hard drive managed by an HP Smart Array controller (on page 46) •...
Page 9: Revision History
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 13) section to provide troubleshooting information for the HP ProLiant ML110 G7 Server and HP ProLiant DL120 G7 Server.
Page 10: 375445-Xx8 (July 2009)
c-Class server blade POST problems flowchart (on page 34) Server and p-Class server blade fault indications flowchart (on page 36) • Added and updated sections in Software tools and solutions (on page 69): Integrated Lights-Out 3 technology ("iLO 3 technology" on page 75) Firmware (on page 80) HP Smart Update Manager (on page 80) •...
Page 11: 375445-Xx7 (November 2008)
• Added new error messages: ADU Error Messages (on page 93) POST error messages and beep codes (on page 123) 375445-xx7 (November 2008) The seventh edition of the HP ProLiant Servers Troubleshooting Guide, part number 375445-xx7, included the following additions and updates: •...
Page 12: 375445-Xx5 (June 2006)
375445-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: c-Class server blade power-on problems flowchart (on page 30) c-Class server blade POST problems flowchart (on page 34) c-Class server blade fault indications flowchart (on page 38) •...
Page 13: Getting Started
Getting started HP 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 troubleshooting 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.
Page 14: Pre-Diagnostic Steps
When additional information becomes necessary, use this section to identify websites and supplemental documents that contain troubleshooting information. • Error messages (on page 93) Use this section for a complete list of the following messages: ADU error messages (on page 93) POST error messages and beep codes (on page 123) Event list error messages (on page 173) HP BladeSystem infrastructure error codes...
Page 15: Warnings And Cautions
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.
Page 16: 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 manual • weight in kg handling. weight in lb Obtain adequate assistance to lift and stabilize the chassis during installation or •...
Page 17: Symptom Information
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? • Did you recently add or remove hardware or software? If so, did you remember to change the appropriate settings in the server setup utility, if necessary? •...
Page 18 Performing processor procedures in the troubleshooting process Because this document supports multiple generations of HP ProLiant server models, it also covers processes that include troubleshooting of various models and types of processors. Before performing any troubleshooting steps that involve processors, review the following guidelines: •...
Page 19: Performing Processor Procedures In The Troubleshooting Process (On
Always 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 replacing any processors, be sure to follow the guidelines provided in "Performing processor procedures in the troubleshooting process (on page 18)."...
Page 20: 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 21: 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 16). • Always hold DIMMs by the side edges only. •...
Page 22: 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 LED Interpretation LED (1) LED (2) On or off Flashing...
Page 23: Server Updates With An Hp Trusted Platform Module And Bitlocker™ Enabled
Interpretation Online/activity Fault/UID LED LED (green) (amber/blue) On, off, or flashing Alternating amber The drive has failed, or a predictive failure alert has been received and blue 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.
Page 24: 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 26)," 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 26)."...
Page 25 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 p-Class Support and Documents (http://www.hp.com/products/servers/proliant-bl/p-class/info) To locate the HP BladeSystem p-Class System Maintenance and Service Guide, select the product. Select Manuals (guides, supplements, addendums, etc).
Page 26: Start Diagnosis Flowchart
Start diagnosis flowchart Use the following flowchart to start the diagnostic process. General diagnosis flowchart Diagnostic flowcharts 26...
Page 27 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 27...
Page 28: 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 29 Diagnostic flowcharts 29...
Page 30 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). Diagnostic flowcharts 30...
Page 31 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 •...
Page 32: Post Problems Flowchart
POST problems flowchart Symptoms: • Server does not complete POST 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 •...
Page 33 Server and p-Class server blade POST problems flowchart Diagnostic flowcharts 33...
Page 34: 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 Diagnostic flowcharts 34...
Page 35 • 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. •...
Page 36: Server Fault Indications Flowchart
Server 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.
Page 37 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 37...
Page 38 c-Class server blade fault indications flowchart Diagnostic flowcharts 38...
Page 39: 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. CAUTION: Before removing or replacing any processors, be sure to follow the guidelines provided in "Performing processor procedures in the troubleshooting process (on page 18)."...
Page 40: System Open Circuits And Short Circuits
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 information, 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.
Page 41: General Hardware Problems
Be sure the power cord is the correct 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 repeatedly, contact an authorized service provider.
Page 42: Unknown Problem
Installation of a SCSI device without termination or without proper ID settings Setting of an IDE device to Primary/Secondary when the other device is set to CS Connection of the data cable, but not the power cable, of a new device Be sure no memory, I/O, or interrupt conflicts exist.
Page 43: Third-Party Device 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 18)." Failure 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.
Page 44: Internal System Problems
Internal system problems Battery pack problems The 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.
Page 45: Diskette Drive Problems
Drive is not detected Action: Be sure no loose connections (on page 20) exist. Refer to the drive documentation to be sure cables are connected as required. Be sure the cables are working properly. Replace with known functional cables to test whether the original cables were faulty.
Page 46: Drive Problems (Hard Drives And Solid State Drives)
Be sure enough space is available on the diskette. Drive problems (hard drives and solid state drives) HP SIM reports a drive fault on a hard drive managed by an HP Smart Array controller Action: • If the drive fault LED is illuminated, see the drive LED combination tables in "Hard drive LED combinations (on page 22)."...
Page 47 Be sure no loose connections (on page 20) 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.
Page 48: Sd Card Problems
Be sure the drive bay is not defective by installing the hard drive in another bay. Run HP Insight Diagnostics (on page 77). 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.
Page 49: Fan Problems
Fan problems General fan problems are occurring Action: 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. Replace the access panels, and then attempt to restart the server.
Page 50: Hp Trusted Platform Module Problems
All 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.
Page 51 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 memory. • To test the memory, run HP Insight Diagnostics (on page 77).
Page 52: Ppm Problems
Test the memory by installing the memory into a known working server. Be sure the memory meets the requirements of the new server on which you are testing the memory. Replace the memory. See the server documentation. Server fails to boot, all DIMM LEDs illuminate amber, ..the health LED is blinking red, the system emits continuous beeps, and an entry is logged to the Integrated Management Log (IML) Possible cause: The server is an HP ProLiant G6 server with 5500-series Xeon processors installed.
Page 53: Processor Problems
Processor 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.
Page 54 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). Stuck tape issue Action: Manually press the Eject button. Allow up to 10 minutes for the tape to rewind and eject. Perform a forced eject: Press and hold the Eject button for at least 10 seconds.
Page 55: Graphics And Video Adapter Problems
Media 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.
Page 56 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 20) exist.
Page 57: Mouse And Keyboard Problems
Mouse and keyboard problems Action: Be sure no loose connections (on page 20) 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 the switch is correctly set for the server.
Page 58: Cable Problems
Cable problems Drive errors, retries, timeouts, and unwarranted drive failures when using an older Mini SAS cable Action: The Mini SAS connector life expectancy is 250 connect/disconnect cycles (for external, internal, and cable Mini SAS connectors). If using an older cable that could be near the life expectancy, replace the Mini SAS cable.
Page 59 Be sure the software is set for the correct terminal emulation. Reconfigure the software correctly. Restart the server. Run the communications software, checking settings and making corrections where needed. Restart the server, and then reestablish the modem connection. Modem does not answer an incoming call Action: Enable the auto-answer option in the communications software.
Page 60: Network Controller Problems
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. Be sure the modem is current and compliant with CCITT and Bell standards. Replace with a supported modem if needed.
Page 61: Expansion Board Problems
Network controller has stopped working Action: Check the network controller LEDs to see if any statuses indicate the source of the problem. For LED information, refer to the network controller documentation. Be sure the correct network driver is installed for the controller and that the driver file is not corrupted. Reinstall the driver.
Page 62: 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 77) and HP SIM. Use either utility to gather critical system hardware and software information and to help with problem diagnosis.
Page 63: 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 64: Restoring To A Backed-Up Version
Restoring 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 system.
Page 65: Linux Operating Systems
IBM OS/2—Power up the server from the startup diskettes. For more information, see the OS/2 documentation. Linux—For more information, see the operating system documentation. Linux operating systems For troubleshooting information specific to Linux operating systems, refer to the Linux for ProLiant website (http://h18000.www1.hp.com/products/servers/linux).
Page 66: Rom Problems
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: • A local administrative client system that is running the Microsoft® Windows NT® 4.0, Windows®...
Page 67: Boot Problems
Failure occurs during ROM flash After the online flash preparation has been successfully completed, the system ROM is flashed offline. The flash cannot be interrupted during this process, or the ROM image is corrupted and the server does not start. The most likely reason for failure is a loss of power to the system during the flash process.
Page 68 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.
Page 69: 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 70: Using Rbsu
• 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). Using RBSU To use RBSU, use the following keys: •...
Page 71: Boot Options
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. After the settings are selected, exit RBSU and allow the server to reboot automatically.
Page 72: 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 73: Option Rom Configuration For Arrays
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 Option ROM Configuration for Arrays Before installing an operating system, you can use the ORCA utility to create the first logical drive, assign...
Page 74: Management Tools
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 automatically 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.
Page 75: Rompaq Utility
ROMPaq 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 ROMPaq, 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.
Page 76: Erase Utility
• Use the shared iLO 3 Remote Console 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. •...
Page 77: Diagnostic Tools
• POST • RBSU • 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 78: 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 79: Remote Support And Analysis Tools
Remote support and analysis tools HP 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 Pack Service, or HP contractual support agreement.
Page 80: Version Control
For example: http://www.hp.com/support/dl360g6 (http://www.hp.com/support/dl360g6) Version 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.
Page 81: System Online Rom Flash Component Utility
• 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 between components • Deploys software and firmware on Windows and Linux operating systems •...
Page 82: Care Pack
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). Care Pack HP Care Pack Services offer upgraded service levels to extend and expand bundled services with easy-to-buy, easy-to-use support packages that help you make the most of your server investments.
Page 83: Automatic Backup
Redundant ROM support The server enables you to upgrade or 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.
Page 84: Verifying Firmware Versions
Verifying firmware versions To locate and verify the most current firmware versions, use the following tools: • Insight Diagnostics Online Edition ("HP Insight Diagnostics" on page 77) Access this tool from the System Management Homepage. • ("Version control" on page 80) Access this tool from the System Management Homepage.
Page 85: Hp Smart Update Manager Deployment
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.
Page 86: Rom Update Utility
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 available in this method of installation.
Page 87: Unsupported Processor Stepping With Intel® Processors
HP SmartStart CD 6.x HP Firmware Maintenance CD 7.0 or later HP Smart Update Firmware DVD Select the Maintenance tab. 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.
Page 88: 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 89: 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 90: 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 91: 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 92: 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 DVD, 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 93: 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 78) 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 94 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 95 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 96: Board In Use By Expand Operation
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 97 Configuration Signature is Zero Description: ADU ("Array diagnostic software" on page 78) 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 98 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 78) did not find a valid configuration signature to use to get the data.
Page 99 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 100 Drive Monitoring Features Are Unobtainable Description: ADU ("Array diagnostic software" on page 78) 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 101 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 102 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 103 Logical 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.
Page 104 Other Controller Indicates Different Hardware Model Description: The other controller in the redundant controller configuration is a different hardware model. Action: Be sure both controllers are using the same hardware model. If they are, make sure the controllers are fully seated in their slots. Other Controller Indicates Different Firmware Version Description: The other controller in the redundant controller configuration is using a different firmware version.
Page 105 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 106 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 107 Soft firmware upgrade required Description: ADU ("Array diagnostic software" on page 78) 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 108 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 109 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 110 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 111: 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 112 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 113: 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 114 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 115 Array status: The array currently has a drive erase operation queued, running, stopped or completed on a logical or physical drive. Action: No action is required. Array Status: The array has a spare drive assigned which is smaller than the smallest data drive in the array…...
Page 116 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.
Page 117 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"...
Page 118 Drive Offline due to Erase Operation: The physical drive is offline and currently being erased. Action: No action is required. The logical drive containing this physical drive cannot be migrated or extended while the erase operation is in progress. Drive Offline due to Erase Operation: The physical drive is offline and the erase process has been failed...
Page 119 Logical 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. Logical drive state: The logical drive is not configured. Action: Refresh the system using the Array Configuration Utility (on page 72). Logical drive state: The logical drive is not yet available.
Page 120 Action: Update the controller firmware. If the update fails, contact HP support ("Contacting HP" on page 187). Physical Drive State: 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.
Page 121 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 creation, array expansion, etc.) or modification to the controller will result in the loss of all existing data on the disabled logical drive(s).
Page 122 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.
Page 123: Post Error Messages And Beep Codes
Storage 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"...
Page 124 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. Advanced Memory Protection mode: Multi-board mirrored memory with Advanced ...Xxxx MB System memory and xxxx MB memory reserved for Mirroring. Audible Beeps: None Possible Cause: This message indicates Mirrored Memory is enabled and indicates the amount of memory reserved for this feature.
Page 125 Fan Solution Not Sufficient Audible Beeps: Possible Cause: The minimum number of required fans is missing or failed. Action: Install fans or replace any failed fans. Fatal 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"...
Page 126 Fatal 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 77) and replace failed components as indicated. FATAL ROM ERROR: The System ROM is not Properly Programmed. Audible Beeps: 1 long, 1 short Possible Cause: The System ROM is not properly programmed.
Page 127 Internal CPU Check - Processor Audible Beeps: None Possible Cause: A processor has experienced an internal error. Action: Run Insight Diagnostics ("HP Insight Diagnostics" on page 77). CAUTION: Before removing or replacing any processors, be sure to follow the guidelines provided in "Performing processor procedures in the troubleshooting process (on page 18)."...
Page 128 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 129 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 130: Processor X Unsupported Wattage
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 131 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. 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.
Page 132 Trusted Execution Error found: 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).
Page 133 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 Attempting to enable OBDR for the attached USB tape drive...
Page 134: 100 Series
CAUTION: Before removing or replacing any processors, be sure to follow the guidelines provided in "Performing processor procedures in the troubleshooting process (on page 18)." Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board. Correct the processor configuration.
Page 135: System Board Failure
102-System Board Failure 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 136: Series
Action: Run Insight Diagnostics ("HP Insight Diagnostics" on page 77) and replace failed components as indicated. 162-System Options Not Set Audible Beeps: 2 long Possible Cause: Configuration is incorrect. The system configuration has changed since the last boot (addition of a hard drive, for example) or a loss of power to the real-time clock has occurred. The real-time clock loses power if the onboard battery is not functioning correctly.
Page 137 203-Memory Address Error Audible Beeps: None Possible Cause: Memory failure detected. Action: Run Insight Diagnostics ("HP Insight Diagnostics" on page 77) and replace failed components as indicated. 207 - Invalid Memory Configuration Detected. DIMMs installed when no corresponding processor is detected. Description: Processor is required to be installed for memory to be used.
Page 138 207-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. 207-Invalid 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.
Page 139 207-Memory Configuration Warning - DIMM In Socket X does not have Primary Width of 4 and only supports standard ECC. Advanced ECC does not function when mixing DIMMs with Primary Widths of x4 and x8. Audible Beeps: 1 long, 1 short, or none Possible Cause: Installed DIMMs have a primary width of x8.
Page 140 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 141: 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 142: 400 Series
Run Insight Diagnostics ("HP Insight Diagnostics" on page 77) 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 143: 1100 Series
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 144 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). 1610-Temperature Violation Detected. - Waiting 5 Minutes for System to Cool ...Press Esc key to resume booting without waiting for the system to cool.
Page 145 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. If the problem persists, replace the failed fans.
Page 146 Be sure each fan cable is properly connected, if applicable, and each fan is properly seated. If the problem persists, replace the failed fans. 1611- Power Supply Zone Fan Assembly Failure Detected. Either..the Assembly is not installed or multiple fans have failed. Audible Beeps: None Possible Cause: Required fans are missing or not spinning.
Page 147: 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 148 Audible Beeps: None Possible Cause: The battery needs to be installed and charged. Action: Install and charge the Array Accelerator battery. 1702-SCSI Cable Error Detected Audible Beeps: None Possible Cause: SCSI cable failed. Action: Check all SCSI cable connectors for bent pins. Reseat the SCSI cable on the controller and all connected devices.
Page 149 Audible Beeps: None Possible Cause: The Bootstrap NVRAM on the specified Smart Array controller is corrupt or invalid. Action: Update the controller with the latest firmware version. If the problem still exists, replace the controller. 1708 - Slot X Drive Array Controller - Bootstrap NVRAM restored from backup. System restart required Audible Beeps: None Possible Cause: The specified Smart Array controller Bootstrap NVRAM was restored in one of the following...
Page 150 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 72). 1712-Slot X Drive Array - RAID 5 logical drive(s) configured with 56 Drives, but Array Accelerator size <= 32 MB...
Page 151 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.
Page 152 • If this drive is part of a fault-tolerant configuration, do not replace this drive unless all other drives in the array are online. 1721-Slot X Drive Array - Drive Parameter Tracking Predicts Imminent Failure..The following devices should be replaced when conditions permit. Port X Box Y Bay(s) Z Audible Beeps: None Possible Cause: Drive parameter tracking reports a predictive-failure condition on the indicated drive.
Page 153 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.
Page 154 1730-Fixed Disk 0 Does Not Support DMA Mode Audible Beeps: None Possible Cause: Fixed drive error detected. Action: Run the server setup utility and correct the configuration. 1731-Fixed Disk 1 Does Not Support DMA Mode Audible Beeps: None Possible Cause: Fixed drive error detected. Action: Run the server setup utility and correct the configuration.
Page 155 1736-HP Trusted Platform Module Error Audible Beeps: 2 short Possible Cause: A TPM is installed, but the System ROM is unable 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"...
Page 156 Audible Beeps: None Possible Cause: A problem exists with the storage enclosure redundant cabling. A single path was found 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: •...
Page 157 1743-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 erased are offline. Action: Do one of the following: • Wait for the erase process to complete before using the logical drive. •...
Page 158 * Configuration information indicates one or more hard drive(s) are located in drive bays that are inaccessible when the memory module is detached. * Capacity Expansion operation(s) are pending but cannot continue because the Array Accelerator module has been detached. * ALL logical drive(s) have been disabled.
Page 159 1750-Fixed Disk 0 failed ID command Audible Beeps: None Possible Cause: Fixed drive error detected. Action: Run the server setup utility and correct the configuration. 1751-Fixed Disk 1 failed ID command Audible Beeps: None Possible Cause: Fixed drive error detected. Action: Run the server setup utility and correct the configuration.
Page 160 1757-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, update the controller firmware before attaching the new module.
Page 161 Audible Beeps: None Possible Cause: The current controller firmware does not support the attached Array Accelerator module type. Action: Upgrade the controller firmware, or replace the Array Accelerator module. 1763-Slot X Drive Array - Array Accelerator daughtercard critical error; please replace...
Page 162 * 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 expanded; therefore, the drives have been temporarily disabled.
Page 163 1773-Primary Fixed Disk port Address conflict Audible Beeps: None Possible Cause: Fixed drive error detected. Action: Run the server setup utility and correct the configuration. 1774-Slot X Drive Array - Obsolete data found in Array Accelerator..Data Found in Array Accelerator was Older Than Data Found on Drives. Obsolete Data has been Discarded 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.
Page 164 1776-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"...
Page 165 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 Enclosure Problem Detected..." on page 165). 1777-Slot X Drive Array - Storage Enclosure Problem Detected... (followed by one or more of the following): ...* Cooling Fan Malfunction Detected * Overheated Condition Detected...
Page 166 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 failure. Action: Be sure the system is always powered up and down correctly: •...
Page 167 1782-Disk Controller Failure Audible Beeps: None Possible Cause: Hard drive circuitry error detected. Action: Run Insight Diagnostics ("HP Insight Diagnostics" on page 77) and replace failed components as indicated. 1783-Slot X Drive Array Controller Failure... followed by one of the following:) ...* [Board ID not programmed (replace ROMs or replace controller)] * [I2C read error] * [Image checksum error]...
Page 168: 1786-Slot X Drive Array Recovery Needed
Replace defective cables, drive X, or both. 1784-Slot X Drive Array – Logical Drive Failure Audible Beeps: None Possible Cause: Defective drive or cables detected. Action: Be sure all cables are connected properly and securely. Be sure all drives are fully seated. Replace defective cables, drive X, or both.
Page 169: Drive Array Reports Incorrect Drive Replacement
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. Press the F2 key to continue without recovery of data to the drive.
Page 170 Repair the connection and press the F2 key. If the problem persists, run ADU ("Array diagnostic software" on page 78) to resolve. • Be sure the cable is routed properly. 1789-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"...
Page 171 If the problem persists, run Insight Diagnostics ("HP Insight Diagnostics" on page 77) and replace the failed assembly as indicated. 1792-Slot X Drive Array - 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.
Page 172: 1800 Series
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 173: Event List Error Messages
1801-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. Event list error messages Introduction to event list error messages This section contains event list error messages recorded in the IML...
Page 174: Automatic Operating System Shutdown Initiated Due To Fan Failure
or the SmartStart Support and Documents website (http://www.hp.com/support/smartstart/documentation). Automatic operating system shutdown initiated due to fan failure Event Type: Fan failure Action: Replace the fan. Automatic Operating System Shutdown Initiated Due to Overheat Condition..Fatal Exception (Number X, Cause) Event Type: Overheating condition Action: Check fans.
Page 175: Processor Correctable Error Threshold Passed (Slot X, Socket Y)
Processor Correctable Error Threshold Passed (Slot X, Socket Y) Event Type: Correctable error threshold exceeded 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 18)." Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board.
Page 176: System Fans Not Redundant
System Fans Not Redundant Event Type: Fans not redundant Action: Add a fan or replace the failed fan. System Overheating (Zone X, Location) Event Type: Overheating condition Action: Check fans. System Power Supplies Not Redundant Event Type: Power supply not redundant Action: Add a power supply or replace the failed power supply.
Page 177: Server Blade Management Module Error Codes
Access the diagnostics. 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). Server blade management module error codes Server blade error codes Location LED codes 1-1 or 1-2 Server Blade - Slot 1 2-1 or 2-2 Server Blade - Slot 2 3-1 or 3-2...
Page 178 Press the server blade management module reset button. Replace the power backplane. 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). Server blade management module power backplane B error codes LED code: 12-1, 12-2, 12-3, or 12-4 Location: Server blade power backplane B Action: Perform the following steps to resolve the problem.
Page 179 Location: Interconnect module - side A (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. Reseat the interconnect module. 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).
Page 180: 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). Replace the interconnect module. 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). Unknown server blade management module error code LED code: 19-1 Location: Unknown Action: Perform the following steps to resolve the problem.
Page 181: Port 85 Codes And Ilo Messages
Action: Perform the following steps to resolve the problem. Stop when the problem is resolved. Press the power management module reset button. Unknown power management module error code LED code: 19-1 Location: Unknown Action: Perform the following steps to resolve the problem. Stop when the problem is resolved. Press the power management module reset button.
Page 182: Memory-Related Port 85 Codes
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 18)." Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board.
Page 183: Expansion Board-Related Port 85 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 18)." This process can include removing all: Expansion boards DIMMs, except the first bank Hard drives...
Page 184: Miscellaneous Port 85 Codes
CAUTION: Before removing or replacing any processors, be sure to follow the guidelines provided in "Performing processor procedures in the troubleshooting process (on page 18)." 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 in socket 1 and the corresponding PPM.
Page 185: 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: CAUTION: Before removing or replacing any processors, be sure to follow the guidelines provided in "Performing processor procedures in the troubleshooting process (on page 18)."...
Page 186 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 guidelines provided in "Performing processor procedures in the troubleshooting process (on page 18)." Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board.
Page 187: 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 187) and operating system information ("Operating system information you need"...
Page 188: Operating System Information You Need
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...
Page 189: Linux Operating Systems
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 •...
Page 190: Novell Netware Operating Systems
Novell NetWare operating systems Collect the following information: • Whether the operating system was factory installed • Operating system version number • Printouts or electronic copies (to e-mail to a support technician) of AUTOEXEC.NCF, STARTUP.NCF, and the system directory • A list of the modules.
Page 191: Ibm Os/2 Operating Systems
/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 192: Oracle Solaris Operating Systems
• A detailed description of the problem and any associated error messages Oracle Solaris operating systems Collect the following information: • Operating system 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 •...
Page 193: 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 194 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 195 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 195...
Page 196 RBSU ROM-Based Setup Utility 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 uninterruptible power system universal serial bus Version Control Agent Acronyms and abbreviations 196...
Page 197 VCRM Version Control Repository Manager video graphics array Acronyms and abbreviations 197...
Page 198: Index
Index beep codes BIOS Serial Console blank screen accelerator error log blue screen event accelerator status 93, 94, 95 board in use by expand operation ACPI support board not attached ACU (Array Configuration Utility) boot options adapters 95, 100 boot problems additional information booting problems ADG enabler dongle is broken or missing...
Page 199 controllers, array 96, 97, 103, 109, 158, 159 EISA expansion bus master timeout critical error electrostatic discharge CSR (customer self repair) end user license agreement (EULA) 84, 85 customer self repair (CSR) energy saver features erase operation 116, 117 Erase Utility error codes, HP BladeSystem p-Class data loss infrastructure...
Page 200 guided troubleshooting Insight Diagnostics 76, 78, 172 guidelines, cabling installation and configuration installation instructions 88, 89 insufficient adapter resources Integrated Lights-Out (iLO) 74, 90, 132 hard drive guidelines Integrated Management Log (IML) 77, 172 hard drive LED combinations inter-controller link connection hard drive LEDs 22, 45 internal health LED...
Page 201 memory, interleaving memory, mirrored 70, 71, 139 panic error memory, RAID 70, 139 parallel port memory-related port 85 codes parameters Microsoft operating systems parity errors 92, 99, 128 Mini SAS cable part numbers 88, 89 minimum hardware configuration passwords mirror data miscompare patches mirrored memory 70, 71, 123...
Page 202 power-on problems flowchart 28, 30 reloading software PPM (processor power module) 51, 52, 126 remote ROM flash 65, 66 PPM failure LEDs 51, 52 remote ROM flash problems PPM problems 51, 139 remote support and analysis tools required information 186, 187 PPM slots pre-diagnostic steps resources...
Page 203 System ROMPaq Firmware Upgrade Utility server setup 90, 95 service notifications 20, 87 Service Packs shared ports tape drives shared SAS port connection conflict tape drives, failure of short circuits tasks Smart Array SCSI Diagnosis feature 45, 76 teardown procedures Smart Update Manager 79, 84 technical support...
Page 204 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 Index 204...

This manual is also suitable for:

Ml570 - proliant - 1 gb ram Proliant dl360p Proliant dl380p Proliant dl388p Proliant ml350p Proliant dl380 g3 with msa1000 ... Show all

Compaq ML530R - HP ProLiant - 128 MB RAM Troubleshooting Manual

Introduction

Getting Started

Common Problem Resolution

Diagnostic Flowcharts

Hardware Problems

Software Problems

Software Tools and Solutions

HP Resources for Troubleshooting

Error Messages

Contacting HP

Acronyms and Abbreviations

Index

Quick Links

Troubleshooting Guide

Troubleshooting

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Compaq ML530R - HP ProLiant - 128 MB RAM

Summary of Contents for Compaq ML530R - HP ProLiant - 128 MB RAM

This manual is also suitable for:

Table of Contents