System Administration Bugs

sd Driver May Not Detect New fdisk Partition Table Information (4304790)

If you attempt to reformat a Zip or Jaz disk and change the disk file system from a PC file system (like PCFS) to a UNIX file system (like UFS or UDFS), you may receive the following error message:

No Solaris Partition, eject and retry: I/O Error

Workaround: If you receive the error message listed above, follow these steps to resynchronize the sd driver with the disk contents:

1. Manually eject the Zip or Jaz disk from the drive.

2. Reinsert the Zip or Jaz disk into the drive.

3. Format the Zip or Jaz disk, using the same format command you used previously to format the disk.

CIM_ERR_LOW_ON_MEMORY Error Occurs When Trying to Add Data With WBEM (4312409)

The following error message is displayed when memory is low:

CIM_ERR_LOW_ON_MEMORY

Workaround: To reset the CIM Object Manager Repository:

1. Become superuser.

2. Stop the CIM Object Manager.

   # /etc/init.d/init.wbem stop

3. Remove the JavaSpaces log directory.

   # /bin/rm -rf /var/sadm/wbem/log

4. Restart the CIM Object Manager.

   # /etc/init.d/init.wbem start

   ---

   Note -

   You will lose any proprietary definitions in your datastore. You must recompile the MOF files that contain those definitions using the mofcomp command. For example:

   # /usr/sadm/bin/mofcomp -u root -p root_password your_mof_file

   ---

WBEM Common Information Model Object Manager Crashes When Solaris_FileSystem Instances Are Requested (4301275)

If you enumerate instances of the Solaris_FileSystem class by using CIM WorkShop or the WBEM APIs, then the CIMOM no longer runs and the following error message is displayed:

Attempted to complete RMI action
enumInstances and received exception 
java.rmi.UnmarshalException: Error 
unmarshaling return header; nested 
exception is:
java.io.EOFException

Workaround: In superuser mode, restart the CIMOM by typing the following command:

# /etc/init.d/init.wbem start