Error Message

Continue with operation? [y,n,q,?] (default: y)
This disk device does not appear to be valid. The disk may not be
formatted (format(1M)), may have a corrupted VTOC, the device file
for the disk may be missing or invalid, or the device may be turned-off
or detached from the system. This disk will be ignored.
Output format: [Device_Name,Disk_Access_Name]

A un-initialized variable gets a different value after OS (Operating System) patch installation, thereby making vxparms command outputs give different result.

vxdiskadm (option 2) does few additional checks before proceeding with encapsulation.One of the checks it does is to ensure if the DANAME matches with the STAT_SDI_NAME returned by vxparms command. In this case, vxparms is not returning STAT_SDI_NAME and hence vxdiskadm is failing with an error.

 

Workaround

• Downgrade to a lower revision of patch, for example Solaris Patch 147440-19.
• Or one can use vxencap command directly to encapsulate the boot disk after confirming the daname represented by VxVM is pointing to the correct boot disk 

  Syntax:

  # vxencap -c -f sliced -g rootdg dmname=daname

Solution: 

• For Storage Foundation version 5.1 releases the fix is available in the form of a Hotfix in VxVM 5.1SP1RP2P3HF5 or later. The General Availability (GA) fix is targeted to be included in 5.1SP1RP3 release.
• For Storage Foundation version 6.0 releases the fix is available in the form of a Hotfix in VxVM 6.0RP1HF2. The Storage Foundation 6.0.1 release did not include the fix for this issue and the General Availability fix is targeted to be included in 6.0.1P1 patch.

Kindly search in SORT ( https://sort.Veritas.com ) for the etrack number listed below. If a fix is not found in any available GA patch, then please contact Veritas Technical Support for access to the appropriate patch.

Applies To

Solaris 10 with kernel patch 147440-20 or later

Storage Foundation 5.1x or 6.0x