Chapter 12.  Booting a System (Tasks)

Table of Contents

Booting a System (Task Map)
Booting an x86 Based System
Booting From the Network
Using the Device Configuration Assistant
Forcing a Crash Dump and Reboot of the System
Troubleshooting a Failed 64-Bit Boot

Booting a System (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

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 Boot a System From the Network

Solaris 10: Use the Device Configuration Assistant on a Solaris Operating System x86 based system.

Note

Starting with the Solaris 10 1/06 and the Solaris Express 6/05 release, the Device Configuration Assistant has been replaced by the GRUB menu.

Used after changing the hardware configuration of the system. This utility enables you to boot the Solaris system from a different boot device, configure new or misconfigured hardware, or perform other device-related or boot-related tasks.

How to Enter the Device Configuration Assistant

Boot a system for recovery purposes.

Boot for recovery purposes - Used to boot the system when a damaged file is preventing the system from booting. You might need to do one or both of the following to boot for recovery purposes:

  1. First, stop the system to attempt recovery.

  2. Force a crash dump and reboot the system - Used to force a crash dump for troubleshooting purposes.

  3. Boot to repair an important system file that is preventing the system from booting successfully.

How to Stop a System for Recovery Purposes

Forcing a Crash Dump and Reboot of the System

How to Boot a System for Recovery Purposes

Boot kmdb – Used to troubleshoot system problems.

How to Boot a System With the Kernel Debugger (kmdb)

Use the reboot and halt command with the d option if you do not have time to debug the system interactively. Running 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.

Troubleshoot boot problems on systems that have 64-bit computing capabilities.

If you have hardware that requires the system to load one or more device drivers that are not available in 64-bit mode, booting the system to 64-bit mode could fail. You would then need to boot the system to 32-bit mode.

Troubleshooting a Failed 64-Bit Boot