Chapter 1 Installation Bugs

Solaris Web Start Issues

SPARC^TM only: Limited Browser Support in Client-Server Mode

To use the client-server mode of Solaris Web Start, you must have one of the following software configurations installed on the client:

• Solaris 2.6 or Solaris 7 with its accompanying version of the HotJava^TM or Netscape Navigator^TM 4.0, or Netscape Navigator^TM 4.5 browser

• Windows 95 with the HotJava or Netscape Navigator 4.0 browser, or Netscape Navigator 4.5 browser

Solaris Web Start may not run or display properly with older versions of HotJava, older versions of Navigator, or with Internet Explorer.

Solaris^TM Web Start Bugs

This section only describes known installation bugs that may occur when using Solaris Web Start, the browser-based program that enables you to install both the Solaris software and co-packaged software. These problems do not occur when using the Solaris Interactive Installation program.

x86 only: Cannot Move the Root File System (4046659)

You choose a system disk in Solaris Web Start, but you cannot move the root file system off the system disk afterwards. If you need to do this, use the Solaris Interactive Installation program instead of Solaris Web Start.

Products May Not Use All Reserved Space (4059182)

Solaris Web Start reserves disk space based on the total requirements of all the products that you install. If you check disk space allocation after installing but before using the products, you may find a substantial amount of apparently unused space. Some of this space may be taken up when you run the software; some of it may remain unused.

Workaround: If you want to allocate less total disk space than Solaris Web Start requires, use the Solaris Interactive Installation program instead.

x86 only: The Root '/' File Sytem Extends Beyond HBA Cylinder 1023 (4062008)

If a manual file system layout is used in Solaris Web Start, an error message may display after the start of an installation because too much space has been allocated in the root (/) file system.

Workaround: Restart Solaris Web Start and use Automatic File System Layout.

Installation Issues

SPARC only: New JumpStart^TM Behavior

When you turn on a system with the JumpStart software already installed (this includes new systems and preinstalled systems that have been installed again) in the Solaris 7 or the Solaris 2.6 operating environments, Solaris Web Start's introductory screen is displayed. You can now exit Solaris Web Start and perform a JumpStart installation.

Solaris dtlogin Screen

The Solaris 7 and the Solaris 2.6 operating environments default to a login screen when you initially boot your workstation regardless of which desktop you are using. You can select your desktop from the login screen. The login screen requires the user's name and password.

Upon authentication of your name and password, your desktop displays. For more information about the login screen, see the DtLogin man page (provided with the Solaris CDE man pages) or the Solaris Common Desktop Environment: Advanced User's and System Administrator's Guide (provided with the AnswerBook2 documentation CD-ROM).

dtlogin Notes for System Administrators

A System Administrator who is new to CDE needs to know about CDE's graphical login program (dtlogin). Review the Solaris Common Desktop Environment: Advanced User's and System Administrator's Guide or the dtlogin and dtconfig man pages.

Interactive Installation Bugs

Before Installation

Not All Locales Supported Outside of Entire Metacluster (4181942)

All locales are supported only in the Entire Distribution and Entire Distribution plus OEM metaclusters. Subsets of these locales are supported in the Developer, End User, and Core metaclusters.

If you select a locale at the beginning of the installation that is not supported by the metacluster that you choose to install later in the installation on the metacluster selection screen, the following occur:

• Web Start installation of co-packaged products fails without installing the co-packaged products.

• You cannot open terminal windows in CDE.

For Desktop editions of the Solaris 7 3/99 operating environment, the Web Start installer installs the End User metacluster. For Server editions of the Solaris 7 3/99 operating environment, Web Start installs the Entire metacluster. You can change the defaults by selecting a Custom installation.

The following is the list of locales supported by each metacluster:

Workaround: To prevent the problem, install the metacluster that contains the desired locale.

To repair an existing installation, in the /etc/default/init file change the references to the unsupported locale to reference a supported locale for the installed metacluster.

x86 only: DiskSuite^TM May Cause Data Loss (4121281)

Be sure to read bug description ID 4121281 before you start upgrading your x86 system to the Solaris 7 operating environment.

The DiskSuite metadb replicas contain driver names as part of the DiskSuite configuration data. In x86-based systems that run versions 2.4, 2.5, 2.5.1, and 2.6 of the Solaris operating environment, the SCSI driver name is called cmdk. The cmdk driver has been replaced by the sd driver in the Solaris 7 operating environment for x86 systems.

Workaround: To avoid potential data loss during upgrades to the Solaris 7 operating environment, you must save the system's metadevice configurations in text files and remove their metadb replicas before upgrading any x86 system that is running DiskSuite. After you finish upgrading your x86 system, you must restore the metadevice configurations by using the DiskSuite command line interface.

The DiskSuite Version 4.2 Release Notes contain a procedure for saving metadb configurations, removing metadb replicas, upgrading x86 systems to the Solaris 7 operating environment, upgrading DiskSuite to version 4.2, and restoring metadevice configurations. Bourne shell scripts that automate the procedure will be available for the FCS version of the Solaris 7 operating environment.

During Installation

The following bugs only occur during an installation.

Erroneous Messages Indicating Packages Added A Second Time (1235464)

This appears as an attempt to install the same architecture and version of a package that is already installed. This installation overwrites this package.

When upgrading a system with the "Entire Distribution plus OEM Cluster," the following packages seem to be added twice:

• SUNWolinc

• SUNWxwdim

• SUNWxwinc

• SUNWxwman

• SUNWxwpmn

• SUNWxwsrc

• SUNWolbk

• SUNWoldim

• SUNWolman

• SUNWolsrc

Workaround: If you try to add a package that has already been installed on a system, the installed package is overwritten.

Installation Progress Bar May be Inaacurate (1266156)

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

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

Installation complete

Installation of Diskless Client Does Not Preserve Changes in dfstab File on Server (4045544)

When you upgrade the Solaris operating environment on a server with diskless clients, the options on the dfstab line are not preserved for /usr. For example, if you entered the following in the dfstab file,

share -F nfs -o rw /export/exec/Solaris_2.7_sparc.all/usr

then this entry is automatically replaced with the following entry during the upgrade:

share -F nfs -o ro /export/exec/Solaris_2.7_sparc.all/usr

Workaround: Before you attempt to upgrade the Solaris operating environment on an OS server that has a diskless client or AutoClient, back up the /etc/dfs/dfstab file for the clients.

TotalNET Advanced Server (SunLink^TM) Drivers Cause Panic After A Reboot (4121961)

 Warning:  mod_install: MT-unsafe driver 'tnatp' rejected panic[cpu0] /
thread=7051e040:mutex-enter:bad_mutex lp=1046aa20 owner=7051e040
thread=7051e040    

An upgrade to TotalNET Advanced Server (SunLink^TM) version 5.2 is required with the Solaris 7 operating environment because of a driver conflict. Version 5.0 and version 5.1 for the TotalNET Advanced Server cause the Solaris 7 operating environment to not boot correctly.

Workaround: Before you install the Solaris 7 operating environment, you must upgrade all installations to version 5.2 for the TotalNET Advanced Server, which is available on the Solaris Easy Access Server 2.0 CD. Follow the instructions provided to upgrade existing TotalNET Advanced Server installations.

Installation Fails With a False Non-Mountable File System Error (4164303)

The following message may be displayed:

The Solaris operating environment on slice c0t0d0s0 cannot be upgraded.A file system listed in the file system table (vfstab) could not be mounted.

The installation software may interpret inodes that are stored on striped DiskSuite^TM meta devices for root inodes and attempt to mount the meta devices as upgradable slices. When this problem occurs, the mounts fail and the installation aborts.

Installation Bugs Before the Start of an Upgrade

Be sure to read bug description ID 4121281 before you start upgrading your x86 system to the Solaris 7 operating environment. This bug is described in the section called "Before Installation" earlier in this file. This problem may cause data loss.

Installation Bugs That May Occur During an Upgrade

All bugs described in this section only occur if you perform an upgrade.

Multiple Architecture Server Cannot Be Patched (1249343)

After upgrading a server with diskless clients of more than one SPARC kernel architecture, such as a sun4u server with diskless sun4c, sun4d, and sun4m clients, the SUNWkvm packages for clients whose kernel architectures differ from that of the server cannot be patched.

Workaround: Manually add all of the SUNWkvm packages before applying any patches that affect them.

# pkgadd -d  SUNWkvm.*

Disk Space Requirements can be Exaggerated by the Upgrade Process (4041733)

The upgrade program can exaggerate by as much as 30 percent the amount of space required for upgrades to systems with the Solaris software. Therefore, it prevents many systems from being upgraded without deselecting packages or finding more space.

Workaround: You can manually reallocate disk space among file systems or use the Software Customization menu to remove software packages that are not needed.

sun4m Solstice AutoClients Fail to Mount Cache After an Upgrade From the Solaris 2.6 Hardware: 3/98 Release (4121951)

The Solstice AutoClients display the following message when rebooting:

fsck -F cachefs: Cache directory /.cache/rootcache does not exist.mount -F cachefs: cache fsck mount failedfsck -F cachefs: Cache directory /.cache/rootcache does not exist.mount -F cachefs: cache fsck mount failed

This directive indicates to the kernel that the root file system is of type cachefs. To determine whether or not a specific Solstice AutoClient can be affected by this problem before you attempt an upgrade, examine the directory /export/root/client-name/var/sadm/pkg on the server (this is the Solstice AutoClient's /var/sadm/pkg directory). If this directory contains a subdirectory called TADcar, the Solstice AutoClients may be affected.

Workaround: Edit the /etc/system file for the Solstice AutoClients after the upgrade by appending the following line:

rootfs:cachefs

The Solstice AutoClients' /etc/system file is stored on the server as /etc/root/client-name/etc/system.

Addition of Solaris 7 Service to an OS Server Results in an Upgrade Failure Message (4171470)

When the Solaris 7 system software is added to an OS server as a service, the following error message is displayed:

celebris:  Error:  Error adding OS service Solaris 2.7 i386 i86pc: 
service modification failed.
See /var/sadm/system/logs/upgrade_log for more information
(/var/sadm/install_data/upgrade_log on Solaris 2.3 or 2.4).

Where celebris is the name of the OS server.

If you review the indicated log file, you will see that the addition of the SUNWplow package failed with the following message:

Doing pkgadd of SUNWplow to /.
ERROR: attribute verification of <export/exec/Solaris_2.7_i386.all/etc/default/init> failed
pathname does not exist

Workaround: Ignore the error message.

64-Bit Solaris Issues

This section describes installation-related 64-bit Solaris issues.

SPARC only: Sun UltraSPARC^TM System (sun4u) May Need Boot PROM Upgrade

If you want to run the 64-bit Solaris operating environment on an UltraSPARC system, you may need to upgrade its Open Boot PROM firmware. The Solaris 7 installation programs have a new checkbox for adding 64-bit support. This new 64-bit support is selected by default when installing on Sun UltraSPARC systems.

If you choose to run the 32-bit Solaris operating environment on any Sun or UltraSPARC system, the Open Boot PROM upgrade is not needed.

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

If the system is not listed in the above table, it may not need a Boot PROM upgrade.

To upgrade your UltraSPARC system's Open Boot PROM, contact the Sun representative from whom you received this kit and request the sun4u Open Boot PROM upgrade kit.

Sun Microsystems, Inc. kits already include the Boot PROM upgrade components.