Chapter 1 Installation Issues

This chapter describes problems relating to the installation of the Solaris 7 5/99 software environment.

The information in this chapter supersedes any information listed in the installation_bugs file that is part of the SUNWrdm package on the Solaris 7 5/99 CD. If you boot from the Solaris 7 5/99 CD, the installation_bugs file is located in the directory:

/cdrom/sol_7_599_sparc/s0/Solaris_2.7/Docs/release_info/C

The default installed location for the installation_bugs file is located in the directory:

/usr/share/release_info/Solaris_2.7/C

The name of this product is Solaris 7 5/99, but code and path or package path names may use Solaris 2.7 or SunOS 5.7. Always follow the code or path as it is written.

READ THIS FIRST

Remote Login From dtgreet Freezes Local Window System (4213502)

If you select Remote Login from the main CDE login menu by clicking the Options button, a login to another host system occurs. When you terminate the remote login session and return to the original system, the screen freezes. To start another CDE session on a hung screen, log in remotely to the system and kill the hung DT session.

Workaround: Apply patch ID 107180-05 or later to prevent this problem. This patch is available through approved Sun support channels.

Solaris Web Start Issues

This section only describes known installation issues 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.

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:

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

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

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

Solaris 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 copackaged software.

Cannot Move the Root File System (4046659)

You can choose a system disk in Solaris Web Start but you cannot move the root file system off the system disk afterwards.

Workaround: 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.

Interactive Installation Issues

New JumpStart Behavior

When you turn on a system with the JumpStart^TM software already installed (this includes new systems and preinstalled systems on which another installation has been performed) in the Solaris 7 as well as 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 as well as 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. Your desktop is displayed upon authentication of your login name and password. For more information about the login screen, see the dtlogin man page (provided with the Solaris Common Desktop Environment (CDE) man pages) or the Common Desktop Environment: Advanced User's and System Administrator's Guide.

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 dtconfig man pages.

Interactive Installation Bugs

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.

TotalNET Advanced Server (SunLink) 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 Bugs That Occur During an Interactive 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

Installation Progress Bar May Be Inaccurate (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 the dfstab File on a 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 Solstice AutoClient, back up the /etc/dfs/dfstab file for the clients.

Installation Bugs That May Occur During 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: 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.

Clients Do Not Receive All Patches When a Server Is Upgraded (4175220)

Patches located in the Patches directory on the Solaris 7 5/99 CD are not automatically applied to clients whenever a server is upgraded.

Workaround: Apply the patches located in the Patches directory to clients after the upgrade has been completed.

SUNWcvc.u and SUNWdrr.u Packages Are Missing If You Upgrade From the Solaris 2.6 Hardware 3/98 or Solaris 2.6 5/98 Operating Environment to the Solaris 7 Operating Environment (4229675)

After you upgrade from the Solaris 2.6 Hardware 3/98 or the Solaris 2.6 5/98 operating environment and if your systems have sun4u diskless clients or Solstice AutoClients, then the SUNWcvc.u and SUNWdrr.u packages are not installed on diskless or Solstice AutoClients.

Workaround: After you have completed an upgrade, add the SUNWcvc.u and SUNWdrr.u packages to a sun4u diskless client or Solstice AutoClient as follows with a client called foo:

1. Mount the Solaris 7 5/99 CD for the SPARC platform.

2. Change to the following directory:

   # cd /cdrom/cdrom0/s0/Solaris_2.7/Product

3. Add the following packages using the pkgadd command:

   # pkgadd -R /export/root/foo -d `pwd` SUNWcvc.u

Errors May Occur When Applying the European Locale Updates Patch During an Upgrade (4230247)

If you applied any of the European locale update patches, 106857-04, 106931-04, 107616-01, or 107617-01, and then upgraded your system, the following errors are then reported in the upgrade logs:

Doing pkgadd of SUNWplow to /.
pkgadd: ERROR: unable to create package object </a/usr/openwin/share/locale/de.ISO8859-15>.
    file type <s> expected <d> actual
    unable to remove existing directory at </a/usr/openwin/share/locale/de.ISO8859-15>
....
Installation of <SUNWplow> partially failed.
pkgadd return code = 2


Doing pkgadd of SUNWpldte to /.
WARNING: /a/usr/dt/appconfig/types/de.ISO8859-15 
may not overwrite a populated directory.
......
pkgadd: ERROR: /a/usr/dt/appconfig/types/de.ISO8859-15 could not be installed.
.......
Installation of <SUNWpldte> partially failed.
pkgadd return code = 2

This warning occurs because the patch switches the affected directories listed in the upgrade logs from symbolic links to directories. The upgrade process then attempts to install an updated version of the package that does not include the change. These errors do not affect the operating environment on your system.

Workaround: Ignore these error messages.

Solaris Installation Bugs

Warnings May Occur When Creating a File System (4189127)

One of the following error messages may be displayed when creating a file system during installation:

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 being created does not map exactly to the space on the disk being used. This 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 error message.

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 5/99 operating environment, the Web Start installer installs the End User metacluster. For Server editions of the Solaris 7 5/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.

System Administration Installation Bugs

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.

User Disabling of Daemons and Servers in inetd.conf Overridden by Package Instance (4220923)

The interactive installation program adds lines for the KCMS Profile Server, Font Server, CacheFS Daemon, and Kerbd Daemon even though they already exist and are commented out in /etc/inetd.conf.

Workaround: The unnecessary entries in /etc/inetd.conf can be deleted or commented out with a text editor.

64-Bit Solaris Issues

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

Sun UltraSPARC System (sun4u) May Need Flash PROM (Open Boot) Upgrade

If you want to run the 64-bit Solaris operating environment on an UltraSPARC system, you may need to upgrade its Flash PROM firmware. The Solaris 7 installation programs have a new check box 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 Flash PROM upgrade is not needed.

The following table lists the UltraSPARC (sun4u) systems that are affected and the minimum firmware versions needed. If the system is not listed in the table, it does not need a Boot PROM upgrade. Use uname -i to check the system type. Use prtconf -V to identify the firmware version.

For instructions on performing the Flash PROM update using the Solaris CD, refer to the Solaris 7 Sun Hardware Platform Guide. If you do not have this manual, it can be obtained at http://docs.sun.com.

AnswerBook2 Documentation Bug

ab2cd -s Does Not Add Locally-Installed Document Collections to the Server (4208243)

When running the AnswerBook2 server from the CD, the command ab2cd -s causes any locally-installed document collections to be added to the server database. However, it does not find any local document collections.

Workaround: If you have locally-installed document collections, install the AnswerBook2 server software. Do not run the server from the CD.