The VDID is used to uniquely identify a disk by the volume daemon (vold). In some cases, the device discovery module (emc.dll) incorrectly categorizes the disks as Count Key Data (CDK) devices, leading to a change in the VDID.

Due to this change, the vold is unable to find the disk with the original VDID. A failure of the SCSI INQUIRY command in the ddlprov.dll file on a disk can also cause an inconsistent VDID. If a disk group import, refresh or rescan is subsequently issued, the previously imported disk groups, which contain disks that have inconsistent VDIDs, may get deported.

A hotfix is now available for this issue in the current version(s) of the product(s) mentioned at the end of this article.

The hotfix is available here: https://sort.veritas.com/patch/detail/10878

This article contains a link to a hot fix that addresses three, related issues.

1. A disk group that was created using EMC Invista devices is automatically deported while another disk group is imported
2. A failure of a SCSI INQUIRY command, in the ddlprov.dll file, causes the incorrect generation of a Veritas Disk ID (VDID).
3. The value of the VDID attribute for EMC Invista devices is not consistent.