Lenovo System x3630 M4, Installation And Service Manual

Page: 149 / 1050

Table 11. Light path diagnostics panel LEDs (continued)
• Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved.
• If a action step is preceded by "(Trained technician only)," that step must be performed only by a trained
technician.
LED Description Action
5. (Trained technician only) replace the server system board.
HDD A hard disk drive has failed or is
missing. 1. Check the LEDs on the hard disk drives for the drive with a
lit status LED and reseat the hard disk drive.
2. Make sure that the cables are correctly connected to the
hard disk drive backplane.
3. For more information, see “Hard disk drive problems” on
page 143.
4. If the error remains, replace the following components in
the order listed, restarting the server after each:
a. Replace the hard disk drive.
b. Replace the hard disk drive backplane.
5. If the error remains, replace the following components one
at a time, in the order listed, restarting the server after
each:
a. Replace the hard disk drive.
b. Replace the hard disk drive backplane.
6. If the problem remains, go to
http://www.lenovo.com/support.
Event logs
Error codes and messages are displayed in POST event log, system-event log, integrated management
module (IMM2) event log, and DSA event log.
• 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 99). For more information about POST error codes, see Appendix B “UEFI/POST
diagnostic codes” on page 831.
• System-event log: This log contains POST and system management interrupt (SMI) events and all
events that are generated by the baseboard management controller that is embedded in the integrated
management module (IMM). You can view the contents of the system-event log through the Setup
utility and through the Dynamic System Analysis (DSA) program (as IPMI event log). 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 you are troubleshooting an error,
you might have to save and then clear the system-event log to make the most recent events available for
analysis. For more information about the system-event log, see Appendix A “Integrated management
module II (IMM2) error messages” on page 327.
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.
Some IMM sensors cause assertion events to be logged when their setpoints are reached. When a
setpoint condition no longer exists, a corresponding deassertion event is logged. However, not all events
are assertion-type events.
Chapter 4
.
Troubleshooting
135