IBM RS/6000 Enterprise Server M80 Service Manual page 94

Symptom
The system does not respond to the password being
entered or the system login prompt is displayed when
booting in service mode.
No codes are displayed on the operator panel within a
few seconds of turning on the system. The operator panel
displays OK before the system is powered on.
The SMS configuration list or boot sequence selection
menu shows more SCSI devices attached to a
controller/adapter than are actually attached.
The System Management Services menu is displayed.
76
Service Guide
Action
v If the password is being entered, or the service mode
boot is being initiated on a keyboard attached to the
system, then the keyboard or its controller may be
faulty. In this case, replace the following, one at a time,
in the sequence listed:
1. Keyboard
2. Primary I/O backplane, location: U0.1-P1
v If the password is being entered, or the service mode
boot is being initiated, from an ASCII terminal, first
insure that the terminal is connected to S1 or S2. Use
the problem determination procedures for the ASCII
terminal.
If the problem persists, replace the primary I/O
backplane, location: U0.1-P1.
Reseat the operator panel cable. If problem not resolved,
replace these parts, one at a time, in the order listed:
1. Operator panel assembly. Swap the VPD module.
2. Primary I/O drawer backplane, location: U0.1-P1.
(See notes on 71.)
A device may be set to use the same SCSI bus ID as the
control adapter. Note the ID being used by the
controller/adapter (this can be checked and/or changed
via an SMS utility), and verify that no device attached to
the controller is set to use that ID.
If settings do not appear to be in conflict:
1. Replace the SCSI cable.
2. Replace the device.
3. Replace the SCSI adapter
Note: In a "twin-tailed" configuration where there is more
than one initiator device (normally another system)
attached to the SCSI bus, it may be necessary to use
SMS to change the ID of the SCSI controller or adapter.
The device or media you are attempting to boot from may
be faulty.
1. Check the SMS error log for any errors. To check the
error log:
v Choose error log
v If an error is logged, check the time stamp.
v If the error was logged during the current boot
attempt, record it.
v Look up the error in Chapter 5, "Error Code to FRU
Index," on page 159 and do the listed action.
v If no recent error is logged in the error log,
continue to the next step below.
2. Try to boot from an alternate boot device connected
to the same controller as the original boot device. If
the boot succeeds, replace the original boot device
(for removable media devices, try the media first).
3. Go to "MAP 1540: Minimum Configuration" on page
110.