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.