Table of Contents
Advertisement
Symptom
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.
You have a problem that does not prevent the
system from booting.
You have an SRN.
You suspect a cable problem.
Action
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 or changed through 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 (or system board
if connected to one of the two integrated
SCSI controllers on the system board). (See
system board note 3 on page 41 if the
system board is replaced.)
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 change the ID of the
SCSI controller or adapter with the System
Management Services.
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:
a. Choose error log.
b. If an error is logged, check the time
stamp.
c. If the error was logged during the
current boot attempt, record it.
d. Look up the error in "Firmware
Checkpoints" on page 91 and do the
listed action.
e. If no recent error is logged in the error
log, continue to the next step below.
2. Go to "Boot Problems and Concerns" on
page 102.
Go to the Fast Path MAP in RS/6000 and
Eserver pSeries Diagnostic Information for
Multiple Bus Systems.
Go to the Fast Path MAP in RS/6000 and
Eserver pSeries Diagnostic Information for
Multiple Bus Systems.
See RS/6000 and Eserver pSeries Adapters,
Devices, and Cable Information for Multiple Bus
Systems.
Chapter 3. Maintenance Analysis Procedures
47
Advertisement
Table of Contents
