Table of Contents
Advertisement
Error symptoms
You can use the error symptom table to find solutions to problems that have definite
symptoms.
If you cannot find the problem in the error symptom charts, go to "EFI-based
SELViewer task" on page 23 to test the server.
If you have just added new software or a new option and your server is not
working, do the following before using the error symptom charts:
v Remove the software or device that you just added.
v Run the diagnostic tests to determine if your server is running correctly.
v Reinstall the new software or new device.
In the following table, if the entry in the FRU/action column is a suggested action,
perform that action; if it is the name of a component, reseat the component and
replace it if necessary. The most likely cause of the symptom is listed first.
Table 17. Error symptoms
Note: See "System" on page 92 to determine which components should be replaced by a field service technician.
Symptom
Cause
System does not
v Power cords not plugged in or faulty.
power up.
v Boards not fully seated.
v Power supplies not installed correctly.
System powers on,
v Short on one of the boards due to
but then turns off,
often with fault light.
v Bent pins on connectors.
System powers up but
v Boards, power pods, or processors not
does not complete
POST.
v System speed set higher than processors
v Memory not stuffed in documented order
86
IBM eServer xSeries x382 Type 8834: Hardware Maintenance Manual and Troubleshooting Guide
conductive item touching it.
fully seated. Wrong stepping of
microprocessor in system for the BIOS.
installed support.
or unsupported/validated DIMMS used.
FRU/action
1. Check power cords to ensure that they
are not damaged and are installed
correctly
2. Verify that modules are seated properly.
3. Verify that power supplies are installed
correctly
1. Check to make sure that you haven't
dropped a screw or other conductive item
into the system during the upgrade.
2. Check the connections on all boards.
Begin with those connections that gave
you the most trouble during installation.
That is typically where a pin may have
gotten bent.
3. Check for bent pins on VHDM
connectors. Check for bent pins on
processors.
1. Check seating on all boards, power pods
and processors. Make sure you have the
FSB to CPU core ratio set appropriately
for the processors you're using.
2. Check the BIOS release notes to ensure
the BIOS installed on the platform
supports the stepping and family of the
processors currently installed.
3. Check that you have stuffed the memory
banks in the proper order. See system
documentation for proper stuffing options.
4. Use only validated DIMMS at least until
you've made sure your upgrade has gone
successfully prior to testing an unknown.
Advertisement
Table of Contents
