A patch is needed to install Solaris Live
Upgrade. Ensure that you have the most recently updated patch list by consulting http://sunsolve.sun.com.
Search for the info doc 72099 on the SunSolve web site.

Upgradeable Solaris root devices were
found, however, no suitable partitions to hold the Solaris install software
were found. Upgrading using the Solaris Installer is not possible. It might
be possible to upgrade using the Solaris Software 1 CDROM. (x86 based systems
only)

Cause:

You cannot upgrade with the Solaris Software - 1 CD
because you do not have enough space.

Solution:

To upgrade, you can either create a swap
slice that is larger than or equal to 512 Mbytes or use another method of
upgrading such as the Solaris installation program from Solaris Operating System DVD, a net installation image,
or JumpStart.

ERROR: Could not select locale (x86 based systems only)

Cause:

When you test your JumpStart profile by using
the pfinstall-D command, the dry run test
fails under the following conditions:

The profile contains the locale keyword.

You're testing a release that contains GRUB software. Starting with the Solaris 10 1/06 release, the GRUB
boot loader facilitates booting different operating systems installed on your
system with the GRUB menu.

With the introduction of GRUB software, the miniroot is compressed.
The software can no longer find the list of locales from the compressed miniroot.
The miniroot is the smallest possible Solaris root (/)
file system and is found on the Solaris installation media.

The upgrade fails because the Solaris
installation program cannot mount a file system.

Cause:

During an upgrade, the script attempts to mount all the file systems
that are listed in the system's /etc/vfstab file on the
root (/) file system that is being upgraded. If the installation
script cannot mount a file system, it fails and exits.

Solution:

Ensure that all file systems in the system's /etc/vfstab file can be mounted. Comment out any file systems in
the /etc/vfstab file that cannot be mounted or that might
cause the problem so that the Solaris installation program does not try to
mount them during the upgrade. Any system-based file systems that contain
software to be upgraded (for example, /usr) cannot be
commented out.

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

Description:

The error messages are seen
when using the luupgrade command to upgrade a new boot
environment.

Cause:

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

Solution:

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

Example:

In the following example, the error message
indicates that the Solaris 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 Solaris Live Upgrade has not
been installed.

Cause:

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

Solution:

Before using Solaris Live Upgrade, always
install all the required patches. Ensure that you have the most recently updated
patch list by consulting http://sunsolve.sun.com. Search for the info doc 72099 on the SunSolve web site.

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. Solaris 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 Solaris 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:

Contain a mountable file system

Remain a part of the same Solaris Live Upgrade boot environment
where the slice resided previously

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 Solaris
Live Upgrade Running Veritas VxVm

When you use Solaris Live Upgrade while upgrading and running Veritas
VxVM, the system panics on reboot unless you upgrade by using the following
procedure. The problem occurs if packages do not conform to Solaris advanced
packaging guidelines.

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

If you install the Solaris 10 8/07 OS on a system that does
not currently include a service or diagnostic partition, the installation
program might not create a service partition by default. If you want to include
a service partition on the same disk as the Solaris partition, you must
re-create the service partition before you install the Solaris 10 8/07 OS.

If you installed the Solaris 8 2/02 OS on a system with a service partition,
the installation program might not have preserved the service partition.
If you did not manually edit the fdisk boot partition
layout to preserve the service partition, the installation program deleted
the service partition during the installation.

Note –

If you did not specifically preserve the service partition when
you installed the Solaris 8 2/02 OS, you might not be able to re-create the
service partition and upgrade to the Solaris 10 8/07 OS.

If you want to include a service partition on the disk that contains
the Solaris partition, choose one of the following workarounds.

To Install Software From a Network Installation Image or From
the Solaris Operating System DVD

To install the software from a net installation image or from the Solaris Operating System DVD over
the network, follow these steps.

Delete the contents of the disk.

Before you install, create the service partition by using the
diagnostics CD for your system.

For information about how to create
the service partition, see your hardware documentation.

Boot the system from the network.

The Customize fdisk Partitions screen is displayed.

To load the default boot disk partition layout, click Default.

The installation program preserves the service partition and creates
the Solaris partition.

To Install From the Solaris Software - 1 CD or From a Network
Installation Image

To use the Solaris installation program to install from the Solaris Software - 1 CD
or from a network installation image on a boot server, follow these steps.

Delete the contents of the disk.

Before you install, create the service partition by using the
diagnostics CD for your system.

For information about how to create
the service partition, see your hardware documentation.

The installation program prompts you to choose a method for creating
the Solaris partition.

Boot the system.

Select the Use rest of disk for Solaris partition option.

The installation program preserves the service partition and
creates the Solaris partition.