Go to main content

Booting and Shutting Down Oracle® Solaris 11.4 Systems

Exit Print View

Updated: August 2018
 
 

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

If a system does not support the Fast Reboot feature, the automatic update of the boot archive might fail. Consequently, the system might be unable to reboot from the same boot environment.

In this case, a warning similar to the following is displayed, and the system goes into 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 following steps describe how to recover from this failure.

Before You Begin

Ensure that your role has the appropriate rights profiles to perform this procedure. See Using Rights Profiles to Administer Boot Features.

  1. Reboot the system.
    $ reboot
  2. 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