Chapter 3. General Checkout; Problem Determination Tips - Lenovo ThinkServer TS200v Hardware Maintenance Manual

Lenovo thinkserver ts200v hardware maintenance manual
Hide thumbs Also See for ThinkServer TS200v:
Table of Contents

Advertisement

Chapter 3. General Checkout

General error messages appear if a problem or conflict is found by an application
program, the operating system, or both. For an explanation of these messages, refer
to the information supplied with that software package.
Before replacing a FRU, ensure that the latest level of BIOS is installed on the
system. A down-level BIOS might cause false errors and unnecessary replacement
of the system board.
Use the following procedure to help determine the cause of a problem:
1. Turn off the server and all external devices.
2. Check all cables and power cords.
3. Set all display controls to the middle position.
4. Power-on all external devices.
5. Turn on the server.
6. Look at the following conditions and follow the instructions:
7. Run the Diagnostic programs. See Chapter 4, "Diagnostics," on page 13.

Problem determination tips

Due to the variety of hardware and software combinations that can be
encountered, use the following information to assist you in problem determination.
If possible, have this information available when requesting assistance from Service
Support and Engineering functions.
v Machine type and model
v Processor or hard disk drive upgrades
v Failure symptom
© Copyright Lenovo 2010
Attention
The drives in the servers you are servicing might have been rearranged or the
drive startup sequence might have been changed. Be extremely careful during
write operations such as copying, saving, or formatting. Data or programs
can be overwritten if you select an incorrect drive.
v Look for displayed error codes
v Listen for beep codes
v Look for readable instructions or a main menu on the display.
If you did not receive the correct response, proceed to step 6.
If you do receive the correct response, proceed to step 7.
v If you hear beep codes during POST, go to "Beep symptoms" on page 17.
v If the server displays a POST error, go to "POST error codes" on page 18.
v If the server hangs and no error is displayed, continue at step 7.
v If you receive an error, replace the part that the diagnostic program calls out.
v If the test stops and you cannot continue, replace the last device tested.
– Do diagnostics indicate a failure?
– What, when, where, single, or multiple systems?
– Is the failure repeatable?
11

Advertisement

Table of Contents
loading

Table of Contents