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 | | |
|---|
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
|
|
|