Go to main content

Booting and Shutting Down Oracle® Solaris 11.3 Systems

Exit Print View

Updated: October 2017

x86: How to Clear a Failed Automatic Boot Archive Update on a System That Does Not Support Fast Reboot

During the process of rebooting a system, if the system does not support the Fast Reboot feature, the automatic update of the boot archive could fail. This problem might result in the system's inability to reboot from the same boot environment.

In this case, a warning similar to the following is displayed, and the system enters system maintenance mode:

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 svc:/system/boot-config:default SMF service contains the auto-reboot-safe property, which is set to false by default. Setting the property to true communicates that both the system's firmware and the default GRUB menu entry are set to boot from the current boot device. The value of this property can be changed so that a failed automatic boot archive update can be cleared, as described in the following procedure.

  1. Assume the root role.

    See Using Your Assigned Administrative Rights in Securing Users and Processes in Oracle Solaris 11.3.

  2. Reboot the system.
    # reboot
  3. If the active BIOS or UEFI boot device and the GRUB menu entries point to the current boot instance, follow these steps to prevent a boot archive update failure:
    1. Set the auto-reboot-safe property of the svc:/system/boot-config SMF service to true, as follows:
      # svccfg -s svc:/system/boot-config:default setprop config/auto-reboot-safe = true
    2. Verify that the auto-reboot-safe property is set correctly.
      # svccfg -s svc:/system/boot-config:default listprop |grep config/auto-reboot-safe
      config/auto-reboot-safe            boolean  true