x86: How to Boot the Failsafe Archive to Forcibly
Update a Corrupt Boot Archive

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.

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.

Use the arrow keys to navigate the GRUB menu, then select the
failsafe entry. Press Return to boot the failsafe archive.

If
any boot archives are out of date, a message that is 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,?]

Type y, then press Enter to update the inconsistent
boot archive.

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 that is 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.

Mount the device that contains the corrupt boot archive on /a by typing the corresponding number of the device, then press
Enter.

Note –

If any inconsistent boot archives were updated in the previous
step, the device is already mounted on /a. Proceed to
Step 6.