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)
Booting a SPARC Based System (Task Map)
SPARC: How to Boot a System to Run Level 3 (Multiuser Level)
SPARC: How to Boot a System to Run Level S (Single-User Level)
SPARC: How to Boot a System Interactively
SPARC: How to Boot a Kernel Other Than the Default Kernel
Booting From a Specified ZFS Root File System on a SPARC Based System
SPARC: How to List Available Bootable Datasets Within a ZFS Root Pool
SPARC: How to Boot From a Specified ZFS Root File System
Booting a SPARC Based System in Failsafe Mode
How to Boot a SPARC Based System in Failsafe Mode
Booting a SPARC Based System From the Network
SPARC: How to Boot a System From the Network
Booting an x86 Based System by Using GRUB (Task Map)
x86: How to Boot a System to Run Level 3 (Multiuser)
x86: How to Boot a System to Run Level S (Single-User Level)
x86: How to Boot a System Interactively
x86: Booting From a Specified ZFS Root File System on an x86 Based System
x86: How to Display a List of the Available ZFS Boot Environments
x86: How to Boot From a Specified ZFS Root File System
Booting an x86 Based System in Failsafe Mode
How to Boot an x86 Based System in Failsafe Mode
x86: How to Boot in Failsafe Mode to Forcibly Update a Corrupt Boot Archive
Booting an x86 Based System from the Network
x86: How to Perform a GRUB Based Boot From the Network
13. Managing the Oracle Solaris Boot Archives (Tasks)
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)
To boot an x86 based system in failsafe mode, select the failsafe boot entry when the GRUB menu is displayed during a system boot. During the failsafe boot procedure, when prompted by the system, type y to update the primary boot archive.
Failsafe booting is also supported on systems that are booted from ZFS. When booting from a UFS-rooted BE, each BE has its own failsafe archive. The failsafe archive is located where the root file system is located, as is the case with a ZFS-rooted BE. On x86 based systems, each failsafe archive has an entry in the pool-wide GRUB menu. The default failsafe archive is the archive that is in the default bootable file system. The default bootable file system (dataset) is indicated by the value of the pool's bootfs property.
For more information about boot archive recovery, see the Chapter 13, Managing the Oracle Solaris Boot Archives (Tasks).
Note - The GRUB failsafe interaction in some Oracle Solaris releases prompts you to update the boot archive, regardless of whether any inconsistent boot archive are detected. In this release, the system only prompts you to update the boot archive if an inconsistent boot archive is detected.
You can also use the Reset button at this prompt. Or, you can use the power switch to reboot the system.
When the boot sequence begins, the GRUB menu is displayed.
GNU GRUB version 0.95 (637K lower / 3144640K upper memory) +-------------------------------------------------------------------+ | be1 | be1 failsafe | be3 | be3 failsafe | be2 | be2 failfafe +------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line.
Note - The GRUB menu that is displayed varies, depending on which Oracle Solaris release you are running.
The system searches for installed OS instances. If an inconsistent boot archive is detected, a message similar to the following is displayed:
Searching for installed OS instances... An out of sync boot archive was detected on /dev/dsk/c0t0d0s0. The boot archive is a cache of files used during boot and should be kept in sync to ensure proper system operation. Do you wish to automatically update this boot archive? [y,n,?]
If multiple inconsistent boot archives are detected, the system will prompt you to type y to update each inconsistent boot archive.
For each archive that is updated successfully, the following message is displayed:
Updating boot archive on /dev/dsk/c0t0d0s0. The boot archive on /dev/dsk/c0t0d0s0 was updated successfully.
After the boot archive is updated, the system searches again for all installed OS instances, then prompts you to select a device to mount on /a. Note that this same message is displayed when the system first boots if no inconsistent boot archives are detected.
Searching for installed OS instances... Multiple OS instances were found. To check and mount one of them read-write under /a, select it from the following list. To not mount any, select 'q'. 1 pool10:13292304648356142148 ROOT/be10 2 rpool:14465159259155950256 ROOT/be01 Please select a device to be mounted (q for none) [?,??,q]:
The system mounts the device on /a, and returns you to a shell prompt.
# umount /a
# reboot
This procedure shows how to rebuild an inconsistent or corrupt boot archive in the event you are not prompted by the system to update the boot archive the system, or in the event of a system hang or looping sequence occurs.
# reboot
If the system displays the Press any key to reboot prompt, press any key to reboot the system.
You can also use the Reset button at this prompt.
When the boot sequence begins, the GRUB menu is displayed.
+---------------------------------------------------------------------+ | Solaris 10.1... X86 | | Solaris failsafe | | | | | +-------------------------------------------------------------------------+ Use the and keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line.
Note - The contents of the GRUB menus vary, depending on the Solaris release you are running.
If any boot archives are out of date, a message t similar to the following is displayed:
Searching for installed OS instances... An out of sync boot archive was detected on /dev/dsk/c0t0d0s0. The boot archive is a cache of files used during boot and should be kept in sync to ensure proper system operation. Do you wish to automatically update this boot archive? [y,n,?]
The system displays the following message:
Updating boot archive on /dev/dsk/c0t0d0s0. The boot archive on /dev/dsk/c0t0d0s0 was updated successfully.
If no inconsistent boot archives are found, a message similar to the following is displayed:
Searching for installed OS instances... Solaris 10.1... X86 was found on /dev/dsk/c0t0d0s0. Do you wish to have it mounted read-write on /a? [y,n,?]
This message is also displayed after any inconsistent boot archives are updated successfully.
Note - If any inconsistent boot archives were updated in the previous step, the device is already mounted on /a.
# bootadm update-archive -f -R /a
# umount /a
# reboot
Example 12-14 x86: Booting in Failsafe Mode to Forcibly Update a Corrupt Boot Archive
This example shows how to boot the failsafe archive to forcibly update a corrupt boot archive.
GNU GRUB version 0.95 (635K lower / 523200K upper memory) +-------------------------------------------------------------------------+ | Solaris 10 1/06 s10x_u1wos_19a X86 | | >Solaris failsafe< | | | | | +-------------------------------------------------------------------------+ Use the and keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line. SunOS Release 5.10 Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Booting to milestone "milestone/single-user:default". Configuring devices. Searching for installed OS instances... Multiple OS instances were found. To check and mount one of them read-write under /a, select it from the following list. To not mount any, select 'q'. 1 /dev/dsk/c0t0d0s0 Solaris 10 1/06 s10x_u1wos_19a X86 2 /dev/dsk/c0t1d0s0 Solaris 10 5/08 X86 Please select a device to be mounted (q for none) [?,??,q]: 1 mounting /dev/dsk/c0t0d0s0 on /a Starting shell. # rm /a/platform/i86pc/boot_archive # bootadm update-archive -f -R /a Creating boot_archive for /a updating /a/platform/i86pc/amd64/boot_archive updating /a/platform/i86pc/boot_archive # umount /a # reboot syncing file systems... done rebooting... . . .