1. Oracle Solaris Management Tools (Road Map)
2. Working With the Solaris Management Console (Tasks)
3. Working With the Oracle Java Web Console (Tasks)
4. Managing User Accounts and Groups (Overview)
5. Managing User Accounts and Groups (Tasks)
6. Managing Client-Server Support (Overview)
7. Managing Diskless Clients (Tasks)
8. Introduction to Shutting Down and Booting a System
9. Shutting Down and Booting a System (Overview)
10. Shutting Down a System (Tasks)
11. Modifying Oracle Solaris Boot Behavior (Tasks)
12. Booting an Oracle Solaris System (Tasks)
13. Managing the Oracle Solaris Boot Archives (Tasks)
Managing the Oracle Solaris Boot Archives (Task Map)
Description of the Oracle Solaris Boot Archives
Managing the boot-archive Service
How to Enable or Disable the boot-archive Service
Automatic Boot Archive Recovery
x86: How to Clear Automatic Boot Archive Update Failures by Using the auto-reboot-safe Property
How to Clear Automatic Boot Archive Update Failures by Using the bootadm Command
Using the bootadm Command to Manage the Boot Archives
How to Manually Update the Boot Archive by Using the bootadm Command
How to Manually Update the Boot Archive on a Solaris Volume Manager RAID-1 (Mirrored) Root Partition
How to List Contents of the Boot Archive
x86: How to Locate the Active GRUB Menu and List Current Menu Entries
x86: How to Set the Default Boot Entry for the Active GRUB Menu
14. Troubleshooting Booting an Oracle Solaris System (Tasks)
15. x86: GRUB Based Booting (Reference)
16. x86: Booting a System That Does Not Implement GRUB (Tasks)
17. Working With the Oracle Solaris Auto Registration regadm Command (Tasks)
18. Managing Services (Overview)
20. Managing Software (Overview)
21. Managing Software With Oracle Solaris System Administration Tools (Tasks)
22. Managing Software by Using Oracle Solaris Package Commands (Tasks)
Starting with the Oracle Solaris 10 9/10 release, boot archive recovery on the SPARC platform is fully automated. On the x86 platform, boot archive recovery is partially automated.
To support auto-recovery of the boot archives on the x86 platform, a new auto-reboot-safe property has been added to the boot configuration SMF service, svc:/system/boot-config:default. By default, this property's value is set to false, which prevents the system from automatically rebooting to an unknown boot device. However, if your system is configured to automatically reboot to the BIOS boot device and default GRUB menu entry that the Oracle Solaris OS is installed on, you can enable automatic recovery of the boot archives by setting this property's value to true. The following procedure describes how to clear automatic boot archive update failures on the x86 platform.
For information about how to clear automatic boot archive update failures by using the bootadm command, see How to Clear Automatic Boot Archive Update Failures by Using the bootadm Command.
On an x86 based systems, during the process of booting the system, if a warning similar to the following is displayed, take action as described in the following procedure.
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.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# reboot
To prevent this type of failure, if the active BIOS boot device and the GRUB menu entries point to the current boot instance, do the following:
# 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, take action accordingly:
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.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# bootadm update-archive
Manages the boot archives on a system.
Updates the current boot archive, if required. Applies to both SPARC and x86 based systems.
# reboot