GRUB Based Booting (Task Map)
Prev Chapter 11.  GRUB Based Booting (Tasks) Next

GRUB Based Booting (Task Map)

Task

Description

For Instructions

Boot a system.

Select one of the following boot options:

Boot to run level 3 – Used after shutting down the system or performing some system hardware maintenance task.

How to Boot a System to Run Level 3 (Multiuser Level)

Boot to run level S – Used after performing a system maintenance task, such as backing up a file system.

How to Boot a System to Run Level S (Single-User Level)

Boot interactively – Used after making temporary changes to a system file or the kernel for testing purposes.

How to Boot a System Interactively

Customize the Solaris boot behavior.

You can customize the Solaris boot behavior by using the eeprom command from the command-line. You can also customize the Solaris boot behavior by using the kernel command that is available in the GRUB menu.

Boot options that are set by using the eeprom command persist over a system reboot, unless these options are overridden by the kernel command. Boot options that are set by editing the GRUB menu or by using the kernel command persist until the next system reboot.

How to Set Solaris Boot Parameters by Using the eeprom Command

How to Modify the Solaris Boot Behavior by Editing the GRUB Menu

Boot a system from the network.

Used to boot a PXE or non-PXE device from the network with the default network configuration strategy. This method is used for booting a diskless client.

How to Perform a GRUB Based Boot From the Network

Boot the system in the failsafe archive for recovery purposes.

Used to boot the system when a damaged file is preventing the system from booting normally. You might need to do the following to boot for recovery purposes:

  • Stop the system to attempt recovery.

  • Boot the failsafe archive to update the boot archive or repair an important system file that is preventing the system from booting successfully.

How to Stop a System for Recovery Purposes

How to Boot the Failsafe Archive for Recovery Purposes

How to Boot the Failsafe Archive to Forcibly Update a Corrupt Boot Archive

  • Force a crash dump. Then, reboot the system – Used to force a crash dump for troubleshooting purposes.

  • Boot kmdb – Used to troubleshoot system problems.

Use the reboot and halt command with the d option if you do not have time to debug the system interactively. To run the halt command with the d option requires a manual reboot of the system afterwards. Whereas, if you use the reboot command, the system boots automatically. See the reboot ( 1M ) for more information.

Forcing a Crash Dump and Reboot of the System

How to Boot a System With the Kernel Debugger in the GRUB Based Boot Environment (kmdb)

Prev Up Next
GRUB Based Booting (Overview) Home  Booting a System in the GRUB Based Boot Environment