 |
» |
|
|
|
This section describes the Series 700 boot process. See the
previous section for the Series 800 boot process. To boot the system from a halted state, reset the system by
pressing the TOC button or by cycling the main power. During the boot ROM sequence, use the ESC
key to terminate or interrupt the current process. The boot ROM
initiates startup and displays a screen similar to the following
(the display will vary depending on the model of your computer): (c) Copyright. Hewlett-Packard Company. 1995.
All rights reserved. |
16 MB of memory configured and tested. |
Selecting a system to boot. |
To stop selection process, press and hold the ESCAPE key. |
You can now automatically boot the default operating system
or halt the boot process and select an alternate operating system
or program. If you do not interrupt the boot process, HP-UX automatically
takes control and completes the boot process. Watch the messages
during the process and note actions. The startup process ends when
you see the login
prompt on the console. You are now ready to use your HP-UX system.
If you do not get the prompt, the system did not start up and you
will need to determine why. During the startup process, the system
will perform a file system consistency check of the root disk if
the system was improperly shut down. If your system is spread over
multiple disks, the system will perform a consistency check on the
other file systems (that is, the file systems listed in /etc/fstab).
See hpux(1M) for further information
on booting. Booting From Other Devices | |
If you do not want to boot the first system found by the boot
ROM, you can select from alternate operating systems or programs: Turn off the power to the computer, wait a few seconds, then
turn the power back on. Wait for the prompt to press the escape
key (ESC) to stop the selection
process. Press the ESC
key. (Note: The following interface may vary depending on the model
of your computer. For example, some machines will take you to a
BOOT_ADMIN menu.)
In a few seconds, a message appears: Terminating selection process. |
A short time later, a message appears: Searching for potential boot devices.
To terminate search, press and hold the ESCAPE key. |
Your computer is now searching for devices that might
be bootable. As they are found, they appear in a list. A list of
devices might look like this: Device Selection Device Path Device Type and Utilities |
P0 scsi.6.0 QUANTUM PD210S
P1 scsi.5.0 QUANTUM PD210S
P2 scsi.4.0 DDS_tape_drive_identifier
P3 scsi.3.0 TOSHIBA CD-ROM DRIVE:XM
P4 lan.123456-89abc homebase |
This process can take several minutes. When the search ends,
this list of actions appears: b) Boot from specified device
s) Search for bootable devices
a) Enter boot administration mode
x) Exit and continue boot sequence
?) Help |
If no devices are listed: Check for SCSI bus address collisions,
loose connections, or improper termination. Check and verify that the power switch is ON for
all peripherals.
If there are still no devices listed, there is a serious problem.
Contact your designated service representative for assistance. If no disk devices are listed and your system is equipped
with disk drives, your workstation is failing to communicate with
its disks. Recheck the SCSI connections and try again. To boot, enter boot
or b followed
by the index listed to the left of the hardware address (for example,
P0 or P1
as shown in the previous listing), followed by isl
if you want to interact with the ISL interface. The ISL interface
allows you to select a kernel to boot. A sample command is: Select from menu: b P0 isl |
The ISL prompt, ISL>,
should then be displayed. Enter the hpux
command to boot your operating system. For example, to boot a backup
kernel, you might enter:
|
ISL> hpux /stand/vmunix.prev |
This command will boot with a SCSI disk at hardware address
scsi.6.0 (see
P0 on the previous
page). If your computer fails to boot, there might be something wrong
with the file system, the hardware, or boot area. If you have a
file system failure, see "Dealing with File System Corruption" in
Chapter 4 of this manual. If you have a hardware problem, refer
to isl(1M) and to the "Dependencies" section
of hpux(1M) for information on a recovery
mechanism for a corrupted disk. A bad boot area can occur if you
accidentally wrote data to a raw device file of root. To list the available kernels to boot in any directory in
the root file system, use the ll
operation of the hpux
command. For example, to list kernels in the /stand
directory, enter: ISL> hpux ll disk(;0)/stand/. |
The result might be the following listing: : disc(2/0/1.3.0.0.0.0.0;0)/stand/. |
drwxr-xr-x 17 2 2 1024 ../ |
-rw-r--r-- 1 0 0 528 ioconfig |
-rw-r--r-- 1 0 3 190 bootconf |
-rw-r--r-- 1 0 0 752 system |
-rw-r--r-- 1 0 3 82 kernel |
-rw-r--r-- 1 0 3 759 system.prev |
drwxr-xr-x 2 0 0 1024 build/ |
-rwxr-xr-x 1 0 0 5675984 vmunix* |
In this example, an available kernel to boot is /stand/vmunix,
as indicated by the asterisk (*). | | | |  | NOTE: Listing the files of a diskless server from a diskless
client is not supported. | | | | |
Reviewing the Status of the File System | |
During the startup process, the /sbin/bcheckrc
script executes /bin/fsclean.
This command determines the shutdown status of the system and returns
one of three possibilities: If the file systems were shut down properly, the startup process
continues and you see a message like this: /sbin/fsclean:/dev/dsk/c1t5d0(root device) ok
file system is OK, not running fsck |
If any file systems were not shut down properly,
the startup process is interrupted and you see: /sbin/fsclean:/dev/dsk/c1t5d0 not ok
run fsck
FILE SYSTEM(S) NOT PROPERLY SHUTDOWN,
BEGINNING FILE SYSTEM REPAIR. |
At this point, the system runs /sbin/fsck
in a mode that can correct certain inconsistencies in the file systems
without your intervention and without removing data. fsck will
either repair and reboot the system, incorporating the changes,
or you might be asked to run fsck
manually. For details, see fsck(1M) and "Locating
and Correcting Corruption Using fsck" in Chapter 4 of this manual. If /sbin/fsclean
detects any other errors (for example, not being able to open a
specified device file), you will get an error message. The startup
process will end and you will need to resolve the problem by following
the directions given in the error message.
Booting in Maintenance Mode | |
For a description of booting in maintenance mode on an LVM
system, see the subsection "Booting in Maintenance Mode" in the
section "Booting Series 800 Systems" earlier in this chapter. |
Printable version
