The procedure for upgrading Solstice DiskSuiteTM is complex. You should read the entire section on upgrading before attempting to upgrade to Solstice DiskSuite 4.2.1 from an earlier version of the software.
If your system is running Solstice DiskSuite and you are upgrading your system to SolarisTM 8, you must upgrade to Solstice DiskSuite 4.2.1.
All the conversion procedures are outlined in "Converting to Solstice DiskSuite 4.2.1".
If you are using mirrored root or /usr, messages similar to the following may appear during system boot:
WARNING: forceload of misc/md_hotspares failed WARNING: forceload of misc/md_trans failed WARNING: forceload of misc/md_raid failed
These warnings are harmless, and may be ignored. They are an artifact of the way drivers are loaded during the boot process when you have a mirrored root or /usr file system.
Any bootable disk can be used for the root file system. Refer to Solstice DiskSuite 4.2.1 User's Guide for information on constructing a bootable device.
DiskSuite's diskset feature (metaset(1M)) is supported only on the SPARCTM platform edition of Solaris. This feature is not supported on x86 systems. The diskset feature is intended to be used only in conjunction with Solstice High Availability or the clustering software.
When you reboot the system after installing the DiskSuite SNMP log daemon (SUNWmdn package), the following message appears:
Starting mdlogd ... /etc/lvm/mdlogd.cf: no configuration information
DiskSuite displays this message because you have not yet configured the mdlogd.cf file.
Do not attempt to put the power supply management statefile on a metadevice. If you are using power supply management (suspend/resume), you must edit the /etc/power.conf file and change the default statefile line to locate the statefile on a bootable device which is not a metadevice.
AnswerBook2TM online documentation is now part of the DiskSuite distribution. For users upgrading to DiskSuite 4.2.1, remove the 4.0 AnswerBook to avoid confusion.