Solaris 7 3/99 Release Notes (Intel Platform Edition)

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 DiskSuiteTM 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

An upgrade to TotalNET Advanced Server (SunLinkTM) 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

Caution - Caution -

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

DiskSuite May Cause Data Loss (4121281)

If you are running DiskSuiteTM 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:

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

JumpStart Installs on Wrong Default Boot Disk (4027156)

JumpStart does not install the default boot on the current default boot disk under some conditions. A condition under which the problem has been observed involves using a fully automated install on a SPARCstationTM 5 with two hard disk drives. Therefore, the previous version of the Solaris operating environment is booted instead of the current one when you reboot.

Workaround: Install the Solaris operating environment without JumpStart.

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 3/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: 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.

elxl: elx: After Upgrading, the Ethernet Controller Does Not Work (4193228)

After upgrading an x86 machine with the Etherlink XL Ethernet chip to the Solaris 7 3/99 operating environment, the machine may lose network connectivity and display the following error message when booting:

configuring network interfaces: elxl0: No such device or address

Workaround: Remove the following duplicate entries from the /etc/driver_aliases file:

elx "pci10b7,9000"elx "pci10b7,9050"