test

Solaris 9 12/03 Release Notes

Chapter 1 Installation Issues

This chapter describes problems that relate to the installation of the Solaris 9 12/03 Operating System.

For late-breaking Solaris installation issues that were not identified in time to be included in these release notes, refer to the Solaris 9 12/03 Release Notes at http://docs.sun.com/db/doc/817-2706.

The following installation bug descriptions have been added to this chapter since this document was published on the Solaris 9 12/03 Documentation CD and in the Installation Kiosk on the Solaris 9 12/03 Installation CD:

Issues You Need to Know About Before Installing Solaris 9 12/03 Software

SPARC: Installation of Solaris 9 12/03 Software on Sun Fire V880 Results in Warnings After Reboot

The Sun FireTM V880 software is included in the Solaris 9 12/03 release. When you install the Solaris 9 12/03 release on a Sun Fire V880 server, the V880 software attempts to load the bbc and gptwo drivers.

The fix for Bug 4717004 removed the bbc and gptwo drivers. Since these drivers have been deleted and are no longer available, the following error messages are displayed when you reboot the system:


WARNING: Failed to install "bbc" driver.
WARNING: Failed to install "gptwo" driver.

Workaround: These messages are benign and can safely be ignored.

x86: Systems With Certain ATA Hard Disk Drives Hang When Rebooted After Solaris 9 Software Installation

Installing the Solaris 9 software on systems with certain types of ATA hard disk drives results in a system hang. The system hangs when you attempt a soft reboot after the installation has completed.

This problem occurs in systems with ATA hard disk drives that implement the revert to default conditions feature of ATA/ATAPI-6 T13 specification, with respect to the Ultra DMA mode.

Such disk drives revert from Ultra DMA mode to Multiword DMA mode after the software reset, unless the behavior is disabled. The behavior is disabled by using the SET FEATURES / Disable reverting to power-on to defaults command.

The way the problem manifests itself depends upon the BIOS and the type of ATA hard drive that is in the system. This problem might manifest itself in one of the following ways:

Workaround: To correct the problem, complete the following steps:

  1. If the system hangs when booted, power cycle the system by turning the power off and then on again. The system should then boot normally.

  2. After the system is booted, log in to the system and become superuser.

  3. Use a text editor to edit the /platform/i86pc/kernel/drv/ata.conf file.

    Add the following line:


    ata-revert-to-defaults=0;

The next system reboot should proceed without a hang.

x86: Solaris 9 12/03 Installation CD Partition Issue

If the Solaris Web Start 3.0 program on the Solaris 9 12/03 Installation CD is unable to locate a Solaris fdisk partition on a system, you must create a Solaris fdisk partition on your root disk.

Caution – Caution –

If you change the size of an existing fdisk partition, all data on that partition is automatically deleted. Back up your data before you create a Solaris fdisk partition.

The Solaris Web Start 3.0 program requires two fdisk partitions to perform an installation.

Note –

The installation program on the Solaris 9 12/03 Installation CD creates the x86 boot partition, removing 10 Mbytes from the Solaris fdisk partition. This removal prevents any existing fdisk partitions from being altered.

This partition should not be created manually.

This requirement also prevents you from using the Solaris 9 12/03 Installation CD to upgrade from the Solaris 2.6 or Solaris 7 releases to the Solaris 9 12/03 software. For more information, refer to Upgrade Issues.

x86: Change in Default Boot-Disk Partition Layout

In the Solaris 9 12/03 release, the Solaris Web Start and suninstall installation programs use, by default, a new boot-disk partition layout to accommodate the Service partition on Sun LX50 systems. This installation program enables you to preserve an existing Service partition.

The new default includes the following partitions:

If you want to use this default layout, select Default when the Solaris Web Start or suninstall program asks you to choose a boot-disk layout.

Note –

If you install the Solaris 9 12/03 (x86 Platform Edition) software on a system that does not currently include a Service partition, the Solaris Web Start and suninstall programs do not create a new Service partition by default. If you want to create a Service partition on your system, see x86: Service Partition Not Created by Default on Systems With No Existing Service Partition.

You can also choose to manually edit the disk partition layout by using the fdisk utility. You might want to manually edit the boot-disk partitions under the following conditions:

Note –

If your system contains an upgradable version of the Solaris software, but does not contain an x86 boot partition, you might not be able to upgrade by using the Solaris Installation CD. To upgrade a system with no x86 boot partition to the Solaris 9 12/03 release, use the suninstall installation program on the Solaris 9 12/03 Software 1 of 2 CD.

SPARC: Default Solaris JumpStart Profile Might Not Install Multiple Locales on Small Disks

If you use the default Solaris JumpStartTM profile on the Solaris 9 12/03 media to install multiple locales on a system with a small disk, the installation might fail. This problem might occur under the following conditions:

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

If you install the Solaris 9 12/03 software on a system that does not currently include a Service partition, the installation program might not create a Service partition by default. If you are including a Service partition on the same disk as the Solaris partition, you must re-create the Service partition before you install the software.

If you installed the Solaris 8 2/02 software on a Sun LX50 system, 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 software, you cannot re-create the Service partition and upgrade to the Solaris 9 12/03 release. You must perform an initial installation of the software.

Workaround: If you are including a Service partition on the disk that contains the Solaris partition, choose one of the following:

x86: Solaris Device Configuration Assistant Boot Diskette Is Not Available

The Solaris 9 Device Configuration Assistant is not delivered as a boot diskette in the Solaris 9 12/03 release. To boot the Device Configuration Assistant, choose one of the following options:

For more information, see the Solaris 9 12/03 Installation Guide.

x86: Do Not Upgrade Hewlett-Packard (HP) Vectra XU Series Systems With BIOS Version GG.06.13

The Solaris 9 12/03 software includes a feature that enables you to install large partitions. The system BIOS must support logical block addressing (LBA). BIOS Version GG.06.13 does not support LBA access. The Solaris boot programs cannot manage this conflict. This issue can also affect other HP Vectra systems.

If you perform this upgrade, your HP system can no longer boot. Only a blank black screen with a flashing underscore cursor is displayed.

Workaround: Do not upgrade HP Vectra XU Series systems with the latest BIOS Version GG.06.13 to the Solaris 9 12/03 release. This version no longer supports these systems.

You can still boot your system by using the boot diskette or boot CD because the boot paths do not use the hard disk code. Then select the hard disk as your bootable device instead of the network or CD-ROM drive.

Bugs You Need to Know About Before Installing Solaris 9 12/03 Software

Solaris 9 12/03 Software 2 of 2 CD Does Not Mount Correctly on Systems With Multiple CD-ROM Drives (4751439)

If you use the suninstall program to install the Solaris 9 12/03 Software from CD onto a system that has multiple CD-ROM drives, the Solaris 9 12/03 2 of 2 CD might not install correctly.

After the installation of the Solaris Software 1 of 2 CD completes, the system reboots. The installation program then prompts you to insert the 2 of 2 CD. After you insert the CD, the installation program does not mount the CD.

For SPARC systems, the following message is displayed repeatedly:


Please insert the CD/DVD for Solaris 9 Software 2 of 2
	(12/03 SPARC Platform Edition)

For x86 systems, the following message is displayed repeatedly:


Please insert the CD/DVD for Solaris 9 Software 2 of 2
	(12/03 x86 Platform Edition)
Note –

If your installation does not require software on the Solaris Software 2 of 2 CD, you do not encounter this error.

Workaround: Choose from the following workarounds:

SPARC: Upgrade Firmware on Sun Fire and Netra Servers Before Installation (4747307, 4799331)

To install the Solaris 9 12/03 software on specific Sun Fire and NetraTM servers, you must first update the firmware on the server. If you do not update the firmware before you install the Solaris 9 12/03 software, the server panics. This problem affects the following servers:

If this problem occurs, the following error message is displayed:


panic[cpu0]/thread=140a000: BAD TRAP: type=34 rp=147e9e0
       addr=5586ee326973add3 mmu_fsr=0

The ok prompt is displayed.

Workaround: Update the firmware by applying the appropriate firmware patch.

Firmware update patches are available by going to the SunsolveSM Web site at http://sunsolve.sun.com. Be sure to download and apply the most current version of the patch.

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 9 12/03 DVD.

Workaround: Apply patch 111649–03, or a later version, to update the Toshiba SD-M1401 DVD-ROM drive's firmware. You can download patch 111649–03 or a later version by going to the SunSolve Web site at http://sunsolve.sun.com.

Cannot Access Data on Solaris 9 12/03 DVD When Running Solaris 2.6 and Solaris 7 Software (4511090)

If your system is running the Solaris 2.6 or the Solaris 7 software, Volume Management incorrectly mounts the Solaris 9 12/03 DVD. The DVD can be mounted, but the data is inaccessible. As a result, you cannot set up an install server, perform a Live Upgrade, or access any data on the media.

Workaround: Choose one of the following workarounds:

Installation Bugs

x86: PXE Boot Fails With the 3Com 3C905C Network Card (4847803)

If you use the Preboot Execution Environment (PXE) to install the Solaris software with a 3Com 3C905C network card, the system might hang and fail to boot.

Workaround: Use the 3Com Managed Boot Agent (MBA) version 4.11 with the 3Com 3C905C network card. Or, use a different type of network card.

SPARC: Systems With Multiple Interfaces Recognize All Interfaces as Usable After Installation or Upgrade (4640568)

If you install or upgrade to the Solaris 9 12/03 release on a system with multiple network interfaces, the system recognizes all system interfaces as usable. Interfaces that are not connected to the network, or that are not intended for use, appear in the output of the ifconfig -a command. Additionally, interfaces with identical Ethernet addresses might be assigned identical IP addresses. The following error message is displayed:


ifconfig: setifflags: SIOCSLIFFLAGS: qfe3: Cannot assign requested address

This problem also occurs on systems that have the local-mac-address PROM variable set to false. The problem occurs because all interfaces are configured with the same IP address.

Workaround: Choose one of the following workarounds:

Installation Bug That Occurs During an Installation From Solaris 9 12/03 Software 1 of 2 CD

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

When a file system is created during installation, one of the following warning messages might be displayed:


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 you created does not equal 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.

Upgrade Issues

Additional Patches Are Needed to Run Solaris Live Upgrade

Correct operation of Solaris Live Upgrade requires that a limited set of patch revisions be installed for a given OS version.

Before installing or running Live Upgrade, you are required to install a limited set of patch revisions. Make sure you have the most recently updated patch list by consulting http://sunsolve.sun.com. For additional information, search for the info Doc 72099 on the SunSolve Web site.

Limitation When Installing Solaris Live Upgrade Packages

If you are running the Solaris 2.6, Solaris 7, or Solaris 8 release, you might not be able to run the Solaris Live Upgrade installer. These releases do not contain the set of patches that is needed to run the JavaTM 2 runtime environment.

The typical failure that results is a Java exception error. The following are messages that might be displayed:


InvocationTargetException in ArchiveReader constructornull
          java.lang.reflect.InvocationTargetException
                 at install.instantiateArchiveReader(Compiled Code)
                 at install.<init>(Compiled Code)
                 at install.main(Compiled Code)

To run the Solaris Live Upgrade installer and install the packages, you must have the Java 2 runtime environment recommended patch cluster.

Workaround: Complete the following workaround:

Cannot Access Storage Area Networks Through SUNWsan With Solaris 9 12/03 Software

If your Solaris 8 system is connected to storage area networks (SANs), check with your support engineer before you upgrade to the Solaris 9 12/03 release. Solaris 8 systems that have the SUNWsan package installed might require special procedures to upgrade to the Solaris 9 12/03 release. To find out if the SUNWsan package is installed on the system, type the following command in a terminal window:


# pkginfo SUNWsan

If the SUNWsan package is installed, the following information is displayed:


	system      SUNWsan       SAN Foundation Kit

x86: Cannot Use Solaris 9 12/03 (x86 Platform Edition) Installation CD to Upgrade x86 Systems From Solaris 2.6 or Solaris 7 Software

You cannot use the Solaris 9 12/03 (x86 Platform Edition) Installation CD to upgrade x86-based systems from the Solaris 2.6 or the Solaris 7 software to the Solaris 9 12/03 release. The upgrade cannot be performed because of the x86 boot-partition requirement.

Workaround: On x86-based systems, use the Solaris 9 12/03 Software (x86 Platform Edition) 1 of 2 CD to upgrade from the Solaris 2.6 or the Solaris 7 software to the Solaris 9 12/03 release.

Solaris Management Console 2.1 Software Is Not Compatible With Solaris Management Console 1.0, 1.0.1, or 1.0.2 Software

Solaris Management Console 2.1 software is not compatible with Solaris Management Console 1.0, 1.0.1, or 1.0.2 software. If you are upgrading to the Solaris 9 12/03 release, and you have Solaris Management Console 1.0, 1.0.1, or 1.0.2 software installed, you must first uninstall the Solaris Management Console software before you upgrade. 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:

Installation Bugs That Occur During an Upgrade

Upgrade Fails to Install SUNWceudt Package (4826785)

If you are upgrading to the Solaris 9 12/03 OS from a previous Solaris 9 release, the following errors occur when you use the pkgchk command with the -n option:


ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/datatypes.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/develop.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/dtfile.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/dtmail.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/dtpad.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/print.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/uxstd.dt
pathname does not exist

Workaround: Use the Solaris 9 12/03 DVD or the Solaris 9 12/03 Software 1 of 2 CD to add back the SUNWceudt package. Follow these steps:

  1. Become superuser.

  2. Remove the SUNWceudt package.


    # pkgrm SUNWceudt

  3. Change directories to the product directory.


    # cd path-to-Solaris-9/Product

  4. Add the SUNWceudt package.


    # pkgadd -d `pwd` SUNWceudt

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:

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

When you upgrade from the Solaris 8 software to the Solaris 9 or the Solaris 9 12/03 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 9 12/03 Release Might Disable Existing Secure Shell Daemon (sshd) (4626093)

If you upgrade to the Solaris 9 12/03 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, the Solaris 9 12/03 software overwrites the contents of /etc/init.d/sshd.

Workaround: Choose one of the following workarounds:

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

If the /export directory is near capacity when you upgrade to the Solaris 9 12/03 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:

Upgrading Diskless Client Servers and Clients (4363078)

If your system currently supports diskless clients that were installed with the Solstice AdminSuiteTM 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 9 12/03 release.

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

If you attempt to install the Solaris 9 12/03 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.

Installation Bug That Occurs After an Upgrade

SPARC: Removing Patches After Upgrade Might Corrupt WBEM Repository (4820614)

The WBEM Repository Common Information Model (CIM) database can be corrupted under the following conditions:

If the WBEM Repository is corrupted, the following error message is displayed in the Solaris Management Console Log Viewer:


CIM_ERR_FAILED:
/usr/sadm/lib/wbem/../../../../var/sadm/wbem/logr/
preReg/PATCH113829install/Solaris_Application.mof,18,ERR_SEM,
ERR_EXC_SET_CLASS,CIM_ERR_FAILED:Other Exception:
java.io.StreamCorruptedException: invalid stream header

Workaround: Choose one of the following workarounds:

64–Bit Solaris Issue

SPARC: Sun UltraSPARC System (Sun4U) Might 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 software on an UltraSPARCTM system, you might need to update the system's flash PROM firmware. The Solaris 9 12/03 installation programs enable you to add 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 software on any SunTM or UltraSPARC system, the flash PROM update is not needed.

The following table lists the UltraSPARC (Sun4UTM) 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 determine which firmware version that you are running by using the prtconf -V command.

Table 1–2 Minimum Firmware Versions Required to Run 64–Bit Solaris Software 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, the system does not need a flash PROM update.

For instructions on how to perform the flash PROM update by using the Solaris CD, refer to the Solaris 9 on Sun Hardware Collection. You can obtain the manual at http://docs.sun.com.

Documentation CD Issue

Cannot Install Documentation Packages With Names Longer Than Nine Characters on Documentation Servers Running Solaris 2.6, 7, and 8 Software

Some localized documentation collections in PDF format have package names that are longer than nine characters. To install these PDF collections on servers that are running Solaris 7 or 8 software, you must first install two patches.

Note –

No patches exist at the time of this release for Solaris 2.6 servers.

Workaround: For instructions on how to install these patches, see the Solaris Documentation Important Information file on the documentation media, Solaris 9 12/03 Documentation CD 1 of 2, 2 of 2, or DVD. This file is located in the following directory:


mount-point/README/locale/install_locale.html

For example, the English file on the Solaris 9 12/03 Documentation CD 1 of 2 is located in the following directory:


sol_9_doc_1of2/README/C/install_C.html

Documentation CD Installation Bugs

Uninstall Mode of Solaris 9 12/03 Documentation CD uninstaller Utility Does Not Work Properly (4675797)

If you run the Solaris 9 12/03 Documentation CD uninstaller in Uninstall All mode, the uninstaller removes only those documentation packages that are installed by default.

Workaround: Run the uninstaller in Uninstall Partial mode. Select the specific packages that you want to uninstall.

Documentation CD Verify Panel Might Not Page in Command-Line Interface Mode (4520352)

If you use the Solaris 9 12/03 Documentation CD installer program with the nodisplay option, the verify panel might not page correctly.

Workaround: Do not specify the nodisplay option with the Solaris 9 12/03 Documentation CD installer program. Use the graphical user interface (GUI) mode to install the Solaris 9 12/03 Documentation CD.

Localization Issue That Occurs During Installation

Additional Related Locales Might Be Installed

When you select a locale for your installation, additional related locales might also be installed. This change in behavior occurs in the Solaris 9 12/03 release because all full locales, with message translations, and the Asian and Japanese partial locales, locale enabler, have been repackaged based on language support for locales. Other partial locales are still packaged and installed based on geographic region, such as Central Europe.

Localization Bugs That Occur During Installation

Languages CD Installs All Languages By Default With Solaris Live Upgrade (4898832)

If you use Solaris Live Upgrade with multiple CDs to install the Solaris 9 12/03 release, the Languages CD installs all languages by default.

After the installation, if you log in to the system in a locale that is different than the locale you selected during installation, garbled characters might be displayed. After you log in to any of these locales, the English locale is displayed.

Workaround: During installation, select the custom install option. Uncheck any languages that you do not want to install during the Languages CD installation.

Upgrading Systems Running Solaris 8 Software With Full Thai/Russian/Polish/Catalan Support Leaves Invalid Packages on System (4650059)

Upgrading to the Solaris 9 12/03 release, on a system running the Solaris 8 software with the Solaris 8 Language Supplement CD installed, results in several invalid packages. Thai, Russian, Polish, and Catalan locale packages remain on the system. These locale packages have an ARCH=sparcall value and are not removed during the upgrade to the Solaris 9 12/03 release.

Workaround: Before you upgrade to the Solaris 9 12/03 release, use the Solaris Product Registry application to remove the Solaris 8 Languages Supplement CD packages.