Chapter 1 Installation Issues

This chapter describes problems relating to the installation of the Solaris 7 8/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 8/99 CD. If you boot from the Solaris 7 8/99 CD, the installation_bugs file is located in the directory:

/cdrom/sol_7_899_x86/s2/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 8/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.

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.

The Root (/) File System 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 the Automatic File System Layout.

Installing With Solaris Web Start in Client/Server Mode May Produce Exception Messages in the HotJava Console Window (4248436)

When installing with Solaris Web Start in client/server mode, you may see the following exception messages in the HotJava console window:

sun.applet.AppletSecurityException: checkaccess.thread
		at java.lang.Throwable.<init>(Compiled Code)
		at java.lang.Exception.<init>(Compiled Code)
		at java.lang.RuntimeException.<init>(Compiled Code)
		at java.lang.SecurityException.<init>(Compiled Code)
		at	 sun.applet.AppletSecurityException.<init>(Compiled Code)
		at sun.hotjava.security.PolicyUntrusted.checkAccess(Compiled Code)
		at sun.hotjava.security.HotjavaSecurity.checkAccess(Compiled Code)
		at java.lang.Thread.checkAccess(Compiled Code)
		at java.lang.Thread.stop(Compiled Code)
		at MouseOverPanel.handleMouseEnter(Compiled Code)
		at SolsticeConfTaskPage.handleEvent(Compiled Code)
		at java.awt.Component.postEvent(Compiled Code)
		at java.awt.Component.postEvent(Compiled Code)
		at java.awt.Component.postEvent(Compiled Code)
		at java.awt.Component.postEvent(Compiled Code)
		at java.awt.Component.postEvent(Compiled Code)
		at java.awt.Component.postEvent(Compiled Code)
		at java.awt.Component.postEvent(Compiled Code)
		at java.awt.Component.postEvent(Compiled Code)
		at java.awt.Component.dispatchEventImpl(Compiled Code)
		at java.awt.Container.dispatchEventImpl(Compiled Code)
		at java.awt.Component.dispatchEvent(Compiled Code)
		at java.awt.EventDispatchThread.run(Compiled Code)
Exception occurred during event dispatching:
sun.applet.AppletSecurityException: checkaccess.thread

When exception messages appear, mouse clicks may become slow to update and some information panels may not display properly.

Workaround: To improve the responsiveness of the mouse and complete the installation process, close the HotJava Console window. Some information panels may not update properly, but this does not affect the installation process. Web Start installs the products that you selected, however, the description may be inaccurate if you have moved the cursor over more than one product.

To prevent the exception messages, do not open the HotJava Console window before or during installation.

Interactive Installation Issues

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 Before the Start of an Interactive Installation

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

DiskSuite May Cause Data Loss (4121281)

If you are running DiskSuite^TM and upgrading to Solaris 7, you must also upgrade to DiskSuite 4.2. The DiskSuite 4.2 distribution includes a script called metacvt that automates removal and replacement of the metadb replicas. You can use that script to change the SCSI driver name stored in the replicas from cmdk to sd when you upgrade to Solaris 7 and DiskSuite 4.2.

Workaround: To avoid potential data loss during upgrades to the Solaris 7 operating environment, you must save the system's meta device configurations in text files and remove their metadb replicas before upgrading any x86 based system that is running DiskSuite. After you finish upgrading your x86 based system, you must restore the meta device 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 based systems to the Solaris 7 operating environment, upgrading DiskSuite to version 4.2, and restoring meta device configurations. Bourne shell scripts that automate the procedure are available for the Solaris 7 operating environment.

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 You Need to Know About Before the Start of an Upgrade

Be sure to read bug description ID 4121281 mentioned in"Installation Bugs That Occur Before the Start of an Interactive Installation" earlier in this chapter as well as any other bug description listed in this section before you start upgrading your x86 based system to the Solaris 7 8/99 operating environment. This problem may cause data loss.

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.

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

Patches located in the Patches directory on the Solaris 7 8/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.

Errors May Occur During A European Upgrade (4230247, 4225787)

After upgrading from the Solaris 7 3/99 or 5/99 operating environments to the Solaris 7 8/99 operating environment, the following errors may appear 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.

Upgrading With Disk Space Reallocation Removes Language Packages (4258815)

An upgrade using disk space reallocation in which the /usr partition is resized or moved causes some language packages to be removed from the system. The packages appear in the package database as installed, but the language files are not installed on the file system.

This does not occur on systems installed with only the English language.

Workaround: You may choose one of the following workarounds:

• To manually adjust file system sizes before upgrading:

  1. Back up the system.

  2. Using the format command, adjust the file system sizes according to the requirements described in the install program.

  3. Restore the system on to the new file systems.

  4. Start the upgrade. The upgrade will proceed without disk space reallocation as you have adjusted the file systems so that there is enough space to complete the upgrade.

• To install the missing packages after the upgrade is complete:

  1. Determine which packages are missing. The missing packages are those that do not appear in the do_pkgadd lines in the /var/sadm/system/admin/upgrade_script and who have non-empty lines in SUNW_LOC in their pkginfo files in the /var/sadm/pkg directory.

  2. Create an admin file as /tmp/admin with the following lines:

     instance=overwrite mail=

     For detailed instructions about creating an admin file, refer to admin(4).

  3. Install the missing packages by typing the following command for each package to install:

     # pkgadd -a /tmp/admin -d /cdrom/cdrom0/Solaris_2.7/Product package_name

     where package_name is the name of the package to install.

     ---

     Note -

     If your Solaris 7 8/99 software is mounted somewhere other than the CD-ROM drive, change the argument to the -d option to be the absolute path to the Solaris_2.7/Product directory.

     ---

Symbolic Links to SUNWjvrt Are Missing After Upgrading from Solaris 7 (4259033)

After upgrading from the Solaris 7 operating environment using disk space reallocation, the java commands may not be found due to missing symbolic links.

Workaround: To restore the symbolic links, complete these steps:

1. Remove the SUNWjvdev and SUNWjvrt packages.

   # pkgrm SUNWjvdev SUNWjvrt

2. Re-install the SUNWjvrt and SUNWjvdev packages.

   # pkgadd -d /cdrom/cdrom0/s0/Solaris_7 SUNWjvrt SUNWjvdev

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 metacluster. 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 8/99 operating environment, the Web Start installer installs the End User metacluster. For Server editions of the Solaris 7 8/99 operating environment, Web Start installs the Entire metacluster. You can change the defaults by selecting a Custom installation.

The following table indicates which locales are 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.

Font Package Warning Occurs During Installation (4226416)

The font packages listed below in the warning messages cover all language locales, including those that may not be on your Solaris CD. If you cannot find all the packages listed in the warning message, then only install those packages that you can find on your CD.

Warning!  It is strongly recommended that the following font package be 
installed for all locales:

SUNWi1of

Warning!  It is strongly recommended that the following font packages be 
installed to support locales (other than ISO8859-1 locales) as needed:

SUNWi2of SUNWi2rf SUNWi4of SUNWi4rf SUNWi5of SUNWi7of SUNWi7rf
SUNWi9of SUNWi9rf SUNWjxcft SUNWkcoft SUNWcttf SUNWhttf SUNW5xfnt

This message is only advisory and does not indicate an installation failure.

Workaround: Installation of the font packages listed in the warning message is strongly recommended.

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.

AnswerBook2 Documentation Installation Bugs

Installing SUNWab2u Before SUNWab2r and SUNWab2s Causes Problems (4230969)

Installing the SUNWab2u package before the other AnswerBook2 packages, SUNWab2r and SUNWab2s, causes the following:

• Warning messages will display during the installation

• The scan option will not find any AnswerBook1 collections

• Links between books will attempt to retrieve the book from docs.sun.com, rather than from the local server

Workaround: Use the installer (Web Start utility) or the pkgrm command to remove the SUNWab2u, SUNWab2r, and SUNWab2s packages.

To install the packages in the correct order, use the installer (Web Start utility).

If you install the packages manually using the pkgadd command, install them in the following order:

1. SUNWab2r

2. SUNWab2s

3. SUNWab2u

The fr.UTF-8 Locale Displays ab2cd Installation Messages in English (4248169)

If you are using the fr.UTF-8 french locale you will see ab2cd installation status and error messages displayed in English. This occurs because on the Solaris 7 8/99 Documentation CD, the .ab2cd_msgs/i386/fr.UTF-8/ directory was incorrectly named .ab2cd_msgs/i386/fr..UTF-8/.

Workaround: None.

Solstice AutoClient Installation Issue

The Solstice AutoClient product is not included in the SEAS 3.0 product shipped with the Solaris 7 8/99 release. If you have installed diskless clients and AutoClient systems, you can continue to use those systems. You can manage those systems using an earlier release of Solstice AdminSuite.