test

Solaris 8 (SPARC Platform Edition) 2/02 Release Notes

Chapter 1 Installation Issues

This chapter describes problems that relate to the installation of the Solaris 8 2/02 operating environment.

The following installation bug descriptions have been added to this chapter since this document was published on the Solaris 8 2/02 Documentation CD and in the Installation Kiosk on the Solaris 8 2/02 Installation CD.

Note -

The name of this product is Solaris 8 2/02 , but code and path or package path names might use Solaris 2.8 or SunOSTM 5.8. Always follow the code or path as it is written.

Issues You Need to Know About Before Installing Solaris 8 Software from DVD

Booting From the Solaris 8 2/02 DVD

The Solaris 8 2/02 operating environment is now available on DVD. To install or upgrade from DVD, insert the Solaris 8 2/02 DVD into the DVD-ROM drive and boot the system from the ok prompt with the following command. 


ok boot cdrom

Boot From Solaris DVD Fails on Systems With Toshiba SD-M1401 DVD-ROM (4467424)

If your system has a Toshiba SD-M1401 DVD-ROM drive with firmware revision 1007, the system cannot boot from the Solaris 8 2/02 DVD.

Workaround: Apply patch 111649 to update the Toshiba SD-M1401 DVD-ROM drive's firmware. Patch 111649 is included on the Solaris 8 Supplement CD in the following directory.


DVD_Firmware/Patches

See the README file in this directory for instructions on installing the patch. Be sure to read and follow all the cautions and warnings in this README file before you install the patch.

Cannot Access Data on Solaris 8 2/02 DVD in Solaris 2.6 and Solaris 7 Operating Environment (4511090)

If your system is running the Solaris 2.6 or Solaris 7 operating environment, Volume Management incorrectly mounts the Solaris 8 2/02 DVD. The Solaris 8 2/02 DVD will mount, but the data is inaccessible. As a result, you cannot setup an install server, perform a Live Upgrade, or access any data on the media.

Workaround: Choose one of the following workarounds.

Solaris Web Start 3.0 Bugs You Need to Know About Before Using the Solaris 8 Installation CD

Initial Install Might Not Be Possible If Swap Slice Does Not Start At Cylinder 0 (4508297)

When you install from the Solaris 8 Installation CD, the SolarisTM Web Start installation program might prompt you to use an existing swap slice to hold the installation software. However, the installation program does not indicate whether the existing swap slice starts at cylinder 0 or not. If you choose to use this slice and it does not begin at cylinder 0, installation might not be possible on some disk configurations.

Workaround: If you intend to perform an initial install, follow these steps.

Note -

This will prevent any file system preservations on the disk.

  1. During setup, answer No to all questions that prompt you to use an existing swap slice.

  2. If prompted, select None from the list of alternatives, then answer No when you are prompted to re-select a slice to hold the Solaris installation software.

  3. Select a disk to re-partition when you are prompted by the installer.

  4. Choose a size when you are prompted to provide a size for the swap slice.

  5. When the installer asks if the swap slice can start at the beginning of the disk, answer Yes.

  6. Complete the installation.

For more information on re-partitioning disks or choosing a size for the swap slice, see the Solaris 8 Advanced Installation Guide.

Default Install Might Be Disabled If Swap Slice Is Not on The Default Boot Disk (4527984)

When you install from the Solaris 8 Installation CD and you choose a swap slice that is not on the default boot disk, the Default Install selection might be disabled. This problem can occur even when the swap slice starts at cylinder 0 and the default boot disk contains sufficient space for a Default Install. The following error message is displayed.


Note:Default install is not possible.The file system requires manual layout.

Workaround: Choose one of the following workarounds.

Cannot Specify an Alternate Network Interface to Use During System Identification on Network Gateway Systems (4302896)

A network gateway is used to communicate with other networks. A gateway system contains multiple network interface adapters and each adapter connects with a different network.

If you use the Solaris 8 Installation CD to install the Solaris 8 2/02 operating environment on a gateway system, Solaris Web Start 3.0 uses the primary interface to gather system information. You cannot instruct Solaris Web Start 3.0 to use an alternate network interface to gather information for system identification.

Workaround: To specify another interface for gathering system information, choose one of the following workarounds.

Issues You Need to Know About Before Installing Solaris 8 Software

Insufficient Space for Extra Languages During Upgrade (4414329)

When you upgrade from the Solaris 2.6 and Solaris 7 operating environments using a CD or CD images, extra European languages might be installed for locales that are not present on the system. If there is insufficient space in the file system, the upgrade will not complete. Languages for locales that are present on the system may not be installed.

Workaround: Choose one of the following workarounds.

Previous Versions of Solaris Management Console Software Are Not Compatible With Solaris Management Console 2.0 Software

If you upgrade to the Solaris 8 2/02 , or compatible, operating environment and you have Solaris Management ConsoleTM 1.0, 1.0.1, or 1.0.2 software installed, you must uninstall the Solaris Management Console software before you upgrade. Solaris Management Console 2.0 software is not compatible with any previous version of the console. Solaris Management Console software might exist on your system if you installed the SEAS 2.0 overbox, the SEAS 3.0 overbox, or the Solaris 8 Admin Pack.

Workaround: Choose one of the following workarounds.

Locale Installation Mechanism Change

The locale support installation mechanism has changed in the Solaris 8 operating environment. In the Solaris 2.5.1, 2.6, and 7 operating environments, the level of locale support that was installed depended on the software cluster that was chosen. The Solaris 8 operating environment includes a new installation interface that prompts you to select specific geographic regions for which you require locale support. Therefore, you can customize the configuration of your system at installation of the Solaris 8 operating environment with more freedom than in the Solaris 2.5.1, 2.6, and 7 operating environments.

Notice especially the following behaviors:

Installation Bugs That Occur During an Installation From Solaris 8 1 of 2 CD

Solaris 8 Software 2 of 2 Installation Program Does Not Automatically Start When Using Custom JumpStart or re-preinstall (4556860)

If you install using the custom JumpStartTM program or the re-preinstall command, when the Solaris 8 Software 1 of 2 CD completes, the Solaris 8 Software 2 of 2 CD installation program does not automatically start. The system will reboot normally, but the installation is not complete.

Workaround: If you are performing a custom JumpStart installation, or you are using the re-preinstall command, choose one of the following workarounds.

Installation Progress Bar May Be Inaccurate (1266156)

The Installing Solaris Software - Progress bar sometimes indicates that an installation is complete when it is still in progress. The installation program might add packages for several minutes after the progress bar has indicated that the installation is complete.

Do not rely on the progress bar to indicate that the installation is complete. The installation displays the following message when the program has completed all installation operations.


Installation complete

Warnings May Occur When a File System Is Created (4189127)

One of the following warning messages might be displayed when a file system is created during installation.


Warning: inode blocks/cyl group (87) >= data blocks (63) 
in last cylinder group. This implies 1008 sector(s) cannot be allocated.

Or


Warning: 1 sector(s) in last cylinder unallocated

The warning occurs when the size of the file system that is being created does not map exactly to the space on the disk that is being used. This discrepancy can result in unused space on the disk that is not incorporated into the indicated file system. This unused space is not available for use by other file systems.

Workaround: Ignore the warning message.

Custom JumpStart Does Not Prompt for the Solaris 8 Software 2 of 2 CD (4304912)

After you install the Solaris 8 Software 1 of 2 CD, a custom JumpStart installation does not prompt you to install the Solaris 8 Software 2 of 2 CD.

Workaround: Choose one of the following workarounds.

Installation Bugs That Occur During an Upgrade

Live Upgrade Might Not Determine Boot Device (4525464)

If you boot from a Solstice DiskSuiteTM or a SolarisTM Volume Manager mirrored root, or a Veritas encapsulated root, the lucreate command might be unable to determine the boot device. The following error message is displayed.


WARNING: Unable to determine root device by accessing boot device settings directly.
ERROR: Unable to determine root device for current BE.
ERROR: Unable to determine the physical boot device for the current BE <...>.
Use the <-C> command line option to specify the physical boot device for the current BE 
<...>

If you use lucreate -C to specify the physical boot device the command fails.

Workaround: Manually edit /usr/sbin/lucreate to enable Live Upgrade to determine the boot device from a Solstice DiskSuite or a Solaris Volume Manager mirrored root, or a Veritas encapsulated root. Follow these steps.

  1. Make a backup copy of /usr/sbin/lucreate.

  2. Open /usr/sbin/lucreate in a text editor.

  3. Locate the following line in /usr/sbin/lucreate.


    elif [ "${dpbe_pbeBootDev}" -eq "-" ] ; then

  4. Change the previous line to the following. 


    elif [ "${dpbe_pbeBootDev}" = '-' ] ; then

  5. Locate the following line in /usr/sbin/lucreate.


     if [ "${OPTARG}" -ne "-" ] ; then

  6. Change the previous line to the following.


    if [ "${OPTARG}" != '-' ] ; then

  7. Save the changes to /usr/sbin/lucreate.

The lucreate command can now determine the boot device and the -C option will function correctly.

You can remove the backup copy of /usr/sbin/lucreate when the upgrade completes.

Upgrade Fails if /export Is Near Capacity (4409601)

If the /export directory is near full capacity and you upgrade to the Solaris 8 2/02 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.

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

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


rm: Unable to remove directory /a/var/sadm/pkg/.save.SUNWcsr: File exists

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 that were installed with the AdminSuite 2.3 Diskless Client tool, you must first delete all existing diskless clients prior to installing the Solaris 8 2/02 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 2/02 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.

Upgrading the JavaSpaces Datastore to Prevent Web-Based Enterprise Management (WBEM) Data Loss (4365035)

If you are upgrading from the Solaris 8 (Solaris WBEM Services 2.0), Solaris 8 6/00 (WBEM Services 2.1), Solaris 8 10/00 (WBEM Services 2.2), or Solaris 8 1/01 (WBEM Services 2.3) operating environments to the Solaris 8 2/02 operating environment (Solaris WBEM Services 2.4), you must convert any proprietary custom Managed Object Format (MOF) data to the new Reliable Log repository format that is used with Solaris WBEM Services 2.4. Failure to convert the data results in data loss.

Workaround: To convert WBEM data, before upgrading you must save the JavaSpacesTM software. After upgrading, you must run the wbemconfig convert command.

Before upgrading to the Solaris 8 2/02 operating environment, follow these steps to save the JavaSpaces software.

  1. Become superuser.

  2. Save the JavaSpaces software.

    cp /usr/sadm/lib/wbem/outrigger.jar /usr/sadm/lib/wbem/outrigger.jar.tmp

  3. Check and record the version of the JDKTM software that is installed on your machine. For example:

    # /usr/bin/java -version 
java version "1.2.1" 
Solaris VM (build Solaris_JDK_1.2.1_04c, native threads, sunwjit)

    You must be running the same version of the JDK software that was running when the original JavaSpaces datastore was created.

Note -

After upgrading to the Solaris 8 2/02 operating environment, you must convert the WBEM data. For specific instructions, see "Upgrading the CIM Object Manager Repository" in Solaris WBEM Services Administrator's Guide.

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 that run 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 might fail because the reallocation mechanism does not allow for the extra space that is 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 several messages that indicate 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.

Upgrading the Solaris 7 Operating Environment With WBEM 1.0 to the Solaris 8 Operating Environment Causes WBEM 2.0 to Fail (4274920)

If you installed WBEM 1.0 from the Solaris Easy Access Server (SEAS) 3.0 CD on a system that runs 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 you upgrade 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.

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


    % pkginfo | grep WBEM

  2. Become superuser.

  3. Use the pkgrm command to remove all WBEM 1.0 packages by typing the following.


    # pkgrm SUNWwbapi
# pkgrm SUNWwbcor
# pkgrm SUNWwbdev
# pkgrm SUNWwbdoc
# pkgrm SUNWwbm

SUNWeeudt Partially Fails to Install During an Upgrade (4304305)

The upgrade log might state that the SUNWeeudt package was only partially installed.


     Doing pkgadd of SUNWeeudt to /.
     ERROR: attribute verification of 
     </a/usr/dt/appconfig/types/ru_RU.KOI8-R/datatypes.dt> 
     failed pathname does not exist ...

     Installation of <SUNWeeudt> partially failed.
     pkgadd return code = 2

Workaround: Perform the following steps after the upgrade has been completed.

  1. To remove the SUNWeeudt package, type the following.


    # pkgrm SUNWeeudt

  2. To add the SUNWeeudtpackage, type the following.


    # pkgadd SUNWeeudt

64-bit Packages Are Unnecessarily Installed During Upgrade From Solaris 2.6 or Solaris 7 Operating Environment (4323398)

When you upgrade to the Solaris 8 2/02 operating environment from the Solaris 2.6 or Solaris 7 operating environment and do not select 64-bit support as an upgrade option, the following 64-bit packages are unnecessarily installed:

Workaround: After you complete the upgrade, remove these 64-bit packages by using the pkgrm command:


# pkgrm SUNWceuox SUNWeeuox SUNWneuox SUNWseuox SUNWweuox

64-Bit Solaris Issues

Sun UltraSPARC System (sun4u) May Need Boot Flash PROM Update

Note -

If your system is already running 64-bit ready firmware, then the flash PROM update is not required.

If you want to run the 64-bit Solaris operating environment on an UltraSPARCTM system, you might need to update its flash PROM firmware. The Solaris 8 installation programs have an option for adding 64-bit support. This 64-bit support is selected by default when you install on Sun UltraSPARC systems. A 64-bit system only boots in the 64-bit mode by default if it has a CPU speed of 200 MHz or greater.

Note -

If you choose to run the 32-bit Solaris operating environment on any SunTM or UltraSPARC system, the flash PROM update is not needed.

The following table lists the UltraSPARC (sun4u) systems that are affected and the minimum firmware versions that are needed. System type is the equivalent of the output of the uname -i command. You can tell which firmware version you are running by using the prtconf -V command.

Table 1-2 Minimum Firmware Versions Required to Run 64-Bit Solaris Operating Environment on UltraSPARC Systems

System Type From uname -i

Minimum Firmware Version From prtconf -V

SUNW,Ultra-1-Engine 

3.10.0 

SUNW,Ultra-1 

3.11.1 

SUNW,Ultra-2 

3.11.2 

SUNW,Ultra-4 

3.7.107 

SUNW,Ultra-Enterprise 

3.2.16 

Note -

If a system is not listed in the previous table, it does not need a flash PROM update.

For instructions on performing the flash PROM update by using the Solaris CD, refer to the Solaris 8 on Sun Hardware Collection. If you do not have this manual, you can obtain it at http://docs.sun.com.

System Administration Bugs

awk and nawk Field Limitation Might Cause Installation of Additional Software to Fail (4533901)

The 200 field limitation of the awk and nawk utilities might cause installations of additional software to fail. This problem occurs under the following circumstances.

A message similar to the following text displays.


Installing VxVM for Solaris 8
awk: record `Patch: 108528-13 Obs...' has too many fields
 record number 12

        Alternate Pathing (AP) version 2.3.1 has been detected.

        This version of VxVM requires the following patch(es) 
        to co-existwith AP 2.3.1:

                110722

        Install the above patch(es) before you continue the VxVM
        installation. This installation will now be aborted.

pkgadd: ERROR: request script did not complete successfully

Installation of <VRTSvxvm> failed.
No changes were made to the system.

Workaround: Contact your support channels to obtain the Solaris patch that increases the awk and nawk field limitation.

Localization Bugs That Occur During Installation

Solaris Web Start Installation Kiosk Menu Not Localized for European Locales (4510925)

If you use the Solaris 8 2/02 Installation CD to install in a European locale, the Kiosk menu that appears at the end of the installation process displays in the C locale.

Error Messages May Occur During European Upgrade (4230247, 4225787)

After upgrading from the Solaris 7 3/99, 5/99, 8/99, or 11/99 operating environment to the Solaris 8 2/02 operating environment, the following errors might appear in the upgrade logs.


Doing pkgadd of SUNWplow to /.
pkgadd: ERROR: unable to create package object 
</a/usr/openwin/share/locale/de.ISO8859-15>.
    file type <s> expected <d> actual
    unable to remove existing directory at 
</a/usr/openwin/share/locale/de.ISO8859-15>
....
Installation of <SUNWplow> partially failed.
pkgadd return code = 2


Doing pkgadd of SUNWpldte to /.
WARNING: /a/usr/dt/appconfig/types/de.ISO8859-15 
may not overwrite a populated directory.
......
pkgadd: ERROR: /a/usr/dt/appconfig/types/de.ISO8859-15 
could not be installed.
.......
Installation of <SUNWpldte> partially failed.
pkgadd return code = 2

This warning occurs because the patch switches the affected directories in the upgrade logs from symbolic links to directories. The upgrade process then attempts to install an updated version of the package that does not include the change. These errors do not affect the operating environment on your system.

Workaround: Ignore these error messages.