OPERATIONAL DEFECT DATABASE
...
...
During the instant clone provisioning, the pool provisioning will fail with the error message "UNKNOWN_FAULT_FATAL - Failed to retrieve snapshot for the vm"Connection Server Debug logs show the following events: YYYY-MM-DDTHH:MM:SS.ms+TIMEZONE DEBUG (13B8-2280) <PendingOperation-vm-141336:snapshot-143395-SchedulePushImage> [NgvcHelper] Priming of pool <PoolName> has failed. - VC_FAULT_FATAL: A specified parameter was not correct: : com.vmware.daas.cloneprep.common.CPCbrcWarningException: A specified parameter was not correct: , VM moid: vm-XXXXXXXX, disk key: XXXXXXX, timedout: false at com.vmware.daas.cloneprep.vcsubsystem.LroVcTask.processCbrcDigestConfigureResult(LroVcTask.java:257) at com.vmware.daas.cloneprep.vcsubsystem.LroVcTask.handleTaskChanges(LroVcTask.java:15 at com.vmware.daas.cloneprep.vcsubsystem.VcTask.updateState(VcTask.java:164) at com.vmware.daas.cloneprep.vcsubsystem.PropertyCollectorUpdateTracker.checkTaskUpdates(PropertyCollectorUpdateTracker.java:761) at com.vmware.daas.cloneprep.vcsubsystem.PropertyCollectorUpdateTracker.checkTasks(PropertyCollectorUpdateTracker.java:1102) at com.vmware.daas.cloneprep.vcsubsystem.PropertyCollectorUpdateTracker.run(PropertyCollectorUpdateTracker.java:447) at java.base/java.lang.Thread.run(Unknown Source) Caused by: com.vmware.vim25hic.MethodFaultFaultMsg: A specified parameter was not correct: at com.vmware.daas.cloneprep.common.CPVcSubsystemException.<init>(CPVcSubsystemException.java:91) at com.vmware.daas.cloneprep.common.CPCbrcWarningException.<init>(CPCbrcWarningException.java:60) vSphere ESXi Hostd Logs will show the following events: YYYY-MM-DDTHH:MM:SS:MS.866Z info hostd[37181B70] [Originator@6876 sub=Vimsvc.TaskManager opID=7858cefc-ff-f408 user=vpxuser:VSPHERE.LOCAL\vc_admin] Task Created : haTask--vim.CbrcManager.configureDigest-179755342 YYYY-MM-DDTHH:MM:SS:MS.104Z info hostd[37140B70] [Originator@6876 sub=DiskLib opID=7858cefc-ff-f408 user=vpxuser:VSPHERE.LOCAL\vc_admin] DISKLIB-VMFS : VmfsExtentCommonOpen: DiskLibIsExtentPathSecure claims extent path "/vmfs/volumes/vsan:XXXXXXXXXXXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXX/cp-replica-XXXXX-XXXXX-XXXXX-XXXXX-XXX-digest-flat.vmdk" is insecure, failing disk open. YYYY-MM-DDTHH:MM:SS:MS.107Z info hostd[37140B70] [Originator@6876 sub=DiskLib opID=7858cefc-ff-f408 user=vpxuser:VSPHERE.LOCAL\vc_admin] DISKLIB-VMFS : "/vmfs/volumes/vsan:XXXXXXXXXXXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXX/cp-replica-XXXXX-XXXXX-XXXXX-XXXXX-XXX-digest-flat.vmdk" : failed to open (The specified device is not a valid physical disk device): . Type 3 YYYY-MM-DDTHH:MM:SS:MS.107Z info hostd[37140B70] [Originator@6876 sub=DiskLib opID=7858cefc-ff-f408 user=vpxuser:VSPHERE.LOCAL\vc_admin] DISKLIB-LINK : "/vmfs/volumes/vsan:XXXXXXXXXXXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXX/cp-replica-XXXXX-XXXXX-XXXXX-XXXXX-XXX-digest.vmdk" : failed to open (The specified device is not a valid physical disk device). YYYY-MM-DDTHH:MM:SS:MS.107Z info hostd[37140B70] [Originator@6876 sub=DiskLib opID=7858cefc-ff-f408 user=vpxuser:VSPHERE.LOCAL\vc_admin] DISKLIB-CHAIN : "/vmfs/volumes/vsan:XXXXXXXXXXXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXX/cp-replica-XXXXX-XXXXX-XXXXX-XXXXX-XXX-digest.vmdk" : failed to open (The specified device is not a valid physical disk device). YYYY-MM-DDTHH:MM:SS:MS.107Z info hostd[37140B70] [Originator@6876 sub=DiskLib opID=7858cefc-ff-f408 user=vpxuser:VSPHERE.LOCAL\vc_admin] DISKLIB-LIB : Failed to open '/vmfs/volumes/vsan:XXXXXXXXXXXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXX/cp-replica-XXXXX-XXXXX-XXXXX-XXXXX-XXX-digest.vmdk' with flags 0x20a The specified device is not a valid physical disk device (20). YYYY-MM-DDTHH:MM:SS:MS.107Z info hostd[37140B70] [Originator@6876 sub=DiskLib opID=7858cefc-ff-f408 user=vpxuser:VSPHERE.LOCAL\vc_admin] DISKLIB-LIB_DIGEST : DiskLibDigestDiskProcess: could not initialize digest meta data: DiskLib failed (7). YYYY-MM-DDTHH:MM:SS:MS.107Z info hostd[37140B70] [Originator@6876 sub=DiskLib opID=7858cefc-ff-f408 user=vpxuser:VSPHERE.LOCAL\vc_admin] DISKLIB-LIB_DIGEST : DiskLibDigestDiskCreateAndProcess: cannot process the digestfile: /vmfs/volumes/vsan:XXXXXXXXXXXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXX/cp-replica-XXXXX-XXXXX-XXXXX-XXXXX-XXX-digest.vmdk vmdk /vmfs/volumes/vsan:XXXXXXXXXXXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXX/cp-replica-XXXXX-XXXXX-XXXXX-XXXXX-XXX.vmdk error A digest operation has failed
This article descibes about the event of Digest disk operation failure during the instant clone pool provisioning
If the scratch partition on the datastore is misconfigured on the datastore where the same datastore is used for Instant clones can result in digest operation failures
Pool creation and provisioning oprerations will be failed
Ensure the scratch partition is not configured on the root of any datastore.Please refer to Storing ESXi coredump and scratch partitions in vSAN for more information about best practices for creating the scratch partition.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
