1. Oracle Solaris Management Tools (Road Map)
2. Working With the Solaris Management Console (Tasks)
3. Working With the Oracle Java Web Console (Tasks)
4. Managing User Accounts and Groups (Overview)
5. Managing User Accounts and Groups (Tasks)
6. Managing Client-Server Support (Overview)
7. Managing Diskless Clients (Tasks)
8. Introduction to Shutting Down and Booting a System
9. Shutting Down and Booting a System (Overview)
10. Shutting Down a System (Tasks)
11. Modifying Oracle Solaris Boot Behavior (Tasks)
12. Booting an Oracle Solaris System (Tasks)
13. Managing the Oracle Solaris Boot Archives (Tasks)
14. Troubleshooting Booting an Oracle Solaris System (Tasks)
15. x86: GRUB Based Booting (Reference)
16. x86: Booting a System That Does Not Implement GRUB (Tasks)
x86: Booting a System (Task Map)
x86: Booting a System That Does Not Implement GRUB
x86: How to Boot a System to Run Level 3 (Multiuser Level)
x86: How to Boot a System to Run Level S (Single-User Level)
x86: How to Boot a System Interactively
x86: How to Boot a System From the Network
x86: Using the Device Configuration Assistant
x86: How to Enter the Device Configuration Assistant
x86: How to Stop a System for Recovery Purposes
x86: How to Boot a System for Recovery Purposes
x86: How to Boot a System With the Kernel Debugger (kmdb)
x86: Forcing a Crash Dump and Reboot of the System
x86: Boot Processes (Reference)
x86: Booting the Solaris Release
x86: Screens Displayed During the Device Identification Phase
x86: Device Configuration Assistant Screen
x86: Identified Devices Screen
x86: Menus Displayed During the Boot Phase
x86: Current Boot Parameters Menu
17. Working With the Oracle Solaris Auto Registration regadm Command (Tasks)
18. Managing Services (Overview)
20. Managing Software (Overview)
21. Managing Software With Oracle Solaris System Administration Tools (Tasks)
22. Managing Software by Using Oracle Solaris Package Commands (Tasks)
The following procedures use the reset button to restart the system. If your system does not have a reset button, use the power switch to restart the system. You might be able to press Ctrl-Alt-Del to interrupt system operation, depending upon the state of the system.
Use this procedure to boot a system that is currently at run level 0 to run level 3.
You can also use the Reset button at this prompt. If the system is shut down, turn the system on with the power switch.
The Current Boot Parameters menu is displayed after a few minutes.
If you do not make a selection within five seconds, the system is automatically booted to run level 3.
The login prompt is displayed when the boot process has finished successfully.
hostname console login:
Example 16-1 x86: Booting a System to Run Level 3 (Multiuser Level)
For new installations, typing b at the boot prompt automatically boots 64-bit capable x86 based systems to 64-bit mode. For upgrades, typing b at the boot prompt also boots 64-bit capable x86 based systems to 64-bit mode, unless the eeprom boot-file parameter was previously set to a value other than kernel/unix.
This example shows how to boot an x86 based system that has 64-bit computing capabilities to run level 3.
Press 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 SunOS Release 5.10 Version amd64-gate-2004-09-27 64-bit Copyright 1983-2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. DEBUG enabled Hostname: venus NIS domain name is example.com checking ufs filesystems /dev/rdsk/c1d0s7: is logging. venus console login:
Example 16-2 x64: Manually Booting a System That Has 64-Bit Computing Capabilities in 64-Bit Mode to Run Level 3 (Multiuser Level)
For new installations, typing b at the boot prompt automatically boots 64-bit capable x86 based systems to 64-bit mode. For upgrades, typing b at the boot prompt also boots 64-bit capable x86 based systems to 64-bit mode, unless the eeprom boot-file parameter was previously set to a value other than kernel/unix.
This example shows how to manually boot this type of system in 64-bit mode to run level 3.
# init 0 # svc.startd: The system is coming down. Please wait. svc.startd: 68 system services are now being stopped. umount: /etc/svc/volatile busy svc.startd: The system is down. syncing file systems... done Press any key to reboot. Initializing system Please wait... <<< 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 kernel/amd64/unix SunOS Release 5.10 Version amd64-gate-2004-09-27 64-bit Copyright 1983-2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. DEBUG enabled Hostname: venus NIS domain name is example.com checking ufs filesystems /dev/rdsk/c1d0s7: is logging. venus console login:
Example 16-3 Manually Booting a System That Has 64-Bit Computing Capabilities in 32–Bit Mode to Run Level 3 (Multiuser Level)
For new installations, typing b at the boot prompt automatically boots 64-bit capable x86 based systems to 64-bit mode. For upgrades, typing b at the boot prompt also boots 64-bit capable x86 based systems to 64-bit mode, unless the eeprom boot-file parameter was previously set to a value other than kernel/unix.
This example shows how to manually boot this type of system in 32-bit mode to run level 3.
# init 0 # svc.startd: The system is coming down. Please wait. svc.startd: 68 system services are now being stopped. umount: /etc/svc/volatile busy svc.startd: The system is down. syncing file systems... done Press any key to reboot. Resetting... If the system hardware has changed, or to boot from a different device, interrupt the autoboot process by pressing ESC. Initializing system Please wait... <<< 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 kernel/unix SunOS Release 5.10 Version amd64-gate-2004-09-30 32-bit Copyright 1983-2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. DEBUG enabled Hostname: venus NIS domain name is example.com checking ufs filesystems /dev/rdsk/c1d0s7: is logging. venus console login:
Use this procedure to boot a system that is currently at run level 0 to run level S.
You can also use the Reset button at this prompt. If the system is shut down, turn the system on with the power switch.
The Current Boot Parameters menu is displayed after a few minutes.
If you do not make a selection within five seconds, the system is automatically booted to run level 3.
# who -r . run-level S Jul 19 14:37 S 0 3
Example 16-4 x86: Booting a System to Run Level S (Single-User Level)
Press any key to reboot. Resetting... . . . Initializing system Please wait... <<< 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 SunOS Release 5.10 Version amd64-gate-2004-09-30 32-bit Copyright 1983-2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. DEBUG enabled Booting to milestone "milestone/single-user:default". Hostname: venus NIS domain name is example.com Requesting System Maintenance Mode SINGLE USER MODE Root password for system maintenance (control-d to bypass): xxxxxx Entering System Maintenance Mode . . . # who -r . run-level S Jul 19 14:37 S 0 3 (Perform some maintenance task) # ^D
Use this procedure to boot a system when you need to specify an alternate kernel or the /etc/system file.
You can also use the reset button at this prompt. If the system is shut down, turn the system on with the power switch.
The Primary Boot Subsystem menu is displayed after a few minutes.
If you do not make a selection within five seconds, the active boot partition is selected automatically.
The Current Boot Parameters menu is displayed after a few minutes.
If you do not make a selection within five seconds, the system is automatically booted to run level 3.
Press enter to use the default kernel file name. Otherwise, provide the name of an alternate kernel, press Enter.
Press enter to use the default module directories. Otherwise, provide the alternate paths to module directories, press Enter.
Type /dev/null if your /etc/system file has been damaged.
Press enter to select local disk booting with UFS, which is the default, or enter NFS for network booting.
Provide an alternate device name or press return to use the default.
Example 16-5 x86: Booting a System Interactively
In the following example, the default choices (shown in square brackets []) are accepted.
Press any key to reboot. Resetting... . . . Autobooting from bootpath: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a If the system hardware has changed, or to boot from a different device, interrupt the autoboot process by pressing ESC. Initializing system Please wait... <<< 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 Running Configuration Assistant... <<< timeout in 5 seconds >>> Select (b)oot or (i)nterpreter: b -a Enter default directory for modules [/platform/i86pc/kernel /kernel /usr/kernel]: Press Enter Name of system file [etc/system]: Press Enter SunOS Release 5.10 Version amd64-gate-2004-09-30 32-bit Copyright 1983-2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. DEBUG enabled root filesystem type [ufs]: Press Enter Enter physical name of root device[/pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a]: Press Enter Hostname: venus NIS domain name is example.com checking ufs filesystems /dev/rdsk/c1d0s7: is logging. venus console login:
Any system can boot from the network if a boot server is available. You might want to boot a stand-alone system from the network for recovery purposes if the system cannot boot from the local disk.
You can boot Solaris OS x86 based systems directly from a network without the Solaris boot diskette on x86 based systems that support the Preboot Execution Environment (PXE) network booting protocol. The PXE network boot is available only for devices that implement the Intel Preboot Execution Environment specification. If the system is capable of a PXE network boot, you might want to boot the system directly from the network without using either the Device Configuration Assistant boot diskette or the Solaris Software 1 CD or DVD.
Note - In this Oracle Solaris release, the software is delivered on DVD only.
This procedure includes instructions for booting an x86 based system from the network with the Solaris Device Configuration Assistant. Note that the behavior of the Device Configuration assistant changed, starting with the Oracle Solaris OS.
Starting with the Solaris 10 1/06 release, GRUB based booting has been implemented on x86 based systems that are running the Solaris OS. The GRUB menu replaces the Device Configuration Assistant. For information about booting an x86 based system from the Network with GRUB, see Booting an x86 Based System from the Network.
There are two network configuration strategies, Reverse Address Resolution Protocol (RARP) or Dynamic Host Configuration Protocol (DHCP). The default network boot strategy for a PXE network boot is DHCP. The default network boot strategy for non-PXE devices is RARP. For non-PXE devices, you can use either strategy, depending on whether a RARP boot server or a DHCP boot server is available on your network.
Note - If you use a DHCP server for PXE network boots, additional DHCP configuration is required. For general information on DHCP configuration, see Part III, DHCP, in System Administration Guide: IP Services. If you want to set up your DHCP server to support installation, see Oracle Solaris 10 9/10 Installation Guide: Network-Based Installations.
If you are performing a PXE network boot, or if you are booting the system from the Solaris Software media, the system boots automatically. The Device Configuration Assistant menu is no longer displayed by default. If you are booting a non-PXE device, you will need to follow the steps in this procedure that describe how to enter the Device Configuration Assistant menu to change the network configuration.
If you are using the boot diskette, the first menu of the Device Configuration Assistant is displayed.
If you are using the Oracle Solaris Software 1 CD, DVD, or booting a PXE device from the network, the system boots automatically.
If you choose to change the network configuration and enter the Device Configuration Assistant menu, press ESC when the following message is displayed.
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.
The Device Configuration Assistant screen is displayed.
You can also use the reset button at this prompt. If the system is shut down, turn the system on with the power switch.
Device identification is performed. Then, the Identified Devices screen is displayed.
Bootable drivers are loaded. Then, the Boot Solaris menu is displayed.
Note - The previous step applies only if you are booting a non-PXE device from the network. For a PXE network boot, you must use DHCP, which is the default network boot strategy.
A message that confirms your new network boot strategy is displayed. Your network boot strategy selection is saved as the default network boot method for the next time the diskette is used for booting.
The Solaris boot option screen is displayed.
Note - In this Solaris release the Device Configuration Assistant has been replaced by the GRUB menu. For more information about this feature, see Booting an x86 Based System by Using GRUB (Task Map).
Solaris 10: The Device Configuration Assistant for the Oracle Solaris x86 based systems is a program that enables you to perform various hardware configuration and booting tasks.
You can access the Device Configuration Assistant menu from either of the following:
Solaris boot diskette
Oracle Solaris Software 1 CD or DVD
PXE network boot
Hard disk with Solaris OS installed
For the procedures in this chapter, you might be requested to insert the Device Configuration Assistant boot diskette to boot the Configuration Assistant. Alternately, if your system's BIOS supports booting from the CD or DVD, you can insert the Solaris Software 1 CD or DVD to boot the Device Configuration Assistant.
Solaris 10: This procedure shows how to interrupt the boot process to enter the Device Configuration Assistant. In the current Solaris release, the GRUB menu replaces the Device Configuration Assistant.
If you are booting from the Device Configuration boot diskette, the first menu of the Device Configuration Assistant is displayed after a few minutes.
If you are booting from the Oracle Solaris Software 1 CD, DVD, hard disk, or performing a PXE network boot, the following message is displayed:
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.
If you choose to enter the Device Configuration Assistant menu, press ESC to interrupt the autoboot process.
The Device Configuration Assistant menu is displayed.
You can also use the reset button at this prompt. If the system is shut down, turn the system on with the power switch.
Follow these steps to boot the system to repair a critical system resource. The example shows you how to boot from an Oracle Solaris Software CD, DVD, or from 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 device-name variable. If you need help identifying a system's device names, refer to Displaying Device Configuration Information in System Administration Guide: Devices and File Systems.
Use the Stop key sequence for your system if you don't know the root password, or if you can't log in to the system. For more information, see x86: How to Stop a System for Recovery Purposes.
Note - If you are using the boot diskette the Device Configuration Assistant menu is displayed. If you are using the Oracle Solaris Software CD or DVD, the system boots automatically. To enter the Device Configuration Assistant menu, press ESC to interrupt the boot process, when prompted by the system.
You can also use the Reset button at this prompt. If the system is shut down, turn the system on with the power switch.
After a few minutes, the single-user mode # prompt is displayed.
The login prompt is displayed when the boot process has finished successfully.
host-name console login:
Example 16-6 x86: Solaris 10: Booting a System for Recovery Purposes
The following example shows how to repair the /etc/passwd file after booting the system automatically from a local CD-ROM in Oracle Solaris 10. GRUB based booting was introduced in the Solaris 10 1/06 release. For information about booting a system for recovery purposes in a GRUB based boot environment, see How to Boot an x86 Based System in Failsafe Mode.
SunOS Secondary Boot version 3.00 Solaris Booting System Running Configuration Assistant... 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. Initializing system Please wait... <<< Current Boot Parameters >>> Boot path: /pci@0,0/pci-ide@7,1/ide@1/sd@0,0:a Boot args: Select the type of installation you want to perform: 1 Solaris Interactive 2 Custom JumpStart 3 Solaris Interactive Text (Desktop session) 4 Solaris Interactive Text (Console session) Enter the number of your choice followed by the <ENTER> key. Alternatively, enter custom boot arguments directly. If you wait for 30 seconds without typing anything, an interactive installation will be started. Select type of installation: b -s . . . # mount /dev/dsk/c0t0d0s0 /a . . . # cd /a/etc # vi passwd (Remove invalid entry) # cd / # umount /a # init 6
This procedure shows the basics for loading the kernel debugger (kmdb) in Oracle Solaris 10. The savecore feature is enabled by default. For more detailed information about using the kernel debugger, see the Oracle Solaris Modular Debugger Guide.
For step-by-step instructions on booting a system with the kernel debugger in the current Solaris release, see x86: How to Boot a System With the Kernel Debugger in the GRUB Boot Environment (kmdb).
The method used to enter the debugger is dependent upon the type of console that is used to access the system:
If a locally attached keyboard is being used, press F1–A.
If a serial console is being used, send a break by using the method appropriate to the type of serial console that is being used.
A welcome message is displayed when you access the kernel debugger for the first time.
Example 16-7 x86: Booting a System With the Kernel Debugger (kmdb)
Typing b -k at the Select (b)oot or (i)nterpreter boot prompt boots a system to its default mode and also loads kmdb. This example shows how to boot an x86 based system that has 32–bit computing capabilities to 32–bit mode and also load kmdb.
Press 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 Running Configuration Assistant... <<< timeout in 5 seconds >>> Select (b)oot or (i)nterpreter: b -k Loading kmdb... SunOS Release 5.10 Version gate:2004-10-21 32-bit Copyright 1983-2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. . . .
Example 16-8 x64: Manually Booting a System That Has 64-Bit Computing Capabilities to 64-Bit Mode With the Kernel Debugger (kmdb)
This example shows how to manually boot an x86 based system that has 64-bit computing capabilities to 64-bit mode with kmdb.
Press 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 kernel/amd64/unix -k Loading kmdb...
Example 16-9 32-bit x64: Manually Booting a System That Has 64-Bit Computing Capabilities to 32-Bit Mode With the Kernel Debugger (kmdb)
This example shows how to manually boot an x86 based system that has 64-bit computing capabilities to 32-bit mode with kmdb.
Press 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 kernel/unix -k Loading kmdb...
Forcing a crash dump and rebooting the system is sometimes necessary for troubleshooting purposes. The savecore feature is enabled by default.
For more information on system crash dumps, see Chapter 17, Managing System Crash Information (Tasks), in System Administration Guide: Advanced Administration.
If you cannot use the reboot -d or the halt -d command, you can use the kernel debugger, kmdb, to force a crash dump. The kernel debugger must have been loaded, either at boot, or with the mdb -k command, for the following procedure to work.
Note - You must be in text mode to enter the kernel debugger (kmdb). So, first exit any window system.
The kmdb prompt is displayed.
[0]> $<systemdump
Panic messages are displayed, the crash dump is saved, and the system reboots.
Example 16-10 x86: Forcing a Crash Dump and Reboot of the System by Using halt -d
This example shows how to force a crash dump and reboot of the x86 based system neptune by using the halt -d and boot commands. Use this method to force a crash dump of the system. You will need to manually reboot the system after running the halt command with the -d option.
# halt -d Aug 11 12:51:27 neptune halt: halted by <user> panic[cpu45]/thread=d3971a00: forced crash dump initiated at user request d363ae58 genunix:kadmin+bd (5, 0, 0, d3fefac0) d363af88 genunix:uadmin+88 (5, 0, 0, 0, 0, d363afb4) syncing file systems... done dumping to /dev/dsk/c0t0d0s1, offset 107806720, content: kernel 100% done: 40223 pages dumped, compression ratio 4.11, dump succeeded Press any key to reboot. Resetting... . . . SunOS Secondary Boot version 3.00 Autobooting from bootpath: /pci@0,0/pci1028,10a@3/sd@0,0:a Running Configuration Assistant... If the system hardware has changed, or to boot from a different device, interrupt the autoboot process by pressing ESC. Initializing system Please wait... <<< Current Boot Parameters >>> Boot path: /pci@0,0/pci1028,10a@3/sd@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: Loading kmdb... SunOS Release 5.10 Version s10_62 32-bit Copyright 1983-2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. configuring IPv4 interfaces: iprb0. add net default: gateway 172.20.26.248 Hostname: neptune The system is coming up. Please wait. checking ufs filesystems /dev/rdsk/c0t0d0s7: is logging. NIS domain name is example.com starting rpc services: rpcbind keyserv ypbind done. Setting netmask of iprb0 to 255.255.255.0 Setting default IPv4 interface for multicast: add net 224.0/4: gateway venus syslog service starting. System dump time: Wed Aug 11 12:51:29 2004 Aug 11 13:13:26 venus savecore: saving system crash dump in /var/crash/venus/*.1 Constructing namelist /var/crash/venus/unix.1 Constructing corefile /var/crash/venus/vmcore.1 100% done: 42157 of 42157 pages saved volume management starting. The system is ready. . . .
In some instances, an attempt to boot a 64-bit capable x86 based system to 64-bit mode might fail. This failure might produce an error similar to the following:
Select (b)oot or (i)nterpreter: b kernel/amd64/unix . . . pci: cannot load driver Cannot load drivers for /pci@0,0/pci1022,7450@a/pci17c2,10@4/sd@0,0:a (Can't load the root filesystem) Press any key to reboot. . . .
In the event such a failure occurs, boot the system to 32-bit mode by typing the following command at the Select (b)oot or (i)nterpreter boot prompt:
Select (b)oot or (i)nterpreter: b kernel/unix
For more information, see Example 16-3.