IBM eserver 630 6C4, Service Manual

Page: 170 / 573

Boot Problems/Concerns
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 booting from CD-ROM or tape,
watch for activity on the drive’s LED indicator. A blinking LED indicates that the loading
of either the boot image or additional information required by the operating system
being booted is still in progress. If the checkpoint is displayed for an extended period of
time and the drive LED is not indicating any activity, there might be a problem loading
the boot image from the device.
Note: 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 will still attempt to boot. Because
time-out durations are necessarily long to accommodate retries, the system may
appear to be hung.
This procedure assumes that a diagnostic CD-ROM is available and that an IDE
CD-ROM or IDE DVD-RAM drive is connected to the internal IDE connector. If your
CD-ROM or DVD-RAM drive is SCSI then the drive must be connected to a SCSI
cable, running from a PCI SCSI adapter loaded into either PCI-X slot 3 or 4 located on
the PCI riser card. Booting the diagnostics image from CD-ROM or a NIM server is
referred to as running standalone diagnostics.
Step 1
Restart the system and access the firmware SMS Main Menu. Select Select Boot
Options.
1. Check to see if the intended boot device is correctly specified in the boot list. If it is
in the boot list:
a. Remove all removable media from devices in the boot list from which you do not
want to boot.
b. If attempting to boot from the network, go to “Step 2”.
c. If attempting to boot from a disk drive or CD-ROM, go to “Step 3” on page 151.
2. If the intended boot device is not correctly identified in the boot sequence, add it to
the boot sequence using the SMS menus. If the device can be added to the boot
sequence, reboot the system, then go to MAP 0410: Repair Checkout in the
RS/6000
Eserver
pSeries Diagnostic Information for Multiple Bus Systems. If the
intended boot device cannot be added to the boot list, go to “Step 3” on page 151.
Step 2
If attempting to boot from the network:
1. Verify that IP parameters are correct.
2. Attempt to
″
ping
″
the target server using the SMS Ping utility. If the ping is not
successful, have the network administrator verify the server configuration for this
client.
3. Check with the network administrator to ensure that the network is up.
4. Check the network cabling to the adapter.
5. Turn the power off, then on and retry the boot operation.
150 Eserver
pSeries 630 Models 6C4 and 6E4 Service Guide