test

System Administration Guide: Basic Administration

ProcedureHow to Boot an x86 Based System in Failsafe Mode

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.

  1. Stop the system by using one of the methods described in the procedure, x86: How to Stop a System for Recovery Purposes.

  2. 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. 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.

  3. Use the arrow keys to navigate the GRUB menu to select a failsafe entry.

  4. Press Return to boot the failsafe archive.

    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,?]

  5. Type y to update the boot archive.

    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]:

    • If you choose not to mount a device, type q to continue to boot process.

    • If you choose to mount a device, follow these steps:

      1. Type the number of the device, then press Return.

        The system mounts the device on /a, and returns you to a shell prompt.

      2. Repair the critical system resource.

      3. When you are done repairing the critical system resource, unmount the device.


        # umount /a

      4. Reboot the system.


        # reboot