Sun Microsystems System Administration Guide, Volume 1 (2000) - page 5
SPARC: Using the Boot PROM
System administrators typically use the PROM level to boot a system. Occasionally,
however, you might need to change the way the system works, such as resetting
which device to boot from or running hardware diagnostics, before the system is
brought to a multiuser state.
Changing the default boot device is necessary to add a new drive to the system
either permanently or temporarily, change the network boot strategy, or if you want
to temporarily boot a standalone system from the network.
See monitor(1M) or eeprom(1M) for a complete list of PROM commands.
SPARC: How to Switch to the ok Prompt
When the system is halted, the PROM monitor prompt is either the greater than sign
(>) or ok.
Switch from the > prompt to the ok prompt on SPARC based systems by typing the
following command.
> n
ok
All examples in this section use the ok prompt.
SPARC: How to Find the PROM Release for a
System
Display a system’s PROM release level with the banner command.
ok banner
Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 333MHz), No Keyboard
OpenBoot 3.15, 128 MB memory installed, Serial #nnnnnnnn.
Ethernet address 8:0:20:a5:d1:3b, Host ID: nnnnnnnn.
Hardware configuration information, including the release number of the PROM, is
displayed. The PROM release level is indicated by the ROM Rev. number.
SPARC: How to Change the Default Boot Device
1. Become superuser.
134
2. Halt the system by using the init(1M) command.
# init 0
3. If the > PROM prompt is displayed, type n and press Return.
> n
ok
The ok PROM prompt is displayed.
4. Change the boot-device setting by using the setenv command.
ok setenv boot-device device[n]
boot-device
Identifies the parameter for setting the device from
which to boot.
device[n]
Identifies the boot-device value such as a disk or the
network. The n can be specified as the disk number.
Use the probe-scsi-all command if you need help identifying the disk
number.
5. Verify the default boot device change by using the printenv command.
ok printenv boot-device
6. Save the new boot-device value by using the reset command.
ok reset
The new boot-device setting is written to the PROM.
SPARC: Examples—Changing the Default Boot Device
In this example, the default boot device is set to disk.
SPARC: Booting a System (Tasks)
135
# init 0
#
INIT: New run level: 0
The system is down.
syncing file systems... done
Program terminated
ok setenv boot-device disk
boot-device =
disk
ok printenv boot-device
boot-device
disk
disk
ok reset
Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 333MHz), No Keyboard
OpenBoot 3.15, 128 MB memory installed, Serial #nnnnnnnn.
Ethernet address 8:0:20:a5:d3:4b, Host ID: nnnnnnnn.
Boot device: disk File and args:
SunOS Release 5.8 Version 64-bit
pluto console login:
In this example the default boot device is set to the network.
# init 0
#
INIT: New run level: 0
The system is down.
syncing file systems... done
Program terminated
ok setenv boot-device net
boot-device =
net
ok printenv boot-device
boot-device
net
disk
ok reset
Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 333MHz), No Keyboard
OpenBoot 3.15, 128 MB memory installed, Serial #nnnnnnnn.
Ethernet address 8:0:20:a3:d54:4b, Host ID: nnnnnnnn.
Boot device: net File and args:
pluto console login:
136
SPARC: How to Reset the System
Run the reset command from the ok prompt.
ok reset
The self-test program, which runs diagnostic tests on the hardware, is executed and
the system is rebooted.
SPARC: Booting a System
The table below describes the boot scenarios covered in this chapter.
TABLE 10-1
Boot Type Descriptions
Booting the System ...
Is Usually Done ...
See ...
To run level 3 (multiuser
After halting the system or performing
“SPARC: How to
state with NFS resources
some system hardware maintenance
Boot a System to
shared)
task. This is the default boot level where
Run Level 3
all resources are available and users can
(Multiuser State)”
log into the system.
on page 138
To run level S (single-user
After performing some system
“SPARC: How to
state)
maintenance task such as backing up a
Boot a System to
file system. At this level, only local file
Run Level S
systems are mounted and users cannot
(Single-User State)”
log into the system.
on page 139
Interactively
After making temporary changes to a
“SPARC: How to
system file or the kernel for testing
Boot a System
purposes. This type of boot allows you to
Interactively” on
recover easily if there are problems with
page 140
the system file or kernel by supplying an
alternative pathname to these files when
prompted. Use the default settings for
the other system prompts.
Over the network
To boot a system over the network. This
“SPARC: How to
procedure assumes the necessary setup
Boot a System
has been completed on the boot server.
Over the Network”
on page 142
SPARC: Booting a System (Tasks)
137
TABLE 10-1
Boot Type Descriptions
(continued)
Booting the System ...
Is Usually Done ...
See ...
From local CD-ROM or
To repair an important system file that is
“SPARC: How to
the network for recovery
preventing the system from booting
Boot a System for
purposes
successfully. This type of boot is also
Recovery
used for installing (or upgrading) a new
Purposes” on page
release of the operating system.
143
Using kadb
To troubleshoot system problems by
“SPARC: How to
running the kernel debugger.
Stop the System for
Recovery
Purposes” on page
145
If a system is turned off, turning it on starts the multiuser boot sequence. The
following procedures show how to boot to different run levels from the ok PROM
prompt.
Use the who -r command to verify that the system is brought to the specified run
level.
See Chapter 8 for a description of run levels.
SPARC: How to Boot a System to Run Level 3
(Multiuser State)
1. Boot to run level 3 by using the boot(1M) command.
ok boot
The automatic boot procedure displays a series of startup messages, and brings
the system to run level 3.
2. Verify the system boots to run level 3.
The login prompt is displayed when the boot process has finished successfully.
hostname console login:
138
SPARC: Example—Booting a System to Run Level 3
(Multiuser State)
The following example displays the messages from booting a system to run level 3.
ok boot
SPARCstation 10 (1 X 390Z50)
ROM Rev. 2.14, 32 MB memory installed, Serial #number.
Ethernet address number, Host ID: number.
Rebooting with command:
Boot device: /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,8...
SunOS Release 5.8 Version Generic 32-bit
Copyright (c) 1983-2000 by Sun Microsystems, Inc.
configuring IPv4 interfaces: le0.
Hostname: earth
The system is coming up. Please wait.
checking ufs filesystems
/dev/rdsk/c0t3d0s7: is clean.
NIS domainname is Solar.COM
starting rpc services: rpcbind keyserv ypbind done.
Setting netmask of le0 to 255.255.255.0
Setting default IPv4 interface for multicast: add net 224.0/
4: gateway earth
syslog service starting.
Print services started.
volume management starting.
The system is ready.
earth console login:
SPARC: How to Boot a System to Run Level S
(Single-User State)
1. Boot the system to run level S by using the boot -s command.
ok boot -s
2. Enter the superuser password when the following message is displayed.
INIT: SINGLE USER MODE
Type Ctrl-d to proceed with normal startup,
(or give root password for system maintenance): xxx
SPARC: Booting a System (Tasks)
139
3. Use the who -r command to verify that the system is at run level S.
# who -r
run-level 3
Jun 10 15:27
3
0
4. To bring the system up to multiuser state after the system maintenance task is
performed, press Control-d.
SPARC: Example—Booting a System to Run Level S
(Single-User State)
The following example displays a system booted to run level S.
ok boot -s
SunOS Release 5.8 Version Generic 32-bit
Copyright (c) 1983-2000 by Sun Microsystems, Inc.
configuring IPv4 interfaces: le0.
Hostname: earth
INIT: SINGLE USER MODE
Type control-d to proceed with normal startup,
(or give root password for system maintenance): xxx
Sun Microsystems Inc.
SunOS 5.8
generic August 1999
# who -r
run-level S Jul 14 11:37
S
0
?
(Perform some maintenance task)
# Press <Control-d>
SPARC: How to Boot a System Interactively
1. Boot the system interactively by using the boot -a command.
ok boot -a
2. Answer the system prompts as described in the following table.
140
If the System Displays ...
Do the Following ...
Enter filename [kernel/unix]:
Provide the name of another kernel to use
for booting.
Or, press Return to use the default kernel
(/platform/‘uname -m‘/kernel/
unix).
Name of default directory for
Provide the name of another kernel to use
modules [/platform/‘uname -m‘/
for booting.
kernel /kernel /usr/kernel]:
Or, press Return to use the default kernel
(/platform/‘uname -m‘/kernel/
unix).
Provide the name of an alternate system
Name of system file [/etc/system]:
file and press Return. Type /dev/null if
your /etc/system file has been damaged.
Or, press Return to use the default /etc/
system file.
root filesystem type [ufs]:
Press Return to use the default root file
system type: UFS for local disk booting, or
NFS for network booting.
Enter physical name of root device
Provide an alternate device name and
press Return.
[physical_device_name]:
Or, press Return to use the default physical
name of the root device.
3. If you are not prompted to answer the questions in the table above, verify that
you entered the boot -a command correctly.
SPARC: Example—Booting a System Interactively
In the following example, the default choices (shown in square brackets []) are
accepted.
ok boot -a
Rebooting with command: boot -a
Boot device: /pci@1f,0/pci@1,1/ide@3/disk@0,0:a File and args: -a
Enter filename [kernel/sparcv9/unix]: Return
Enter default directory for modules [/platform/SUNW,Ultra-5_10/kernel
(continued)
SPARC: Booting a System (Tasks)
141
(Continuation)
/platform/sun4u/kernel /kernel /usr/kernel]: Return
Name of system file [etc/system]: Return
SunOS Release 5.8 Version Generic 64-bit
Copyright (c) 1983-2000 by Sun Microsystems, Inc.
root filesystem type [ufs]: Return
Enter physical name of root device
[/pci@1f,0/pci@1,1/ide@3/disk@0,0:a]: Return
configuring IPv4 interfaces: hme0.
Hostname: starbug
The system is coming up. Please wait.
checking ufs filesystems
The system is ready.
earth console login:
SPARC: How to Boot a System Over the Network
Any system can boot over the network if there is a boot server available. You might
want to boot a standalone system over the network temporarily if it cannot boot
from the local disk. See “SPARC: How to Change the Default Boot Device” on page
134 for information on changing or resetting the default boot device.
There are two network configuration boot strategies to choose from on sun4u
systems: RARP (Reverse Address Resolution Protocol and ONC+ RPC Bootparams
Protocol) or DHCP (Dynamic Host Configuration Protocol). The default network
boot strategy is set to RARP. You can use either one depending on whether a RARP
or DHCP boot server is available in your network.
Note - Sun Ultra systems must have PROM version 3.25 or later to use the DHCP
network boot strategy.
If both methods are available, you can specify which service to use in the boot
command temporarily, or save the network boot strategy across system reboots at the
PROM level, by setting up an NVRAM alias. The following nvalias command
example sets up a network device alias for booting DHCP by default on a Sun Ultra
10 system.
ok nvalias net
/pci@1f,4000/network@1,1:dhcp
This alias means that when you type boot net, the system will boot using DHCP.
142
Caution - You should not use the nvalias command to modify the NVRAMRC file
unless you are very familiar with the syntax of this command and the nvunalias
command. See the OpenBoot 3.x Command Reference Manual for information on
using these commands.
1. Determine the method for booting over the network and select one of the
following.
There must be a RARP or DHCP boot server already set up in your network for
either of these methods to boot successfully.
a. Boot the system over the network by using the DHCP method.
ok boot net[:dhcp]
If you have changed the PROM setting to boot DHCP by default, like in the
nvalias example above, you only have to specify boot net to boot using
the DHCP method.
b. Boot the system over the network by using the RARP method.
ok boot net[:rarp]
Since RARP is the default network boot strategy, you only have to specify
boot net:rarp if you have changed the PROM value to boot DHCP.
SPARC: How to Boot a System for Recovery
Purposes
This procedure is needed when an important file, such as /etc/passwd, has an
invalid entry and cause the boot process to fail.
If you need help identifying a system’s device names, refer to Chapter 26.
1. Follow the instructions below depending on whether you are booting from the
Solaris installation CD or the network.
SPARC: Booting a System (Tasks)
143
If You Are Booting From ...
Then ...
Solaris installation CD
1. Insert the Solaris installation CD into the
CD caddy.
2. Insert the CD caddy into the CD-ROM
drive.
3. Boot from the installation CD in
single-user mode:
ok boot cdrom -s
The network, and an installation server or Use the following command:
remote CD drive are available
ok boot net -s
2. Mount the file system that has the file with an invalid entry.
# mount /dev/dsk/device-name /a
3. Change to the newly mounted directory.
# cd /a/directory
4. Set the terminal type.
# TERM=sun
# export TERM
5. Remove the invalid entry from the file using an editor.
# vi filename
6. Change to the root (/) directory.
# cd /
144
7. Unmount the /a directory.
# umount /a
8. Reboot the system.
# init 6
9. Verify the system boots to run level 3.
The login prompt is displayed when the boot process has finished successfully.
hostname console login:
SPARC: Example—Booting a System for Recovery Purposes
The following example shows how to repair an important system file (in this case,
/etc/passwd) after booting from a local CD-ROM.
ok boot cdrom -s
# mount /dev/dsk/c0t3d0s0 /a
# cd /a/etc
# TERM=sun
# export TERM
# vi passwd
(Remove invalid entry)
# cd /
# umount /a
# init 6
SPARC: How to Stop the System for Recovery
Purposes
1. Type the abort key sequence for your system.
The monitor displays the ok PROM prompt.
ok
The specific stop key sequence depends on your keyboard type. For example, you
can press Stop-a or L1-a. On terminals, press the Break key.
SPARC: Booting a System (Tasks)
145
2. Use the sync command to synchronize the disks.
ok sync
3. When you see the syncing file systems... message, press the abort key
sequence for your system again.
4. Type the appropriate boot(1M) command to start the boot process.
5. Verify the system is booted to the specified run level.
# who -r
run-level 3
May
2 07:39
3
0
S
SPARC: Example—Stopping the System for Recovery Purposes
Press <Stop-a>
ok sync
syncing file systems...
Press <Stop-a>
ok boot
SPARC: Forcing a Crash Dump and Rebooting the
System
Saving crash dumps of the operating system is sometimes necessary for
troubleshooting purposes. The savecore feature and how it is set up is described in
“Managing System Crash Information” in System Administration Guide, Volume 2.
This section only describes how to reboot the system when the savecore feature is
enabled.
SPARC: How to Force a Crash Dump and Reboot
the System
1. Type the stop key sequence for your system. The specific stop key sequence
depends on your keyboard type. For example, you can press Stop-a or L1-a.
On terminals, press the Break key.
The monitor displays the ok PROM prompt.
146
2. Use the sync command at the ok prompt to synchronize the disk and write the
crash dump.
> n
ok sync
After the crash dump is written to disk, the system will continue to reboot.
3. Verify the system boots to run level 3.
The login prompt is displayed when the boot process has finished successfully.
hostname console login:
SPARC: Example—Forcing a Crash Dump and Rebooting the
System
Press <Stop-a>
ok sync
SPARC: How to Boot the System With the Kernel
Debugger (kadb)
1. Type the stop key sequence for your system. The specific stop key sequence
depends on your keyboard type. For example, you can press Stop-A or L1-A.
On terminals, press the Break key.
The monitor displays the ok PROM prompt.
2. Use the sync command at the ok prompt to synchronize the disk and write the
crash dump.
SPARC: Booting a System (Tasks)
147
> n
ok sync
3. When you see the syncing file systems... message, press the abort key
sequence for your system again.
4. Boot the system by using the kernel debugger.
ok boot kadb
5. Identify kadb booting messages to verify that the system has booted using the
kernel debugger.
Rebooting with command: kadb
Boot device: /iommu/sbus/espdma@4,800000/esp@4,8800000/sd@3,0
SPARC: Example—Booting the System With the Kernel
Debugger (kadb)
Press <Stop-a>
ok sync
syncing file systems...
Press <Stop-a>
ok boot kadb
148
CHAPTER
11
IA: Booting a System (Tasks)
This chapter describes the procedures for booting an IA based system.
This is a list of the step-by-step instructions in this chapter.
“IA: How to Boot the Solaris Device Configuration Assistant” on page 151
“IA: How to Boot a System to Run Level 3 (Multiuser State)” on page 151
“IA: How to Boot a System to Run Level S (Single-User State)” on page 152
“IA: How to Boot a System Interactively” on page 154
“IA: How to Boot a System Over the Network” on page 156
“IA: How to Boot a System for Recovery Purposes” on page 157
“IA: How to Stop the System for Recovery Purposes” on page 160
“IA: How to Boot a System with the Kernel Debugger (kadb)” on page 160
“IA: How to Force a Crash Dump and Reboot the System” on page 161
For overview information about the boot process, see Chapter 12.
For step-by-step instructions on booting a SPARC based system, see Chapter 10.
IA: Booting a System
The following table describes the boot types covered in this chapter.
149
TABLE 11-1
Boot Type Descriptions
Booting the System ...
Is Usually Done ...
See ...
To run the Solaris Device
After changing the hardware configuration of
“IA: How to Boot the
Configuration Assistant
the system. This utility enables you to boot the
Solaris Device
Solaris system from a different boot device,
Configuration Assistant”
configure new or misconfigured hardware, or
on page 151
perform other device- or boot-related tasks.
To run level 3 (multiuser state)
After shutting down the system or performing
“IA: How to Boot a
some system hardware maintenance task. This
System to Run Level 3
is the default boot level where all resources are
(Multiuser State)” on
available and users can log into the system.
page 151
To run level S (single-user state)
After performing some system maintenance
“IA: How to Boot a
task such as backing up a file system. At this
System to Run Level S
level only some file systems are mounted and
(Single-User State)” on
users cannot log into the system.
page 152
Interactively
After making temporary changes to the
“IA: How to Boot a
system file or the kernel for testing purposes.
System Interactively” on
This type of boot allows you to recover easily
page 154
if there are problems with the system file or
kernel by supplying an alternative pathname
to these files when prompted. Use the default
settings for the other system prompts.
Over the network
To boot a system over the network. This
“IA: How to Boot a
procedure assumes the necessary setup has
System Over the
been completed on the boot server.
Network” on page 156
From local CD-ROM or the
To repair an important system file that is
“IA: How to Boot a
network for recovery purposes
preventing the system from booting
System for Recovery
successfully. This type of boot is also used for
Purposes” on page 157
installing (or upgrading) a new release of the
operating system.
To run the Solaris kernel
To troubleshooting system problems.
“IA: How to Boot a
debugger (kadb)
System with the Kernel
Debugger (kadb)” on
page 160
To force a crash dump
To troubleshoot system problems and saving
“IA: How to Force a
core dumps of the operating system.
Crash Dump and Reboot
the System” on page 161
150
TABLE 11-1
Boot Type Descriptions
(continued)
The following procedures use the reset button to restart the system. If your system
does not have a reset button, use the on/off switch to restart the system. You might
be able to press the Control-Alt-Del keys to interrupt system operation, depending
upon the state of the system.
IA: Booting the Solaris Device Configuration
Assistant
The Solaris Device Configuration Assistant is a program that enables you to perform
various hardware configuration and booting tasks. Two ways to access the Solaris
Device Configuration Assistant are from the:
Solaris Boot Diskette
Solaris Installation CD
In the following sections you might be requested to insert the Solaris Device
Configuration Assistant Boot Diskette to boot the Configuration Assistant. If your
system’s BIOS supports booting from the CD, you may, instead, insert the Solaris
installation CD to boot the Configuration Assistant.
IA: How to Boot the Solaris Device Configuration
Assistant
1. Insert the Solaris Device Configuration Boot Diskette or the Solaris Installation
CD in the appropriate drive.
2. Press any key to reboot the system if the system displays the Type any key
to reboot prompt. You can also use the reset button at this prompt. If the
system is shut down, turn the system on with the power (on/off) switch.
3. The first menu of the Configuration Assistant is displayed after a few minutes.
IA: How to Boot a System to Run Level 3
(Multiuser State)
1. Press any key to reboot the system if the system displays the Type any key
to reboot prompt. You can also use the reset button at this prompt. If the
system is shut down, turn the system on with the power (on/off) switch.
IA: Booting a System (Tasks)
151
The Current Boot Parameters menu is displayed after a few minutes.
2. Type b to boot the system to run level 3. Press Enter.
If you do not make a selection within five seconds, the system is automatically
booted to run level 3.
3. Verify the system boots to run level 3.
The login prompt is displayed when the boot process has finished successfully.
hostname console login:
IA: Example—Booting a System to Run Level 3 (Multiuser
State)
Type any key to reboot
<<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
Boot args:
Type
b [file-name] [boot-flags] <ENTER>
to boot with options
or
i <ENTER>
to enter boot interpreter
or
<ENTER>
to boot with defaults
<<< timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b
venus console login:
IA: How to Boot a System to Run Level S
(Single-User State)
1. Press any key to reboot the system if the system displays the Type any key
to reboot prompt. You can also use the reset button at this prompt. If the
system is shut down, turn the system on with the power (on/off) switch.
The Current Boot Parameters menu is displayed after a few minutes.
2. Type b -s to boot the system to run level S. Press Enter.
152
If you do not make a selection within five seconds, the system is automatically
booted to run level 3.
3. Type the superuser password, if prompted.
4. Verify the system is at run level S by using the who -r command.
# who -r
run-level S Jul 19 14:37
S
0
3
5. Perform the maintenance task that needed the run level change to S.
6. Press Control-d to bring the system back to run level 3.
IA: Example—Booting a System to Run Level S (Single-User
State)
Type any key to reboot
<<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
Boot args:
Type
b [file-name] [boot-flags] <ENTER>
to boot with options
or
i <ENTER>
to enter boot interpreter
or
<ENTER>
to boot with defaults
<<< timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b -s
INIT: SINGLE USER MODE
Type Ctrl-d to proceed with normal startup,
(or give root password for system maintenance): xxx
Entering System Maintenance Mode
# who -r
(continued)
IA: Booting a System (Tasks)
153
(Continuation)
run-level S Jul 19 14:37
S
0
3
(Perform some maintenance task)
# Press <Control-d>
IA: How to Boot a System Interactively
1.
Press any key to reboot the system if the system displays the Type any key
to reboot prompt. You can also use the reset button at this prompt. If the
system is shut down, turn the system on with the power (on/off) switch.
The Primary Boot Subsystem menu is displayed after a few minutes.
2.
Select the Solaris partition (if not marked as active) from the list and press
Enter. If you do not make a selection within 30 seconds, the active boot
partition is selected automatically.
The Current Boot Parameters menu is displayed after a few minutes.
3.
Type b -a to boot the system interactively. Press Enter.
If you do not make a selection within five seconds, the system is automatically
booted to run level 3.
4.
Answer the system prompts as described in the following table.
If the System Displays ...
Do the Following ...
Enter default directory for
Provide an alternate path for the modules
modules: [/platform/i86pc/kernel
directory and press Enter, or press Enter to
use the default modules directory path.
/kernel /usr/kernel]:
Name of system file [etc/system]:
Provide the name of an alternate system
file and press Enter, or press Enter to use
the default /etc/system file. Type/dev/
null if your /etc/system file has been
damaged.
154
If the System Displays ...
Do the Following ...
root filesystem type [ufs]:
Press Enter to use the default root file
system type: UFS for local disk booting, or
NFS for network booting.
Provide an alternate device name and
Enter physical name of root device
[physical_device_name]:
press Enter, or press Enter to use the
default physical name of the root device
bootpath.
IA: Example—Booting a System Interactively
In the following example, the default choices (shown in square brackets []) are
accepted.
Type any key to reboot
<<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
Boot args:
Type
b [file-name] [boot-flags] <ENTER>
to boot with options
or
i
<ENTER>
to enter boot interpreter
or
<ENTER>
to boot with defaults
<<< timeout in 5 seconds >>>>
Select (b)oot or (i)nterpreter: b -a
Enter default directory for modules [/platform/i86pc/kernel /kernel /usr/
kernel]: Enter
Name of system file [etc/system]:Enter
SunOS Release 5.8 Version Generic 32-bit
Copyright (c) 1983-2000 by Sun Microsystems, Inc.
root filesystem type [ufs]: Enter
Enter physical name of root device
[/pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a]: Enter
configuring IPv4 interfaces: dnet0.
Hostname: venus
(fsck messages)
The system is coming up. Please wait
(More messages)
venus console login:
IA: Booting a System (Tasks)
155
IA: How to Boot a System Over the Network
Any system can boot over the network if there is a boot server available. You might
want to boot a standalone system over the network temporarily if it cannot boot
from the local disk.
The new menu, Set Network Configuration Strategy, on the Configuration Assistant’s
Boot Tasks Menu, enables you to select the appropriate boot strategy.
1.
Determine whether you want to boot over the network using the RARP/
bootparams method or the DHCP method.
There are two network configuration strategies to choose from, RARP (Reverse
Address Resolution Protocol) or DHCP (Dynamic Host Configuration Protocol).
The default network boot strategy is set to RARP. You can use either one
depending on whether a RARP or DHCP boot server is available in your network.
2.
Insert the Configuration Assistant Boot Diskette or the Installation CD you
wish to boot from.
3.
Press any key to reboot the system if the system displays the Type any key
to reboot prompt. You can also use the reset button at this prompt. If the
system is shut down, turn the system on with the power (on/off) switch.
4.
Press F2_Continue at the Solaris Device Configuration Assistant screen to scan
for devices.
Device identification is performed and a screen that displays the identified
devices appears.
5.
Press F2_Continue at the Identified Devices screen to load drivers.
Bootable drivers are loaded.
6.
Press F4_Boot Tasks from the Boot Solaris menu.
7.
Select Set Network Configuration Strategy and press F2_Continue.
8.
Select either RARP or DHCP and press F2_Continue.
A screen that confirms your new network configuration strategy appears.
Your network configuration strategy selection is saved as the default network
boot method the next time this diskette is used for booting.
9.
Press F3_Back to return to the Boot Solaris menu.
10. Select NET as the boot device from the Boot Solaris menu. Then press
F2_Continue to boot the network device.
The Solaris boot option screen is displayed.
156
IA: How to Boot a System for Recovery Purposes
Follow these steps to boot the system to repair a critical system resource. The
example shows you how to boot from a Solaris Installation CD or the network,
mount the root (/) file system on the disk, and repair the /etc/passwd file.
Substitute the device name of the file system to be repaired for the devicename
variable in the procedures below. If you need help identifying a system’s device
names, refer to Chapter 26.
Follow the instructions below to boot from the Solaris installation CD or the network.
1.
Boot from the Solaris installation CD (or the network) to single-user mode.
a.
Insert the Configuration Assistant Boot Diskette or the Installation CD you
wish to boot from.
b.
Press any key to reboot the system if the system displays the Type any
key to reboot prompt. You can also use the reset button at this prompt. If
the system is shut down, turn the system on with the power (on/off) switch.
c.
Press the F2 key (F2_Continue) at the Solaris Device Configuration Assistant
screen.
Device identification is performed and a screen that displays the identified
devices appears.
d.
Press the F2 key (F2_Continue) at the Identified Devices screen.
Bootable drivers are loaded.
e.
Press the F2 key (F2_Continue) at the Solaris Device Configuration Assistant
screen.
Device identification is performed and a screen that displays the identified
devices appears.
f.
Press the F2 key (F2_Continue) at the Identified Devices screen.
Bootable drivers are loaded.
g.
Select the CD-ROM drive or network device from the Boot Solaris menu.
Then press the F2 key (F2_Continue).
The Current Boot Parameters menu is displayed.
h.
Type b -s at the prompt. Press Enter.
After a few minutes, the single-user mode # prompt is displayed.
2. Mount the root (/) file system that has the invalid passwd file.
# mount /dev/dsk/devicename /a
IA: Booting a System (Tasks)
157
3. Change to the newly mounted etc directory.
# cd /a/etc
4. Make the necessary change to the passwd file using an editor.
# vi passwd
5. Change to the root (/) directory.
# cd /
6. Unmount the /a directory.
# umount /a
7. Reboot the system.
# init 6
8. Verify the system boots to run level 3.
The login prompt is displayed when the boot process has finished successfully.
hostname console login:
IA: Example—Booting a System for Recovery Purposes
Type any key to reboot
SunOS Secondary Boot version 3.00
Solaris Intel Platform Edition Booting System
Running Configuration Assistant...
Autobooting from Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
(continued)
158
(Continuation)
If the system hardware has changed, or to boot from a different
device, interrupt the autoboot process by pressing ESC.
Press ESCape to interrupt autoboot in 5 seconds.
Boot Solaris
Select one of the identified devices to boot the Solaris kernel and
choose Continue.
To perform optional features, such as modifying the autoboot and property
settings, choose Boot Tasks.
An asterisk (*) indicates the current default boot device.
> To make a selection use the arrow keys, and press Enter to mark
it
[X].
[ ] NET : DEC 21142/21143 Fast Ethernet
on Board PCI at Dev 3
[ ] DISK: (*) Target 0, QUANTUM FIREBALL1280A
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
[ ] DISK: Target 1:ST5660A
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
[ ] DISK: Target 0:Maxtor 9 0680D4
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
[ ] CD
: Target 1:TOSHIBA CD-ROM XM-5602B
1546
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
F2_Continue
F3_Back
F4_Boot Tasks
F6_Help
<<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
Boot args: kernel/unix -r
Select the type of installation you want to perform:
1 Solaris Interactive
2 Custom JumpStart
3 Solaris Web Start
Enter the number of your choice followed by <ENTER> the key.
If you enter anything else, or if you wait for 30 seconds,
an interactive installation will be started.
Select type of installation: b -s
(continued)
IA: Booting a System (Tasks)
159
(Continuation)
# mount /dev/dsk/c0t0d0s0 /a
# cd /a/etc
# vi passwd
(Remove invalid entry)
# cd /
# umount /a
# init 6
IA: How to Stop the System for Recovery Purposes
If possible, stop the system by using one of the following commands:
If the system is running, become superuser and type init 0 to stop the system.
Press any key to reboot the system after the Type any key to reboot prompt
appears.
If the system is running, become superuser and type init 6 to reboot the system.
If the system doesn’t respond to any input from the mouse or keyboard, press the
reset key, if it exists, to reboot the system. Or you can use the power (on/off) switch
to reboot the system.
IA: How to Boot a System with the Kernel
Debugger (kadb)
1. Press any key to reboot the system if the system displays the Type any key
to reboot prompt. You can also use the reset button at this prompt. If the
system is shut down, turn the system on with the power (on/off) switch.
2. Type b kadb to boot the kernel debugger. Press Enter.
If you do not make a selection within five seconds, the system is automatically
booted to run level 3.
3. Verify the system boots to run level 3.
The login prompt is displayed when the boot process has finished successfully.
160
hostname console login:
4. Verify that you can access the kernel debugger by pressing F1-a.
The kadb[0]: prompt is displayed when you enter the kernel debugger.
IA: Example—Booting a System with the Kernel Debugger
(kadb)
Type any key to reboot
<<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
Boot args:
Type
b [file-name] [boot-flags] <ENTER>
to boot with options
or
i <ENTER>
to enter boot interpreter
or
<ENTER>
to boot with defaults
<<< timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b kadb
naboo console login: (Enter login and password)
(Press F1-a to verify you can access the kernel debugger)
IA: Forcing a Crash Dump and Rebooting the
System
Saving core dumps of the operating system is sometimes necessary for
troubleshooting purposes. The savecore feature and how it is set up is described in
“Managing System Crash Information” in System Administration Guide, Volume 2.
This section only describes how to reboot the system when the savecore feature is
enabled.
IA: How to Force a Crash Dump and Reboot the
System
The system must be booted with the kernel debugger option, kadb, to get to the
kadb[0]: prompt and to enable forcing the crash dump.
IA: Booting a System (Tasks)
161
Note - You must be in text mode to enter the kernel debugger (kadb), so exit any
window system (CDE or Open Windows) first.
1. Press F1-a.
kadb[0]:
The kadb[0]: prompt is displayed.
2. Type the following commands at the kadb[0]: prompt.
Press <F1-a>
kadb[0]: vfs_syncall/W ffffffff
kadb[0]: 0>eip
kadb[0]: :c
kadb[0]: :c
kadb[0]: :c
After the first :c is typed, the system panics, so you need to type :c again. The
system panics again, so type :c a third time to force the crash dump and reboot
the system.
After the crash dump is written to disk, the system continues to reboot.
3. Verify that the system has rebooted by logging in at the console login prompt.
162
CHAPTER
12
The Boot Process (Reference)
This chapter describes the hardware used for booting on SPARC based and IA based
systems and a conceptual overview of the boot process on each platform.
This is a list of overview information in this chapter.
“SPARC: The Boot PROM” on page 163
“SPARC: The Boot Process” on page 164
“IA: The PC BIOS” on page 164
“IA: Boot Subsystems” on page 165
“IA: The Boot Process” on page 170
For instructions on booting a system, see Chapter 10 or Chapter 11.
SPARC: The Boot PROM
Each SPARC based system has a PROM (programmable read-only memory) chip
with a program called the monitor. The monitor controls the operation of the system
before the kernel is available. When a system is turned on, the monitor runs a quick
self-test procedure that checks things such as the hardware and memory on the
system. If no errors are found, the system begins the automatic boot process.
SPARC platform only - Some older systems might require PROM upgrades before
they will work with the Solaris system software. Contact your local service provider
for more information.
163
SPARC: The Boot Process
The following table describes the boot process.
TABLE 12-1
Description of the Boot Process
Boot Phase
Description
Boot PROM
1. The PROM displays system identification information and then runs
self-test diagnostics to verify the system’s hardware and memory.
2. Then the PROM loads the primary boot program, bootblk, whose
purpose is to load the secondary boot program located in the ufs file
system from the default boot device.
Boot Programs
3. The bootblk program finds and executes the secondary boot
program, ufsboot, and loads it into memory.
4. After the ufsboot program is loaded, the ufsboot program loads
the kernel.
Kernel
5. The kernel initializes itself and begins loading modules, using
Initialization
ufsboot to read the files. When the kernel has loaded enough
modules to mount the root file system, it unmaps the ufsboot
program and continues, using its own resources.
6. The kernel creates a user process and starts the /sbin/init
process, which starts other processes by reading the /etc/inittab
file.
init
7. The /sbin/init process starts the run control (rc) scripts, which
execute a series of other scripts. These scripts (/sbin/rc*) check and
mount file systems, start various processes, and perform system
maintenance tasks.
IA: The PC BIOS
Before the kernel is started, the system is controlled by the read-only-memory (ROM)
Basic Input/Output System (BIOS), the firmware interface on a PC.
164
Hardware adapters can have an onboard BIOS that displays the physical
characteristics of the device and can be used to access the device.
During the startup sequence, the PC BIOS checks for the presence of any adapter
BIOS, and if found, loads and executes each one. Each individual adapter’s BIOS
runs self-test diagnostics and displays device information.
IA: Boot Subsystems
At three times during the Solaris boot process, you can make the following choices
about a booting system:
Primary Boot Subsystem (Partition Boot Menu) - This first menu appears if
multiple operating environments exist on the disk. The menu enables you to boot
any of the operating environments installed. By default, the operating
environment designed as active is booted.
Note that if you choose to boot a non-Solaris operating environment, the next two
menus cannot be reached.
Interrupt the Autoboot Process - If the autoboot process is interrupted, you can
access the Configuration Assistant.
The Configuration Assistant enables you to boot the Solaris system from a
different boot device, configure new or misconfigured hardware, or perform other
device- or boot-related tasks.
Current Boot Parameters Menu - Two forms of this menu exist, one for a normal
Solaris boot and one for a Solaris installation boot:
The normal Current Boot Parameters menu enables you to boot the Solaris
system with options, or enter the boot interpreter.
The install Current Boot Parameters menu enables you to select the type of
installation to be performed, or customize the boot.
The following table summarizes the purpose of the primary IA boot interfaces. See
the sections that follow for a detailed description and example of each boot
subsystem.
The Boot Process (Reference)
165
TABLE 12-2
Boot Subsystems
Boot Subsystem
Purpose
Primary Boot Subsystem
This menu appears if the disk you are booting from contains
multiple operating environments, including the Solaris
operating environment.
Secondary Boot Subsystem
This menu appears each time you boot the Solaris release.
The Solaris release is booted automatically unless you
choose to run the Solaris Device Configuration Assistant by
interrupting the autoboot process.
Solaris Device Configuration There are two ways to access the Solaris Device
Assistant/Boot Diskette
Configuration Assistant menus:
1. Use the Solaris Device Configuration Assistant Boot
Diskette or the Solaris Installation CD (on systems that
can boot from the CD-ROM drive) to boot the system.
2. Interrupt the autoboot process when booting Solaris
from an installed disk.
Current Boot Parameters
This menu appears when you boot the Solaris release from
Menu
the disk, CD-ROM, or the network. The menu presents a list
of boot options.
During the boot process, the boot subsystem menus allow you to customize boot
choices. If the system receives no response during the time-out periods, it continues
to boot automatically using default selections. You can stop the boot process when
each boot subsystem menu is displayed, or you can let it continue automatically.
The following section provides examples of each subsystem screen.
IA: Booting Solaris
During the device identification phase, the Configuration Assistant:
Scans for devices installed on the system
Displays the identified devices
Enables you to perform optional tasks such as selecting a keyboard type and
editing devices and their resources
During the Boot phase, the Configuration Assistant:
Displays a list of devices from which to boot. A device marked with an asterisk (*)
is the default boot device.
Enables you to perform optional tasks, such as editing autoboot and property
settings, and choosing the network configuration strategy.
166