JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 10 1/13 Installation Guide: Live Upgrade and Upgrade Planning     Oracle Solaris 10 1/13 Information Library
search filter icon
search icon

Document Information

Preface

Part I Upgrading With Live Upgrade

1.  Where to Find Oracle Solaris Installation Planning Information

2.  Live Upgrade (Overview)

3.  Live Upgrade (Planning)

4.  Using Live Upgrade to Create a Boot Environment (Tasks)

5.  Upgrading With Live Upgrade (Tasks)

6.  Failure Recovery: Falling Back to the Original Boot Environment (Tasks)

7.  Maintaining Live Upgrade Boot Environments (Tasks)

8.  Upgrading the Oracle Solaris OS on a System With Non-Global Zones Installed

9.  Live Upgrade Examples

Part II Upgrading and Migrating With Live Upgrade to a ZFS Root Pool

10.  Live Upgrade and ZFS (Overview)

11.  Live Upgrade for ZFS (Planning)

12.  Creating a Boot Environment for ZFS Root Pools

13.  Live Upgrade for ZFS With Non-Global Zones Installed

Part III Appendices

A.  Live Upgrade Command Reference

B.  Troubleshooting (Tasks)

Problems With Setting Up Network Installations

Problems With Booting a System

Error Messages When Booting From Media

General Problems When Booting From Media

Booting From the Network, Error Messages

General Problems When Booting From the Network

Initial Installation of the Oracle Solaris OS

x86: How to Check an IDE Disk for Bad Blocks

Upgrading the Oracle Solaris OS

Upgrading Error Messages

General Problems When Upgrading

How to Continue Upgrading After a Failed Upgrade

x86: Problems With Live Upgrade When You Use GRUB

System Panics When Upgrading With Live Upgrade Running Veritas VxVm

How to Upgrade When Running Veritas VxVm

x86: Service Partition Not Created by Default on Systems With No Existing Service Partition

How to Include a Service Partition When Installing Software From a Network Installation Image or From the Oracle Solaris Operating System DVD

How to Include a Service Partition When Installing From the Oracle Solaris Software - 1 CD or From a Network Installation Image

C.  Additional SVR4 Packaging Requirements (Reference)

D.  Using the Patch Analyzer When Upgrading (Tasks)

Glossary

Index

How to Continue Upgrading After a Failed Upgrade

If the upgrade fails and the system cannot be soft-booted for reasons beyond your control, such as a power failure or a network connection failure, try to continue upgrading.

  1. Reboot the system from the Oracle Solaris Operating System DVD, the Oracle Solaris Software - 1 CD, or from the network.
  2. Choose the upgrade option for installation.

    The Oracle Solaris installation program determines whether the system has been partially upgraded and continues the upgrade.

x86: Problems With Live Upgrade When You Use GRUB

The following errors can occur when you use Live Upgrade and the GRUB boot loader on an x86 based system.

ERROR: The media product tools installation directory path-to-installation-directory does not exist.

ERROR: The media dirctory does not contain an operating system upgrade image.

Description: These error messages can occur when using the luupgrade command to upgrade a new boot environment.

Cause: An older version of Live Upgrade is being used. The Live Upgrade packages you have installed on your system are incompatible with the media and the release on that media.

Solution: Always use the Live Upgrade packages from the release you are upgrading to.

Example: In the following example, the error message indicates that the Live Upgrade packages on the system are not the same version as on the media.

# luupgrade -u -n s10u1 -s /mnt
    Validating the contents of the media </mnt>.
    The media is a standard Solaris media.
    ERROR: The media product tools installation directory 
</mnt/Solaris_10/Tools/Boot/usr/sbin/install.d/install_config> does 
not exist.
    ERROR: The media </mnt> does not contain an operating system upgrade 
image.

ERROR: Cannot find or is not executable: </sbin/biosdev>.

ERROR: One or more patches required by Live Upgrade has not been installed.

Cause: One or more patches required by Live Upgrade are not installed on your system. Beware that this error message does not catch all missing patches.

Solution: Before using Live Upgrade, always install all the required patches. Ensure that you have the most recently updated patch list by consulting http://support.oracle.com (My Oracle Support). Search for the knowledge document 1004881.1 - Live Upgrade Software Patch Requirements (formerly 206844) on My Oracle Support.

ERROR: Device mapping command </sbin/biosdev> failed. Please reboot and try again.

Cause: Reason 1: Live Upgrade is unable to map devices because of previous administrative tasks.

Solution: Reason 1: Reboot the system and try Live Upgrade again

Cause: Reason 2: If you reboot your system and get the same error message, you have two or more identical disks. The device mapping command is unable to distinguish between them.

Solution: Reason 2: Create a new dummy fdisk partition on one of the disks and then reboot the system. For more information, see the fdisk(1M) man page.

Cannot delete the boot environment that contains the GRUB menu

Cause: Live Upgrade imposes the restriction that a boot environment cannot be deleted if the boot environment contains the GRUB menu.

Solution: Use the lumake(1M) or luupgrade(1M) commands to reuse that boot environment.

The file system containing the GRUB menu was accidentally remade. However, the disk has the same slices as before. For example, the disk was not re-sliced.

Cause: The file system that contains the GRUB menu is critical to keeping the system bootable. Live Upgrade commands do not destroy the GRUB menu. But, if you accidentally remake or otherwise destroy the file system containing the GRUB menu with a command other than a Live Upgrade command, the recovery software attempts to reinstall the GRUB menu. The recovery software puts the GRUB menu back in the same file system at the next reboot. For example, you might have used the newfs or mkfs commands on the file system and accidentally destroyed the GRUB menu. To restore the GRUB menu correctly, the slice must adhere to the following conditions:

Before rebooting the system, make any necessary corrective actions on the slice.

Solution: Reboot the system. A backup copy of the GRUB menu is automatically installed.

The GRUB menu's menu.lst file was accidentally deleted.

Solution: Reboot the system. A backup copy of the GRUB menu is automatically installed.

System Panics When Upgrading With Live Upgrade Running Veritas VxVm