|
|||
Part I Upgrading With Solaris Live Upgrade 1. Where to Find Solaris Installation Planning Information 2. Solaris Live Upgrade (Overview) 3. Solaris Live Upgrade (Planning) 4. Using Solaris Live Upgrade to Create a Boot Environment (Tasks) 5. Upgrading With Solaris Live Upgrade (Tasks) 6. Failure Recovery: Falling Back to the Original Boot Environment (Tasks) 7. Maintaining Solaris Live Upgrade Boot Environments (Tasks) 8. x86: Locating the GRUB Menu's menu.lst File (Tasks) 9. Upgrading the Solaris OS on a System With Non-Global Zones Installed 10. Solaris Live Upgrade (Examples) Example of Detaching and Upgrading One Side of a RAID-1 Volume (Mirror) Example of Migrating From an Existing Volume to a Solaris Volume Manager RAID-1 Volume Example of Creating an Empty Boot Environment and Installing a Solaris Flash Archive 11. Solaris Live Upgrade (Command Reference) |
Example of Upgrading With Solaris Live UpgradeIn this example, a new boot environment is created by using the lucreate command on a system that is running the Solaris 9 release. The new boot environment is upgraded to the Solaris Express 5/07 release by using the luupgrade command. The upgraded boot environment is activated by using the luactivate command. An example of falling back to the original boot environment is also given. To Install Solaris Live Upgrade on the Active Boot EnvironmentNote - This procedure assumes that the system is running removable media services. If you have questions about removable media services that manage discs, refer to System Administration Guide: Devices and File Systems for detailed information.
To Create a Boot EnvironmentThe source boot environment is named c0t4d0s0 by using the -c option. Naming the source boot environment is required only when the first boot environment is created. For more information about naming using the -c option, see the description in “To Create a Boot Environment for the First Time” Step 2. The new boot environment is named c0t15d0s0. The -A option creates a description that is associated with the boot environment name. The root (/) file system is copied to the new boot environment. Also, a new swap slice is created rather than sharing the source boot environment's swap slice. # lucreate -A 'BE_description' -c /dev/dsk/c0t4d0s0 -m /:/dev/dsk/c0t15d0s0:ufs\ -m -:/dev/dsk/c0t15d0s1:swap -n /dev/dsk/c0t15d0s0 To Upgrade the Inactive Boot EnvironmentThe inactive boot environment is named c0t15d0s0. The operating system image to be used for the upgrade is taken from the network. # luupgrade -n c0t15d0s0 -u -s /net/ins-svr/export/Solaris_11 \ combined.solaris_wos To Check if Boot Environment Is BootableThe lustatus command reports if the boot environment creation is complete. lustatus also shows if the boot environment is bootable. # lustatus boot environment Is Active Active Can Copy Name Complete Now OnReboot Delete Status ------------------------------------------------------------------------ c0t4d0s0 yes yes yes no - c0t15d0s0 yes no no yes - To Activate the Inactive Boot EnvironmentThe c0t15d0s0 boot environment is made bootable with the luactivate command. The system is then rebooted and c0t15d0s0 becomes the active boot environment. The c0t4d0s0 boot environment is now inactive. # luactivate c0t15d0s0 # init 6 (Optional) To Fall Back to the Source Boot EnvironmentThe following procedures for falling back depend on your new boot environment activation situation:
In this example, the original c0t4d0s0 boot environment is reinstated as the active boot environment although it was activated successfully. The device name is first_disk. # /sbin/luactivate first_disk # init 6Example 10-2 SPARC: To Fall Back From a Failed Boot Environment Activation In this example, the new boot environment was not bootable. You must return to the OK prompt before booting from the original boot environment, c0t4d0s0, in single-user mode. OK boot net -s # /sbin/luactivate first_disk Do you want to fallback to activate boot environment c0t4d0s0 (yes or no)? yes # init 6 The original boot environment, c0t4d0s0, becomes the active boot environment. Example 10-3 SPARC: To Fall Back to the Original Boot Environment by Using a DVD, CD, or Net Installation ImageIn this example, the new boot environment was not bootable. You cannot boot from the original boot environment and must use media or a net installation image. The device is /dev/dsk/c0t4d0s0. The original boot environment, c0t4d0s0, becomes the active boot environment. OK boot net -s # fsck /dev/dsk/c0t4d0s0 # mount /dev/dsk/c0t4d0s0 /mnt # /mnt/sbin/luactivate Do you want to fallback to activate boot environment c0t4d0s0 (yes or no)? yes # umount /mnt # init 6Example 10-4 x86: To Fall Back to the Original Boot Environment By Using the GRUB Menu Starting with the Solaris 10 1/06 release, the following example provides the steps to fall back by using the GRUB menu. In this example, the GRUB menu is displayed correctly, but the new boot environment is not bootable. To enable a fallback, the original boot environment is booted in single-user mode.
# b # fsck /dev/dsk/c0t4d0s0 # mount /dev/dsk/c0t4d0s0 /mnt # /mnt/sbin/luactivate Do you want to fallback to activate boot environment c0t4d0s0 (yes or no)? yes # umount /mnt # init 6Example 10-5 x86: To Fall Back to the Original Boot Environment With the GRUB Menu by Using the DVD or CD Starting with the Solaris 10 1/06 release, the following example provides the steps to fall back by using the DVD or CD. In this example, the new boot environment was not bootable. Also, the GRUB menu does not display. To enable a fallback, the original boot environment is booted in single-user mode.
|
||
|