Checkout procedureThis section contains a checkout procedure that you should follow to solvehardware problems in the server.About the checkout procedureBefore you perform the checkout procedure for diagnosing hardware problems,review the following information:v Read the safety information that begins on page vii.v The diagnostic programs provide the primary methods of testing the majorcomponents of the server, such as the I/O board, Ethernet controller, keyboard,mouse (pointing device), serial ports, and hard disk drives. You can also usethem to test some external devices. If you are not sure whether a problem iscaused by the hardware or by the software, you can use the diagnostic programsto confirm that the hardware is working correctly.v When you run the diagnostic programs, a single problem might cause more thanone error message. When this happens, correct the cause of the first errormessage. The other error messages usually will not occur the next time you runthe diagnostic programs.Exception: If multiple error codes or light path diagnostics LEDs indicate amicroprocessor error, the error might be in a microprocessor or in amicroprocessor socket. See “Microprocessor problems” on page 86 forinformation about diagnosing microprocessor problems.v Before you run the diagnostic programs, you must determine whether the failingserver is part of a shared hard disk drive cluster (two or more servers that shareexternal storage devices). If it is part of a cluster, you can run all diagnosticprograms except the ones that test the storage unit (that is, a hard disk drive inthe storage unit) or the storage adapter that is attached to the storage unit. Thefailing server might be part of a cluster if any of the following conditions is true:– You have identified the failing server as part of a cluster (two or more serversthat share external storage devices).– One or more external storage units are attached to the failing server and atleast one of the attached storage units is also attached to another server orunidentifiable device.– One or more servers are located near the failing server.Important: If the server is part of a shared hard disk drive cluster, run one testat a time. Do not run any suite of tests, such as “quick” or “normal” tests,because this might enable the hard disk drive diagnostic tests.v If the server is halted and a POST error code is displayed, see “Event logs” onpage 24. If the server is halted and no error message is displayed, see“System-board switches and jumpers” on page 19 and “Solving undeterminedproblems” on page 147.v For information about power-supply problems, see “Solving power problems” onpage 145.v For intermittent problems, check the error log; see “Event logs” on page 24 and“Diagnostic messages” on page 95.80 IBM System x3100 M4 Type 2582: Problem Determination and Service Guide