Troubleshooting; Troubleshooting Preparation; Pre-Diagnostic; Symptom Collection - HP Cloudline CL5200 Gen9 User And Maintenance Manual

Troubleshooting

Troubleshooting preparation

Pre-diagnostic

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: Refer to the server documentation for information on procedures, hardware
options, software tools and operating systems supported by the server.
Follow the following pre-diagnostic steps before system troubleshooting process:
Review the important safety information.
1.
Collect symptom information.
2.
Prepare the server for troubleshooting.
3.
Use the troubleshooting flowchart to begin the troubleshooting process.
4.

Symptom collection

Before troubleshooting a server problem, collect the following information:

Does the server power on?

Does the server complete POST?
If not, then what do the health LEDs indicate? Is video display available? If the server completes
POST and video is available, are there any POST error messages?
Record the text of the POST error message as displayed.

Does the server successfully boot an operating system or hypervisor? If not, does the server display
any of the following symptoms?
o An uncorrectable machine check exception
o Stop error or blue screen (Windows)
o Purple diagnostic screen (Linux)
o
Linux kernel panic
A system "hang"
o
A system "freeze"
o

If the problem occurs after an OS is installed:
o Does the problem occur when a new application is loading or a patch is applying?
o What symptoms did the server display when the server malfunctioned? (for example, did it
reboot, were there LED codes, health logs, messages on the screen, and so forth)

Are any indications present that show that the malfunction was reported as a memory error, PCI
error, or so forth? The processor now contains the memory controller and PCI Express controller, so
faults in other areas may be attributed to a processor malfunction.
When did the problem occur?
Troubleshooting 124