Solstice DiskSuite 4.2.1 Installation and Product Notes

Previous: Book Information

Solstice DiskSuite 4.2.1 Installation and Product Notes

General Information

The procedure for upgrading Solstice DiskSuite^TM 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 Solaris^TM 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 SPARC^TM 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.
AnswerBook2^TM 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.

New Features

Solstice DiskSuite 4.2.1 includes the following new features:

Solstice DiskSuite 4.2.1 supports the new device drivers for the fibre channel driver architecture products.
Numerous bug fixes enhance the reliability and performance on both SPARC and x86 platforms. These fixes include the following:
- 4208254 -- Solutions are now offered for the write-on-write problem. Refer to the metainit(1M) man page for details.
- 4008267 -- Errored logs can now be deleted from a mounted trans device using the metatool(1M) graphical user interface.
- 4158871 -- Provides information about a device that fails to open. The information is presented in the the device naming format, CnTnDnSn.
- 4189276 -- No longer get multiple instances of the same disk for dual ported SPARC storage arrays (SSA).
- 4155935 -- Solstice DiskSuite now shows all available paths to a disk. It also detects when a disk drive is identified by different names.
- 4191069 -- Replica algorithm now sees device ID (DID) devices as separate controllers.
- 4221096 -- The SUNWmdg package now can be installed using the jumpstart software.
- 4181214 -- The mdlogd(1M) no longer reports inaccurate warning messages.

File and Package Relocation

Most Solstice DiskSuite pathnames and package names have changed in the 4.2.1 release. The pathname changes are shown in the following table.

Previous Pathname	New Pathname
`/usr/opt/SUNWmd/sbin`	`/usr/sbin`
`/usr/opt/SUNWmd/man`	`/usr/share/man`
`/usr/opt/SUNWmd/lib`	`/usr/lib/lvm`
`/usr/opt/SUNWmd/locale`	`/usr/lib/locale`
`/usr/opt/SUNWmd/locale/`	`/usr/lib/lvm/locale`
`/usr/opt/SUNWmd/lib/X11`	`/usr/lib/lvm/X11`
`/etc/opt/SUNWmd`	`/etc/lvm`

Other files that have been relocated are listed in the following table.

Previous Path	New Path
`/usr/opt/SUNWmd/lib/X11/app-defaults/Metatool`	`/usr/lib/livm/X11/app-defaults/Metatool`
`/usr/opt/SUNWmd/lib/metatool-toolsmenu`	`/usr/lib/lvm/metatool-toolsmenu`
`/etc/init.d/SUNWmd.init`	`/usr/init.d/lvm.init`
`/etc/init.d/SUNWmd.sync`	`/usr/init.d/lvm.sync`
`/etc/rcS.d/S35SUNWmd.init`	`/etc/rcS.d/S35lvm.init`
`/etc/rc2.d/S95SUNWmd.sync`	`/etc/rc2.d/S95lvm.sync`

The package name changes are shown in the following table.

Previous Package Name	New Package Name
`SUNWmd`	`SUNWmdr`, `SUNWmdx`, and `SUNWmdu`
`SUNWmdg`	`SUNWmdg`
`SUNWmdn`	`SUNWmdnr` and `SUNWmdu`

Known Bugs

The following is a list of the priority 1, 2, and 3 bugs associated with Solstice DiskSuite 4.2.1. The priority and severity of the bugs is given in parentheses following the BugID number.

4182141 (P2/S2) -- Access to a UFS filesystem on Solstice DiskSuite volume can hang. If a trans device, which has a shared log, is cleared using metaclear(1M) the log thread is shutdown. This causes other filesystems that use the shared log to hang.
4234927 (P2/S3) -- Using metaoffline(1M) to take a metadevice offline after lockfs(1M) fails to leave the file system in a consistent state. This problem is a result of the mirror being the master device of a trans. There is nothing in metaoffline to flush the trans log which can result in an inconsistent file system for backups.

Solstice DiskSuite 4.2.1 Usage Notes

Requirements of the Solstice DiskSuite 4.2.1 program include the following:

You must be root to administer Solstice DiskSuite 4.2.1.
Before you can commit metadevices created using Solstice DiskSuite 4.2.1, metadevice state database replicas must exist on the Solstice DiskSuite 4.2.1 system. Refer to Solstice DiskSuite 4.2.1 User's Guide for instructions on how to create metadevice state database replicas.

If the GUI is displayed on a system that does not run true color or is running programs that do not share color maps, an error message similar to the following may be displayed when DiskSuite Tool is invoked:

Warning: Cannot allocate colormap entry for "#8caaba"
Warning:
    Cannot parse default background color spec
 
Warning: Cannot allocate colormap entry for "orange"
Warning: Cannot allocate colormap entry for "purple"
Warning: Cannot allocate colormap entry for "mediumseagreen"
Warning: Cannot allocate colormap entry for "firebrick"
Warning: Cannot allocate colormap entry for "tan"

If this error is displayed, exit DiskSuite Tool and the other applications. Then restart DiskSuite Tool.

AnswerBook2 Online Documentation

The Solaris 8 CD (one of two) contains the AnswerBook2 server. Versions of the following DiskSuite documentation can be found on the Solaris 8 CD (two of two).

Solstice DiskSuite 4.2.1 User's Guide
Solstice DiskSuite 4.2.1 Reference Guide

Installation

Solstice DiskSuite 4.2.1 is supported on systems running Solaris 8. Systems running earlier versions of Solaris must be upgraded to Solaris 8 before Solstice DiskSuite 4.2.1 can be installed.

If you are performing the initial installation of Solstice DiskSuite on a system, you can simply install or upgrade the system to Solaris 8, then install the DiskSuite packages by using the Software Manager (swmtool(1M)) graphical user interface, the pkgadd(1M) command, or by using Solaris Web Start. Refer to Solaris Easy Access Server 2.0 Installation Library for information on Web Start.

If an earlier version of DiskSuite is already running on the system, the installation method will vary according to the system configuration. The following section describes how the system configuration affects these installations.

Upgrading Systems Running Earlier Versions of DiskSuite

On a system which uses DiskSuite, the procedures for upgrading the Solaris operating system and DiskSuite are interrelated. The definitions below can help you understand the procedures and the issues that they address.

Simple metadevice -- A metadevice composed of a single component (disk slice) with a "Start Block" (as shown by metastat) of 0.
Simple mirror metadevice -- A mirror whose submirrors are all simple metadevices.
Simple trans metadevice -- A trans device whose master device is a simple metadevice.
Operating system mount point -- A directory that contains Solaris system software and is used as a mount point in /etc/vfstab. Operating system mount points are affected by upgrades of Solaris. Operating system mount points always include root, /usr, and swap. The directories /var, /opt, /usr/openwin, /export, /export/root, and /export/exec may also be operating system mount points depending on how Solaris was installed.
Operating system metadevice -- A metadevice is considered an operating system metadevice if /etc/vfstab mounts an operating system mount point on it. An operating system metadevice must be either a simple metadevice, a simple mirror metadevice, or a simple trans metadevice. Some systems that use DiskSuite will not have any operating system metadevices. If root is on a metadevice, all underlying components of that metadevice must be bootable.

The factors that affect installation on systems already running earlier versions of DiskSuite are:

You must be running Solaris 8 to use DiskSuite 4.2.1
System architecture (that is, SPARC or x86)
Solaris version running on the system before installation
Solstice DiskSuite version running on the system before installation
Whether you have operating system metadevices

The Solaris installation program cannot upgrade Solaris software that resides on metadevices, so each operating system metadevice must be decomposed into a single component (slice) before the Solaris installation program runs. After Solaris has been installed, these operating system metadevices must be reconstructed.

DiskSuite configuration and state information is stored in a private replicated database called a metadevice state database (or metadb). Disk drives are described in the database using the driver name and minor number of the device. Since the release of DiskSuite 4.0, Solstice DiskSuite has allowed old metadbs to be read by new releases of Solaris and DiskSuite. Each release of DiskSuite supports at least two versions of Solaris. That enables you to upgrade to a desired Solaris/DiskSuite combination from your current versions by upgrading Solaris and then upgrading DiskSuite. The support matrix is depicted in the following table.

Table 1-1 Solstice DiskSuite Support Matrix


	Solaris 2.5.1	Solaris 2.6	Solaris 7	Solaris 8
DiskSuite 4.0	Supported
DiskSuite 4.1	Supported	Supported
DiskSuite 4.2 SPARC		Supported	Supported
DiskSuite 4.2 x86		Supported*	Supported*
DiskSuite 4.2.1				Supported

* -- Use the metacvt command delivered with Solstice DiskSuite 4.2.1 to remove the system metadevice state database replicas and metadevices before Solaris 8 upgrades on x86 machines. The metacvt command creates a shell script that restores the replicas and metadevices after the upgrade.

For the metadevice state database information to be valid, new Solaris software must be applied via upgrade, preserving the device bindings across the upgrade.

Caution -

If a full install of Solaris is performed, all DiskSuite configuration information will be lost. Losing the DiskSuite configuration information can result in data loss or complete system failure.

It is important not to change the hardware configuration of a machine during an upgrade to avoid changes in device bindings. Again, loss of device bindings invalidates the metadevice state database information and can result in data loss or complete system failure.

One of the features of Solaris 8 for x86 is unification of the SCSI drivers. The same sd driver is now used on both SPARC and x86. Because the metadevice state database information contains device driver names, an upgrade to Solaris 8 on x86 requires that the DiskSuite metadbs be rebuilt. The DiskSuite 4.2.1 software distribution includes a version of the metacvt(1M) command that automates metadb removal and reconstruction.

The procedures for dealing with the factors just described can be condensed into the following rules:

Always run the "Upgrade" option of the Solaris installation program when upgrading Solaris on a system that is already configured and running Solstice DiskSuite.
Never change the hardware configuration of a machine during an upgrade.
To upgrade to DiskSuite 4.2.1 and Solaris 8, the system must be running Solaris 2.5.1, Solaris 2.6, or Solaris 7 and DiskSuite 4.0, DiskSuite 4.1, or DiskSuite 4.2. If necessary, follow the instructions given in the Solstice DiskSuite 4.0 Product Notes to upgrade the system to Solaris 2.5 and DiskSuite 4.0, then upgrade to Solaris 2.5.1.
To upgrade an x86 system to DiskSuite 4.2.1 and Solaris 8, all metadevices must be decomposed, the DiskSuite metadevice state databases must be removed from the system, and the DiskSuite packages must be removed before the system is upgraded to Solaris 8. After the upgrade to Solaris 8, the DiskSuite 4.2.1 packages must be added and the metadevices reconstructed. The metacvt script supplied with DiskSuite 4.2.1 automatically decomposes the metadevices, removes the metadevice state database from the system, and writes a shell script that can be used to restore the metadevice state database and reconstruct the metadevices after the upgrade and installation of the DiskSuite 4.2.1 packages.
To upgrade to DiskSuite 4.2.1 and Solaris 8, the system must be running Solaris 2.5.1, and DiskSuite 4.1. If necessary, follow the instructions given in the Solstice DiskSuite 4.0 Product Notes to upgrade the system to Solaris 2.4 and DiskSuite 4.0.
Metadevices containing operating system files (operating system metadevices) must be decomposed into simple components (single slices) before the operating system can be upgraded.

Caution -
Failure to decompose operating system metadevices prior to upgrading the system will result in loss of data and can result in complete system failure.
Metadevices must not be reconstructed or mounted on file systems until the new version of the Solstice DiskSuite software has been installed.

Converting to Solstice DiskSuite 4.2.1

Depending on the operating level and version of Solstice DiskSuite you are running on your system, the upgrade procedure will vary.

If you are converting to Solstice DiskSuite 4.2.1, your system will fall into one of the following three categories:

SPARC or x86 systems running Solaris 2.3 or Solaris 2.4 with Online: DiskSuite 2.0 or Online: DiskSuite 3.0
SPARC systems running Solaris 2.5, Solaris 2.5.1, or Solaris 2.6 with Solstice DiskSuite 4.0 or 4.1
x86 systems running Solaris 2.5, Solaris 2.5.1, Solaris 2.6, or Solaris 7 with Solstice DiskSuite 4.0, 4.1, or 4.2

The following subsections provide instructions for upgrading systems in each category to Solstice DiskSuite 4.2.1.

How to Convert to DiskSuite 4.2.1 on Systems Running Solaris 2.3 or Solaris 2.4 With Online: DiskSuite 2.0 or Online: DiskSuite 3.0

You must first upgrade your system to Solstice DiskSuite 4.0 and Solaris 2.5, using the instructions in the DiskSuite 4.0 Installation notes. Then you can use the instructions in the following subsections to upgrade to Solstice DiskSuite 4.2.1. Follow the upgrade procedure in the Solaris 2.5 and Solstice DiskSuite 4.0 product notes.

How to Convert to DiskSuite 4.2.1 on SPARC Systems Running DiskSuite 4.0, 4.1, or 4.2

The procedure in this section only works for customers who have SPARC machines running Solstice DiskSuite 4.0, 4.1 or 4.2 on Solaris 2.5, 2.5.1, 2.6, or Solaris 7 and upgrading to Solaris 8.

Caution -

Before you begin this procedure, back up all file systems. See the ufsdump(1M) man page for details.

Repair any mirrors that have errors.

Save the metadb configuration, the metadevice configuration, the device bindings, and /etc/vfstab on a remote or a floppy disk.

One or more of these files can be overwritten when you reboot the machine, upgrade the operating system, or install the new version of DiskSuite. Here are some example commands that save the metadb configuration, the metadevice configuration, and /etc/vfstab on a local floppy disk:

# /usr/sbin/metadb > /dev/fd/metadb.cfg
# /usr/sbin/metastat -p > /dev/fd/metadevice.cfg
# cp /etc/vfstab /dev/fd/meta_vfstab
# ls -l /dev/rdsk/*s0 > /dev/fd/binding
# cp /etc/path_to_inst /dev/fd/path_to_inst

The following example commands save the metadb configuration, the metadevice configuration, and the /etc/vfstab to another machine called other_machine on the network connected to the system being upgraded:

# /usr/sbin/metadb -i > /net/other_machine/save/metadb.cfg
# /usr/sbin/metastat -p > /net/other_machine/save/metadevice.cfg
# cp /etc/vfstab /net/other_machine/save/meta_vfstab
# ls -l /dev/rdsk/*s0 > /net/other_machine/save/bindings
# cp /etc/path_to_inst /net/other_machine/dev/fd/path_to_inst

Caution -

Make sure you save the metadb configuration, metadevice configuration and /etc/vfstab before going on to the next step in this procedure. Inability to restore any of them after the upgrade will result in data loss, and can result in complete system failure.

Clear any trans metadevices that may be used during the Solaris upgrade (for example, /usr, /var, and /opt).

See Solstice DiskSuite 4.2.1 User's Guide for information on clearing (removing logging from) trans metadevices. If you are uncertain which trans metadevices should be cleared, clear all trans metadevices.

In /etc/vfstab comment out file systems mounted on metadevices that are not simple metadevices or simple mirrors.

A simple metadevice is composed of a single component with a Start Block of 0. A simple mirror is composed of submirrors, all of which are simple metadevices.

Convert the remaining (simple) mirrors to one-way mirrors with the metadetach command.

Upgrade will be performed on a single submirror of each mirror. The other submirrors will be synced up with metattach after the upgrade.

If root (/) is mounted on a metadevice or mirror, set the root file system to be mounted on the underlying component of the metadevice or the underlying component of the remaining attached submirror.

Use the metaroot command to do this safely.

Edit the /etc/vfstab file to change any file systems or swap devices still mounted on metadevices or mirrors after Step 3.

Mount the file systems on the underlying component of the metadevices or the underlying component of the remaining attached submirrors.

Remove symbolic links to the DiskSuite startup file so that it is no longer initialized at boot time.
# rm /etc/rcS.d/S35lvm.init /etc/rc2.d/S95lvm.sync
These links will be added back later by reinstalling DiskSuite after the Solaris upgrade.

Halt the machine and upgrade to the Solaris 8 operating environment, then reboot the machine.

Caution -
Make sure you upgrade the correct slice. On machines with mirrored root file systems, the Solaris installation software displays all slices used in the root mirror as available for upgrade. Choose the slice that the system boots from. The section, "How to Find the System Boot Slice When Upgrading the Solaris Operating System", explains how to locate the boot slice.

Note -
If you have unbundled software running on your system, refer to the product documentation for any information about upgrading before upgrading to Solaris 8 operating environment and Solstice DiskSuite 4.2.1.

Install the Solstice DiskSuite 4.2.1 software using the instructions in "Initial Installation of Solstice DiskSuite" of this document.

This will re-establish the symbolic links removed in Step 8.

If root (/) was originally mounted on a metadevice or mirror, set the root (/) file system to be mounted back on the original metadevice or mirror.

Use the metaroot command to do this safely.

Edit the /etc/vfstab file to change any file systems or swap devices edited in Step 7 to be mounted back on their original metadevice or mirror.

Edit the /etc/vfstab file to uncomment the file systems commented out in Step 4.

Reboot the machine to remount the file systems.

Use the metattach command to reattach and resync any submirrors detached in Step 5.

Recreate the cleared trans metadevices. See Solstice DiskSuite 4.2.1 User's Guide for information on creating trans metadevices.

How to Convert to DiskSuite 4.2.1 and Solaris 8 on x86 Systems Running Solaris 2.5 or 2.5.1 and DiskSuite 4.0 or 4.1

The procedure in this section only works for customers who have x86 machines running Solstice DiskSuite 4.0 or 4.1 on Solaris 2.5 or Solaris 2.5.1 and are upgrading to Solaris 8.

Caution -

Before you begin this procedure, back up all file systems. See the ufsdump(1M) man page for details.

Repair any mirrors that have errors.

Save the metadb configuration, the metadevice configuration, the device bindings, and /etc/vfstab on a remote or a floppy disk.

# /usr/sbin/metadb > /dev/fd/metadb.cfg
# /usr/sbin/metastat -p > /dev/fd/metadevice.cfg
# cp /etc/vfstab /dev/fd/meta_vfstab
# ls -l /dev/rdsk/*s0 > /dev/fd/binding
# cp /etc/path_to_inst /dev/fd/path_to_inst

# /usr/sbin/metadb -i > /net/other_machine/save/metadb.cfg
# /usr/sbin/metastat -p > /net/other_machine/save/metadevice.cfg
# cp /etc/vfstab /net/other_machine/save/meta_vfstab
# ls -l /dev/rdsk/*s0 > /net/other_machine/save/bindings
# cp /etc/path_to_inst /net/other_machine/dev/fd/path_to_inst

Caution -

Clear any trans metadevices that may be used during the Solaris upgrade (for example, /usr, /var, and /opt).

See Solstice DiskSuite 4.2.1 User's Guide for information on clearing (removing logging from) trans metadevices. If you are uncertain which trans metadevices should be cleared, clear all trans metadevices.

In /etc/vfstab comment out file systems mounted on metadevices that are not simple metadevices or simple mirrors.

A simple metadevice is composed of a single component with a Start Block of 0. A simple mirror is composed of submirrors, all of which are simple metadevices.

Convert the remaining (simple) mirrors to one-way mirrors with the metadetach command.

Upgrade will be performed on a single submirror of each mirror. The other submirrors will be synced up with metattach after the upgrade.

If root (/) is mounted on a metadevice or mirror, set the root file system to be mounted on the underlying component of the metadevice or the underlying component of the remaining attached submirror.

Use the metaroot command to do this safely.

Edit the /etc/vfstab file to change any file systems or swap devices still mounted on metadevices or mirrors after Step 3.

Mount the file systems on the underlying component of the metadevices or the underlying component of the remaining attached submirrors.

Remove symbolic links to the DiskSuite startup files so that it is no longer initialized at boot time.
# rm /etc/rcS.d/S35lvm.init /etc/rc2.d/S95lvm.sync
These links will be added back later by reinstalling DiskSuite after the Solaris upgrade.

Halt the machine and upgrade to Solaris 8, then reboot the machine.

Caution -
Make sure you upgrade the correct slice. On machines with mirrored root file systems, the Solaris installation software displays all slices used in the root mirror as available for upgrade. Choose the slice that the system boots from. The section, "How to Find the System Boot Slice When Upgrading the Solaris Operating System", explains how to locate the boot slice.

Install the Solstice DiskSuite 4.2.1 software using the instructions in the "Initial Installation of Solstice DiskSuite" section of this document.

This will re-establish the symbolic links removed in Step 8.

If root (/) was originally mounted on a metadevice or mirror, set the root (/) file system to be mounted back on the original metadevice or mirror.

Use the metaroot command to do this safely.

Edit the /etc/vfstab file to change any file systems or swap devices edited in Step 7 to be mounted back on their original metadevice or mirror.

Edit the /etc/vfstab file to uncomment the file systems commented out in Step 4.

Reboot the machine to remount the file systems.

Use the metattach command to reattach and resync any submirrors detached in Step 5.

Recreate the cleared trans metadevices. See Solstice DiskSuite 4.2.1 User's Guide for information on creating trans metadevices.

How to Convert to DiskSuite 4.2.1 and Solaris 8 on x86 Systems Running Solaris 2.5, 2.5.1, 2.6, or 7 and DiskSuite 4.0 or 4.1

If you are running Solaris 2.5, Solaris 2.5.1, Solaris 2.6, or Solaris 7 on an x86 machine using Solstice DiskSuite 4.0 or 4.1, use the following procedure to upgrade to Solaris 8 and DiskSuite 4.2.1.

Run the metacvt(1M) command included with the DiskSuite 4.2.1 software distribution. The metacvt command is located in the /tools subdirectory on the CD. Make sure you save the S94SUNmd.cvt output.

Refer to the metacvt man page for detailed instruction on how to use this command and a list of actions the command performs.

Caution -
The metacvt command generates a script called S94SUNWmd.cvt. Make sure you save this script in a location that will not be overwritten during the software upgrade.

Reboot the system and upgrade the operating system to the new version.

If a mirrored system partition must be resized to accommodate the new system files, resize each submirror that mirrors the partition to match the partition's new size.

Caution -
Do not perform an initial installation. An initial installation will reformat the system disks and destroy the data on them. It may also change the disk device bindings and invalidate the metadevice configuration saved in the S94SUNmd.cvt output.

Caution -
Make sure you upgrade the correct slice. On machines with mirrored root file systems, the Solaris installation software displays all slices used in the root mirror as available for upgrade. Choose the slice that the system boots from. The section, "How to Find the System Boot Slice When Upgrading the Solaris Operating System", explains how to locate the boot slice.

Remove all the old Solstice DiskSuite packages that may reside on the system.

Install the Solstice DiskSuite 4.2.1 software using the instructions in the "Initial Installation of Solstice DiskSuite".

Run the S94SUNmd.cvt script.

Refer to the S94SUNmd.cvt(1M) man page for additional information on the script.

Reboot the system.

Initial Installation of Solstice DiskSuite

The following sections describe how to get ready for a local or remote installation of Solstice DiskSuite on a SPARC or x86 machine that has never had the software installed.

How to Prepare for Local Installation

This procedure assumes that Volume Management is running on the system. This procedure should be used for both SPARC and x86 architectures.

Insert the CD containing the software into the CD-ROM drive.

If necessary, insert the CD into a caddy first.

Change to the /cdrom/cdrom0/products/DiskSuite_4.2.1 directory.
local# cd /cdrom/cdrom0/products/DiskSuite_4.2.1/`uname -p`
uname with the -p option places you in the directory that contains the correct version of DiskSuite for your architecture (either sparc or i386). You are now ready to install Solstice DiskSuite 4.2.1.

How to Prepare for Remote Installation

On the remote machine, insert the CD containing the software into the CD-ROM drive.

If necessary, insert the CD into a caddy first.

Put a line similar to one of the following into the /etc/dfs/dfstab file.
share -F nfs -o ro -d "CD-ROM Directory" /cdrom/cdrom0/products
This line may be different, depending on how your system is networked.

Export the /cdrom/cdrom0/ directory with the shareall command.
remote# shareall

On the local machine, log in as root.

Create the directory /cdrom/cdrom0/ (if it doesn't already exist).
local# mkdir -p /cdrom/cdrom0/
You may choose another directory besides /cdrom/cdrom0/.

Mount the CD-ROM as follows.
local# mount remote_machinename:/cdrom/cdrom0/ /cdrom/cdrom0/
Change to the /cdrom/cdrom0/products/DiskSuite_4.2.1 directory.
local# cd /cdrom/cdrom0/products/DiskSuite_4.2.1/`uname -p`
uname with the -p option places you in the directory that contains the correct version of DiskSuite for your architecture (either sparc or i386).

You are now ready to install Solstice DiskSuite 4.2.1.

Choosing Packages

This section describes the six Solstice DiskSuite 4.2.1 packages.

Table 1-2 Solstice DiskSuite 4.2.1 Packages


Package	Contains ...	Required or Optional
`SUNWmdg`	Solstice DiskSuite Tool Graphical User Interface	Optional, but recommended
`SUNWmdnr`	Solstice DiskSuite Log Daemon Configuration Files	Optional
`SUNWmdnu`	Solstice DiskSuite Log Daemon (user)	Optional
`SUNWmdr`	Solstice DiskSuite Drivers (root)	Required
`SUNWmdu`	Solstice DiskSuite Commands	Required
`SUNWmdx`	Solstice DiskSuite Drivers (64-bit)	Required for 64-bit hardware

Adding Packages

This section describes three methods available for installing the DiskSuite packages. To install packages with the Software Manager graphical user interface, go to "How to Add Packages Using Software Manager". To install packages with the pkgadd command, go to "How to Add Packages Using the pkgadd Command".

How to Add Packages Using Software Manager

This procedure assumes that root is a member of the sysadmin group (GID 14).

As root, start Software Manager.
# swmtool &
In Solaris 2.5 and later versions, Admintool is invoked.

Select Add from the Edit menu.

The Admintool: Set Source Media window may appear. If so, specify the path to the installation media, then click OK. The default path is a mounted CD.

Choose the packages you want to install.

Click the box next to each software component in the Software list. There are multiple packages per component.

When you choose to install software using Admintool, the packages are installed in the proper order, regardless of the selection order.

Click the Add button.

A Command Tool window appears for the installation process.

Respond with y to any prompts about continuing the installation.

Ignore the following message that appears after the installation has finished.

System warning: No such file or directory, extras menu file 
/usr/lib/.text_extras_menu (Textsw package)

How to Add Packages Using the `pkgadd` Command

As root, change to the directory on which the CD-ROM is mounted.

Use the directory that you specified when preparing for a local or remote installation. Change to the /cdrom/cdrom0/products/DiskSuite_4.2.1/`uname -p` directory to be placed automatically in the directory that contains the distribution for your system's architecture.
# cd /cdrom/cdrom0/products/DiskSuite_4.2.1/`uname -p`

Run pkgadd to install packages.
# pkgadd -d .
Note -
If the pkgadd command is not in your current path, you must specify the full path to the command (/usr/sbin/pkgadd).

Choose the packages you want to install.

pkgadd displays the available packages and prompts you to enter the number associated with a package.

Respond with y to any prompts about continuing with the installation.

pkgadd installs the DiskSuite files in the appropriate system directories. The program loops until you press q to quit.

Example -- SPARC: Adding Packages from a Local CD Using `pkgadd`

The example shown on the following pages demonstrates installing DiskSuite on a SPARC system running Solaris 7.

Note -

Do not be concerned if the screens displayed when you install this product do not appear exactly as shown in the following example.

# pkgadd -d .
The following packages are available:
  1  SUNWmdg      Solstice DiskSuite Tool
                  (sparc) 4.2.1
  2  SUNWmdnr     Solstice DiskSuite Log Daemon Configuration Files
                  (sparc) 4.2.1
  3  SUNWmdnu     Solstice DiskSuite Log Daemon
                  (sparc) 4.2.1
  4  SUNWmdr      Solstice DiskSuite Drivers
                  (sparc) 4.2.1
  5  SUNWmdu      Solstice DiskSuite Commands
                  (sparc) 4.2.1
  6  SUNWmdx      Solstice DiskSuite Drivers(64-bit)
                  (sparc) 4.2.1

Select package(s) you wish to process (or 'all' to process a
all packages). (default: all) [?,??,q]: all

Processing package instance <SUNWmdg> from </cdrom/cdrom0>

Solstice DiskSuite Tool
(sparc) 4.2.1
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
Using (/) as the package base directory.
## Processing package information.
## Processing system information.
   5 package pathnames are already properly installed.
## Verifying package dependencies.
WARNING:
    The <SUNWmdr> package "Solstice DiskSuite Drivers" is a 
    prerequisite package and should be installed.

Do you want to continue with the installation of <SUNWmdg> [y,n,?] y
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of <SUNWmdg> [y,n,?] y

Installing Solstice DiskSuite Tool as <SUNWmdg>

## Executing preinstall script.
## Installing part 1 of 1.
/usr/lib/lvm/X11/bitmaps/SDStool.xpm
/usr/lib/lvm/X11/bitmaps/battery_16.xpm
/usr/lib/lvm/X11/bitmaps/battery_32.xpm
/usr/lib/lvm/X11/bitmaps/browser_icon.xpm
/usr/lib/lvm/X11/bitmaps/browser_icon_mask.xbm
/usr/lib/lvm/X11/bitmaps/concat_16.xpm
/usr/lib/lvm/X11/bitmaps/concat_16_insens.xpm
/usr/lib/lvm/X11/bitmaps/concat_32.xpm
/usr/lib/lvm/X11/bitmaps/concat_32_insens.xpm
/usr/lib/lvm/X11/bitmaps/concat_drag.xbm
/usr/lib/lvm/X11/bitmaps/concat_drag_mask.xbm
/usr/lib/lvm/X11/bitmaps/controller_16.xpm
/usr/lib/lvm/X11/bitmaps/controller_32.xpm
/usr/lib/lvm/X11/bitmaps/diskview_icon.xpm
/usr/lib/lvm/X11/bitmaps/diskview_icon_mask.xbm
/usr/lib/lvm/X11/bitmaps/drop_none.xbm
/usr/lib/lvm/X11/bitmaps/drop_none_mask.xbm
/usr/lib/lvm/X11/bitmaps/drop_not_ok.xbm
/usr/lib/lvm/X11/bitmaps/drop_not_ok_mask.xbm
/usr/lib/lvm/X11/bitmaps/drop_ok.xbm
/usr/lib/lvm/X11/bitmaps/drop_ok_mask.xbm
/usr/lib/lvm/X11/bitmaps/drop_site_selection.xbm
/usr/lib/lvm/X11/bitmaps/editor_icon.xpm
/usr/lib/lvm/X11/bitmaps/editor_icon_mask.xbm
/usr/lib/lvm/X11/bitmaps/fan_16.xpm
/usr/lib/lvm/X11/bitmaps/fan_32.xpm
/usr/lib/lvm/X11/bitmaps/fibre_16.xpm
/usr/lib/lvm/X11/bitmaps/fibre_32.xpm
/usr/lib/lvm/X11/bitmaps/help_icon.xpm
/usr/lib/lvm/X11/bitmaps/help_icon_mask.xbm
/usr/lib/lvm/X11/bitmaps/hsp_16.xpm
/usr/lib/lvm/X11/bitmaps/hsp_16_insens.xpm
/usr/lib/lvm/X11/bitmaps/hsp_32.xpm
/usr/lib/lvm/X11/bitmaps/hsp_32_insens.xpm
/usr/lib/lvm/X11/bitmaps/hsp_drag.xbm
/usr/lib/lvm/X11/bitmaps/hsp_drag_mask.xbm
/usr/lib/lvm/X11/bitmaps/lock_16.xpm
/usr/lib/lvm/X11/bitmaps/lock_32.xpm
/usr/lib/lvm/X11/bitmaps/log_icon.xpm
/usr/lib/lvm/X11/bitmaps/log_icon_mask.xbm
/usr/lib/lvm/X11/bitmaps/metadb_16.xpm
/usr/lib/lvm/X11/bitmaps/metadb_16_insens.xpm
/usr/lib/lvm/X11/bitmaps/metadb_32.xpm
/usr/lib/lvm/X11/bitmaps/metadb_32_insens.xpm
/usr/lib/lvm/X11/bitmaps/metadb_drag.xbm
/usr/lib/lvm/X11/bitmaps/metadb_drag_mask.xbm
/usr/lib/lvm/X11/bitmaps/mirror_16.xpm
/usr/lib/lvm/X11/bitmaps/mirror_16_insens.xpm
/usr/lib/lvm/X11/bitmaps/mirror_32.xpm
/usr/lib/lvm/X11/bitmaps/mirror_32_insens.xpm
/usr/lib/lvm/X11/bitmaps/mirror_drag.xbm
/usr/lib/lvm/X11/bitmaps/mirror_drag_mask.xbm
/usr/lib/lvm/X11/bitmaps/multi_drag.xbm
/usr/lib/lvm/X11/bitmaps/multi_drag_mask.xbm
/usr/lib/lvm/X11/bitmaps/perfview_icon.xpm
/usr/lib/lvm/X11/bitmaps/perfview_icon_mask.xbm
/usr/lib/lvm/X11/bitmaps/raid_16.xpm
/usr/lib/lvm/X11/bitmaps/raid_16_insens.xpm
/usr/lib/lvm/X11/bitmaps/raid_32.xpm
/usr/lib/lvm/X11/bitmaps/raid_32_insens.xpm
/usr/lib/lvm/X11/bitmaps/raid_drag.xbm
/usr/lib/lvm/X11/bitmaps/raid_drag_mask.xbm
/usr/lib/lvm/X11/bitmaps/slice_16.xpm
/usr/lib/lvm/X11/bitmaps/slice_16_insens.xpm
/usr/lib/lvm/X11/bitmaps/slice_drag.xbm
/usr/lib/lvm/X11/bitmaps/slice_drag_mask.xbm
/usr/lib/lvm/X11/bitmaps/spundown_16.xpm
/usr/lib/lvm/X11/bitmaps/spundown_32.xpm
/usr/lib/lvm/X11/bitmaps/trans_16.xpm
/usr/lib/lvm/X11/bitmaps/trans_16_insens.xpm
/usr/lib/lvm/X11/bitmaps/trans_32.xpm
/usr/lib/lvm/X11/bitmaps/trans_32_insens.xpm
/usr/lib/lvm/X11/bitmaps/trans_drag.xbm
/usr/lib/lvm/X11/bitmaps/trans_drag_mask.xbm
/usr/lib/lvm/X11/bitmaps/wrench_16.xpm
/usr/lib/lvm/X11/bitmaps/wrench_32.xpm
/usr/lib/lvm/X11/bitmaps/wrench_8.xpm
/usr/lib/lvm/X11/uid/Metatool/Editor.uid
/usr/lib/lvm/X11/uid/Metatool/EditorTmpl.uid
/usr/lib/lvm/X11/uid/Metatool/PerfMonWindow.uid
/usr/lib/lvm/X11/uid/Metatool/concat.uid
/usr/lib/lvm/X11/uid/Metatool/hsp.uid
/usr/lib/lvm/X11/uid/Metatool/logs.uid
/usr/lib/lvm/X11/uid/Metatool/md.uid
/usr/lib/lvm/X11/uid/Metatool/mirror.uid
/usr/lib/lvm/X11/uid/Metatool/physicalview.uid
/usr/lib/lvm/X11/uid/Metatool/popups.uid
/usr/lib/lvm/X11/uid/Metatool/raid.uid
/usr/lib/lvm/X11/uid/Metatool/slice.uid
/usr/lib/lvm/X11/uid/Metatool/slicer.uid
/usr/lib/lvm/X11/uid/Metatool/stripe.uid
/usr/lib/lvm/locale/C/help/metatool/howto/Howto
/usr/lib/lvm/locale/C/help/metatool/howto/help.h.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/Reference
/usr/lib/lvm/locale/C/help/metatool/reference/catinfo.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/cflog.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/controllerinfo.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/devicestats.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/diskinfo.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/diskview.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/diskview.slicefilters.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/find.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/hspbrowser.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/hspfilters.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/hspinfo.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/logtofile.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/mappingselect.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/mdbrowser.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/mded.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/mdfilters.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/metadbinfo.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/mirrorinfo.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/phytolog.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/problist.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/raidinfo.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/restore.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/save.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/slicebrowser.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/slicefilters.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/sliceinfo.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/statgraphs.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/stripeinfo.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/transinfo.r.hlp
/usr/lib/lvm/locale/C/help/metatool/reference/trayinfo.r.hlp
/usr/lib/lvm/locale/C/help/metatool/topics/Topics
/usr/lib/lvm/locale/C/help/metatool/topics/glossary.t.hlp
/usr/sbin/metatool
/usr/share/man/man1m/metatool.1m
/usr/share/man/man4/metatool-toolsmenu.4
[ verifying class (none) ]
/usr/lib/lvm/X11/app-defaults/Metatool
/usr/lib/lvm/metatool-toolsmenu
[ verifying class (preserve) ]
## Executing postinstall script.

Installation of <SUNWmdg> was successful.

Processing package instance <SUNWmdnr> from </cdrom/cdrom0>

Solstice DiskSuite Log Daemon Configuration Files
(sparc) 4.2.1
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
Using (/) as the package base directory.
## Processing package information.
## Processing system information.
   3 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of <SUNWmdnr> [y,n,?] y

Installing Solstice DiskSuite Log Daemon Configuration Files as <SUNWmdnr>

## Executing preinstall script.
## Installing part 1 of 1.
/etc/init.d/init.mdlogd
/etc/rc3.d/S25mdlogd (symbolic link)
[ verifying class (none) ]
/etc/lvm/mdlogd.cf
[ verifying class (preserve) ]
## Executing postinstall script.

Installation of (SUNWmdnr) was successful.

Processing package instance (SUNWmdnu) from (/cdrom/cdrom0)

Solstice DiskSuite Log Daemon
(sparc) 4.2.1
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
Using (/) as the package base directory.
## Processing package information.
## Processing system information.
   5 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of <SUNWmdnu> [y,n,?] y

Installing Solstice DiskSuite Log Daemon as <SUNWmdnu>

## Installing part 1 of 1.
/usr/sbin/mdlogd
/usr/share/man/man1m/mdlogd.1m
[ verifying class (none) ]
## Executing postinstall script.

Installation of <SUNWmdnu> was successful.

Processing package instance <SUNWmdr> from </cdrom/cdrom0>

Solstice DiskSuite Drivers
(sparc) 4.2.1
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
Using (/) as the package base directory.
## Processing package information.
## Processing system information.
   8 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of <SUNWmdr> [y,n,?] y

Installing Solstice DiskSuite Drivers as <SUNWmdr>

## Executing preinstall script.
## Installing part 1 of 1.
/etc/init.d/lvm.init
/etc/init.d/lvm.sync
/etc/lvm/lock
/etc/rc2.d/S95lvm.sync (symbolic link)
/etc/rcS.d/S35lvm.init (symbolic link)
/kernel/drv/md
/kernel/misc/md_hotspares
/kernel/misc/md_mirror
/kernel/misc/md_notify
/kernel/misc/md_raid
/kernel/misc/md_stripe
/kernel/misc/md_trans
[ verifying class (none) ]
/etc/lvm/devpath
/etc/lvm/md.cf
/etc/lvm/md.ctlrmap
/etc/lvm/md.tab
/etc/lvm/mddb.cf
/etc/lvm/runtime.cf
cp /net/boulder/export/sdspkgs/sds-421/421_4/sparc/SUNWmdr/reloc/kernel/drv/md.conf \
   /kernel/drv/md.conf
[ verifying class (preserve) ]
## Executing postinstall script.
postinstall: configure driver

                (This may take a while.)

Installation of <SUNWmdr> was successful.

Processing package instance <SUNWmdu> from </cdrom/cdrom0>

Solstice DiskSuite Commands
(sparc) 4.2.1
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
Using (/) as the package base directory.
## Processing package information.
## Processing system information.
   10 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of <SUNWmdu> [y,n,?] y

Installing Solstice DiskSuite Commands as <SUNWmdu>

## Executing preinstall script.
## Installing part 1 of 1.
/usr/lib/drv/config_md.so.1
/usr/lib/drv/preen_md.so.1
/usr/lib/libap_dmd.so.1
/usr/lib/libssd.so.1
/usr/lib/locale/C/LC_MESSAGES/SUNW_MD.po
/usr/sbin/growfs
/usr/sbin/metaclear
/usr/sbin/metadb
/usr/sbin/metadetach
/usr/sbin/metahs
/usr/sbin/metainit
/usr/sbin/metaoffline
/usr/sbin/metaonline
/usr/sbin/metaparam
/usr/sbin/metarename
/usr/sbin/metareplace
/usr/sbin/metaroot
/usr/sbin/metaset
/usr/sbin/metastat
/usr/sbin/metasync
/usr/sbin/metattach
/usr/sbin/rpc.metad
/usr/sbin/rpc.metamhd
/usr/share/man/man1m/growfs.1m
/usr/share/man/man1m/metaclear.1m
/usr/share/man/man1m/metadb.1m
/usr/share/man/man1m/metadetach.1m
/usr/share/man/man1m/metahs.1m
/usr/share/man/man1m/metainit.1m
/usr/share/man/man1m/metaoffline.1m
/usr/share/man/man1m/metaonline.1m
/usr/share/man/man1m/metaparam.1m
/usr/share/man/man1m/metarename.1m
/usr/share/man/man1m/metareplace.1m
/usr/share/man/man1m/metaroot.1m
/usr/share/man/man1m/metaset.1m
/usr/share/man/man1m/metastat.1m
/usr/share/man/man1m/metasync.1m
/usr/share/man/man1m/metattach.1m
/usr/share/man/man1m/rpc.metad.1m
/usr/share/man/man1m/rpc.metamhd.1m
/usr/share/man/man4/md.cf.4
/usr/share/man/man4/md.tab.4
/usr/share/man/man4/mddb.cf.4
/usr/share/man/man7/md.7
[ verifying class (none) ]
## Executing postinstall script.

Installation of <SUNWmdu> was successful.

Processing package instance <SUNWmdx> from </cdrom/cdrom0>

Solstice DiskSuite Drivers(64-bit)
(sparc) 4.2.1
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
Using (/) as the package base directory.
## Processing package information.
## Processing system information.
   5 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user 
permission during the process of installing this package.

Do you want to continue with the installation of <SUNWmdx> [y,n,?] y

Installing Solstice DiskSuite Drivers(64-bit) as <SUNWmdx>

## Executing preinstall script.
## Installing part 1 of 1.
/kernel/drv/sparcv9/md
/kernel/misc/sparcv9/md_hotspares
/kernel/misc/sparcv9/md_mirror
/kernel/misc/sparcv9/md_notify
/kernel/misc/sparcv9/md_raid
/kernel/misc/sparcv9/md_stripe
/kernel/misc/sparcv9/md_trans
[ verifying class (none) ]
## Executing postinstall script.
postinstall: configure driver

                (This may take a while.)

Installation of <SUNWmdx> was successful.

The following packages are available:
  1  SUNWmdg      Solstice DiskSuite Tool
                  (sparc) 4.2.1
  2  SUNWmdnr     Solstice DiskSuite Log Daemon Configuration Files
                  (sparc) 4.2.1
  3  SUNWmdnu     Solstice DiskSuite Log Daemon
                  (sparc) 4.2.1
  4  SUNWmdr      Solstice DiskSuite Drivers
                  (sparc) 4.2.1
  5  SUNWmdu      Solstice DiskSuite Commands
                  (sparc) 4.2.1
  6  SUNWmdx      Solstice DiskSuite Drivers(64-bit)
                  (sparc) 4.2.1

Select package(s) you wish to process (or 'all' to process a
all packages). (default: all) [?,??,q]: q
#

Viewing Installed Packages

You can confirm that the DiskSuite software has been installed by using the pkginfo(1) command:

# pkginfo
system      SUNWaccr							System Accounting, (Root)
system      SUNWaccu							System Accounting, (Usr)
system      SUNWadmap						System administration applications
 
. . . (other package information)
 
system      SUNWmdg        Solstice DiskSuite Tool
system      SUNWmdnr       Solstice DiskSuite Log Daemon Configuration Files
system      SUNWmdnu       Solstice DiskSuite Log Daemon
system      SUNWmdr        Solstice DiskSuite Drivers
system      SUNWmdu        Solstice DiskSuite Commands
system      SUNWmdx        Solstice DiskSuite Drivers(64-bit)
 
. . . (other package information)

The -l option gives detailed information about packages:

# pkginfo -l SUNWmdr
      PKGINST:  SUNWmdr
      NAME:  Solstice DiskSuite Drivers
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  4.2.1
   BASEDIR:  /
    VENDOR:  Sun Microsystems, Inc.
      DESC:  Solstice DiskSuite Drivers
    PSTAMP:  10/01/99-17:54:26
  INSTDATE:  Oct 04 1999 11:12
    VSTOCK:  258-6252-11
   HOTLINE:  Please contact your local service provider
    STATUS:  completely installed
     FILES:     27 installed pathnames
                 8 shared pathnames
                 8 directories
                10 executables
               969 blocks used (approx)
  #

Setting the Path Variables

After installing the software, you must set the environment variables PATH and MANPATH.

The general requirements are as follows:

Modify your PATH variable to include /usr/sbin, /usr/lib/lvm, and /etc/lvm.

If you do not set this path, you may get other versions of the software.
Modify your MANPATH to include /usr/share/man.

If you do not set this path, you could get man pages for the wrong release, or no man pages at all.

You can set these paths by using an editor to change your $HOME/.profile or ~/.cshrc file, as follows.

If you installed DiskSuite in the default directory, and:

If you're using the Bourne shell, your $HOME/.profile file should have lines like this:

PATH=/usr/sbin:/etc/lvm:/usr/lib/lvm:$PATH
MANPATH=/usr/share/man:$MANPATH
export PATH MANPATH

If you're using the C shell (csh.1), the ~/.cshrc file should have lines that look something like this:
set path = (/usr/sbin,/usr/lib/lvm,/etc/lvm:$path) setenv MANPATH /usr/share/man:$MANPATH

Removing Packages

If you want to remove a DiskSuite package, you can remove the installed files using the pkgrm command. For example, to remove the SUNWmdu package, type the following (as root):

# pkgrm SUNWmdu

Note -

Do not remove DiskSuite files using the rm command. Using pkgrm is the only valid way to remove these files.

How to Find the System Boot Slice When Upgrading the Solaris Operating System

On machines with mirrored root file systems, the Solaris installation software will display all slices used in the root mirror as available for upgrade. The slice names may also contain different controller numbers than those used for the same slices in the system's vfstab and in the DiskSuite configuration database. BugIDs 4046177, 4043749, 4017614, and 4041649 describe this problem.

If all the upgradable slices are on the same controller, you can ignore controller number changes and choose the slice with the same target and disk number as the root slice in the system vfstab. You can display the system vfstab during the upgrade, and before choosing which slice to upgrade, by performing the following steps:

When the Solaris installation software displays the list of upgradable slices, either start up a subshell in the windowing system or write down the names of the slices and exit the installation program.

In a command shell, mount either of the slices displayed by the install software on /a:
# mount /dev/dsk/slice_name /a

Display the system's vfstab:
# more /a/etc/vfstab

Restart or resume the Solaris installation program and upgrade the slice with the same target and disk numbers as the one mounted on the root filesystem in /a/etc/vfstab.

If the slices are on different controllers, follow the procedure below to find out which slice is the boot slice.

When the Solaris installation software displays the list of upgradable slices, either start up a subshell in the windowing system, or write down the names of the slices and exit the installation program.

In a command shell, mount either of the slices displayed by the install software on /a:
# mount /dev/dsk/slice_name /a

Display the system's vfstab:
# more /a/etc/vfstab

Find the root slice in the vfstab, and display its /device path:
# ls -l /a/dev/dsk/root_slice_name

Find the device path for each of the miniroot's slice names, using the following command:
# ls -l /dev/dsk/slice_name

Restart or resume the installation program and upgrade the slice that has the same /device path as that of the system root slice, or the path most similar to it. There are minor differences between the path displayed in Solaris 8 and Solaris 2.5.1, and 2.6, and cmdk(7D) has been replaced by sd(7D) at the ends of the path names of SCSI devices in Solaris 8. However, you should have little difficulty choosing the path most similar to that of the boot device.

If you can't figure out which slice to upgrade, contact Sun Enterprise Services.

If you choose incorrectly and upgrade the wrong slice, the system will reboot under the old version of Solaris. If that happens, rerun the upgrade on the other slice.

Previous: Book Information

Solstice DiskSuite 4.2.1 Installation and Product Notes

General Information

New Features

File and Package Relocation

Known Bugs

Solstice DiskSuite 4.2.1 Usage Notes

AnswerBook2 Online Documentation

Installation

Upgrading Systems Running Earlier Versions of DiskSuite

Converting to Solstice DiskSuite 4.2.1

How to Convert to DiskSuite 4.2.1 on Systems Running Solaris 2.3 or Solaris 2.4 With Online: DiskSuite 2.0 or Online: DiskSuite 3.0

How to Convert to DiskSuite 4.2.1 on SPARC Systems Running DiskSuite 4.0, 4.1, or 4.2

How to Convert to DiskSuite 4.2.1 and Solaris 8 on x86 Systems Running Solaris 2.5 or 2.5.1 and DiskSuite 4.0 or 4.1

How to Convert to DiskSuite 4.2.1 and Solaris 8 on x86 Systems Running Solaris 2.5, 2.5.1, 2.6, or 7 and DiskSuite 4.0 or 4.1

Initial Installation of Solstice DiskSuite

How to Prepare for Local Installation

How to Prepare for Remote Installation

Choosing Packages

Adding Packages

How to Add Packages Using Software Manager

How to Add Packages Using the pkgadd Command

Example -- SPARC: Adding Packages from a Local CD Using pkgadd

Viewing Installed Packages

Setting the Path Variables

Removing Packages

How to Find the System Boot Slice When Upgrading the Solaris Operating System

How to Add Packages Using the `pkgadd` Command

Example -- SPARC: Adding Packages from a Local CD Using `pkgadd`