JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Booting and Shutting Down Oracle Solaris 11.1 Systems     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information


1.  Booting and Shutting Down a System (Overview)

What's New in Booting and Shutting Down a System

x86: GRUB 2 Is the Default Boot Loader

x86: Support for 64-Bit UEFI Firmware

Support for Booting From GPT Labeled Disks

Large Disk Installation Support

Support for Creating Boot Partitions Based on Firmware Type With the zpool create Command

iSCSI Boot

SPARC: End of Support for Most sun4u Platforms

Guidelines for Booting a System

Reasons to Boot a System

Overview of the Oracle Solaris Boot Architecture

Description of the Oracle Solaris Boot Archives

Description of the Boot Process

x86: Differences Between UEFI and BIOS Boot Methods

x86: Creating Boot Partitions That Support Systems With UEFI and BIOS Firmware

Service Management Facility and Booting

Changes in Boot Behavior When Using SMF

2.  x86: Administering the GRand Unified Bootloader (Tasks)

3.  Shutting Down a System (Tasks)

4.  Booting a System (Tasks)

5.  Booting a System From the Network (Tasks)

6.  Troubleshooting Booting a System (Tasks)


Guidelines for Booting a System

Bootstrapping is the process of loading and executing the bootable operating system. Typically, the stand-alone program is the operating system kernel, but any stand-alone program can be booted. After the kernel is loaded, it starts the UNIX system, mounts the necessary file systems, and runs /usr/sbin/init to bring the system to the initdefault state that is specified in the /etc/inittab file.

Keep the following guidelines in mind when booting a system:

Reasons to Boot a System

The following table lists reasons that you might need to boot a system. The system administration tasks and the corresponding boot option that is used to complete the task is also described.

Table 1-1 Booting a System

Reason for System Reboot
Appropriate Boot Option
For More Information
Turn off system power due to anticipated power outage.
Turn system power back on
Change kernel parameters in the /etc/system file.
Reboot the system to a multiuser state (run level 3 with NFS resources shared)
Perform file system maintenance, such as backing up or restoring system data.
Press Control-D from a single-user state (run level S) to bring the system back to a multiuser state (run level 3)
Repair a system configuration file such as /etc/system.
Interactive boot
Add or remove hardware from the system.
Reconfiguration boot (turn on system power after adding or removing devices, if devices are not hot-pluggable)
Boot a system for recovery purposes due to a lost root password, or to fix a file system or a similar problem.
Depending on the error condition or problem, you might need to boot the system from media, mount the boot environment, or both.
x86 only: Recover from a problem with the GRUB configuration.
Recovery boot from media.
Recover from a hung system by forcing a crash dump.
Recovery boot
Boot the system by using the kernel debugger (kmdb) to track down a system problem.
Booting kmdb