Getting /usr/lib/vxvm/voladm.d/bin/disk.encap: cannot shift when trying to encapsulate the bootdisk

Article:TECH173508  |  Created: 2011-11-02  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH173508
Article Type
Technical Solution


Environment

Issue



Cannot enacapsulate the boot disk


Error



/usr/lib/vxvm/voladm.d/bin/disk.encap: cannot shift  These devices appear to be detached from their disk groups. You may
  wish to reattach these devices. To reattach the devices select "Add
  or initialize one or more disks" from the main disk operations menu
  and enter the device names for these disks.
  Output format: [Device_Name,Disk_Access_Name,Disk_Group,Disk_Media_Name]
  [c0t8d0,c0t8d0s2,
 


Environment



Solaris 10

VxVM5.0MP1


Cause



The error "/usr/lib/vxvm/voladm.d/bin/disk.encap: cannot shift" is a result of the disk c0t8d0 having a public and private region.

To get a better idea of what the actual error is we can manually encapsulate the boot disk as follows

/etc/vx/bin/vxencap -c -g rootdg -f sliced rootdisk=c0t8d0s2

This command fails with:

VxVM vxencap ERROR V-5-2-610
Disk c0t8d0s2 is already being used as auto:sliced disk - in disk group -;
        Disk cannot be encapsulated.

As can be seen, the disk cannot be encapsulated as it already has a public and private region.


Solution



vxdiskunsetup -C c0t8d0

vxdiskadm #2




Article URL http://www.symantec.com/docs/TECH173508


Terms of use for this information are found in Legal Notices