Chapter 10.  Booting a System (Tasks)

Table of Contents

Booting a System (Task Map)
Using the Boot PROM
How to Reset the System
Booting a SPARC Based System
Forcing a Crash Dump and Rebooting the System

Booting a System (Task Map)

Task

Description

For Instructions

Use the Boot PROM.

The boot PROM is used to boot a system. You might need to change the way the system boots. For example, you might want to reset the device to boot from or run hardware diagnostics before you bring the system to a multiuser level. Associated tasks include the following:

  • Identify the PROM revision number.

  • Identify devices on the system to boot from.

  • Change the default boot device when a new disk is added or when you need to change the system boot method.

How to Find the PROM Revision Number for a System

How to Identify Devices on a System

How to Change the Default Boot Device

Reset the system.

When you reset the system, the system runs diagnostic tests on the hardware, then reboots.

How to Reset the System

Boot a system.

Select one of the following boot methods:

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

  • Boot to run level S – Used after performing a system maintenance task such as backing up a file system. At this level, only local file systems are mounted and users cannot log in to the system.

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

  • Boot from the network – Used to boot a system from the network. This method is used for booting a diskless client.

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

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

How to Boot a System Interactively

How to Boot a System From the Network

Boot a system for recovery purposes.

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

  • Stop the system to attempt recovery.

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

How to Stop the System for Recovery Purposes

How to Boot a System for Recovery Purposes

Force a crash dump and reboot a system.

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

How to Force a Crash Dump and Reboot of the System

Troubleshoot problems with the kmdb command.

Boot kmdb – Used to troubleshoot system problems.

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

Use the 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 afterwards. Whereas, if you use the reboot command, the system will reboot automatically.