Table of Contents
Advertisement
Chapter 5. Error Code to FRU Index
Attention:
Start your activity in this chapter by going to "Checkpoint and Error Code Index" on page 162.
In this section, you may be asked to perform additional isolation procedures before looking up the actions
for a 4-character checkpoint or 8-character error code.
The Error Code to FRU Index lists fault symptoms and possible causes. The most likely cause is listed
first. Use this index to help you decide which FRUs to replace when servicing the system.
v If you replace FRUs or perform an action and the problem is still not corrected, go to "MAP 1540:
Problem Isolation Procedures" on page 110 unless otherwise indicated in the tables.
v If you replace FRUs and the problem is corrected, go to "MAP 0410: Repair Checkout" in the RS/6000
Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Note: Do not shut down the system if the FRU was replaced by hot-swap.
Performing Slow Boot
On this system, the error code displayed in the operator panel may not indicate the root cause of the
problem. To fully analyze all of the available information, perform the following steps before doing a
hardware repair or replacement:
1. Record the 8-character error code (and location code if present) in the operator panel.
2. Power off the system using the white button. Refer to "Stopping the System" on page 282.
3. Select slow boot mode (select disable fast boot) on the system power control menu from the service
processor main menu.
4. Do a slow-mode boot to the SMS menus. This boot can be specified using the System Power Control
Menu on the service processor main menu. Refer to "System Power Control Menu" on page 235. (A
fast-mode boot skips much of the built-in diagnostic testing.) A slow-mode boot may yield a new
8-character error code on the operator panel and new errors in the service processor error log. Power
on the system. Refer to "Starting the System" on page 283.
v If a new error code is reported, use it in subsequent steps to continue problem analysis.
v If the system hangs with the same error code, continue with the next step in the Checkpoints and
Error Codes Index.
v If no 8-character error code is displayed in the operator panel, use the original error code and
continue with the next step in the Checkpoints and Error Codes Index.
5. Power off the system.
6. At this point, the service processor menus should be available to examine the service processor error
log.
Confirming Initial Error Code
The service processor may have recorded one or more symptoms in its error log. If the system has
attempted to boot since an error terminated normal operation, there may be specific fault information in the
service processor error log. Examine this error log before proceeding (see "System Information Menu" on
page 238).
In the service processor error log, the most recent error is at the top of the list and the oldest error is at
the bottom. It is also important to look at the time stamp associated with each error. (The time stamps in
the service processor error log reflect coordinated universal time (UTC), which is also referred to as
Greenwich mean time.)
On this system, the error code displayed in the operator panel may not be indicative of the root cause of
the problem. This is also true of the most recent error in the service processor error log.
159
Advertisement
Table of Contents
