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.* |
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.
SolsticeTM AutoClientTM systems 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 system 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 system's /var/sadm/pkg directory). If this directory contains a subdirectory called TADcar, the Solstice AutoClient system may be affected.
Workaround: Edit the /etc/system file for the Solstice AutoClient systems after the upgrade by appending the following line:
rootfs:cachefs |
The Solstice AutoClient systems' /etc/system file is stored on the server as /etc/root/client-name/etc/system.
Patches located in the Patches directory on the Solaris 7 11/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.
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 AutoClient systems, then the SUNWcvc.u and SUNWdrr.u packages are not installed on diskless clients or Solstice AutoClient systems.
Workaround: After you have completed an upgrade, add the SUNWcvc.u and SUNWdrr.u packages to a sun4u diskless client or Solstice AutoClient system as follows with a client called foo:
Mount the Solaris 7 11/99 CD for the SPARC platform.
Change to the following directory:
# cd /cdrom/sol_7_1199_sparc/s0/Solaris_2.7/Product |
Add the following packages using the pkgadd command:
# pkgadd -R /export/root/foo -d `pwd` SUNWcvc.u # pkgadd -R /export/root/foo -d `pwd` SUNWdrr.u |
After upgrading from the Solaris 7 3/99, 5/99, or operating environments to the Solaris 7 11/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.
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:
Remove the SUNWjvdev and SUNWjvrt packages.
# pkgrm SUNWjvdev SUNWjvrt |
Re-install the SUNWjvrt and SUNWjvdev packages.
# pkgadd -d /cdrom/sol_7_1199_sparc/s0/Solaris_2.7/Product SUNWjvrt SUNWjvdev |
If your Solaris 7 11/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.