Boot Problems/Concerns
Depending | on | the | boot |
| device, | a |
| checkpoint may be displayed on | the | operator | pa | |||||||||||||||||||||||
for | an | extended | period | of | time |
| while | the boot image is retrieved | from |
| the | de | ||||||||||||||||||||||
is particularly true tape and network | boot | attempts. | If | booting | from | CDROM | or | ta | ||||||||||||||||||||||||||
watch | for | activity | on |
| the | drive's | LED | indicator. | A | blinking | LED | means | that | the | load | |||||||||||||||||||
of either the boot image or additional | information | required by | the | operating | sy | |||||||||||||||||||||||||||||
being |
| booted | is | still |
| in | progess. | If the checkpoint is displayed for an extend | ||||||||||||||||||||||||||
of time and the drive |
| LED | is | not | indicating any activity there may be a proble | |||||||||||||||||||||||||||||
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 incor | ||||||||||||||||||||||||||||||||
parameters being supplied), the system still attempts to boot and | because | |||||||||||||||||||||||||||||||||
durations are necessarily long to |
| accommodate | retries, | the | system | may | appear | to | ||||||||||||||||||||||||||
hung. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This |
| procedure assumes | that | a | drive | is | installed | and | a | Diagnostics |
|
|
| |||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||
1. Restart | the | system |
| and | get | to | the | Firmware | SMS | Main | Menu. Select | Multiboot. |
| |||||||||||||||||||||
Ÿ |
| Check | if | the | intended | boot |
| device | is |
| correctly | specified | in | the | boot | se | ||||||||||||||||||
Ÿ | If | the | intended boot device | is not |
| correctly | identified | in | the | boot | seq | |||||||||||||||||||||||
|
| add it to the boot sequence using | the | SMS | menus | (if | the | intended |
| boot |
| |||||||||||||||||||||||
|
| device | cannot | be | added | to |
| the | boot sequence go to step | 3). |
|
|
|
| ||||||||||||||||||||
Ÿ |
| If | attempting | to | boot | from |
| the | network | go | to |
| step | 2. |
|
|
|
|
|
|
| |||||||||||||
Ÿ |
| If | attempting | to | boot | from |
| a | disk | drive | or |
| go | to | step | 3. |
|
|
| |||||||||||||||
2. If | attempting to | boot from | the | network: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||
Ÿ |
| Verify | that | IP |
| parameters |
| are | correct. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ŸAttempt to "Ping" the target server using the SMS "Ping" utility. If the ping successful, have network administrator verify the server configuration for th
client.
Ÿ Turn power Off, then On and retry the boot operation.
ŸCheck network cabling to adapter.
3.Try to boot and run standalone diagnostics against the system, particularly
against | the | intended | boot | device. |
Ÿ If | the intended | boot | device is not listed in the "NEW RESOURCE" list go t | |
"MAP 0290: Missing Resource Problem Resolution"Diagnosticsin the | ||||
Information | for Multiple | Bus. Systems |
ŸIf a SRN, not an
Information for Multiple Bus manualSystems.
ŸIf the diagnostics are successful, it may be necessary to perform an
operating | system specific recovery process, or reinstall the operating syst |
Ÿ If unable | to load standalone diagnostics: |
Chapter 4. Error Code to FRU Index for