Table 9-1 describes the boot types covered in this chapter.
Table 9-1 x86: Boot Type Descriptions
Booting the System ... |
Is Usually Done ... |
See an Example On ... |
---|---|---|
To run level 3 (multiuser state) |
After shutting down the system or performing some system hardware maintenance task. This is the default boot level where all resources are available and users can log into the system. |
"x86: Example--Booting a System to Run Level 3 (Multiuser State)" |
To run level S (single-user state) |
After performing some system maintenance task such as backing up a file system. At this level only some file systems are mounted and users cannot log into the system. |
"x86: Example--Booting a System to Run Level S (Single-User State)" |
Interactively |
After making temporary changes to the system file or the kernel for testing purposes. This type of boot allows you to recover easily 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. | |
From local CD-ROM or the network for recovery purposes |
To repair an important system file that is preventing the system from booting successfully. This type of boot is also used for installing (or upgrading) a new release of the operating system. | |
Using kadb |
To troubleshoot system problems by using the kernel debugger and saving core dumps of the operating system. |
"x86: Example--Forcing a Crash Dump and Rebooting the System" |
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.
Press any key to reboot the system if the system displays the type any key to reboot prompt. Or, use the reset button to restart the system if the system is shut down.
The Solaris boot option screen is displayed after a few minutes.
Type b to boot the system to run level 3. Press Return.
If you do not make a selection within 5 seconds, the system is automatically booted to run level 3.
Verify the system boots to run level 3.
The login prompt is displayed when the boot process has finished successfully.
hostname console login: |
type any key to reboot . . . <<< Current Boot Parameters >>> Boot path: /isa/ata@1f0,0/cmdk@0,0:a Boot args: Type b [file-name] [boot-flags] to boot with options or i to enter boot interpreter or to boot with defaults <<< timeout in 5 seconds >>> Select (b)oot or (i)nterpreter: b . . . venus console login: |
Press any key to reboot the system if the system displays the type any key to reboot prompt. Or, use the reset button to restart the system if the system is shutdown.
The Solaris boot option screen is displayed after a few minutes.
Type b -s to boot the system to run level S. Press Return.
If you do not make a selection within 5 seconds, the system is automatically booted to run level 3.
Type the superuser password, if prompted.
Verify the system is at run level S by using the who -r.
# who -r . run-level S Nov 10 13:59 S 0 3 |
Perform the maintenance task that needed the run level change to S.
Press Control-d to bring the system back to run level 3.
type any key to reboot . . . <<< Current Boot Parameters >>> Boot path: /isa/ata@1f0,0/cmdk@0,0:a Boot args: Type b [file-name] [boot-flags] to boot with options or i to enter boot interpreter or 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 # who -r . run-level S Aug 4 13:11 S 0 3 (Perform some maintenance task) # Press <Control-d> |
Press any key to reboot the system if the system displays the type any key to reboot prompt. Or, use the reset button to restart the system if the system is shutdown.
The Solaris Boot Option screen is displayed after a few minutes.
Type b -s to boot the system to run level S. Press Return.
If you do not make a selection within 5 seconds, the system is automatically booted to run level 3.
Answer the system prompts as described in Table 9-2.
Table 9-2 x86: Interactive Boot Procedure Steps
If the System Displays ... |
Do the Following ... |
---|---|
type any key to reboot |
Press any key to reboot the system, or use the reset button to restart the system. The Primary Boot Subsystem menu is displayed after a few minutes. |
The Primary Boot Subsystem menu |
Select the Active Solaris slice as the boot device. Press Return. If you do not make a selection within 30 seconds, the default boot slice is selected automatically. |
Select (b)oot or (i)nterpreter: |
Type b -a and press Return. |
Enter filename [kernel/unix]: |
Provide the name of another kernel to use for booting and press Return. Or, press Return to use the default kernel (/platform/i86pc/kernel/unix). |
Name of system file [etc/system]: |
Provide the name of an alternate system file and press Return, or press Return to use the default /etc/system file. |
Name of default directory for modules [/platform/i86pc/kernel /kernel /usr/kernel]: |
Provide an alternate path for the modules directory and press Return, or press Return to use the default modules directory path. |
root filesystem type [ufs]: |
Press Return to use the default root file system type: UFS for local disk booting or NFS for diskless clients. |
Enter physical name of root device[physical_device_name]: |
Provide an alternate device name and press Return, or press Return to use the default physical name of the root device. |
In the following example, the default choices (shown in square brackets []) are accepted.
type any key to reboot . . . <<< Current Boot Parameters >>> Boot path: /isa/ata@1f0,0/cmdk@0,0:a Boot args: Type b [file-name] [boot-flags] to boot with options or i to enter boot interpreter or to boot with defaults <<< timeout in 5 seconds >>> Select (b)oot or (i)nterpreter: b -a (Copyright notice) Enter filename [kernel/unix]:Return Name of system file [/etc/system]:Return Name of default directory for modules [platform/i86pc/kernel /kernel/usr/kernel]:> Return root filesystem type [ufs]: Return Enter physical name of root device [/eisa/dpt@5c88,0/cmdk@0,0:a]: Return Configuring network interfaces: smc0 Hostname: venus (fsck messages) The system is coming up. Please wait (More messages) venus console login: |
Recovering from a invalid /etc/passwd file is used as an example of how to boot a system for recovery purposes.
Substitute the device name of the file system to be repaired for the devicename variable identified in the procedures below. If you need help identifying a system's device names, refer to Chapter 20, Accessing Devices (Overview).
Follow the instructions below depending on whether you are booting from the Solaris 2.x installation CD or the network.
Boot from the Solaris 2.x installation CD (or the network) to single-user mode using steps a-f.
If you are booting from the network, skip steps a and b.
Insert the Solaris 2.x installation CD into the CD caddy.
Insert the CD caddy into the CD-ROM drive.
Insert the Configuration Assistant/Boot Diskette into the primary diskette drive (DOS drive A).
Press any key to reboot the system if the system displays the type any key to reboot prompt. Or, use the reset button to restart the system if the system is shutdown.
The Boot Solaris screen is displayed after a few minutes.
Press the F2 key (F2_Continue) at the Solaris Device Configuration Assistant screen.
The identified devices are displayed in the next screen.
Press the F2 key (F2_Continue) at the Identified Devices screen.
Select the CD-ROM drive or net(work) as the boot device from the Boot Solaris screen. Then press the F2 key (F2_Boot Solaris).
The Solaris boot option screen is displayed.
Type b -s at the Select the type of installation: prompt.
After a few minutes, the single-user mode # prompt is displayed.
Mount the root (/) file system that has the invalid passwd file.
# mount /dev/dsk/devicename /a |
Change to the newly mounted etc directory.
# cd /a/etc |
Set the terminal type.
# TERM=AT386 # export TERM |
Make the necessary change to the passwd file using an editor.
# vi passwd |
Change to the root (/) directory.
# cd / |
Unmount the /a directory.
# umount /a |
Reboot the system.
# init 6 |
Verify the system boots to run level 3.
The login prompt is displayed when the boot process has finished successfully.
hostname console login: |
type any key to reboot Running Configuration Assistant... Solaris Device Configuration Assistant . . . Boot Solaris Select one of the identified devices to boot Solaris. > To make a selection, use the arrow keys, then press Enter to mark it [X]. Boot Solaris -------------------------------------------------------------------- [ ] DISK: IDE(ATA) QUANTUM FIREBALL1080A target: 0; port: 1F0-1F7, 3F6-3F7; irq: 14 [ ] NET : Intel EtherExpress network card port: 300-30F; irq: 5 FF2_Boot Solaris F3_Back F4_Boot Tasks F6_Help <<< Current Boot Parameters >>> Boot path: /isa/ata@1f0,0/cmdk@0,0:a Boot args: Type b [file-name] [boot-flags] to boot with options or i to enter boot interpreter or to boot with defaults <<< timeout in 5 seconds >>> Select (b)oot or (i)nterpreter: b -s # mount /dev/dsk/c0t3d0s0 /a # cd /a/etc # TERM=AT386 # export TERM # vi passwd (Remove invalid entry) # cd / # umount /a # init 6 |
The specific stop key sequence depends on your system type. For example, press the reset button to stop the system. If your system doesn't have a reset button, turn the power off and back on again.
Saving core dumps of the operating system is sometimes necessary for troubleshooting purposes. The savecore command is used to enable this feature. It can be turned on automatically by editing the /etc/init.d/sysetup script.
The savecore feature and how to set it up is described in Chapter 69, Generating and Saving System Crash Information. This section only describes how to reboot the system if the savecore feature is enabled.
Press Control-Alt-d.
kadb> |
The kadb> prompt is displayed.
Type 0:c at the kadb> prompt.
kadb> 0:c |
Type :c at the kadb> prompt.
kadb> :c |
After the crash dump is written to disk, the system will continue to reboot.
Verify the system has rebooted by logging in at the console login prompt.
Press <C ontrol-Alt-d> kadb> 0:c kadb> :c |