Lenovo 6532 Computer Hardware User Manual


 
Note: Changes are made periodically to the Lenovo Web site. The actual procedure might vary slightly
from what is described in this document.
Go to http://www.lenovo.com/support.
Utilities are available to reset and update the diagnostics code on the integrated USB ash device, if the
diagnostic partition becomes damaged and does not start the diagnostic programs. For more information
and to download the utilities, go to http://www.lenovo.com/support.
Running the diagnostic programs
To run the diagnostic programs, complete the following steps:
Step 1. If the server is running, turn off the server and all attached devices.
Step 2. Turn on all attached devices; then, turn on the server.
Step 3. When the prompt <F2> Diagnostics is displayed, press F2.
Note: The DSA Preboot diagnostic program might appear to be unresponsive for an unusual length
of time when you start the program. This is normal operation while the program loads.
Step 4. Optionally, select Quit to DSA to exit from the stand-alone memory diagnostic program.
Note: After you exit from the stand-alone memory diagnostic environment, you must restart the
server to access the stand-alone memory diagnostic environment again.
Step 5. Select gui to display the graphical user interface, or select cmd to display the DSA interactive menu.
Step 6. Follow the instructions on the screen to select the diagnostic test to run.
If the diagnostic programs do not detect any hardware errors but the problem remains during normal server
operation, a software error might be the cause. If you suspect a software problem, see the information
that comes with your software.
A single problem might cause more than one error message. When this happens, correct the cause of the
rst error message. The other error messages usually will not occur the next time you run the diagnostic
programs.
Note: If multiple error codes or system-board LEDs indicate a microprocessor error, the error might be in a
microprocessor or in a microprocessor socket. See “Microprocessor problems” on page 54
for information
about diagnosing microprocessor problems.
If the server stops during testing and you cannot continue, restart the server and try running the diagnostic
programs again. If the problem remains, replace the component that was being tested when the server
stopped.
Diagnostic text messages
Diagnostic text messages are displayed while the tests are running. A diagnostic text message contains
one of the following results:
Passed: The test was completed without any errors.
Failed: The test detected an error.
Aborted: The test could not proceed because of the server conguration
Additional information concerning test failures is available in the extended diagnostic results for each test.
Chapter 4. Diagnostics 65