E1xx Code Boot Problems:
Depending on the boot device, a checkpoint may
be displayed on the operator panel for an extended period of time while the boot
image is retrieved from the device. This is particularly true for Tape and Network
boot attempts. If the checkpoint/code is displayed for an extended time there may be
a problem loading the boot image from the device. If booting from CD-ROM or
Tape, watch for “activity” on the drive's LED indicator. A blinking LED means that the
loading of either the boot image or additional information required by the operating
system being booted is still in progress.
For network boot attempts, if the system is not connected to an active network or if
the target server is inaccessible (this can also result from incorrect IP parameters
being supplied), the system still attempts to boot and because time-out dur
ations
are necessarily long to accommodate retries, the system may appear to be hung.
1. Restart the system and get to the Firmware SMS utilities.
In the utilities check:
Is the intended boot device correctly specified in the boot sequence?
– If the intended boot device is not correctly specified in the boot
sequence, add it to the boot sequence using the SMS menus.
For network boot attempts:
– Are the IP parameters correct?
– Attempt to “Ping” the target server using the SMS “Ping” utility.
2. If the checkpoint E105 or E15B is displayed for an extended time, there may be
a problem with the integrity of the boot image.
Try to boot and run standalone diagnostics against the system, particularly
against the intended boot device. If the diagnostics are successful, it may be
necessary to perform an operating system specific recovery process, or
reinstall the operating system.
3. If attempting to boot from a Hard disk, CD-ROM, or Tape drive:
a. Try a different CD/Tape (unless booting from Hard disk).
b. Verify proper SCSI bus termination.
c. Replace SCSI cable.
d. It is possible that another attached SCSI device is causing the problem.
Disconnect any other SCSI devices attached to the same controller as the
one the boot device is attached to and retry the boot operation. If this is
successful, one of the devices removed is causing the problem, re-attach
devices one by one and retry the boot operation until the problem recurs and
replace the device that caused the problem.
e. Replace SCSI adapter (if drive is attached to a card rather than the I/O
Board).
f. Replace SCSI drive.
g. It is possible that another installed adapter is causing the problem.
3-46
RS/6000 Enterprise Server Model H50 Installation and Service Guide
Summary of Contents for RS/6000 H50
Page 1: ...RS 6000 Enterprise Server Model H50 IBM Installation and Service Guide SA38 0547 00...
Page 16: ...xvi RS 6000 Enterprise Server Model H50 Installation and Service Guide...
Page 30: ...1 12 RS 6000 Enterprise Server Model H50 Installation and Service Guide...
Page 131: ...Chapter 3 Error Code to FRU Index 3 51...
Page 160: ...5 18 RS 6000 Enterprise Server Model H50 Installation and Service Guide...
Page 245: ...Chapter 8 Parts Information Chapter 8 Parts Information 8 1...
Page 290: ...B 4 RS 6000 Enterprise Server Model H50 Installation and Service Guide...
Page 305: ...expect 8 r or 7 r or 6 r or 4 r or 3 r delay 2 done Appendix C Modem Configurations C 15...
Page 312: ...C 22 RS 6000 Enterprise Server Model H50 Installation and Service Guide...
Page 316: ...D 4 RS 6000 Enterprise Server Model H50 Installation and Service Guide...
Page 324: ...X 8 RS 6000 Enterprise Server Model H50 Installation and Service Guide...
Page 326: ...X 10 RS 6000 Enterprise Server Model H50 Installation and Service Guide...