Upgrade Issues and Bugs

This section describes upgrade bugs. Some might occur while you are upgrading to Solaris 10 OS. Others might occur after you have completed upgrading.

Device ID Discrepancies After Upgrading From Solaris 9 9/04 OS

In this Solaris 10 release, Solaris Volume Manager displays device ID output in a new format. Solaris 9 9/04 OS, which introduced device ID support in disk sets, does not recognize the new format. When you upgrade to Solaris 10 OS from the Solaris 9 9/04 release, device IDs that are associated with existing disk sets are not updated in the Solaris Volume Manager configuration. If you need to revert to Solaris 9 9/04 OS, configuration changes made to disk sets after the upgrade might not be available to Solaris 9 9/04 OS. For more information, see Chapter 25, Troubleshooting Solaris Volume Manager (Tasks), in Solaris Volume Manager Administration Guide.

SPARC: Upgrading From Solaris 9 Releases With Recommended Patch Cluster Partially Succeeds (6202868)

For a system that is running a Solaris 9 release with the recommended patch cluster installed, upgrading to Solaris 10 OS only partially succeeds. This problem affects systems that are running the following releases with the Solaris 9 recommended patch cluster installed.

• Solaris 9 release

• Solaris 9 9/02 release

• Solaris 9 12/02 release

• Solaris 9 4/03 release

• Solaris 9 8/03 release

• Solaris 9 12/03 release

• Solaris 9 4/04 release

When you upgrade to the Solaris 10 release, the SUNWcti2x package is not successfully removed from the system.

Workaround: Choose one of the following workarounds.

• To avoid this problem, apply patch ID 117426-03, or a later version, to the system before you upgrade to the Solaris 10 OS.

  To download this patch, go to http://sunsolve.sun.com.

• If you encounter this problem during the upgrade, follow these steps.

  1. In a text editor, comment out the following line in the /var/sadm/pkg/SUNWcti2x/install/preremove file.

     rem_drv -b ${BASEDIR} sc_nct || EXIT=1

  2. Remove the SUNWcti2x package.

     # pkgrm SUNWcti2x

Obsolete Uninstallers Not Removed When You Use Solaris Live Upgrade to Upgrade From Previous Solaris Releases (6198380)

If you use Solaris Live Upgrade to upgrade from the Solaris 8 or Solaris 9 releases to Solaris 10 OS, obsolete uninstaller programs are not removed. These uninstaller programs from the previous OS remain in the system's /var/sadm/prod directory.

The following obsolete uninstallers are not removed.

uninstall_Alternate_Pathing_2_3_1.class
uninstall_CDRW_1_1.class o uninstall_CDRW_1_0.class
uninstall_Bonus_Localization_-_Catalan_CDE_Desktop.class
uninstall_Bonus_Localization_-_Polish_CDE_Desktop.class
uninstall_Bonus_Localizations_-_Russian_CDE_Desktop.class
uninstall_Capacity_on_Demand_1_0.class
uninstall_Java3D_1_3_1.class
uninstall_Java3D_1_3.class
uninstall_Java3D_1_2_1_04.class
uninstall_Java3D_1_2_1_03.class
uninstall_Lights_Out_Management_2_0.class
uninstall_Man_Page_Supplement.class
uninstall_OpenGL_1_3.class
uninstall_OpenGL_1_2_3.class
uninstall_Netra_ct_Platform_1_0.class
uninstall_Netra_t11xx_Alarms_2_0.class
uninstall_Netscape_6_2_3.class
uninstall_Netscape_6_2_1_Beta.class
uninstall_PC_launcher_1_0_2.class
uninstall_PC_launcher_1_0_1_PCfileviewer_1_0_1.class
uninstall_RSC_2_2_2.class
uninstall_RSC_2_2_1.class
uninstall_RSC_2_2.class
uninstall_ShowMeTV_1_3.class
uninstall_Solaris_9_French_Localization.class
uninstall_Solaris_9_German_Localization.class
uninstall_Solaris_9_Hong_Kong_Traditional_Chinese_Localization.class
uninstall_Solaris_9_Italian_Localization.class
uninstall_Solaris_9_Japanese_Localization.class
uninstall_Solaris_9_Korean_Localization.class
uninstall_Solaris_9_Simplified_Chinese_Localization.class
uninstall_Solaris_9_Spanish_Localization.class
uninstall_Solaris_9_Swedish_Localization.class
uninstall_Solaris_9_Traditional_Chinese_Localization.class
uninstall_Solaris_On_Sun_Hardware_Documentation.class
uninstall_Sun_Hardware_AnswerBook.class
uninstall_SunATM_5_0.class
uninstall_SunATM_5_1.class
uninstall_SunFDDI_PCI_3_0.class
uninstall_SunFDDI_SBus_7_0.class
uninstall_Sun_Fire_880_FC-AL_Backplane_Firmware_1_0.class
uninstall_Sun_Fire_B10n_Load_Balancing_Blade_1_1.class
uninstall_SunForum_3_1.class
uninstall_SunForum_3_2.class
uninstall_SunHSI_PCI_3_0.class
uninstall_SunHSI_SBus_3_0.class
uninstall_SunScreen_3_2.class
uninstall_SunVTS_5_1_PS6.class
uninstall_SunVTS_5_1_PS5.class
uninstall_SunVTS_5_1_PS4.class
uninstall_SunVTS_5_1_PS3.class
uninstall_SunVTS_5_1_PS2.class
uninstall_SunVTS_5_1_PS1.class
uninstall_SunVTS_5_0.class
uninstall_System_Management_Services_1_4.class
uninstall_System_Management_Services_1_3.class
uninstall_System_Management_Services_1_2.class
uninstall_System_Service_Processor_3_5.class
uninstall_WBEM_DR_1_0.class
uninstall_Web_Start_Wizards_SDK_3_0_2.class
uninstall_Web_Start_Wizards_SDK_3_0_1.class
uninstall_Web_Start_Wizards_SDK.class
uninstall_XML_Libraries_2_4_12.class

Workaround: After you upgrade the system, manually remove the obsolete uninstallers in the /var/sadm/prod directory.

Configuration File pam.conf Not Automatically Updated After an Upgrade (5060721)

This Solaris 10 release introduces changes in pam_ldap functionality. When you upgrade to the current release, pam_ldap configurations in your existing pam.conf configuration file are not updated to reflect these changes. If pam_ldap configuration is detected, the CLEANUP file that is generated at the end of the upgrade contains the following notification:

/etc/pam.conf please examine/update the pam_ldap configuration 
because its functionality has changed, 
refer to pam_ldap(5) documentation for more information

Workaround: After the upgrade, examine /etc/pam.conf. If necessary, modify this file manually to be compatible with the new functionalities of pam_ldap. The modifications involve password prompting such as the use_first_pass and try_first_pass options as well as password updates. For more information about updating pam.conf, refer to the pam_ldap(5) man page and documentation.

Solstice DiskSuite Configurations Not Converted to Solaris Volume Manager Format When You Upgrade With Solaris Live Upgrade (4915974)

If you upgrade from the Solaris 8 release to the Solaris 10 release with Solaris Live Upgrade, an error might occur. Your Solstice DiskSuite 4.2.1 configurations might not be converted to Solaris Volume Manager configurations. All RAID-0, RAID-1, and other volumes such as mirrors, stripes, and submirrors might be lost.

The problem occurs if you have applied patches in a particular order to the Solaris 8 system before you upgrade. To determine if your system might experience the problem, check the version information of the SUNWmdr package on the Solaris 8 system. Type the following command:

# grep VERSION /var/sadm/pkg/SUNWmdr/pkginfo

Your system might be affected by the problem if the command generates the following output:

PKG_CLIENT_VERSION=8
VERSION=4.2.1,REV=1999.12.03.10.00

Workaround: Follow these steps.

1. Upgrade the alternate boot environment by using Solaris Live Upgrade.

   See Solaris 10 Installation Guide: Solaris Live Upgrade and Upgrade Planning for more information.

2. Mount the upgraded boot environment disk, but do not activate the upgraded boot environment.

   # mnt -F ufs /mnt/c0t0d0slice_number /mnt

   In the previous example, slice_number refers to the slice that contains the upgraded boot environment.

3. Check the /etc/system file for MDD Database information entries, such as the following text:

   * Begin MDD database info (do not edit)
   set md:mddb_bootlist1="sd:7:16 sd:7:1050 sd:7:2084"
   * End MDD database info (do not edit)

4. In a text editor, open the /kernel/drv/md.conf file for the upgraded boot environment.

   # cd /kernel/drv
   # vi md.conf

5. Modify md.conf as follows:

   1. Add the mddb_bootlist information from the /etc/system file that you checked in Step 3. Make sure that you also include the commented “Begin” and “End” lines that precede and follow the information.

   2. For each sd disk entry on the mddb_bootlist line, add the text string :id0 at the end of the disk entry.

   3. Below the mddb_bootlist entry, insert the following new line:

      md_devid_destroy=1;

   The following example shows how the md.conf file might be modified:

   # Begin MDD database info (do not edit) mddb_bootlist1="sd:7:16:id0 sd:7:1050:id0 sd:7:2084:id0"; md_devid_destroy=1; # End MDD database info (do not edit)

6. Save the md.conf file.

7. Delete the mddb_bootlist entry from the /etc/system file.

8. Unmount the upgraded boot environment disk.

9. Activate the upgraded boot environment.

Invalid Error Messages Are Displayed When You Use Solaris Live Upgrade to Upgrade From the Solaris 7 Release (4872151)

If you use Solaris Live Upgrade to upgrade from the Solaris 7 release to the Solaris 10 OS, error messages similar to the following are displayed.

Removal of package was successful.
/a//var/sadm/system/admin/upgrade_script: /bin/prodreg: not found
/a//var/sadm/system/admin/upgrade_script: /bin/prodreg: not found
/a//var/sadm/system/admin/upgrade_script: /bin/prodreg: not found

This error occurs because the Solaris Product Registry (prodreg) software is not included in the Solaris 7 release.

Workaround: Ignore the error message. These errors do not affect the installation.

Installer Text Display Problem When Using Solaris Live Upgrade (4736488)

When using the Solaris Live Upgrade luupgrade(1M) command with the -i option to complete an upgrade of an inactive boot environment, the text that the installers display might be unreadable in some languages. The text is corrupted when the installers request fonts that do not exist on the older release that is on the current boot environment.

Workaround: Choose one of the following workarounds:

• Use a combined network installation image to do the installation.

• Enable the C locale by setting the environment variable on your system.

  • If you are using the Bourne shell or Korn shell, follow these steps:

    1. Set the C locale.

       # LANG=C; export LANG

    2. Begin the installation.

  • If you are using the C shell, follow these steps:

    1. Type the following:

       # csh

    2. Set the C locale.

       # setenv LANG C

    3. Begin the installation.

SPARC: Removal of SUNWjxcft Package Records Error During Upgrade (4525236)

When you upgrade from the Solaris 8 software to the Solaris 10 release, a problem is encountered when the SUNWjxcft package is removed. The following error message is recorded in the upgrade_log file:

Removing package SUNWjxcft: 
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.upr 
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.scale 
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.alias 
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.upr 
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.scale 
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.alias 
Removal of <SUNWjxcft> was successful

Workaround: Ignore the error message.

Upgrading to Solaris 10 Release Might Disable Existing Secure Shell Daemon (sshd) (4626093)

If you upgrade to the Solaris 10 release on a system that is running a third-party Secure Shell, such as OpenSSH from the /etc/init.d/sshd daemon, the upgrade disables the existing Secure Shell daemon. During an upgrade, Solaris 10 software overwrites the contents of /etc/init.d/sshd.

Workaround: Choose one of the following workarounds:

• If you do not want the Secure Shell protocol server program on your system, do not install the SUNWsshdr and SUNWsshdu packages during the upgrade.

• If you do not want the Secure Shell protocol server or client programs on your system, do not install the Secure Shell Cluster (SUNWCssh) during the upgrade.

Upgrade Fails if /export Directory Is Near Capacity (4409601)

If the /export directory is near full capacity when you upgrade to the Solaris 10 release, space requirements for /export are miscalculated. The upgrade then fails. This problem commonly occurs if a diskless client is installed. Another instance of when the problem occurs is when third-party software is installed in the /export directory. The following message is displayed:

WARNING: Insufficient space for the upgrade.

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

• Rename the /export directory temporarily, until the upgrade is completed.

• Temporarily comment out the /export line in the /etc/vfstab file until the upgrade is completed.

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

Upgrading Diskless Client Servers and Clients (4363078)

If your system currently supports diskless clients that were installed with the Solstice AdminSuite 2.3 Diskless Client tool, you must perform the following two steps:

1. Delete all existing diskless clients that are the same Solaris version and architecture as the server.

2. Install or upgrade to the Solaris 10 release.

For specific instructions, see the System Administration Guide: Basic Administration.

If you attempt to install the Solaris 10 software over existing diskless clients, the following error message might be displayed:

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

In this error message, version-number refers to the Solaris version that is currently running on your system. <xxxxxxxx> refers to the slice that is running this version of the Solaris software.