Chapter 1 Installation Issues

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

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

This section contains installation issues that you need to be aware of before installing the Solaris 9 9/05 software.

Sun StorEdge SAN Foundation Software and Documentation

The Sun StorEdge(TM) SAN Foundation software (SFS) incorporates kernel drivers and utilities that enable a host to connect, monitor, and transfer data on a storage area network (SAN). The Sun StorEdge SAN 4.4 release, firmware upgrades, and documentation are available on the Sun Download Center. Access the Download Center from the SAN product page at http://www.sun.com/storage/san/.

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.

Manifestation of the problem depends upon the BIOS and the type of ATA hard drive in the system. The problem might be manifested in one of the following ways:

• If the Ultra DMA mode is enabled in BIOS, and ATA hard disk drives can operate in the Ultra DMA mode, a soft reboot of the system after installation might cause the system to hang in BIOS. No error messages are displayed.

• If the Ultra DMA mode is disabled in BIOS, and ATA hard disk drives can operate in Ultra DMA mode, a soft reboot of the system after installation might cause the system to hang. Messages that are similar to the following warnings are displayed:

  WARNING: /pci@0,0/pci-ide@1f,1/ide@0 (ata0): timeout: abort request, target=0 lun=0 WARNING: /pci@0,0/pci-ide@1f,1/ide@0 (ata0): timeout: abort device, target=0 lun=0 WARNING: /pci@0,0/pci-ide@1f,1/ide@0 (ata0): timeout: reset target, target=0 lun=0 WARNING: /pci@0,0/pci-ide@1f,1/ide@0 (ata0): timeout: reset bus, target=0 lun=0

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 9/05 Installation CD Partition Issue

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

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.

• Solaris fdisk partition

  This partition is the typical Solaris fdisk partition.

• x86 boot fdisk partition

  This partition is a 10–Mbyte fdisk partition that enables x86-based systems to boot the miniroot that is placed on the newly created swap slice. The swap slice is located on the Solaris fdisk partition.

The installation program on the Solaris 9 9/05 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.

Consequently, you cannot use the Solaris 9 9/05 Installation CD to upgrade from the Solaris 2.6 or Solaris 7 releases to the current release. For more information, refer to Upgrade Issues.

x86: Change in Default Boot-Disk Partition Layout

In the Solaris 9 9/05 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:

• First partition – Service partition (the existing size on the system).

• Second partition – x86 boot partition (approximately 11 Mbytes).

• Third partition – Solaris partition (the remaining space on the boot disk).

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.

If you install the Solaris 9 9/05 (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:

• You want to preserve an existing Sun Linux partition on the system.

• You need to create a Solaris partition, but want to preserve other existing partitions on the disk.

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 9/05 release, use the suninstall installation program on the Solaris 9 9/05 Software 1 of 2 CD.

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

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

• You use the Solaris JumpStart profile that is the default to install any locale other than the C locale on a system with a 2.1-Gbyte disk.

• You use the Solaris JumpStart profile that is the default to install two or more locales on a system with a 4-Gbyte disk.

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

If you install the Solaris 9 9/05 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.

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 9/05 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:

• To use the Solaris Web Start installation program to install from the Solaris 9 9/05 Installation CD, follow these steps:

  1. Delete the contents of the disk.

  2. Before you install, create the Service partition by using the Sun LX50 Diagnostics CD.

     For information on how to create the Service partition, see the Sun LX50 Server User's Manual and the Sun LX50 Knowledge Base at http://cobalt-knowledge.sun.com.

  3. Insert the Solaris 9 9/05 Installation CD in the CD-ROM drive.

  4. Begin the installation.

     When the installation program detects the Service partition, the following message is displayed:

     The default layout for the bootdisk is one x86 Boot partition and a Solaris partition on the remaining space. The Service fdisk partition, if one exists, is also preserved by default. Select one of the following to continue: 1) Use the default layout 2) Run fdisk to manually edit the disk 3) Exit Please make a selection: [?]

  5. Type 1 to use the default layout.

     The installation program preserves the Service partition and creates the x86 boot partition and the Solaris partition.

     ---

     Note –

     The Solaris Web Start installation program creates the x86 boot partition by removing 10 Mbytes from the Solaris fdisk partition. This utility prevents any existing fdisk partitions from being altered. Do not create this partition manually.

     ---

  6. Complete the installation.

• To install from a network installation image or from the Solaris 9 9/05 DVD over the network, follow these steps:

  1. Delete the contents of the disk.

  2. Before you install, create the Service partition by using the Sun LX50 Diagnostics CD.

     For information on how to create the Service partition, see the Sun LX50 Server User's Manual and the Sun LX50 Knowledge Base at http://cobalt-knowledge.sun.com.

  3. Boot the system from the network.

     The Customize fdisk Partitions screen is displayed.

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

     The installation program preserves the Service partition and creates the x86 boot partition and the Solaris partition.

     For more information on booting from the network, see the Solaris 9 9/04 Installation Guide.

• To use the suninstall program to install from the Solaris 9 9/05 Software 1 of 2 CD or from a network installation image on a boot server, follow these steps:

  1. Delete the contents of the disk.

  2. Before you install, create the Service partition by using the Sun LX50 Diagnostics CD.

     For information on how to create the Service partition, see the Sun LX50 Server User's Manual and the Sun LX50 Knowledge Base at http://cobalt-knowledge.sun.com.

  3. Boot the system.

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

  4. Select the Use rest of disk for Solaris partition option.

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

  5. Complete the installation.

     For more information on booting from the network, see the Solaris 9 9/04 Installation Guide.

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 9/05 release. To boot the Device Configuration Assistant, choose one of the following options:

• If your system's BIOS supports CD booting from a CD, boot from the Solaris 9 9/05 (x86 Platform Edition) Installation CD, the Solaris 9 9/05 Software (x86 Platform Edition) 1 of 2 CD, or the Solaris 9 9/05 Software (x86 Platform Edition) DVD.

• If your system does not support booting from a CD, you can copy the boot-diskette image to a diskette. The boot-diskette image is available on the Solaris 9 9/05 Software (x86 Platform Edition) 2 of 2 CD.

• If your system supports Preboot Execution Environment (PXE) booting and an install image is available on the network, boot from the network.

  Enable the system to use PXE by using the system's BIOS setup tool or the network adapter's configuration setup tool.

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

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

The Solaris 9 9/05 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 9/05 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 9/05 Software

This section contains installation bugs that you should be aware of before installing the Solaris 9 9/05 software.

SPARC: Installing Sun Net Connect 3.1 Service Fails on Sun Fire V1280 Servers (6284815)

The installation of Sun^SM Net Connect 3.1 from the Extra Value directory fails on Sun Fire^TM V1280 servers. The Sun Net Connect installation program incorrectly evaluates the capabilities of the Sun Fire V1280 server as a field-replaceable unit (FRU). Consequently, the installation fails and all installed Sun Net Connect packages are removed. The following error message is recorded in the installation logs:

Error: pkgadd failed for SUNWfrunc

Workaround: Download the most recent version of the SRS Net Connect service from http://https://srsnetconnect3.sun.com.

x86: PXE Network Installation Hangs on Systems With Adaptec Ultra-160 SCSI Interface (5039573)

If you use the Intel Preboot Execution Environment (PXE) to perform a network installation on a system with an Adaptec Ultra-160 SCSI interface, the installation hangs. An error similar to the following message might be displayed:

Error: Unable to Find Device Driver
The device driver, cadp160.bef, is missing.

In the previous example, the cadp160.bef driver is not found on the system. The name of the affected driver might differ on your system.

This error occurs if the system BIOS sets the Adaptec Ultra-160 interface to use the same interrupt request (IRQ) as the system network interface card (NIC).

Workaround: Choose one of the following workarounds.

• To install over the network, remove the Adaptec Ultra-160 SCSI interface, and perform an installation over the network with PXE.

• Install from the Solaris 9 9/04 DVD or CDs .

x86: X Server Unable to Open Mouse Device in Sun LX50 Servers (5027771)

On a Sun LX50 system, the X server might be unable to open a PS/2 mouse device. The error might occur either during installation or when the system reboots. When the problem occurs, the following error message is displayed:

ddxSUNWmouse: Error opening mouse device '/dev/kdmouse;
     /dev/kdmouse: No such device or address

Consequently, the Solaris installation program can proceed only in command-line interface mode. After installation, the problem might persist during Solaris runtime.

Workaround: On the Y-cable that connects to the server's PS/2 connector, switch the connections between the PS/2 keyboard and mouse.

If the PS/2 mouse remains unrecognized after a system reboot, press the LX50 server's Reset button. Alternatively, use the reconfigure option (b -r) when the following boot prompt appears:

Select (b)oot or (i)nterpreter:

SPARC: Installing Custom JumpStart Software With the re-preinstall Command Fails (5017239)

The re-preinstall command fails to install custom JumpStart software. The failure occurs because the fsck command cannot update the UFS log for file systems that have read-only permissions.

For example, you type the following command:

# /usr/sbin/install.d/re-preinstall cXt XdXsX

After the system is rebooted, the following error message is displayed:

fsck of device failed, re-preinstall needs to be re-run.
syncing file systems... done
Program terminated

Workaround: Choose one of the following options. You must be superuser to perform either workaround.

• Option 1: If you are using a writable network installation image, proceed with the following steps:

  1. On the server that contains the installation image, edit the /usr/sbin/install.d/rcS.stub file to remove or comment out the following lines:

     # # Make sure the root FS is clean # # /etc/fsck -F ufs -o p ${RootfsRaw} >/dev/null # if [ $? -ne 0 ]; then # echo "fsck of ${RootfsRaw} failed, re-preinstall needs to be re-run." # /usr/sbin/halt # if

  2. On the system where you are installing the JumpStart software, boot the network installation image in single-user mode:

     ok boot net -s

  3. Run the re-preinstall command as usual.

     # /usr/sbin/install.d/re-preinstall cXt XdXsX

• Option 2: If you are booting directly from the CD-ROM or DVD-ROM, proceed with the following steps:

  1. Boot the CD or DVD.

  2. Exit the installer.

  3. Run the re-preinstall command.

  4. Mount the device that you created in step 3.

     For example, if in step 3 you typed re-preinstall c0t0d0s0, mount this file system as follows:

     # mount /dev/dsk/c0t0d0s0 /mnt

  5. On the mounted file system, edit the sbin/rcS script to remove or comment out the same lines as in the first workaround.

  6. Unmount the file system.

     # umount /mnt

  7. Reboot the system to continue installing the JumpStart software.

Cannot Access Data on Solaris 9 9/05 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 9/05 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:

• Apply the patches that are appropriate for your system.

  Release	Patch ID
  Solaris 2.6	107618-03
  Solaris 7	107259-03
  Solaris 2.6	107619-03
  Solaris 7	107260-03

• Mount the Solaris 9 9/05 DVD manually. Do not use Volume Management to mount the DVD. Follow these steps:

  1. Become superuser.

  2. Stop Volume Management.

     # /etc/init.d/volmgt stop

  3. Mount the DVD manually.

     # mkdir /mnt1 # mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /mnt1

  4. Verify that the DVD is mounted. Then verify that the data is accessible.

     # cd /mnt1 # ls

     The system returns the following information if the DVD is correctly mounted.

     Copyright Solaris_9

Installation Bugs

The following installation bugs apply to the Solaris 9 9/05 release.

SPARC: Solaris 9 9/05 Web Start Installation Program Might Not Display Special Case Panels Properly (5002175)

If you install the Solaris 9 9/05 software by using the Solaris Web Start installation program, some of the information and exit panels for the Sun ^SM Remote Services (SRS) Net Connect software might not display properly.

The installation panel frame and Cancel button are displayed, but the installation panel content is missing.

This problem might also occur during a Solaris Web Start installation of other software products that are included in this Solaris OS release.

Workaround: Follow these steps:

1. Bypass the SRS Net Connect installation by clicking the Cancel button when the empty installation panel is displayed.

2. After the installation of the Solaris 9 9/05 software has completed, manually install the SRS Net Connect software from the Solaris DVD or Software 2 of 2 CD.

Installing the SRS Net Connect software after the initial Solaris 9 9/05 software installation has completed ensures that all panels are displayed properly.

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

If you install or upgrade to the Solaris 9 9/05 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:

• To plumb only the configured interface, reboot the system after the initial boot.

• To assign a different IP address to each network interface, set the local-mac-address PROM variable to true in one of the following ways:

  • At the ok prompt, type the following command:

    ok setenv local-mac-address? true

  • In a terminal window, type the following command as superuser:

    # eeprom local-mac-address?=true

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

The following bug occurs during installation of the Solaris 9 9/05 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

This section contains installation issues that occur during an upgrade to the Solaris 9 9/05 release.

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 Java 2 runtime environment.

The typical failure that results is a Java exception error. The following messages 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:

• Install the Solaris Live Upgrade packages by using the pkgadd command.

  For step-by-step instructions, refer to Chapter 35, Using Solaris Live Upgrade to Create a Boot Environment (Tasks), in Solaris 9 9/04 Installation Guide.

• Install the Java 2 runtime environment recommended patch cluster. The patch cluster is available on http://sunsolve.sun.com. Then, you can use the Solaris Live Upgrade installer to install the packages.

Cannot Access Storage Area Networks Through SUNWsan With Solaris 9 9/05 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 9/05 release. Solaris 8 systems that have the SUNWsan package installed might require special procedures to upgrade to the Solaris 9 9/05 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 9/05 (x86 Platform Edition) Installation CD to Upgrade x86 Systems From Solaris 2.6 or Solaris 7 Software

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

Workaround: On x86-based systems, use the Solaris 9 9/05 Software (x86 Platform Edition) 1 of 2 CD to upgrade from the Solaris 2.6 or the Solaris 7 software to the Solaris 9 9/05 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 9/05 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:

• Before you upgrade, use the /usr/bin/prodreg command to perform a full uninstall of Solaris Management Console software.

• If you did not uninstall Solaris Management Console 1.0, 1.0.1, or 1.0.2 software before you upgraded to the Solaris 9 9/05 release, you must first remove all Solaris Management Console 1.0, 1.0.1, or 1.0.2 packages. Use the pkgrm command for package removal instead of the prodreg command. Carefully follow the order of package removal. Complete the following steps:

  1. Become superuser.

  2. Type the following command:

     # pkginfo | grep “Solaris Management Console“

     If the description does not start with “Solaris Management Console 2.1,” the package names in the output identify a Solaris Management Console 1.0 package.

  3. Use the pkgrm command to remove all instances of Solaris Management Console 1.0 packages in the following order:

     ---

     Note –

     Do not remove any package that has “Solaris Management Console 2.1” in its description. For example, SUNWmc.2 might indicate Solaris Management Console 2.1 software.

     If the pkginfo output displays multiple versions of Solaris Management Console 1.0 packages, use the pkgrm command to remove both packages. Remove the original package. Then, remove the package that has been appended with a number. For example, if the SUNWmcman and SUNWmcman.2 packages appear in the pkginfo output, first remove the SUNWmcman package and then remove the SUNWmcman.2 package. Do not use the prodreg command.

     ---

     # pkgrm SUNWmcman # pkgrm SUNWmcapp # pkgrm SUNWmcsvr # pkgrm SUNWmcsvu # pkgrm SUNWmc # pkgrm SUNWmcc # pkgrm SUNWmcsws

  4. In a terminal window, type the following command:

     # rm -rf /var/sadm/pkg/SUNWmcapp

  The Solaris Management Console 2.1 software should now function properly. For future maintenance, or if the Solaris Management Console 2.1 software does not function properly, remove the Solaris Management Console 2.1 software. Reinstall the software by completing the following steps:

  1. Use the pkgrm command to remove all Solaris Management Console 2.1 packages and dependent packages in the following order:

     ---

     Note –

     If your installation has multiple instances of Solaris Management Console 2.1 packages, such as SUNWmc and SUNWmc.2, first remove SUNWmc, and then SUNWmc.2 . Do not use the prodreg command.

     ---

     # pkgrm SUNWpmgr # pkgrm SUNWrmui # pkgrm SUNWlvmg # pkgrm SUNWlvma # pkgrm SUNWlvmr # pkgrm SUNWdclnt # pkgrm SUNWmga # pkgrm SUNWmgapp # pkgrm SUNWmcdev # pkgrm SUNWmcex # pkgrm SUNWwbmc # pkgrm SUNWmc # pkgrm SUNWmcc # pkgrm SUNWmccom

  2. Insert the Solaris 9 9/05 Software 1 of 2 CD into your CD-ROM drive. Type the following in a terminal window:

     # cd /cdrom/sol_9_904_sparcia/s0/Solaris_9/Product # pkgadd -d . SUNWmccom SUNWmcc SUNWmc SUNWwbmc SUNWmcex SUNWmcdev \ SUNWmgapp SUNWmga SUNWdclnt SUNWlvmr SUNWlvma SUNWlvmg SUNWpmgr \ SUNWrmui

  All previous Solaris Management Console versions are removed. The Solaris Management Console 2.1 software is now functional.

Installation Bugs That Occur During an Upgrade

The following installation bugs occur during an upgrade to the Solaris 9 9/05 release.

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 9 or the Solaris 9 9/05 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 9/05 Release Might Disable Existing Secure Shell Daemon (sshd) (4626093)

If you upgrade to the Solaris 9 9/05 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 9/05 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 9 9/05 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^TM 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 9/05 release.

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

If you attempt to install the Solaris 9 9/05 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 Bugs That Occur After an Upgrade

The following installation bugs occur after you upgrade to the Solaris 9 9/05 release.

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

Obsolete uninstaller programs are not removed if you use Solaris Live Upgrade to upgrade to Solaris 9 9/05 OS from the following releases:

• Solaris 8 OS

• Solaris 9 releases previous to Solaris 9 9/05 OS

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

• uninstall_CDRW_1_0.class

• uninstall_Java3D_1_3.class

• uninstall_Java3D_1_2_1_04.class

• uninstall_Java3D_1_2_1_03.class

• uninstall_Man_Page_Supplement.class

• uninstall_OpenGL_1_2_3.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_Sun_Hardware_AnswerBook.class

• uninstall_SunATM_5_0.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_SunForum_3_1.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_WBEM_DR_1_0.class

• uninstall_Web_Start_Wizards_SDK_3_0_1.class

• uninstall_Web_Start_Wizards_SDK.class

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

SPARC: After Upgrading or Applying Recommended Patches, Problems With SAM-FS/QFS Occur (5003346)

The SAM-FS/QFS daemons do not start and the file systems are unmountable if you performed either of the following operations:

• You upgraded to Solaris 9 4/04 Release.

• You applied the Solaris 9 Recommended Patch Cluster (Solaris 9 patch ID 112233-11).

The error occurs because system call 181 that the daemons normally use is being used by a different module. The module was introduced by the patch that you had just applied. The following error messages are recorded in /var/adm/messages :

/var/adm/messages
 Jan  5 13:28:46 host genunix: [ID 147998 kern.warning] WARNING: system 
 call entry 181 is already in use
 Jan  5 13:28:46 host samfs: [ID 798779 kern.warning] WARNING: SAM-FS: 
 modload(samsys) failed.

In addition, the following error messages are also recorded in /var/adm/sam-log :

/var/adm/sam-log
 Jan  5 13:30:08 host sam-fsd[355]: [ID 617651 local4.alert] Fatal error -
 samsys module not loaded
 Jan  5 13:30:08 host sam-fsd[355]: [ID 765074 local4.alert]   Correct 
 problem and 'kill -HUP 355'

Perform the following steps:

1. Become superuser.

2. Issue a grep of 181 from the modinfo output to determine if 181 is in use by another module:

   # modinfo | grep 181 8 1181aa0 38c4 1 1 TS (time sharing sched class) 15 11b1092 181a 12 1 sad (STREAMS Administrative Driver ') 43 1295cd8 ce9 181 1 ssc050 (SSC050 i2c device driver: v1.4) 158 7813a87f 181c 95 1 cpc (cpc sampling driver v1.10) 158 7813a87f 181c 179 1 cpc (cpc sampling system call) 158 7813a87f 181c 179 1 cpc (32-bit cpc sampling system call)

   Because system call 181 is used by another module, configure samsys to use another unused system call value.

3. Edit /etc/name_to_sysnum by changing samsys to use 182 or some other unused value from 0-255.

   samsys 182

4. Boot the system to reconfigure samsys.

   # shutdown -y -g0 -i0

   OK> boot -r

5. Verify that the error messages no longer appear in /var/adm/messages and that all SAM-FS file systems can mount.

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:

• You apply a revision of patch 112945 for a Solaris 9 release to a system that is running the Solaris 9 software.

• You then remove the patch that was applied to the system.

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:

• Follow these steps to prevent the WBEM Repository from being corrupted:

  1. Become superuser.

  2. Before you apply the patch, back up the WBEM Repository.

     # cp —r /var/sadm/wbem/logr path/logr

     where path is the path to the backup WBEM Repository.

  3. If the WBEM Repository is corrupted after you back out the patch, stop the WBEM server.

     # /etc/init.d/init.wbem stop

  4. Restore the backup WBEM Repository.

     # cp -rf path/logr /var/sadm/wbem/logr

     # cp -rf path/logr /var/sadm/wbem/logr

  5. Restart the WBEM server.

     # /etc/init.d/init.wbem start

• Follow these steps to create a new WBEM Repository:

  ---

  Note –

  This workaround does not restore the WBEM data if the WBEM Repository is corrupted. Any data that was added to the repository during the installation is lost.

  ---

  1. Become superuser.

  2. Stop the WBEM server.

     # /etc/init.d/init.wbem stop

  3. Remove the files from the /logr directory.

     # rm /var/sadm/wbem/logr/*

  4. Remove the /notFirstTime directory.

     # rmdir notFirstTime

  5. Start the WBEM server.

     # /etc/init.d/init.wbem start

  6. Compile any proprietary Managed Object Format (MOF) files manually.

     # /usr/sadm/bin/mofcomp MOF-filename

64–Bit Solaris Issue

The following 64–bit issue applies to the Solaris 9 9/05 release.

SPARC: Sun UltraSPARC System (Sun4U) Might Need Boot Flash PROM Update

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 UltraSPARC^TM system, you might need to update the system's flash PROM firmware. The Solaris 9 9/05 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 the CPU speed is 200 MHz or greater.

If you choose to run the 32-bit Solaris software on any Sun^TM or UltraSPARC system, the flash PROM update is not needed.

The following table lists the UltraSPARC (Sun4U^TM) 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.

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

The following Documentation CD issue applies to the Solaris 9 9/05 release.

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.

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 9/05 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 9/05 Documentation CD 1 of 2 is located in the following directory:

sol_9_doc_1of2/README/C/install_C.html

Documentation CD Installation Bugs

The following Documentation CD installation bugs apply to the Solaris 9 9/05 release.

Uninstall Mode of Solaris 9 9/05 Documentation CD uninstaller Utility Does Not Work Properly (4675797, 4627776)

If you run the Solaris 9 9/05 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 9/05 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 9/05 Documentation CD installer program. Use the graphical user interface (GUI) mode to install the Solaris 9 9/05 Documentation CD.

Localization Issue That Occurs During Installation

The following is a Localization issue that occurs during installation of the Solaris 9 9/05 software.

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 9/05 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

The following Localization bugs occur during installation of the Solaris 9 9/05 software.

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 9/05 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 9/05 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 9/05 release.

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