Skip Navigation Links | |
Exit Print View | |
![]() |
Booting and Shutting Down Oracle Solaris on x86 Platforms Oracle Solaris 11 Information Library |
1. Booting and Shutting Down an x86 Based System (Overview)
2. Booting an x86 Based System to a Specified State (Tasks)
3. Shutting Down a System (Tasks)
4. Rebooting an x86 Based System (Tasks)
5. Booting an x86 Based System From the Network (Tasks)
6. Modifying Boot Parameters on an x86 Based System (Tasks)
7. Creating, Administering, and Booting From ZFS Boot Environments on x86 Platforms (Tasks)
8. Keeping an x86 Based System Bootable (Tasks)
9. Troubleshooting Booting an x86 Based System (Tasks)
Troubleshooting Booting an x86 Based System (Task Map)
Shutting Down and Booting an x86 Based System for Recovery Purposes
Stopping and Booting a System for Recovery Purposes
How to Stop a System for Recovery Purposes
How to Boot in Single-User Mode 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
How to Force a Crash Dump and Reboot of the System
How to Boot a System With the Kernel Debugger Enabled (kmdb)
The following sections describe how to identify and resolve some common issues that you might encounter with the Fast Reboot feature of Oracle Solaris on x86 platforms.
Because the boot-config service has dependencies on the multiuser milestone, users who need to debug early panics can patch a global variable, fastreboot_onpanic in the /etc/system file, as shown in the following example:
# echo "set fastreboot_onpanic=1" >> /etc/system # echo "fastreboot_onpanic/W" | mdb -kw
The following are possible conditions under which the Fast Reboot feature might not work:
The GRUB menu cannot be processed.
The driver does not implement the quiesce function.
If you attempt a fast reboot of a system with an unsupported driver, a message similar to the following is displayed:
Sep 18 13:19:12 too-cool genunix: WARNING: nvidia has no quiesce() reboot: not all drivers have implemented quiesce(9E)
If the graphics drivers are the only drivers that do not support the quiesce function, you can attempt to force a fast reboot by running the following commands:
# echo "force_fastreboot/W 1" | mdb -kw# echo "set force_fast \ reboot = 1" #x26;#x26;#x3e;#x26;#x26;#x3e; /etc/system
Note - If the driver for the network interface card (NIC) does not implement the quiesce function, try to unplumb the interface first, then attempt a fast reboot of the system.
There is insufficient memory.
If there is not enough memory on the system, or not enough free memory to load the new kernel and the boot archive, the fast reboot attempt fails with the following messages, then falls back to a regular reboot:
Fastboot: Couldn't allocate size below PA 1G to do fast reboot Fastboot: Couldn't allocate size below PA 64G to do fast reboot
The environment is unsupported.
Fast reboot functionality is not supported in the following environments:
An Oracle Solaris release that is running as a paravirtualized (PV) guest domain
Non-global zones
For more information, see the following man pages: