| Skip Navigation Links | |
| Exit Print View | |
|
Booting and Shutting Down Oracle Solaris 11.1 Systems Oracle Solaris 11.1 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Booting and Shutting Down Oracle Solaris 11.1 Systems Oracle Solaris 11.1 Information Library |
1. Booting and Shutting Down a System (Overview)
2. x86: Administering the GRand Unified Bootloader (Tasks)
3. Shutting Down a System (Tasks)
5. Booting a System From the Network (Tasks)
6. Troubleshooting Booting a System (Tasks)
Managing the Oracle Solaris Boot Archives
How to List Contents of the Boot Archive
Managing the boot-archive SMF Service
How to Enable or Disable the boot-archive SMF Service
How to Clear a Failed Automatic Boot Archive Update by Manually Updating the Boot Archive
Shutting Down and Booting a System for Recovery Purposes
SPARC: How to Stop a System for Recovery Purposes
x86: How to Stop and Reboot a System for Recovery Purposes
How to Boot to a Single-User State to Resolve a Bad root Shell or Password Problem
How to Boot From Media to Resolve an Unknown root Password
Forcing a Crash Dump and Reboot of the System
SPARC: How to Force a Crash Dump and Reboot of the System
x86: How to Force a Crash Dump and Reboot of the System
Booting a System With the Kernel Debugger (kmdb) Enabled
SPARC: How to Boot a System With the Kernel Debugger (kmdb) Enabled
x86: How to Boot a System With the Kernel Debugger (kmdb) Enabled
x86: Troubleshooting Issues With Fast Reboot
x86: Debugging Early Panics That Might Occur
The following are issues you might encounter when booting a system:
Services do not start at boot time.
A system might hang during boot time, if there are problems starting any Service Management Facility (SMF) services. To troubleshoot this type of issue, you can boot the system without starting any services. For more information, see How to Boot Without Starting Any Services in Managing Services and Faults in Oracle Solaris 11.1
system/filesystem/local:default SMF service fails during boot.
Local file systems that are not required to boot the system are mounted by the svc:/system/filesystem/local:default service. When any of those file systems cannot be mounted, the service enters a maintenance state. System startup continues, and any services that do not depend on filesystem/local are started. Subsequently, any services that require filesystem/local to be online before starting through dependencies are not started. The workaround for this issue is to change the configuration of your system so that a sulogin prompt is displayed immediately after the service fails instead of allowing the system startup to continue. For more information, see How to Force an sulogin Prompt If the system/filesystem/local:default Service Fails During Boot in Managing Services and Faults in Oracle Solaris 11.1.
|