System Administration

This section describes system administration bugs in the Oracle Solaris 10 OS.

The Availability Suite Module sdbc Fails to Load During Boot (6952222)

In this release, the sdbc module fails to load during boot and gives the following error message:

[ID 819705 kern.notice]/usr/kernel/drv/sparcv9/sdbc: undefined symbol
WARNING: mod_load: cannot load module 'sdbc'

Workaround: Install patch 123246–07 for SPARC systems and patch 123247–07 for x86 systems.

Oracle Solaris 10 9/10 Clock Stops on Oracle VM 2.2 (6952499)

Virtual machines (VMs) that are running Oracle Solaris 10 9/10 guests can be subject to the following problems:

• The time of day clock can stop moving forward.

• Sleep can hang.

• The guest VM can hang entirely.

Workaround: The workaround is to require Oracle Solaris guests to be pinned to physical CPUs. Pin the domain's virtual CPUs to the host's physical CPUs as follows:

# xm vcpu-pin domain vcpu cpus

See the xm(1) man page for more information.

SPARC: FKU 137137-xx Patch Does Not Support Third-Party Volume Manager Software

The FKU 137137-xx patch does not support third-party Volume Manager software, with some exceptions. This lack of support is due to prepatch, postpatch, and postbackout implementation. If you use unsupported third-party Volume Manager software, you cannot apply the FKU patch. The following error message is displayed during patch installation:

unsupported root slice type xxxxx

However, the Fujitsu and Veritas Volume Manager software is supported.

Workaround: None.

Solaris 10 10/09 DVD Media Might Not Be Automatically Mounted by vold (6712352)

The Solaris 10 10/09 DVD does not mount by default during runtime. No error message is displayed.

Workaround: Perform the following steps:

1. Become superuser.

2. Disable vold:

   • On Oracle Solaris 10 Systems:

     # svcadm disable -t volfs

   • On Solaris 8 and Solaris 9 systems:

     /etc/init.d/volmgt stop

3. Mount the media manually by using the # mount -F hsfs path to block device path to mount point command. For example:

   # mount -F hsfs /dev/rdsk/c0t2d0s2 /mnt

Oracle Solaris Is Unable to Handle Mode Switches Between Legacy and AHCI Modes for the SATA Controller (6520224)

In systems which have an AHCI compliant SATA controller, the BIOS setup typically enables the controller to be set in either AHCI, legacy, or RAID modes. Oracle Solaris OS supports AHCI and legacy modes.

The SATA mode setting in BIOS must not be changed after an initial Oracle Solaris installation. The SATA mode setting must also not be changed before or after an Oracle Solaris upgrade. If the SATA mode BIOS setting is modified after installing Oracle Solaris 10, the system will reset and fail to boot without indicating what led to the failure.

Workaround: If boot failure is encountered as a result of changing the BIOS setting, revert back to the original setting in order to boot the Oracle Solaris OS.

32-bit: Possible Error With Applications When Obtaining the File System State on Large File Systems (6468905)

When run on large file systems, for example ZFS, applications using statvfs(2) or statfs(2) to get information about the state of the file system exhibit an error. The following error message is displayed:

Value too large for defined data type

Workaround: Applications should use statvfs64() instead.

Using patchadd Command With the -R Option to Specify an Alternative Root Path From Systems That Are Not Zones Aware Should Be Restricted (6464969)

On systems running an Oracle Solaris release that is not zones aware, using patchadd -R, or any command that accepts the -R option to specify an alternate root path for a global zone that has non-global zones installed, will not work.

In contrast with the error message that is displayed by using the luupgrade [-t, -T, -p, -P] command, no error message regarding the use of appropriate command-level restrictions is displayed in this instance.

There is no indication that the -R option did not work. As a result of the failure of the command, Oracle Solaris 10 packages or patches are not installed on any of the installed non-global zones.

This problem occurs while installing and uninstalling packages or patches.

For more information, see the following man pages :

• patchadd(1M)

• patchrm(1M)

• pkgadd(1M)

• pkgrm(1M)

Workaround 1: Upgrade the OS to at least the Solaris 10 1/06 release.

If you are running the Solaris 10 3/05 release, install the following patches to enable the use of commands that accept the -R option to create an alternate root path:

• Patch ID 119254-19 for SPARC based systems

• Patch ID 119255-19 for x86 based systems

Workaround 2: Restrict the use of the patchadd -R command or any command that accepts the -R option to create an alternate root path.

Instead, boot the alternate root, for example, the Oracle Solaris 10 release, as the active OS. Then install and uninstall the Oracle Solaris 10 packages and patches without using the -R option.

Sun Patch Manager Tool 2.0 Incompatible With Previous Versions of the Tool

A system that runs the Sun Patch Manager Tool 2.0 can manage remote systems that run Patch Manager Tool, including Sun Patch Manager Tool 1.0.

However, a system with an earlier version of Patch Manager Tool cannot manage remote systems that run Patch Manager Tool 2.0. Earlier versions include the following:

• Sun Patch Manager Base Software 1.x

• Sun Patch Manager Tool 1.0

Cannot Delete Existing Diskless Clients From the System (6205746)

If you use the smdiskless command to delete a diskless client, the command fails. The diskless client is not removed from the system databases. The following error message is displayed:

Failing with error EXM_BMS.

Workaround: Unshare the /export partition before adding the client.

SPARC: smosservice delete Command Does Not Successfully Remove All Service Directories (6192105)

If you use the smosservice delete command to remove a diskless client service, the command does not successfully remove all the service directories.

Workaround: Follow these steps.

1. Make sure that no clients exist that use the service.

   # unshare /export/exec/Solaris_10_sparc.all
   # rm -rf /export/exec/Solaris_10_sparc.all
   # rm -rf /export/exec/.copyofSolaris_10_sparc.all
   # rm -rf /export/.copyofSolaris_10
   # rm -rf /export/Solaris_10
   # rm -rf /export/share
   # rm -rf /export/root/templates/Solaris_10
   # rm -rf /export/root/clone/Solaris_10
   # rm -rf /tftpboot/inetboot.sun4u.Solaris_10

2. Remove the following entry from the /etc/bootparams file.

   fs1-24 boottype=:os

   ---

   Note - Remove this entry only if this file server does not provide functions or resources for any other services.

   ---

3. Remove the following entry from the /etc/dfs/dfstab file.

   share -F nfs -o ro /export/exec/Solaris_8_sparc.all/usr

4. Modify the /var/sadm/system/admin/services/Solaris_10 file.

   • If the file server is not Oracle Solaris 10, delete the file.

   • If the file server is Oracle Solaris 10, remove all entries after the first three lines. The deleted lines indicate the service USR_PATH and SPOOLED ROOT packages in /export/root/templates/Solaris_10 and the supported platforms.