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)
Keeping an x86 Based System Bootable (Task Map)
Description of the Oracle Solaris Boot Archives
Obtaining Information About the Location and Contents of the x86 Boot Archive
How to List the Contents of the Boot Archive
Managing the Boot Archive SMF Service
Determining Whether the boot-archive SMF Service Is Running
How to Enable or Disable the boot-archive SMF Service
Maintaining the Integrity of the Boot Archives
How to Clear a Failed Automatic Boot Archive Update by Using the auto-reboot-safe Property
How to Clear a Failed Automatic Boot Archive Update by Manually Updating the Boot Archive
The boot administration interface, bootadm, enables you to perform the following tasks for maintaining the Oracle Solaris boot archive:
List the files and directories that are included in a system's boot archive.
Manually update the boot archive.
The syntax of the command is as follows:
bootadm [subcommand] [-option] [-R altroot]
For more information about the bootadm command, see the bootadm(1M) man page.
Boot archive recovery on x86 platforms is automated through the Fast Reboot feature. However, during the process of booting the system, if a warning similar to the following is displayed:
WARNING: Reboot required. The system has updated the cache of files (boot archive) that is used during the early boot sequence. To avoid booting and running the system with the previously out-of-sync version of these files, reboot the system from the same device that was previously booted.
The system then enters system maintenance mode. As a result, the automatic update of the boot archive fails. To correct the problem, follow the steps in this procedure.
# reboot
# svccfg -s svc:/system/boot-config:default setprop config/auto-reboot-safe = true
# svccfg -s svc:/system/boot-config:default listprop |grep config/auto-reboot-safe config/auto-reboot-safe boolean true
During the process of booting the system, if a warning message that is similar to the following is displayed, and as a result, the automatic update of the boot archive fails.
WARNING: Automatic update of the boot archive failed. Update the archives using 'bootadm update-archive' command and then reboot the system from the same device that was previously booted.
The following procedure describes how to manually update an out-of-date boot archive by using the bootadm command.
Note - The same procedure can be used to manually update the boot archive on an x86 based system.
# bootadm update-archive
Note - To update the boot archive on an alternate root, type:
# bootadm update-archive -R /a
Specifies an alternate root path to apply to the update-archive subcommand.
Caution - The root file system of any non-global zone must not be referenced with the -R option. Doing so might damage the global zone's file system, compromise the security of the global zone, or damage the non-global zone's file system. See the zones(5) man page. |
# reboot