Table of Contents
Advertisement
8/ Troubleshooting
8.1.1. Pre-diagnostic
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:
1.
Review the important safety information.
2.
Collect symptom information.
3.
Prepare the server for troubleshooting.
4.
Use the troubleshooting flowchart to begin the troubleshooting process.
8.1.2. 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?
An uncorrectable machine check exception
Stop error or blue screen (Windows)
Purple diagnostic screen (Linux)
Linux kernel panic
A system "hang"
A system "freeze"
If the problem occurs after an OS is installed:
Does the problem occur when a new application is loading or a patch is applying?
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?
Record exactly when the problem happens (include the date and time). If it happens more than once, keep a list of all
symptoms for each occurrence.
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?
How long has the server exhibited problem symptoms?
If the problem occurs randomly, what is the duration or frequency?
www.kontron.com
.
ZINC CUBE C232 - Rev. 1.0
// 79
Advertisement
Table of Contents
Troubleshooting
