Installation guide

Troubleshooting D-3
Compaq Confidential – Need to Know Required
Writer: Cynthia Dresden Project: Compaq ProLiant ML370 Generation 2 Server Setup and Installation Guide Comments: Graphics Replaced
Part Number: 203510-001 File Name: o-appd Troubleshooting-J.doc Last Saved On: 7/12/01 11:20 AM
When the Server Does Not Start
This section provides systematic instructions on what to try and where to go
for help for the most common problems encountered during initial POST. The
server must first complete this test each time you power up, before it can load
the operating system and start running software applications.
WARNING: There is a risk of personal injury from hazardous energy levels. The
installation of options, and the routine maintenance and service of this product
shall be performed by individuals who are knowledgeable about the procedures,
precautions, and hazards associated with equipment containing hazardous
energy circuits.
If the server does not start:
1. Verify that the server and monitor are plugged into working outlets.
2. Ensure that your power source is working properly:
G Check the status using the system power LED. For the location and
explanation of the system power LED, see the “Front Panel LEDs”
section in Appendix E, “LED Indicators and Switches.”
G Verify that the Power On/Standby button was pressed firmly.
Refer to the “Power Source” section in the Compaq Servers
Troubleshooting Guide for details on what else to check.
3. Ensure that the power supplies are working properly.
G Check the status using the power supply LEDs. For the location and
explanation of these LEDs, see the “Hot-Plug Power Supply LEDs”
section in Appendix E, “LED Indicators and Switches.”
G Also refer to the “Power Source” section in the Compaq Servers
Troubleshooting Guide.
4. If the system does not complete POST or start loading an operating
system, refer to “General Loose Connections” in the Compaq Servers
Troubleshooting Guide.
5. If the server is rebooting repeatedly, verify that the system is not
rebooting because of a problem that initiates an ASR-2 reboot.