Chapter 1 Installation Issues

This chapter describes problems that relate to the installation of the Solaris 10 Operating System.

Some of the issues and bugs in this chapter have been fixed in subsequent Solaris 10 releases. If you have upgraded your Solaris software, certain issues and bugs in this chapter might no longer apply. To see which bugs and issues no longer apply to your specific Solaris 10 software, refer to Appendix A, Table of Integrated Bug Fixes in the Solaris 10 Operating System.

General Information

This section provides general information such as behavior changes in Solaris 10 OS.

New Minimum Memory Requirement

Beginning with the Solaris 10 1/06 release, all x86 based systems must now have at least 256 Mbytes of RAM to run the Solaris software.

Changes in Upgrade Support for Solaris Releases

Starting with the Solaris 10 1/06 release, you can upgrade the Solaris OS only from the following releases:

• Solaris 8 OS

• Solaris 9 OS

• Solaris 10 OS

To upgrade releases previous to the Solaris 8 software to the Solaris 10 1/06 software, upgrade to any of the releases in the preceding list first. Then upgrade to the Solaris 10 1/06 release.

Support for Products Not Part of the Solaris OS

Although the Solaris 10 software has been tested for compatibility with previous releases, some third-party applications might not be fully ABI compliant. Contact the supplier of these applications directly for information about compatibility.

Your system might run both a Solaris OS and other products that are not part of the Solaris software. These products might be supplied by either Sun or another company. If you upgrade this system to the Solaris 10 release, make sure that these other products are also supported on the Solaris 10 OS. Depending on the status of each of these products, you can perform one of the following options:

• Verify that the existing version of the product is supported on the Solaris 10 software.

• Install a new version of the product that is supported on the Solaris 10 release. You might need to remove the previous version of the product prior to upgrading to the Solaris software. See the product documentation for more details.

• Remove the product prior to upgrading to the Solaris 10 software.

Before You Begin

This section contains critical installation issues that you need to be aware of before installing or upgrading to Solaris 10 OS. These issues might have an impact that would prevent installation or upgrades from completing successfully. If bugs in this section apply to your system, you might need to perform the recommended workarounds before you install or upgrade.

Installation Change for the Solaris Companion DVD

When you are installing the Solaris OS, the Companion DVD is not available to be installed with the Solaris installation program. Use the pkgadd(1M) command to install the Solaris Companion DVD. For detailed installation instructions, see the README file on the Companion DVD.

Solaris Live Upgrade and Solaris Zones

Using Solaris Live Upgrade in conjunction with Solaris zones is not supported. If you have installed non-global zones on a Solaris 10 system, you cannot upgrade to the Solaris 10 1/06 release by using Solaris Live Upgrade.

If you use the luupgrade command, the following error message is displayed:

Unable to upgrade boot environment.

Workaround: To upgrade such a system, use either the Solaris interactive installation program or the custom JumpStart program. These programs apply to your Solaris 10 OS all the patches and new packages that represent the differences between your current OS and the Solaris 10 1/06 software. The programs also apply the packages and patches to all the non-global zones.

Both programs have limitations. For example, you cannot customize your upgrade by installing additional software products or additional locale packages, or by modifying the disk layout. For details about these limitations, see the Upgrading the Solaris OS When Non-Global Zones Are Installed in Solaris 10 6/06 Installation Guide: Custom JumpStart and Advanced Installations.

Patching Miniroot on x86 Machines

The procedures for using patchadd with the -C destination specifier to patch a miniroot on an x86 machine have changed. You must now unpack the miniroot, apply patches, then repack the miniroot.

See the following for the detailed steps:

• Chapter 8, Preparing to Install From the Network With DVD Media (Tasks), in Solaris 10 6/06 Installation Guide: Network-Based Installations

• Chapter 9, Preparing to Install From the Network With CD Media (Tasks), in Solaris 10 6/06 Installation Guide: Network-Based Installations

Correct Solaris Data Encryption Supplement Required for Installation of Solaris 10 1/06 Release

When you install the Solaris 10 1/06 release, you must use the Solaris Data Encryption Supplement that corresponds to the release. The supplement is delivered in the SUNWcry and SUNWcryr packages. If you do not have the correct supplement version, upgrade the supplement by installing the appropriate patch:

• Patch ID 118562-05 or a later revision for SPARC based systems

• Patch ID 118563-04 or a later revision for x86 based systems

To determine your current supplement version, use showrev -p.

Additional Procedures Required When Installing Patches for Solaris 10 1/06 Release

The following patches are applied to resolve problems that were reported in CR 6277164 and CR 6214222:

• Patch ID 119366-05 for SPARC based systems

• Patch ID 119367-05 for x86 based systems

The sections that follow provide further steps that you must perform to completely resolve the reported problems.

Resolving Issues With the GNOME Display Manager (6277164)

Perform this procedure before you use the GNOME Display Manager (GDM) as your login program, or if you have already enabled GDM as your login program. Otherwise, you can skip this procedure.

When applying the patch, load new values into the GDM configuration files. Then restart the GDM application.

1. To load the new values into the configuration file, choose one of the following options.

   • Copy the /etc/X11/gdm/factory-gdm.conf file to the /etc/X11/gdm/gdm.conf file.

     Perform this step if you have not made any modifications to the gdm.conf file. Then you can start the GDM application.

   • Manually merge the differences in the factory-gdm.conf file into the gdm.conf file.

     Perform this step if you have modified the gdm.conf file and want to retain your modifications.

     When merging files, copy the values for the following commands from the factory-gdm.conf file to the gdm.conf file. These commands enable you to obtain the best OS performance.

     • RebootCommand

     • HaltCommand

     • SuspendCommand

     • DefaultPath

     • RootPath

     • GraphicalTheme

2. To restart GDM, perform the following steps:

   1. Become superuser.

   2. Issue the following command:

      # svcadm disable application/gdm2-login

   3. In the console that is now displayed, press Return to display a command prompt.

   4. To restart GDM, issue the following command:

      # svcadm enable application/gdm2-login

Resolving Issues With AccessKeyMouseListeners (6214222)

To further resolve problems that are reported in CR 6214222, perform these steps when applying the patch.

1. Change to the /etc/X11/gdm/modules directory.

2. Copy the files from factory-AccessDwellMouseEvents to AccessDwellMouseEvents.

3. Copy the files from factory-AccessKeyMouseEvents to AccessKeyMouseEvents.

4. Restart GDM by following the steps that are provided in the previous section.

Sun Fire V250 Server Installation

The SUNWCXall software metacluster must be installed on a Sun Fire V250 Server.

NFS Version 4 Introduces New Prompt at First System Boot

Solaris 10 OS uses NFS Version 4 (NFSv4) as the default distributed file system mechanism. In NFSv4, file user and group attributes are exchanged as strings of the form “user@domain” and “group@domain,” respectively.

The domain portion of the string should be common between client and server. This information is automatically derived from the system's name service domain name. However, in certain cases, the derived domain might not match between client and server. This mismatch might typically occur in environments where either of the following circumstances is true:

• The DNS TXT record is not used.

• Multiple administrative domain boundaries are crossed.

If domain information between client and server does not match, NFSv4-accessed files might appear to be owned by “nobody.”

To ensure proper configuration, on the first system boot the system now prompts you for a domain to use for NFSv4. Answer “no” to this prompt if one of the following configurations describes your deployment:

• Your deployment utilizes the DNS TXT record to configure the NFSv4 domain.

• Your deployment has a single (flat) administrative domain.

Custom JumpStart and Advanced Installations

Environments that use the Custom JumpStart^TM method to perform unattended system installations require minimal tuning to suppress the first boot prompts.

A sample script, set_nfs4_domain, is provided in the Solaris 10 distribution media and is located in the ${CDrom_mnt_pt}/Solaris_10/Misc/jumpstart_sample directory. A copy of this script should be modified to set the NFS4_DOMAIN variable to site-specific needs and be called from within JumpStart's finish script. The target system's NFSv4 domain is therefore preconfigured as part of the JumpStart finish phase, and thus suppresses any first boot prompts.

Follow these steps to perform unattended installations:

1. Create a copy of the set_nfs4_domain script in the same directory as your JumpStart's finish.sh scripts.

2. Edit the script and set the NFS4_DOMAIN variable to your specific needs.

3. Edit your finish.sh script and append a call to set_nfs4_domain.

4. Perform the JumpStart installations as usual.

For further details, refer to the sysidconfig(1M), sysidtool(1M), nfsmapid(1M), and nfs(4) man pages. See also the System Administration Guide: Network Services.

x86: Systems With elx or pcelx NICs Fail Network Configuration

Systems with an elx or a pcelx network interface card (NIC) fail to install. During the configuration of the NIC, the following error message might be displayed:

WARNING: elx: transmit or jabber underrun: d0<UNDER, INTR, CPLT>

See the elxl(7D) or pcelx(7D) man page for more information.

Workaround: Install and run on systems that do not have elx or pcelx NICs.

Default Size of /var File System Inadequate for Extra Value Products

The default size of the /var file system might be insufficient for the Extra Value products in the following situations:

• If you install any of the Extra Value products that are provided on the Solaris 10 DVD or CDs

• If the /var file system is located on a separate slice

You must manually specify a larger slice size for the /var file system.

If the /var file system is not on a separate slice or partition, this problem does not occur.

Workaround: Choose one of the following workarounds.

• If you are using the Solaris installation program GUI, follow these steps.

  1. Begin the installation.

  2. From Select Type of Install, select Custom Install.

     The Solaris installation program displays several screens that enable you to customize the software localizations, products, and disk layout that you want to install.

  3. From Lay Out File Systems, select Modify.

     The disk layout screen is displayed.

  4. Type /var in the File System column for a specific slice, then click Apply.

     The installation program suggests a default size for the /var file system.

  5. Edit the Size column entry for the /var file system to twice the disk space size.

     For example, if the installation program assigns 40 Mbytes of space, change the Size value to 80.

  6. Complete the installation.

• If you are using the Solaris installation program's text installer, follow these steps.

  1. Begin the installation.

  2. From Select Type of Install, select Custom Install.

     The Solaris installation program displays several screens that enable you to customize the software localizations, products, and disk layout that you want to install.

  3. From Lay Out File Systems, select Auto Layout.

     The disk layout screen is displayed.

  4. Type /var in the File System column for a specific slice.

     The installation program suggests a default size for the /var file system.

  5. Press F4_Customize to customize the size of the /var file system.

  6. Edit the Size column entry for the /var file system to twice the disk space size.

     For example, if the installation program assigns 40 Mbytes of space, change the Size value to 80.

  7. Complete the installation.

• If you are using the custom JumpStart program, use the filesys profile keyword to set the size of the /var file system. The following example sets the size of the /var file system on slice 5 to 256 Mbytes.

  filesys c0t0d0s5 256 /var

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

The Solaris 10 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 10 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.

SPARC: Older Firmware Might Need Boot Flash PROM Update

On SPARC based systems, Solaris 10 OS runs in 64–bit mode only. Some Sun4U^TM systems might need to be updated to a higher level of OpenBoot^TM firmware in the flash PROM to run the OS in 64-bit mode. The following systems might require a flash PROM update:

• Ultra^TM 2

• Ultra 450 and Sun Enterprise^TM 450

• Sun Enterprise 3000, 4000, 5000, and 6000 systems

The following table lists the UltraSPARC systems and the minimum firmware versions that are required to run the 64–bit Solaris 10 OS. System type is the equivalent of the output of the uname -i command. You can determine which firmware version 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.

See any edition of the Solaris 8 Sun Hardware Platform Guide at http://docs.sun.com for instructions to perform a flash PROM update.

Additional Patches Are Needed to Run Solaris Live Upgrade

For Solaris Live Upgrade to operate correctly, a limited set of patch revisions must be installed for a given OS version. 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^SM web site.

Limitation When Installing Solaris Live Upgrade Packages

If you are running the 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 8, Using Solaris Live Upgrade to Create a Boot Environment (Tasks), in Solaris 10 6/06 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

• 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.

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 10 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 10 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 10 Software - 4 CD into your CD-ROM drive. Type the following in a terminal window:

     # # cd /cdrom/cdrom0/Solaris_10/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.

SPARC: Upgrade Hangs on Sun Blade 1500 Workstations (6363365)

Upgrading to the Solaris 10 1/06 software might hang if you are installing or upgrading from a DVD media. The problem affects certain Sun Blade^TM 1500 workstations that are equipped with the JLMS DVD drive. The error occurs when you use any of the following installation methods:

• Solaris interactive installation program

• Solaris Live Upgrade

When the system hangs, no error messages are displayed.

Workaround: To upgrade such a system, use a network installation image.

x86: Failure of BIOS Device Utility Prevents Installation or Upgrade From Being Completed (6362108)

On certain occasions, the utility for BIOS devices (/sbin/biosdev) might fail and prevent a successful installation or upgrade. The failure can occur under either of the following circumstances:

• Patch ID 117435-02 was applied, but the system was not rebooted.

• The system contains two or more identical disks that have identical fdisk partitions.

The following error message is displayed:

biosdev: Could not match any!!

Workaround: Make sure that you reboot the system after applying Patch ID 117435-02. Ensure that identical disks to be used in the installation or upgrade are configured with different fdisk-partition layouts.

The following example is based on a system that has two disks with identical fdisk-partition layouts. To change the layouts, perform the following steps.

1. Become superuser.

2. Start the disk maintenance utility.

   # format

   A list of available disks in the system is displayed.

3. To select the disk whose fdisk partition you want to change, type the disk's number.

4. From the list of Format options, select fdisk.

   The disk's partition information and a list of fdisk options are displayed.

5. To change the disk's layout, choose one of the following:

   • To specify a different active partition, press 2.

   • To add another disk partition, press 1.

   • To delete an unused partition, press 3.

6. To save your changes and exit the fdisk menu, press 5.

7. To exit the disk maintenance utility, select Quit from the Format options.

8. Reboot the system.

9. After the system reboots, verify that the error message no longer appears. As superuser, type the following command:

   # /sbin/biosdev

   If the error message is still generated, repeat the procedure but select a different option in Step 5.

10. If the system contains other identical disks with identical fdisk-partition layouts, repeat Steps 1-9 on these disks. Otherwise, you can proceed with your Solaris installation or upgrade.

Upgrade Option Unavailable if the Root (/) File System Is a RAID-1 Volume (Mirror) (6263122)

A problem occurs when you upgrade to the Solaris 10 1/06 software a system whose root (/) file system is a RAID-1 volume. This problem occurs when you perform the upgrade as follows:

• You use CD media or an network installation image.

• You use the Solaris interactive installation program or custom JumpStart.

One of the following problems occurs:

• If you are using the Solaris interactive program, you are not given the option of upgrading in the panel Select upgrade or initial install.

• If you use custom JumpStart to upgrade, the following error message is displayed:

  ERROR: No upgradeable root file systems were found.

Workaround: Perform Workaround 1 first. Proceed to Workaround 2 only if the first workaround did not resolve the issue.

• Workaround 1:: Remove the RAID configurations before performing the upgrade. Rebuild your RAID configuration after the upgrade is completed. To remove the RAID configurations, follow these steps.

  1. Find the physical devices that are being used for the root partition's RAID-0 volumes or submirrors, as in the following example:

     # df -k / Filesystem kbytes used avail capacity Mounted on /dev/md/dsk/d0 4459950 3089180 1326171 70% / # metastat -p d0 d0 -m d10 d11 1 d10 1 1 c1t0d0s0 d11 1 1 c1t1d0s0

  2. Remove the mirror that is not being upgraded. In the example, if the disk to be upgraded is c1t0d0s0, you need to remove d11. Type the following:

     # metadetach d0 d11

  3. Revert to using the appropriate physical device to be upgraded. For the previous example, you issue the following command.

     # metaroot c1t0d0s0

  4. If necessary, verify that the /etc/vfstab has been updated with the required device.

     # grep c1t0d0s0 /etc/vfstab /dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no -

  5. Shut down the system.

  6. Boot the system from the DVD or CD media.

     In the panel Select upgrade or initial install, you can now choose to upgrade. You can also select the device to upgrade from the list of devices in the panel. Typically, the list contains the devices that comprise the original root subvolume.

     However, if the option to upgrade remains unavailable, then skip to the alternative workaround.

  7. To proceed with the upgrade, select the device.

  To rebuild your RAID configurations after the upgrade has been completed, follow these steps.

  1. Redefine the boot device.

     # metaroot d0

  2. Reboot the system.

  3. Add the subvolume.

     # metattach d0 d11

• Workaround 2: Use this workaround only if Workaround 1 was not successful. Do not perform this workaround without attempting the previous workaround first.

  1. Reboot the system.

     The system boots back to the existing Solaris release.

  2. Delete the active metadevices that comprise the root partition by using the metaclear command.

     # metaclear d0 d10 d11

  3. Shut down the system.

  4. Boot the system from the DVD or CD media.

  5. Proceed with the installation by following the installation or upgrade options that appear on the screen.

  6. After the upgrade is completed, reconfigure your metadevices by following the normal procedures.

  The following example shows the steps to configure the root (/) metadevice, set up the system files for the metadevice, and reattach the subvolume.

  # metainit d0 -m d10 # metaroot d0 # reboot # metainit d11 1 1 c1t1d0s0 # metattach d0 d11

  ---

  Note –

  You reattach the old subvolume after the system boot is completed.

  ---

Cannot Create a Solaris Flash Archive When Solaris Zones Are Installed (6246943)

Starting with the current Solaris release, a Solaris Flash archive cannot be properly created when a non-global zone is installed. The Solaris Flash feature is not currently compatible with the Solaris containers (zones) feature.

Do not use the flar create command to create a Solaris Flash archive in these instances:

• In any non-global zone

• In the global zone if there are any non-global zones installed

If you create a Solaris Flash archive in such an instance, the resulting archive might not install properly when the archive is deployed.

Workaround: None.

Installation Fails When You Install Solaris Flash Archive on Empty Boot Environment With Solaris Live Upgrade (6222925)

If you use Solaris Live Upgrade to install a Solaris Flash archive on an empty alternate boot environment, the installation fails. Messages that are similar to the following errors are displayed.

sh:  /path_to_install_image/Solaris_10/Tools/Boot/usr/sbin/install.d
/mergescripts/merge_name_service:  not found

ERROR: Transfer list entry (/a/var/svc/profile/name_service.xml):
mergescript failed (/path_to_install_image/Solaris_10/Tools/
Boot/usr/sbin/install.d/mergescripts/merge_name_service)

ERROR: Unable to copy a temporary file to it's final location

ERROR: Flash installation failed

Extracting Flash Archive: 100% completed (of 4361.24 megabytes)
The Solaris flash install of the BE S10B74L2 failed.

In the previous example, path_to_install_image is the directory path to the network installation image you are using for the installation.

Workaround: Follow these steps.

1. Change directories to the mergescripts directory in the network installation image that you are using for the installation.

   # cd path_to_install_image/Solaris_10/Tools /Boot/usr/sbin/install.d/mergescripts

2. Create the merge_name_service file.

   # touch merge_name_service

3. Make the merge_name_service file executable.

   # chmod a+x merge_name_service

4. On the system you want to install, install the Solaris Flash archive on the alternate boot environment with Solaris Live Upgrade.

   For instructions about how to install a Solaris Flash archive with Solaris Live Upgrade, see Installing Solaris Flash Archives on a Boot Environment in Solaris 10 6/06 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

5. Mount the file systems in the alternate boot environment you installed in step 4.

   # lumount alt_boot_env mount-point

   In the previous command, alt_boot_env is the boot environment you installed in step 4. mount-point is the mount point for the alternate boot environment.

6. Change directory to the /var/svc/profile directory in the alternate boot environment.

   # cd mount-point/var/svc/profile

7. Remove the name_service.xml profile.

   # rm name_service.xml

8. Create a symbolic link for the name service profile to the name_service.xml file.

   # ln -s ns_name-service.xml name_service.xml

   In the previous example, name-service is the name service you want to use for the system. Use one of the following strings for this value.

   • nis

   • nisplus

   • dns

   • ldap

   • files

x86: Sun Java Workstations 2100Z Might Panic When Booting From Solaris 10 Operating System DVD (6214356)

The DVD combo-drive firmware in a Sun Java Workstation 2100Z might cause a system panic. The panic occurs when you boot the workstation from the Solaris 10 Operating System DVD. After the kernel banner is displayed, the following message is very quickly flashed:

panic[cpu0]/thread=fec1be20: mod_hold_stub: 
Couldn't load stub module sched/TS_DTBL
fec25cb0 genunix:mod_hold_stub+139 (fec04088, 63, fea11)
fec25cc4 unix:stubs_common_code+9 (1, 8, fec026e4)
fec25ce4 unix:disp_add+3d (fec026dc)
fec25d00 genunix:mod_installsched+a4 (fef01530, fef01518)
fec25d20 genunix:mod_install+2f (fef01518, fec25d3c,)
fec25d2c TS:_init+d (0, d6d89c88, fec25d)
fec25d3c genunix:modinstall+d9 (d6d89c88)
fec25d50 genunix:mod_hold_installed_mod+2e (d6d77640, 1, fec25d)
fec25d7c genunix:modload+ac (fec026c4, fec26c4)
fec25d98 genunix:scheduler_load+3d (fec026c4, fec026dc)
fec25db4 genunix:getcid+50 (fec026c4, fec28514)
fec25dcc unix:dispinit+df (fec25ddc, fe814ba9)
fec25dd4 unix:startup_modules+d5 (fec25dec, fe8cac37)
fec25ddc unix:startup+19 (fe800000, 166130, 7)
fec25dec genunix:main+16 ()

Then the system automatically resets.

Workaround: Choose one of the following options:

Workaround 1: Modify some BIOS configuration settings. This temporary workaround enables a Solaris 10 installation to be completed. However, this method might cause poor read-DVD performance. Follow these steps:

1. During system boot, press F2 at the prompt to enter the setup.

   The screen displays attachment-type options similar to the following example:

   Primary Master [ ] Primary Slave [ ] Secondary Master [CD-ROM] Secondary Slave [ ]

2. Choose the DVD drive's attachment type by selecting the attachment type for CD-ROM.

   ---

   Note –

   The screen might display more than one attachment type for CD-ROM, for example, if your system has multiple optical drives. In such cases, you might need to open the system case to determine the DVD drive's point of attachment. Make sure that you select the correct attachment type that applies to the DVD drive.

   ---

3. After selecting the correct CD-ROM attachment type, press Enter.

   The next screen appears with Type:[Auto] automatically selected.

4. Press the spacebar twice to change the selection to Type:[CD-ROM].

5. Use the arrow keys to select Transfer Mode.

6. Press Enter to display a list of other Transfer Mode options.

7. Use the arrow keys to select Standard, then press Enter to accept your selection.

8. Press F10 to save the configuration changes and exit BIOS setup.

   The system restarts.

Workaround 2: Update the DVD combo drive's firmware to v1.12. This option requires your DVD combo drive to be attached to a system that is running Microsoft Windows. Follow these steps.

1. Remove your DVD combo drive from the Sun Java Workstation 2100z. See the workstation's user's guide for steps to remove the drive properly.

2. Connect the drive to a system that is running Microsoft Windows. Make sure to change the drive's master and slave jumper settings, if needed.

3. Go to AOpen's download center at http://download.aopen.com.tw/default.aspx.

4. Search for your DVD drive's firmware by using the following information:

   • Product: Combo drives

   • Model: COM5232/AAH

   • Categories: Firmware

5. Download and install the firmware version R1.12.

6. Reinstall the drive on the workstation. If needed, restore the original master and slave jumper settings.

Newer versions of the firmware might already be available at the site. Sun's tests confirm that the v1.12 release resolves the panic issue. Sun cannot confirm whether newer firmware revisions after v1.12 similarly resolve the problem.

x86: Serial Consoles of Some Sun Fire Systems Do Not Work (6208412)

The serial console (ttya) on the following Sun Fire systems does not work by default:

• Sun Fire V20z

• Sun Fire V40z

• Sun Fire V60x

• Sun Fire V65x

To use the serial console, you must manually configure the system's BIOS.

Workaround: This workaround requires your system to have a Sun keyboard and a display monitor. Follow these steps:

1. Boot the machine.

2. During system boot, press F2 at the prompt to access the Phoenix BIOS.

3. Under Peripherals, change the comm port from disabled to enabled.

4. Save the configuration and boot the system.

5. Use the eeprom command to change input-device and output-device to ttya.

Pressing the Stop and N keys at system boot to reset the low-level firmware to default settings does not work on these systems.

Solaris Installation GUI Program Might Fail on Systems With Existing x86 fdisk Boot Partitions (6186606)

The Solaris installation GUI program might fail on a system with an existing x86 boot partition. The failure occurs if the existing x86 boot partition was created with the Solaris text-based installer. The following error message is displayed.

Default layout will not work on this system.
Error:
Error: ERROR: Could not create explicit fdisk partition on c0t0d0,
requested cylinders 14581 - 14597 in use by fdisk partition 1
Error:
Error: ERROR: System installation failed
Pfinstall failed. Exit stat= java.lang.UNIXProcess@a89ce3 2 
artition on c0t0d0, requested cylinders 14581 - 14597 in use by fdisk
partition 1  ERROR: System installation failed

Workaround: Choose one of the following workarounds.

Workaround 1: When the installation program prompts you to select an installation type, select 3 Solaris Interactive Text (Desktop Session).

Workaround 2: If you use the Solaris installation GUI program, follow these steps.

1. Begin the installation.

2. At the prompt to select an installation type, select Custom Install.

   The custom installation panels prompt you for information about the locales, software, and disks that you want to install.

3. Answer the questions on the screens as appropriate for your system.

4. On the Fdisk Selection screen, check the disk that contains the x86boot partition.

5. Remove the x86boot partition by changing it to UNUSED in the pull-down menu.

6. Add the x86boot partition back by changing UNUSED back to x86boot.

7. Continue the installation.

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:

Installation Bugs

The following bugs might occur during or after the installation of Solaris 10 OS.

x86: Install Hangs on Systems With 512 Mbyte of Memory (6423854)

Installations can run out of memory and hang on 512-Mbyte systems under the following conditions:

• You install using a network installation image of the OS.

• The Solaris installation program is in a windowing environment:

  • The graphical user interface (GUI).

  • The -text option or “3. Solaris Interactive Text (Desktop session)” in the menu below.

When the system exhausts available memory, the GUI installation process slows and eventually fails. The text does not display in a windowing environment.

Workaround:

To avoid this problem, select a non-windowing environment during the initial installation startup. During startup from the installation media the following menu is displayed:

-----------
 1.     Solaris Interactive (default)
 2.     Custom JumpStart
 3.     Solaris Interactive Text (Desktop session)
 4.     Solaris Interactive Text (Console session)
 5.     Apply driver updates
 6.     Single user shell
 Enter the number of your choice.
 -----------

At this point, choose “4. Solaris Interactive Text (Console session)”. This non-windowing environment will initiate a text-only installation, without using memory-intense processes.

Creating a Solaris Flash Archive Fails When the End User Solaris Software Group is Installed (6397893)

The following example of the flarcreate command shows the error:

# flarcreate -n test.flar -c /net/ins3525-svr/export/rw/test.flar
Full Flash
Checking integrity...
Integrity OK.
Running precreation scripts...
./caplib: ERROR: /usr/ccs/bin/elfdump not found or not executable, exiting...

fdo: ERROR: Customization script failure.
ERROR: Precreation script failure.

Running pre-exit scripts...
Pre-exit scripts done. 

Workaround:

From the DVD or CD installation media, add the SUNWbtool package using the pkgadd command. After this package is added, you can run the flarcreate command successfully.

1. Change directories.

   # cd /cdrom/cdrom0/Solaris_10/Product

2. Add the SUNWbtool package.

   # pkgadd -d `pwd` SUNWbtool

x86: SVM Upgrade Fails From Solaris 9 9/05 OS to Solaris 10 6/06 or to Solaris Express (6397251)

If you upgrade a Solaris Volume Manager (SVM) on x86 platforms, the upgrade fails. The failure occurs if the SVM volume is configured on the root (/) file system and you upgrade from the Solaris 9 9/05 OS to the Solaris 10 6/06 OS or to a Solaris Express release.

The following error message is displayed:

Processing profile

ERROR: The specified root and/or boot was not found or was not upgradeable
Solaris installation program exited.

Solaris Not Sending a PRLI to Tape Device (6379955)

Solaris OS is not sending Process Login (PRLI) data to the tape device during a path recovery sequence.

No error message is displayed to the user, but the problem can be identified from:

• Regular system log messages indicates a path issue, such as offline or online.

• Cfgadm -al command. This command shows the failed condition for the tape device.

• I/O to a tape device has ceased.

Workaround:

To recover from this situation, use the luxadm forcelip command to the FC host bus adapter. For example:

luxadm -e forcelip /dev/cfg/c99

c99 is the specific controller that is being used to communicate with the tape transport.

Java Problem Prevents Accessibility Environment for Speech From Setting Up Correctly (6377106)

If you are installing the Solaris 10 6/06 release from a combined network installation image or DVD media, the installation partially fails. This failure causes some accessibility features, such as speech feedback, not to work. The problem is related to Java^TM packages and accessibility packages that cause an older Java software to become the default version.

Workaround:

After the installation completes, you must manually create some links and copy some files to various locations. After this is done, the Java 1.5.0 version will be the correct default version executed, and the various files for Java will be in place. The speech feedback for accessibility users will work properly.

Follow this procedure:

1. Log in as superuser.

2. Change to the /usr directory.

   # cd /usr

3. Remove the current java directory.

   # rm java

4. Link to the current java directory.

   # ln -s jdk/jdk1.5.0_06 java

5. Change to the /lib directory.

   # cd jdk/jdk1.5.0_06/jre/lib/

6. Link to the accessibility file.

   # ln -s /usr/share/jar/accessibility.properties

7. Copy the Java file.

   # cp /usr/share/jar/gnome-java-bridge.jar ext/

x86: After Installing the OS with a Solaris Flash Archive, Problem With Displaying Console (6372197)

After installing a Solaris Flash archive, the console value in the /boot/solaris/bootenv.rc file is not updated. After the reboot, the system is up and running, but the console does not display properly.

Workaround:

1. Telnet to the system remotely.

2. Modify the /boot/solaris/bootenv.rc file with the correct console value.

   The value is one of the following:

   • ttya

   • ttyb

   • screen

3. Reboot the system.

x86: Custom JumpStart Profile Test Fails With Locale Keyword (6340509)

When you test your JumpStart profile using the pfinstall -D command, the dry run test fails under the following conditions:

• The profile contains the locale keyword.

• You are testing a release that contains GRUB software. Starting with the Solaris 10 1/06 release, the GRUB boot loader facilitates booting different operating systems installed on your system with the GRUB menu.

With the introduction of GRUB software, the miniroot is compressed. The GRUB software can no longer find the list of locales from the compressed miniroot. Aminiroot is the smallest possible Solaris root (/) file system and is found on the Solaris installation media.

The following error message is displayed:

Could not select locale

Workaround:

The script values are as follows:

• MEDIA_DIR=/cdrom/cdrom0/s0

• MINIROOT_DIR=$MEDIA_DIR/Solaris_10/Tools/Boot

• MINIROOT_ARCHIVE=$MEDIA_DIR/boot/x86.miniroot

• TEMP_FILE_NAME=/tmp/test

Perform the following steps:

1. Uncompress the miniroot archive.

   # /usr/bin/gzcat $MINIROOT_ARCHIVE > $TEMP_FILE_NAME

2. Create the miniroot device using the lofiadm command.

   # LOFI_DEVICE=/usr/sbin/lofiadm -a $TEMP_FILE_NAME # echo $LOFI_DEVICE/dev/lofi/1

3. Mount the miniroot with lofi under the miniroot directory.

   # /usr/sbin/mount -F ufs $LOFI_DEVICE $MINIROOT_DIR

4. Test the profile.

   # /usr/sbin/install.d/pfinstall -D -c $MEDIA_DIR $path-to-jumpstart_profile

5. After the pfinstall testing is completed, unmount the lofi device.

   # umount $LOFI_DEVICE

6. Delete the lofi device.

   # lofiadm -d $TEMP_FILE_NAME

Postinstallation Problems With Whole Root Zone, Diskless Client, and Solaris Live Upgrade (6358227)

Postinstallation processes might encounter problems while the SUNWgnome-a11y-libs-share package is being added. The problems affect the following situations:

• Using non-global zones and setting up a whole root zone

• Using Solaris Live Upgrade to upgrade from the Solaris 8 or Solaris 9 release

• Setting up a diskless client from the Solaris 10 1/06 release

1. If you are using non-global zones and have set up a whole root zone, the following error message is displayed:

   # zoneadm -z wholerootzone install Installation of these packages generated warnings: <SUNWgnome-a11y-libs-share> The file </export/home/wholerootzone/root/var/sadm/system/logs/install_log> contains a log of the zone installation . #

   The install_log reports the following error:

   *** package <SUNWgnome-a11y-libs-share> installed with warnings: cp: cannot access ../../../../../share/jar/gnome-java-bridge.jar pkgadd: ERROR: postinstall script did not complete successfully Installation of <SUNWgnome-a11y-libs-share> on zone <wholerootzone> partially failed.

2. If you upgrade by using Solaris Live Upgrade from the Solaris 8 or Solaris 9 release, the upgrade_log reports the following error:

   Doing pkgadd of SUNWgnome-a11y-libs-share to /. 15360 blocks /a/var/sadm/pkg/SUNWgnome-a11y-libs-share/install/postinstall: /sbin/zonename: not found Installation of <SUNWgnome-a11y-libs-share> was successful.

3. If you set up the diskless client service for the Solaris 10 1/06 release, the log file in /var/sadm/system/logs for your specific system reports the following error:

   Doing pkgadd of SUNWgnome-a11y-libs-share to /export/Solaris_10. 15360 blocks /export/Solaris_10/var/sadm/pkg /SUNWgnome-a11y-libs-share/install/postinstall: /export/Solaris_10/usr/java/jre/lib: does not exist pkgadd: ERROR: postinstall script did not complete successfully Installation of <SUNWgnome-a11y-libs-share> failed. pkgadd return code = 1

Workaround: In all three situations, ignore the error messages.

x86: Problem With Choosing a Terminal Type When Installing Solaris 10 1/06 Software (6350819)

When you use the Solaris interactive installation program, the Choose Terminal Type screen causes errors in the installation. The program immediately accepts the first character that you type and then proceeds with the installation. Consequently, you cannot choose an option that requires you to type more than one character. If you accidentally typed one character, which the installation program immediately accepts, the rest of the installation proceeds in error. No error message is displayed.

Workaround: Start the installation normally. At the screen that prompts you for the installation type, select the type before the timer expires in 30 seconds. Subsequent selection of the terminal type should work properly.

x86: Invalid /sbin/dhcpinfo Error During Installation (6332044)

If you install the Solaris 10 1/06 release on an x86 based system, the following error message is displayed.

/sbin/dhcpinfo: primary interface requested but no primary interface is set

The error does not affect the installation, and the installation succeeds.

Workaround: Ignore the error message.

SPARC: Loadkeys Warnings Appear When System Is Booted From Solaris OS DVD (6329642)

When you boot the system from the Solaris OS DVD to install the Solaris software, the following warning is displayed:

/sbin/install-discovery: /usr/bin/loadkeys: not found

Consequently, keyboard mappings for autodetected keyboards are not automatically loaded during the boot process.

Workaround: None. Ignore the warning message. You can continue to install the Solaris software on the system even without the keyboard mappings. After you have completed the installation, these mappings are automatically set when you reboot the system.

Solaris Install Launcher Exiting Causes Reboots (6300863)

In some situations, installation of Solaris 10 3/05 HW1 fails when the Solaris Install Launcher fails to find find_device.out, reboots, then reaches the same point and prompts for a reboot again.

Workaround: Specify the -text option when booting:

boot net -text

x86: Installation From CD Media Appears to Hang After Reboot Selection (6270371)

A problem might occur when you are using the Solaris installation program and are using CD media. After the installation of the Solaris software from the Solaris 10 1/06 Software CD - 4, the following prompt is displayed:

Press Reboot now to continue.

If you press Reboot, the system might not respond. The installation is successful. However, the error prevents the installation program from exiting normally. Consequently, the typical postinstallation cleanup and system reboot cannot occur.

An error message similar to the following example is logged in /tmp/disk0_install.log file:

Exception in thread "Thread-70" java.lang.IndexOutOfBoundsException:
Index: 6, Size: 5
     at java.util.ArrayList.add(ArrayList.java:369)
     at
com.sun.wizards.core.WizardTreeManager.
actualExitButtonPressed(WizardTreeManager.java:1499)
     at
com.sun.wizards.core.WizardTreeManager.
exitButtonPressed(WizardTreeManager.java:1486)
     at
com.sun.wizards.core.AutonextController.
run(AutonextController.java:736)
     at
java.lang.Thread.run(Thread.java:595)

Workaround: Choose one of the following workarounds.

• Workaround 1: Follow these steps.

  1. Shut down the system, then turn on the power again.

  2. After the system starts up, insert the appropriate CD at the prompt. Although the CD is inserted, no additional software is installed on the system. In a moment, the system reboots normally.

• Workaround 2: Follow these steps.

  1. Open a terminal window.

  2. Log in as superuser.

  3. Create or modify access to the .instsuccess file.

     # touch /tmp/.instsuccess

  4. Stop the Java process.

     # pkill -9 java

     The system reboots without prompting for the CD media.

x86: kdmconfig Program Runs Twice After Initial Installation (6209092)

During the first system reboot after an initial Solaris 10 OS installation, the kdmconfig program might run twice. During this initial startup, each time the program starts, you are prompted to select an X server. This situation occurs on x86 based systems that have not been configured to use the X server. An example of such a system is a “headless” system that is not using a graphics display.

Workaround: Each time the program starts and prompts for an X server, press F3_Exit. A short delay might occur before the startup process resumes. After this initial startup is completed, the problem no longer occurs if the system is subsequently rebooted.

x86: System Fails to Boot After Custom JumpStart Installation (6205478)

If you use the Custom JumpStart installation method to install on an x86 based system, and explicitly configure slice 2 as the overlap slice in the profile, an error occurs. The system does not reboot successfully after the installation is completed. The following error message is displayed:

Cannot find Solaris partition

This failure occurs because the overlap slice 2 (c0t0d0s2, for example) is set to begin at cylinder 1 rather than cylinder 0.

Workaround: In the Custom JumpStart profile, remove the filesys keyword entry that configures slice 2 as the overlap slice. For example, you would remove a keyword entry that is similar to the following entry.

filesys c0t0d0s2 all overlap

After you remove the entry, perform the Custom JumpStart installation.

x86: GUI Interactive Installation From DVD Fails if boot-device Variable Is Not Set (5065465)

If you install Solaris from the Solaris 10 Operating System DVD, the interactive GUI installation might fail. This failure occurs if the boot-device configuration variable is not set on the system.

To determine if the boot-device configuration variable is set, type the following command.

# prtconf -pv | grep boot-device

If the output of this command is boot-device: with no associated device, you cannot use the interactive GUI installation program to install from the Solaris 10 Operating System DVD.

Workaround: Use the interactive text installer to install Solaris 10 software. When the installation program asks you to select a type of installation, select option 3, Solaris Interactive Text (Desktop Session).

For more information about installing from the Solaris 10 Operating System DVD, see Solaris 10 6/06 Installation Guide: Basic Installations.

SPARC: Solaris 10 OS Installation Program Might Not Display Special Case Panels Properly (5002175)

If you install the Solaris 10 software by using the Solaris 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 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 10 software has completed, manually install the SRS Net Connect software from the Solaris 10 Operating System DVD or Solaris 10 Software - 2 CD.

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

x86: USB Keyboards Might Freeze During Install on Some Dell Precision Workstations (4888849)

During installation, USB keyboards on some Dell Precision Workstations might freeze or become partially inoperative, thereby preventing installation.

Workaround: Perform one of the following workarounds:

• Switch the USB emulation mode in the firmware.

• Switch to a PS/2 keyboard.

• Reboot and try again.

Alternatively, update the system's BIOS to resolve the problem.

SPARC: Error Messages Might Be Seen When Installing Solaris By Using a Network Image (4704046)

You can install Solaris by using a network image. If that image is created by combining the Solaris 10 Software CDs, the following error messages might be seen:

Error message:    Jun 18 10:51:53 b26b statd[149]: [ID 514559 
daemon.error] svc_tp_create: Could not register prog 100024 vers 1 on udp 
Jun 18 10:51:53 b26b statd[149]: [ID 514559 daemon.error] svc_tp_create: 
Could not register prog 100024 vers 1 on tcp 
Jun 18 10:51:53 b26b statd[149]: [ID 514559 daemon.error] svc_tp_create: 
Could not register prog 100024 vers 1 on ticlts 
Jun 18 10:51:53 b26b statd[149]: [ID 514559 daemon.error] svc_tp_create: 
Could not register prog 100024 vers 1 on ticotsord 
Jun 18 10:51:53 b26b statd[149]: [ID 514559 daemon.error] svc_tp_create: 
Could not register prog 100024 vers 1 on ticots 
Jun 18 10:51:53 b26b statd[149]: [ID 447212 daemon.error] statd: 
unable to create (SM_PROG, SM_VERS) for netpath.

Workaround: None. Ignore the message. After the system boots, the Network File System (NFS) functions normally.

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 and Bugs

For the latest information about upgrade support beginning with the Solaris 10 1/06 release, see Changes in Upgrade Support for Solaris Releases.

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

Upgrade Fails on System With Zones That Have Been Installed But Not Booted

A non-global zone that has been installed but never booted or made ready prevents a system from being upgraded correctly. No error message is displayed.

Workaround:

If such a zone is found, the zone should be made ready and then halted prior to starting the upgrade. For example:

global# zoneadm -z myzone ready ; zoneadm -z myzone halt

Upgrade of System With Zones Installed Fails (6444457, 6444791)

Upgrade of a Solaris 10 or Solaris 10 1/06 system with zones installed to Solaris 10 6/06 will fail if the Core System Support Software Group (SUNWCreq) or End User Solaris Software Group (SUNWCuser) metaclusters are also installed on the system. No error message is displayed.

Workaround: Install the appropriate patch:

• For SPARC: Patch ID 118822-30

• For x86: Patch ID 118844-30

and any patches which 118822-30 or 118844-30 depends on for the system being upgraded and then proceed with the upgrade to Solaris 10 6/06.

Zone Creation Error With SUNWgnome-a11y-libs-share (6437617)

If you are installing whole-root non-global zones in the Solaris 10 6/06 release, the following error message might appear in the zone error log:

/export/home/wholerootzone/root/var/sadm/pkg/SUNWgnome-a11y-libs-share/install/postinstall: 
cannot return when not in function 
pkgadd: ERROR: postinstall script did not complete successfully

Installation of <SUNWgnome-a11y-libs-share> on zone <wholerootzone>

The name wholerootzone in the error message is for illustrative purposes, and the path that appears in the installation log might be different on different systems.

Workaround: None.

qlc.conf Configuration File Not Updated While Upgrading to Solaris 10 6/06 Release (6428334)

While upgrading to Solaris 10 6/06 release with an existing /kernel/drv/qlc.conf configuration file, the qlc.conf file is not acquiring the updated format and parameters. No error message is displayed.

Workaround:

To update the qlc.conf file, install the following patches after upgrading to Solaris 10 6/06 release:

• SPARC: Patch 119130-21 or latest revision.

• i386: Patch 119131-21 or latest revision.

Upgrading a Solaris 10 System with Non-Global Zones to the Solaris 10 6/06 release Might Cause the Local File System Service to Fail (6428258)

Upgrading a Solaris 10 3/05 system or a Solaris 10 1/06 system to the Solaris 10 6/06 release with non-global zones might cause the SMF service that mounts local file systems to fail in the non-global zones. As a result, other services in the non-global zones might fail to start.

After upgrading a Solaris 10 system with non-global zones to the Solaris 10 6/06 release, services might be in the maintenance state. For example:

# zlogin myzone svcs -x
    svc:/system/filesystem/local:default (local file system mounts)
     State: maintenance since Wed May 24 13:18:06 2006
    Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
       See: http://sun.com/msg/SMF-8000-KS
       See: /var/svc/log/system-filesystem-local:default.log
    Impact: 18 dependent services are not running.  (Use -v for list.)

Workaround:

Reboot the non-global zone from the global zone. For example:

global# zoneadm -z myzone reboot

Upgrade From Solaris 10 to Solaris 10 6/06 Gives SMF Errors on Reboot and Contains Solaris Package Issues That Might Impact Patching (6421275)

When upgrading from Solaris 10 to Solaris 10 6/06, multiple SMF and package violation errors occur upon reboot. The following error message is displayed:

oyster console login: May  3 15:05:47 svc.startd[7]: 
svc:/system/basicreg:default: Method "/usr/sbin/sconadm register -c -m autoreg" 
failed with exit status 1.
May  3 15:05:48 svc.startd[7]: svc:/system/basicreg:default: 
Method "/usr/sbin/sconadm register -c -m autoreg" failed with exit status 1.
May  3 15:05:48 svc.startd[7]: svc:/system/basicreg:default: 
Method "/usr/sbin/sconadm register -c -m autoreg" failed with exit status 1.
May  3 15:05:48 svc.startd[7]: system/basicreg:default failed


#scvs -xv
svc:/system/basicreg:default (?)
State: maintenance since Wed May 03 15:05:48 2006
Reason: Start method failed repeatedly, last exited with status 1.
  See: http://sun.com/msg/SMF-8000-KS
  See: /var/svc/log/system-basicreg:default.log
Impact: This service is not running.
#
# cat  /var/svc/log/system-basicreg:default.log
[ May  3 15:05:33 Enabled. ]
[ May  3 15:05:33 Rereading configuration. ]
[ May  3 15:05:47 Executing start method 
("/usr/sbin/sconadm register -c -m autoreg") ]
You must accept terms of use (by passing in -a) in order to register.
The terms of use and binary code license agreement are located at:
Terms of Use : http://sun.com/applink/sunuc/tou1en
Binary Code License Agreement :
http://sun.com/applink/sunuc/bcl1en
[ May  3 15:05:48 Method "start" exited with status 1 ]
[ May  3 15:05:48 Executing start method 
("/usr/sbin/sconadm register -c -m autoreg") ]
You must accept terms of use (by passing in -a) in order to register.
The terms of use and binary code license agreement are located at:
Terms of Use : http://sun.com/applink/sunuc/tou1en

Binary Code License Agreement :
http://sun.com/applink/sunuc/bcl1en
[ May  3 15:05:48 Method "start" exited with status 1 ]
#
we also had multiple packages owning the same type "f" files 
after zones upgrade as follows:

/usr/lib/breg/basicreg.jar
/usr/lib/breg/br-common.jar
/usr/lib/breg/data/RegistrationProfile.properties
/usr/lib/breg/jdom.jar
/usr/lib/breg/resources/i18n/assetStrings_de.properties
/usr/lib/breg/resources/i18n/assetStrings_es.properties
/usr/lib/breg/resources/i18n/assetStrings_fr.properties
/usr/lib/breg/resources/i18n/assetStrings_it.properties
/usr/lib/breg/resources/i18n/assetStrings_ja.properties
/usr/lib/breg/resources/i18n/assetStrings_ko.properties
/usr/lib/breg/resources/i18n/assetStrings_sv.properties
/usr/lib/breg/resources/i18n/assetStrings_zh.properties
/usr/lib/breg/resources/i18n/assetStrings_zh_TW.properties
/usr/lib/breg/resources/i18n/countryStrings_de.properties
/usr/lib/breg/resources/i18n/countryStrings_es.properties
/usr/lib/breg/resources/i18n/countryStrings_fr.properties
/usr/lib/breg/resources/i18n/countryStrings_it.properties
/usr/lib/breg/resources/i18n/countryStrings_ja.properties
/usr/lib/breg/resources/i18n/countryStrings_ko.properties
/usr/lib/breg/resources/i18n/countryStrings_sv.properties
/usr/lib/breg/resources/i18n/countryStrings_zh.properties
/usr/lib/breg/resources/i18n/countryStrings_zh_TW.properties
/usr/lib/breg/resources/i18n/languageStrings_de.properties
/usr/lib/breg/resources/i18n/languageStrings_es.properties
/usr/lib/breg/resources/i18n/languageStrings_fr.properties
/usr/lib/breg/resources/i18n/languageStrings_it.properties
/usr/lib/breg/resources/i18n/languageStrings_ja.properties
/usr/lib/breg/resources/i18n/languageStrings_ko.properties
/usr/lib/breg/resources/i18n/languageStrings_sv.properties
/usr/lib/breg/resources/i18n/languageStrings_zh.properties
/usr/lib/breg/resources/i18n/languageStrings_zh_TW.properties
/usr/lib/breg/resources/i18n/wizardStrings_de.properties
/usr/lib/breg/resources/i18n/wizardStrings_es.properties
/usr/lib/breg/resources/i18n/wizardStrings_fr.properties
/usr/lib/breg/resources/i18n/wizardStrings_it.properties
/usr/lib/breg/resources/i18n/wizardStrings_ja.properties
/usr/lib/breg/resources/i18n/wizardStrings_ko.properties
/usr/lib/breg/resources/i18n/wizardStrings_sv.properties
/usr/lib/breg/resources/i18n/wizardStrings_zh.properties
/usr/lib/breg/resources/i18n/wizardStrings_zh_TW.properties
/usr/lib/breg/resources/i18n/xmlValueStrings_de.properties
/usr/lib/breg/resources/i18n/xmlValueStrings_es.properties
/usr/lib/breg/resources/i18n/xmlValueStrings_fr.properties
/usr/lib/breg/resources/i18n/xmlValueStrings_it.properties
/usr/lib/breg/resources/i18n/xmlValueStrings_ja.properties
/usr/lib/breg/resources/i18n/xmlValueStrings_ko.properties
/usr/lib/breg/resources/i18n/xmlValueStrings_sv.properties
/usr/lib/breg/resources/i18n/xmlValueStrings_zh.properties
/usr/lib/breg/resources/i18n/xmlValueStrings_zh_TW.properties
/usr/lib/breg/wizard.jar
/usr/sbin/sconadm
/usr/sbin/smpatch

Workaround: Follow these steps:

1. Become superuser.

2. List the SUNWbreg and SUNWbrg localization packages that are installed on the system.

   # pkginfo | awk '{print $2}' | grep 'SUNW.breg' > /tmp/list.breg # cat /tmp/list.breg SUNWcbreg SUNWdbreg SUNWebreg SUNWfbreg SUNWhbreg SUNWibreg SUNWjbreg SUNWkbreg SUNWsbreg # pkginfo | awk '{print $2}' | grep 'SUNW.brg' > /tmp/list.brg # cat /tmp/list.brg SUNWcbrg SUNWdbrg SUNWebrg SUNWfbrg SUNWhbrg SUNWibrg SUNWjbrg SUNWkbrg SUNWsbrg

   ---

   Note –

   The contents of the /tmp/list.breg file and /tmp/list.brg file might vary depending on which localization packages are installed on the system, or the files might be empty. If the /tmp/list.brg file contains packages, save the list of package names so that you know which packages you will need to copy in step 5. If the files are empty, skip to step 4.

   ---

3. Uninstall the packages found in step 2.

   # pkgrm `cat /tmp/list.breg /tmp/list.brg`

4. Uninstall the SUNWbrg, SUNWdc, and SUNWbreg packages.

   # pkgrm SUNWbrg SUNWdc SUNWbreg

5. Copy the SUNWbrg package and the localization packages that you need from the distribution media, such as CD or DVD.

   ---

   Note –

   The localization packages that you need are listed in the /tmp/list.brg file.

   ---

   # cd distribution-media # cd Solaris_10/Product # cp -rp SUNWbrg `cat /tmp/list.brg` /tmp

6. Install the SUNWbrg and localization packages.

   # pkgadd -d /tmp SUNWbrg

   If the /tmp/list.brg file is not empty, install the localization packages.

   # pkgadd -d /tmp `cat /tmp/list.brg`

x86: Upgrade Option Is Not Available When Upgrading to Solaris Express 3/06 OS (6386504)

The upgrade operation fails when upgrading the OS to the Solaris Express 3/06 OS as follows:

• For the Solaris installation program, the upgrade option is unavailable.

• For the custom JumpStart program, the upgrade fails.

This problem is due to an unused boot partition that must deleted.

The problem occurs under the following circumstances:

• You have performed an initial installation from the Solaris 8, 9, or 10 3/05 release. An x86 boot partition was created during installation.

• You have performed an initial installation from the Solaris 10 1/06 release or Solaris Express release that supports GRUB. The x86 boot partition is preserved, but is not used.

• You try to upgrade to the Solaris Express 3/06 OS.

The following error will be in /tmp/install_log:

# more /tmp/install_log
kdmconfig: The following warning was noted:
Error while executing loadkeys command.
Checking c1d0s0 for an upgradeable Solaris image.
The x86 Boot fdisk partition is missing /a/boot/solaris/bootenv.rc

Workaround:

• If you are upgrading with the Solaris installation program, delete the unused boot partition using the format or fdisk command. Repartition before you upgrade.

• If you are upgrading with JumpStart, specify the disk that contains the root (/) file system to be upgraded with the root_device keyword. For example, the profile would contain the following keywords:

  • install_type upgrade

  • root_device c1t0d0s0

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.

Locale Problem Occurs After You Upgrade a System That Contains Zones (6361672)

A locale problem occurs when you use the GUI-based installation program to upgrade a system that contains zones. After the installation, the LANG variable in the /etc/default/init file is set to null. If you issue any system command, the following error message is displayed:

couldn't set locale correctly

Workaround: As superuser, choose one of the following workarounds:

• Workaround 1: If you have already upgraded the system, manually edit the /etc/default/init file to set the correct LANG and LC_* variables. Then reboot the system.

  For more information and examples, see the locale(1) man page.

• Workaround 2: Use the text-based installation program to upgrade the system. Perform either of the following steps that is appropriate to your system:

  • For SPARC systems, use the text flag with the boot command. For example, if you are using the CD media to install the software, issue the following command:

    ok boot cdrom - text

  • For x86 systems, at the installation selection screen, select 3 Solaris Interactive Text (Desktop session).

  For more information, see the Solaris 10 Installation Guides.

x86: Adding Driver Updates Might Cause Failure of Network Configuration (6353146)

Installation of the Solaris 10 OS might fail while you are adding Driver Updates (DU), which are also known as Install Time Updates (ITU). This error occurs if you are using the GUI to install the Solaris 10 software. The following message is displayed:

Unable to run cmd: /usr/sbin/sysidput

Workaround: Use either of the following workarounds.

• Workaround 1: Configure the installation to use DHCP to gather network configuration information.

• Workaround 2: Use a text-based installation method.

  • If you are performing the text-based installation in a desktop session, follow these steps.

    1. After you have finished adding ITUs, type Ctrl-c instead of typing e.

    2. Choose option 3.

  • If you specify a serial console to use during the installation, follow these steps.

    1. After you have finished adding ITUs, type Ctrl-c instead of typing e.

    2. Choose option 4.

x86: Cannot Delete the Solaris Live Upgrade Boot Environment That Contains the GRand Unified Bootloader Menu (6341350)

When you use Solaris Live Upgrade to create boot environments, one of the boot environments in the system hosts the GRand Unified Bootloader (GRUB) menu. This boot environment cannot be removed with the ludelete command.

If you attempt to remove the boot environment, the following error message is displayed:

ERROR: The boot environment name-of-boot-environment contains the GRUB menu.
ERROR: You are not allowed to delete this BE.
Unable to delete boot environment.

Workaround: Use either the lumake command or the luupgrade command to reuse this boot environment. Make the boot environment that contains the GRUB menu the last boot environment to be deleted.

Solaris Live Upgrade does not allow the last boot environment to be deleted. Nor can the boot environment that contains the GRUB menu be deleted. Therefore, if the last boot environment also contains the GRUB menu, then you can delete all other boot environments if needed.

x86: Removal of Agilent Fibre Channel HBA Driver Package Fails When Upgrading to Solaris 10 1/06 Release (6330840)

If you use Solaris Live Upgrade to upgrade from the Solaris 8 2/02 release to the Solaris 10 1/06 release, the removal of the Agilent Fibre Channel HBA Driver Package (HPFC) fails. The following error message is recorded in the upgrade_log file.

Removing package HPFC:
Modifying /a/kernel/drv/sd.conf
cmdexec: ERROR: unable to open
/a/var/sadm/pkg/HPFC/save/sed/kernel/drv/sd.conf
pkgrm: ERROR: class action script did not complete successfully

Removal of partially failed.
pkgrm return code = 2

The upgrade succeeds, but two instances of the HPFC package 
are included on the system.

Workaround: Follow these steps.

1. Become superuser.

2. Remove both instances of the HPFC package.

   # pkgrm HPFC # pkgrm HPFC.2

3. Insert the Solaris 10 1/06 OS DVD in the DVD-ROM drive.

4. Change directories to the directory that contains the HPFC package.

   # cd /cdrom/Solaris_10/Product

5. Add the HPFC package to the system.

   # pkgadd -d `pwd` HPFC

Solaris Live Upgrade luupgrade Command Missing the Progress Bar (6239850)

The upgrade progress bar does not appear when you use the Solaris Live Upgrade software in the following manner:

• You use the Solaris 10 1/06 CD media to upgrade the OS.

• You upgrade a boot environment by using the luupgrade command with the following options:

  • -i to install from the CD media

  • -O “-nodisplay -noconsole” to run the installer on the second CD in text mode and without user interaction

• You are upgrading to the Solaris 10 1/06 software from the following releases:

  • Solaris 8 release

  • Solaris 9 release

  • Solaris 10 release

For example, if you run the following command, the progress bar should be displayed after you see the following output:

Running installer on BE s10u1.

However, the bar fails to appear.

# luupgrade -i -n s10u1 -s /net/installsrv/export/s10u1
 -O "-nodisplay -noconsole"


Validating the contents of the media /net/installsvr/export/s10u1.
The media is a standard Solaris media.
The media contains a standard Solaris installer.
The media contains Solaris 3 version 10.
Mounting BE s10u1.
Running installer on BE s10u1.

No error message is displayed.

Workaround: Use the prstat command. This command enables you to watch the progress while packages are being added during the installation.

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.

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^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 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.

Additional Installation Issues

This section describes issues that are related to the installation of the Solaris OS.

Patchadd Fails When Installing Patches From the UpgradePatches Directory (6241052)

If you use the patchadd command to install patches that are in the DVD media UpgradePatches directory, patchadd fails. These patches are used for the standard upgrade process and should not be used with any patch installation program.

No error message is displayed.

smosservice add Command Does Not Install Designated ARCH=all Packages (4871256)

The smosservice add command does not install any packages that are designated ARCH=all in the root (/) or /usr file systems. There is no error message indicating these packages were skipped. This problem exists in all Solaris OS versions, and applies to both SPARC® based and x86 based clients.

Note that the list of missing packages varies, depending on the Solaris release that you are running.

Workaround: Locate and install the missing ARCH=all packages.

For step-by-step instructions on locating and installing missing packages, see How to Locate and Install Missing ARCH=all Packages in System Administration Guide: Basic Administration.

StarOffice Patch Application Requires Additional Steps

The following patches are applied to the Solaris OS to resolve StarOffice^TM problems that were reported in CR 6234855 and CR 6262830:

• For SPARC based systems

  • Patch ID 119412-06

  • Patch ID 119906-03

• For x86 based systems:

  • Patch ID 119413-06

  • Patch ID 119907-03

To completely resolve the reported problems, perform the following steps after applying the patches. These steps enable you to use StarOffice 7 Product 5 software to open, for example, those OpenDocument files that were created in StarOffice 8 software.

1. Become superuser.

2. Issue the following command:

   # update-mime-database /usr/share/mime

3. Log out of the system and then log in again.

StarOffice and StarSuite Software Cannot Coexist in the Same System

When you install Solaris 10 OS, either the StarOffice or the StarSuite^TM software is also automatically installed, depending on which language you select. The languages and the corresponding software that these languages support are listed as follows:

StarOffice and StarSuite cannot coexist in the same system. If you want to replace a software that you accidentally installed, follow these steps.

1. Insert the Solaris 10 Software - 3 CD or Solaris 10 Operating System DVD in the drive.

2. Become superuser.

3. Change to the Product directory, for example, /cdrom/cdrom0/Solaris_10/Product.

4. Replace the software.

   • To replace StarOffice with StarSuite, use the following commands:

     # pkgrm SUNWsogm SUNWsom # pkgadd -d . SUNWsoagm SUNWsoam

   • To replace StarSuite with StarOffice, use the following commands:

     # pkgrm SUNWsoagm SUNWsoam # pkgadd -d . SUNWsogm SUNWsom

Cannot Install Documentation Packages With Names Longer Than Nine Characters on Documentation Servers Running Solaris 7 or Solaris 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.

Workaround: For instructions on how to install these patches, see the Solaris Documentation Important Information file on Solaris 10 OS Documentation DVD. This file is located in the following directory:

mount-point/README/locale/install_
locale.html

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 10 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.

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 10 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.