POST
When you turn on the server, it performs a series of tests to check the operation of the server components
and some optional devices in the server. This series of tests is called the power-on self-test, or POST.
Note:
This server does not use beep codes for server status.
If a power-on password is set, you must type the password and press Enter, when prompted, for POST to run.
If POST detects a problem, an error message is displayed. See “POST error codes” on page 24 for more
information.
Event logs
Error codes and messages are displayed in the following types of event logs. Some of the error codes and
messages in the logs are abbreviated. When you are troubleshooting PCI-X slots, note that the event logs
report the PCI-X buses numerically. The numerical assignments vary depending on the configuration.
You can check the assignments by running the Setup utility (see “Using the Setup Utility” on page 294
for more information).
•
POST event log:
This log contains the three most recent error codes and messages that were generated during POST. You
can view the contents of the POST event log from the Setup utility (see “Starting the Setup Utility” on
page 294).
•
System-event log:
This log contains messages that were generated during POST and all system status messages from the
service processor. You can view the contents of the system-event log from the Setup utility (see “Viewing
event logs from the Setup utility” on page 22 for more information).The system-event log is limited in
size. When it is full, new entries will not overwrite existing entries; therefore, you must periodically clear
the system-event log through the Setup utility (when the IMM logs an event that indicates that the log is
more than 75% full). When you are troubleshooting an error, be sure to clear the system-event log
so that you can find current errors more easily.
Each system-event log entry is displayed on its own page. Messages are listed on the left side of the
screen, and details about the selected message are displayed on the right side of the screen. To move
from one entry to the next, use the Up Arrow (
-
) and Down Arrow (
¯
) keys.
The system-event log indicates an assertion event when an event has occurred. It indicates a deassertion
event when the event is no longer occurring.
•
Integrated management module (IMM) event log:
This log contains a superset of IMM, POST, and system management interrupt (SMI) information that
is in the system-event log. You can only access the event log through the IMM Web interface. For
more information, see “Event logs” on page 22.
•
DSA log:
This log is generated by the Dynamic System Analysis (DSA) Preboot program, and it contains merged
contents of the system-event log and the IMM system event log. You can view the DSA log from the DSA
Preboot program (see “Viewing event logs without restarting the server” on page 23).
Viewing event logs from the Setup utility
To view the event logs, complete the following steps:
Step 1.
Turn on the server.
Step 2.
When the prompt
<F1> Setup
is displayed, press F1. If you have set both a power-on password
and an administrator password, you must type the administrator password to view the event logs.
22
ThinkServer TD200 Hardware Maintenance Manual
Summary of Contents for ThinkServer TD200
Page 2: ......
Page 8: ...viii ThinkServer TD200 Hardware Maintenance Manual ...
Page 28: ...20 ThinkServer TD200 Hardware Maintenance Manual ...
Page 138: ...130 ThinkServer TD200 Hardware Maintenance Manual ...
Page 264: ...256 ThinkServer TD200 Hardware Maintenance Manual ...
Page 300: ...292 ThinkServer TD200 Hardware Maintenance Manual ...
Page 327: ...Lenovo product service Appendix A Getting help and technical assistance 319 ...
Page 328: ...320 ThinkServer TD200 Hardware Maintenance Manual ...
Page 338: ...330 ThinkServer TD200 Hardware Maintenance Manual ...
Page 344: ...336 ThinkServer TD200 Hardware Maintenance Manual ...
Page 345: ......
Page 346: ...Part Number Printed in USA 1P P N ...