GENERAL ERROR: Dissimilar Disk Restore of a Solaris client fails if the client uses Solaris Volume Manager metadevices (volumes) created using slice 2 of Solaris disks.

Problem

GENERAL ERROR: Dissimilar Disk Restore of a Solaris client fails if the client uses Solaris Volume Manager metadevices (volumes) created using slice 2 of Solaris disks.

Solution

Overview:
This issue is observed on Solaris clients using Solaris Volume Manager (SVM) volumes created using slice 2 of disks.  For example, this issue would be seen when using Bare Metal Restore (BMR) to carry out a dissimilar disk restore (DDR) of a Solaris client using metadevices created as follows:

hostname.domain.com# metainit d11 1 1 c1t0d0s2
hostname.domain.com# metainit d21 1 2 c2t500601603A20216Ad3s2 c2t500601603A20216Ad4s2

In the example shown above, the metadevices d11 and d21 are created using slice 2 (s2) of the disks being used for volume creation.

Log Files/Messages:
If a DDR is carried out for such a client, BMR does not allow the user to map the SVM Volumes to any other slice but slice 2 of other disks.

If a mapping is done using slice 2, then the restore process fails with a message similar to the following:
Making database replica(s)
Making SVM plex d21
ERROR: failed to create plex d21.
ERROR: failed to create filesystems on disk NONAME.

Bare Metal Restore has failed.
Now, you will be dropped to a shell prompt.
You may reboot the system when you have completed diagnosis.

The restore log on the BMR master server also shows an error similar to the following:
/usr/sbin/metainit -f d21 1 2 /dev/dsk/c2t500601603A20216Ad2s0 /dev/dsk/c2t500601603A20216Ad3s0 -i 32b
metainit: hostname.domain.com: c2t500601603A20216Ad2s0: No space left on device

Workaround:
This issue is not seen in the following two cases - either may be used as a workaround:
1. Although the Dissimilar Disk Restore fails, a self restore of the client will succeed.
2. If the metadevices are created using an SVM diskset, self restore as well as a DDR will succeed.

In general, slice 2 should never be used in SVM configuration due to its special nature in Solaris as the "backup" slice for the entire disk.

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)