Unable to encapsulate root disk after upgrade.
Article ID: 100003089
Updated On:
Description
Error Message
VxVM ERROR V-5-2-338
The encapsulation operation failed with the following error:
VxVM vxencap ERROR V-5-2-610
Disk disk_1 is already being used as auto:sliced disk - in disk group -;
Disk cannot be encapsulated.
Cause
If an upgrade is attempted with the boot disk encapsulated and some type of problem occurs where the boot drive is no longer encapsulated (the system is booting on partion mounts rather than volume mounts; df -k), sometimes the Volume Manager public and private regions may remain on the disk. For example ...
# prtvtoc /dev/rdsk/c1t0d0s2* /dev/rdsk/c1t0d0s2 partition map** Dimensions:* 512 bytes/sector* 424 sectors/track* 24 tracks/cylinder* 10176 sectors/cylinder* 14089 cylinders* 14087 accessible cylinders** Flags:* 1: unmountable* 10: read-only** Unallocated space:* First Sector Last* Sector Count Sector* 0 8395200 8395199** First Sector Last* Partition Tag Flags Sector Count Sector Mount Directory 0 2 00 8395200 134954112 143349311 1 3 01 81408 8313792 8395199 2 5 00 0 143349312 143349311 3 14 01 71232 143278080 143349311 4 15 01 0 71232 71231
The public and private regions are identified by the TAG values of 14 (public) and 15 (private). These partitions must be removed before re-encapsulating the boot drive.
Resolution
There are 2 methods that can be used here.
Note: Neither one of these methods will overwrite the original Solaris partition information or data. This should only be done if the prtvtoc output displays all the original partitions (see '/etc/vfstab.prevm' for reference).
- The first method uses a Volume Manager command to uninitiaze the public and private region partitions of the drive.
/usr/lib/vxvm/bin/vxdiskunsetup c1t0d0
(run the prtvtoc command again; if the output still shows TAGs 15 and 14, use method #2 below)
- Use the format utility to zero the offset and size of the public and private region partitions.
Applies To
Generic issue.
Issue/Introduction
