HP AlphaServer TS15, Руководство пользователя

Страница: 231 / 252

7.5 Boot Problems
Table 7–6 Troubleshooting Boot Problems
Problem/Possible Cause Action
Operating system (OS)
software is not installed on the
hard disk drive. Install the operating system and license key.
Target boot device is not listed
in the SRM
show device or
show config command.
Check the cables. Are the cables oriented properly and
not cocked? Are there bent pins? Check all the SCSI
devices for incorrect or conflicting IDs. Refer to the
device's documentation.
Check SCSI terminators. The SCSI bus must be
terminated at the end of the internal cable and at the last
external SCSI peripheral.
System cannot find the boot
device. Use the SRM show config and show device commands.
Use the displayed information to identify target devices
for the
boot command, and verify that the system sees
all of the installed devices. If you are attempting to use
bootp, first set the following variables as shown.
(Replace ewa0 with the appropriate device designation.)
>>>set ewa0_inet_init BOOTP
>>>set ewa0_protocols BOOTP
System does not boot. Verify that no unsupported adapters are installed.
Environment variables are
incorrectly set. If the main
logic board has been replaced,
this would cause a loss of the
previous configuration data. Use the SRM show and set commands to check and set
the values assigned to boot-related variables such as
auto_action , bootdef_dev , and boot_osflags.
System will not boot over the
network. For problems booting over a network, check the
ew*0_protocols
,
ei*0_protocols or eg*0_protocols
environment variable settings: Systems booting from a
Tru64 UNIX server should be set to bootp
;
systems
booting from an OpenVMS server should be set to mop .
Run the test command to check that the boot device is
operating.
Troubleshooting 7-7