Installation Bugs That Occur During an Upgrade

Be sure to read bug description ID 4121281 before you start upgrading
your IA (Intel architecture) based system to the Solaris 8 operating environment.

Upgrade Fails if /export Is Near Capacity (4409601)

If the /export directory is near full capacity
and you upgrade to the Solaris 8 7/01 operating environment, the space
requirements for /export are miscalculated and the upgrade
fails. The problem commonly occurs if a diskless client is installed, or if
third-party software is installed in /export. The following
message is displayed.

WARNING: Insufficient space for the upgrade.

Workaround: Before you upgrade, choose
one of the following workarounds.

Temporarily rename the /export directory
until the upgrade completes.

Temporarily comment out the /export line
in the /etc/vfstab file until the upgrade completes.

If /export is a separate file system,
then unmount /export before you perform the upgrade.

Unable to Remove .save.SUNWcsr After Upgrading
(4400054)

After upgrading from the Solaris 2.5.1 8/97 or 11/97 operating environments
to the Solaris 8 operating environment, the following error might appear
in /a/var/sadm/system/logs/upgrade_log.

Workaround: To prevent the error,
before you upgrade to the Solaris 8 operating environment, perform fsck on the root file system.

To resolve the error after you upgrade, perform fsck
on the root file system.

Upgrading Diskless Client Servers and Clients (4363078)

If your system currently supports diskless clients installed with the
AdminSuite 2.3 Diskless Client tool, you must first delete all existing diskless
clients prior to installing the Solaris 8 7/01 operating
environment. For specific instructions, see “How to Set Up Your Diskless
Client Environment” in Solaris 8 System Administration Supplement.

If you attempt to install the Solaris 8 7/01 operating
environment over existing diskless clients, the following error message appears.

The Solaris Version (Solaris 7) on slice <xxxxxxxx> cannot be upgraded.
There is an unknown problem with the software configuration installed
on this disk.

DiskSuite May Cause Data Loss (4121281)

The DiskSuiteTMmetadb replicas
contain driver names as part of the DiskSuite configuration data. In IA-based
systems that run versions 2.4, 2.5, 2.5.1, and 2.6 of the Solaris operating
environment, the SCSI driver name is cmdk. The cmdk driver has been replaced by the sd driver
in the Solaris 7 and 8 operating environments for IA-based systems.

Workaround: To avoid potential data
loss during upgrades to the Solaris 7 and 8 operating environments, you must
save the system's meta device configurations in text files and remove their metadb replicas before upgrading any IA-based system that is running
DiskSuite software. After you finish upgrading your IA-based system, you must
restore the meta device configurations by using the DiskSuite command line
interface.

The DiskSuite Version 4.2 Release Notes describe
a procedure for saving metadb configurations, removing metadb replicas, upgrading IA-based systems to the Solaris 7 and
8 operating environments, upgrading DiskSuite to version 4.2, and restoring
meta device configurations. Bourne shell scripts that automate the procedure
are available for the Solaris 7 and 8 operating environments.

Relocated CDE From the Solaris 2.5.1 Operating Environment Orphaned
by an Upgrade to the Solaris 8 Operating Environment (4260819)

This problem affects systems running the Solaris 2.5.1 and the Solaris
2.5.1 unbundled CDE operating environments. However, these systems are only
affected if the unbundled CDE has been relocated to a directory other than /usr/dt. The CDE relocation on these systems has been accomplished
by creating a symbolic link in /usr/dt
that points to the relocated CDE.

When you upgrade to the Solaris 8 operating environment, CDE is reinstalled
in /usr/dt, and the link to the relocated
version is removed. The relocated CDE is not removed and is therefore orphaned.

If the upgrade involves the reallocation of file systems, the upgrade
may fail because the reallocation mechanism does not account for the extra
space needed in /usr/dt for the new version of CDE. This
failure is not visible until the upgrade has been completed. If this failure
occurs, the upgrade log includes a number of messages indicating that more
space is needed for an upgrade.

Workaround: Uninstall the relocated
CDE before you start upgrading to the Solaris 8 operating environment. You
can uninstall by using the install-cde script from the
Solaris 2.5.1 CDE CD. You should run this script with the -uninstall flag to remove CDE.

If you installed WBEM 1.0 from the Solaris Easy Access Server (SEAS)
3.0 CD on a system running the Solaris 7 operating environment, you must remove
the WBEM 1.0 packages before upgrading to the Solaris 8 operating environment.
The Solaris WBEM Services 2.0 do not start after upgrading the Solaris 7 operating
environment with WBEM 1.0 to the Solaris 8 operating environment. The Common
Information Model (CIM) Object Manager fails to start. The following error
message is displayed.

File not found: /opt/sadm/lib/wbem/cimom.jar

Workaround: Use the pkgrm command to remove the WBEM 1.0 packages before upgrading to the Solaris 8
operating environment.

Use the pkginfo command to check if the
WBEM 1.0 packages are installed by typing: