This chapter explains how to recover from an activation failure.If a failure is detected after upgrading or if the application is not compatible with an upgraded component, fall back to the original boot environment by using one of the following procedures, depending on your platform. For SPARC based systems:To Fall Back Despite Successful New Boot Environment Activation To Fall Back From a Failed Boot Environment Activation To Fall Back to the Original Boot Environment by Using a DVD, CD, or Net Installation Image For x86 based systems:To Fall Back Despite Successful New Boot Environment Activation With the GRUB Menu To Fall Back From a Failed Boot Environment Activation With the GRUB Menu To Fall Back From a Failed Boot Environment Activation With the GRUB Menu and the DVD or CD You can fallback to the original boot environment by using three methods:To Fall Back Despite Successful New Boot Environment Activation To Fall Back From a Failed Boot Environment Activation To Fall Back to the Original Boot Environment by Using a DVD, CD, or Net Installation Image Use this procedure when you have successfully activated your new boot environment, but are unhappy with the results. &suStepA;Type:# /sbin/luactivate BE_nameBE_nameSpecifies the name of the boot environment to be activated Reboot. # init 6The previous working boot environment becomes the active boot environment. If you experience a failure while booting the new boot environment and can boot the original boot environment in single-user mode, use this procedure to fall back to the original boot environment. If you need to boot from media or a net installation image, see To Fall Back to the Original Boot Environment by Using a DVD, CD, or Net Installation Image. At the OK prompt, boot the machine to single-user state from the Solaris Operating System DVD, Solaris Software - 1 CD, the network, or a local disk.OK boot device_name -sdevice_nameSpecifies the name of devices from where the system can boot, for example /dev/dsk/c0t0d0s0 Type:# /sbin/luactivate BE_nameBE_nameSpecifies the name of the boot environment to be activated If this command fails to display a prompt, proceed to To Fall Back to the Original Boot Environment by Using a DVD, CD, or Net Installation Image. If the prompt is displayed, continue. At the prompt, type:Do you want to fallback to activate boot environment <disk name> (yes or no)? yesA message displays that the fallback activation is successful. Reboot. # init 6The previous working boot environment becomes the active boot environment. Use this procedure to boot from a DVD, CD, a net installation image or another disk that can be booted. You need to mount the root (/) slice from the last-active boot environment. Then run the luactivate command, which makes the switch. When you reboot, the last-active boot environment is up and running again. At the OK prompt, boot the machine to single-user state from the Solaris Operating System DVD, Solaris Software - 1 CD, the network, or a local disk:OK boot cdrom -s orOK boot net -sorOK boot device_name -sdevice_nameSpecifies the name of the disk and the slice where a copy of the operating system resides, for example /dev/dsk/c0t0d0s0 If necessary, check the integrity of the root (/) file system for the fallback boot environment.# fsck device_namedevice_nameSpecifies the location of the root (/) file system on the disk device of the boot environment you want to fall back to. The device name is entered in the form of /dev/dsk/cwtxdysz. Mount the active boot environment root (/) slice to some directory, such as /mnt: # mount device_name /mntdevice_nameSpecifies the location of the root (/) file system on the disk device of the boot environment you want to fall back to. The device name is entered in the form of /dev/dsk/cwtxdysz. From the active boot environment root (/) slice, type:# /mnt/sbin/luactivateluactivate activates the previous working boot environment and indicates the result. Unmount /mnt# umount /mnt Reboot. # init 6The previous working boot environment becomes the active boot environment. To fall back to the original boot environment, choose the procedure the best fits your circumstances.To Fall Back Despite Successful New Boot Environment Activation With the GRUB Menu To Fall Back From a Failed Boot Environment Activation With the GRUB Menu To Fall Back From a Failed Boot Environment Activation With the GRUB Menu and the DVD or CD Use this procedure when you have successfully activated your new boot environment, but are dissatisfied with the results. You can quickly switch back to the original boot environment by using the GRUB menu.The boot environments that are being switched must be GRUB boot environments that were created with GRUB software. If a boot environment was created with the Solaris 8, 9, or 10 3/05 release, the boot environment is not a GRUB boot environment. &suStepA;Reboot the system.# init 6The GRUB menu is displayed. The Solaris OS is the original boot environment. The second_disk boot environment was successfully activated and appears on the GRUB menu. The failsafe entries are for recovery if for some reason the primary entry does not boot.GNU GRUB version 0.95 (616K lower / 4127168K upper memory) +-------------------------------------------------------------------+ |Solaris | |Solaris failsafe | |second_disk | |second_disk failsafe | +-------------------------------------------------------------------+ 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. To boot to the original boot environment, use the arrow key to select the original boot environment and press Return. # su # init 6GNU GRUB version 0.95 (616K lower / 4127168K upper memory) +-------------------------------------------------------------------+ |Solaris | |Solaris failsafe | |second_disk | |second_disk failsafe | +-------------------------------------------------------------------+ 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.Select the original boot environment, Solaris. If you experience a failure while booting, use the following procedure to fall back to the original boot environment. In this example, the GRUB menu is displayed correctly, but the new boot environment is not bootable. The device is /dev/dsk/c0t4d0s0. The original boot environment, c0t4d0s0, becomes the active boot environment.For the Solaris 10 3/05 release, the recommended action to fall back if the previous boot environment and new boot environment were on different disks included changing the hard disk boot order in the BIOS. Starting with the Solaris 10 1/06 release, changing the BIOS disk order is unnecessary and is strongly discouraged. Changing the BIOS disk order might invalidate the GRUB menu and cause the boot environment to become unbootable. If the BIOS disk order is changed, reverting the order back to the original settings restores system functionality. &suStepA;To display the GRUB menu, reboot the system.# init 6The GRUB menu is displayed.GNU GRUB version 0.95 (616K lower / 4127168K upper memory) +-------------------------------------------------------------------+ |Solaris | |Solaris failsafe | |second_disk | |second_disk failsafe | +-------------------------------------------------------------------+ 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. From the GRUB menu, select the original boot environment. The boot environment must have been created with GRUB software. A boot environment that was created before the Solaris 10 1/06 release is not a GRUB boot environment. If you do not have a bootable GRUB boot environment, then skip to this procedure, To Fall Back From a Failed Boot Environment Activation With the GRUB Menu and the DVD or CD. Boot to single user mode by editing the Grub menu.To edit the GRUB main menu, type e. The GRUB edit menu is displayed.root (hd0,2,a) kernel$ /platform/i86pc/kernel/$ISADIR/unix module$ /platform/i86pc/$ISADIR/boot_archiveStarting with the 5/07 Developer release, GRUB has enhanced support for directly booting the unix kernel. The new keyword, $ISADIR, resolves to amd64 for 64-bit hardware and to null for 32-bit hardware. See GRUB Menu Commands for Installation in Solaris Express Installation Guide: Network-Based Installations. Select the original boot environment's kernel entry by using the arrow keys. To edit the boot entry, type e. The kernel entry is displayed in the GRUB edit menu.grub edit>kernel$ /boot/platform/i86pc/kernel/unix Type -s and press Enter. The following example notes the placement of the s option.grub edit>kernel$ /boot/platform/i86pc/kernel/unix -s To begin the booting process in single user mode, type b. If necessary, check the integrity of the root (/) file system for the fallback boot environment.# fsck mount_ pointmount_pointA root (/) file system that is known and reliable Mount the original boot environment root slice to some directory (such as /mnt): # mount device_name /mntdevice_nameSpecifies the location of the root (/) file system on the disk device of the boot environment you want to fall back to. The device name is entered in the form of /dev/dsk/cwtxdysz. From the active boot environment root slice, type:# /mnt/sbin/luactivateluactivate activates the previous working boot environment and indicates the result. Unmount /mnt.# umount /mnt Reboot. # init 6The previous working boot environment becomes the active boot environment. If you experience a failure while booting, use the following procedure to fall back to the original boot environment. In this example, the new boot environment was not bootable. Also, the GRUB menu does not display. The device is /dev/dsk/c0t4d0s0. The original boot environment, c0t4d0s0, becomes the active boot environment.For the Solaris 10 3/05 release, the recommended action to fall back if the previous boot environment and new boot environment were on different disks included changing the hard disk boot order in the BIOS. Starting with the Solaris 10 1/06 release, changing the BIOS disk order is unnecessary and is strongly discouraged. Changing the BIOS disk order might invalidate the GRUB menu and cause the boot environment to become unbootable. If the BIOS disk order is changed, reverting the order back to the original settings restores system functionality. &suStepA;Insert the Solaris Operating System for x86 Platforms DVD or Solaris Software for x86 Platforms - 1 CD. Boot from the DVD or CD.# init 6The GRUB menu is displayed.For an installation with CD media:GNU GRUB version 0.95 (631K lower / 2095488K upper memory) +-------------------------------------------------------------------+ |Solaris Express 5/07 image_directory | |Solaris Express 5/07 Serial Console tty | |Solaris Express 5/07 Serial Console ttyb (for lx50, v60x and v65 | +-------------------------------------------------------------------+ 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. For an installation with a DVD media:GNU GRUB version 0.95 (631K lower / 2095488K upper memory) +-------------------------------------------------------------------+ |Solaris Express 5/07 Developer Edition image_directory | |Solaris Express 5/07 | |Solaris Express 5/07 Serial Console ttya | |Solaris Express 5/07 Serial Console ttyb (for lx50, v60x and v65) | +-------------------------------------------------------------------+ 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. Wait for the default option to boot or choose any option displayed.The installation screen is displayed.For CD media you see the following screen.+-------------------------------------------------------------------+ |Select the type of installation you want to perform: | | | | 1 Solaris Interactive | | 2 Custom JumpStart | | 3 Solaris Interactive Text (Desktop session) | | 4 Solaris Interactive Text (Console session) | | 5 Apply driver updates | | 6 Single user shell | | | | Enter the number of your choice followed by the <ENTER> key.| | Alternatively, enter custom boot arguments directly. | | | If you wait 30 seconds without typing anything, | | an interactive installation will be started. | +----------------------------------------------------------------- --+ For DVD media, you see the following screen. +--------------------------------------------------------------------+ |Select the type of installation you want to perform: | | | | 1 Solaris Interactive GUI | | 2 Apply driver updates | | 3 Single user shell | |Enter the number of your choice followed by the <ENTER> key. | |Alternatively, enter custom boot arguments directly. | | | | If you wait 30 seconds without typing anything, | | an interactive installation will be started. | +--------------------------------------------------------------------+ Choose the “Single user shell” option.The following message is displayed.Do you wish to automatically update the boot archive? y /n Type: nStarting shell... #You are now in single user mode. If necessary, check the integrity of the root (/) file system for the fallback boot environment.# fsck mount_ pointmount_pointA root (/) file system that is known and reliable Mount the original boot environment root slice to some directory (such as /mnt): # mount device_name /mntdevice_nameSpecifies the location of the root (/) file system on the disk device of the boot environment you want to fall back to. The device name is entered in the form of /dev/dsk/cwtxdysz. From the active boot environment root slice, type:# /mnt/sbin/luactivate Do you want to fallback to activate boot environment c0t4d0s0 (yes or no)? yesluactivate activates the previous working boot environment and indicates the result. Unmount /mnt.# umount device_namedevice_nameSpecifies the location of the root (/) file system on the disk device of the boot environment you want to fall back to. The device name is entered in the form of /dev/dsk/cwtxdysz. Reboot. # init 6The previous working boot environment becomes the active boot environment.