VMWareDisks resource cannot probe (Unknown status) when virtual machine moves to a different ESX host.

Problem

VMWareDisks resource cannot probe (Unknown status) when virtual machine moves to a different ESX host.

 

Error Message

VCS ERROR V-16-10061-22516 VMwareDisks:<VMWareDisks-resource>:monitor:Failed to check if the disk '[Datastore] disk.vmdk' is valid on ESX <ESX-hostname> with error 'SOAP 1.1 fault: "":ServerFaultCode [no subcode]
"A general system error occurred: Could not open/create change tracking file"
Detail:'VCS ERROR V-16-10061-22517 VMwareDisks:<VMWareDisks-resource>:monitor:Disk '[Datastore] disk.vmdk' is not valid on ESX <ESX-hostname>

 

Cause

Changed Block Tracking (CBT) is enabled in VMWare virtual machine settings.  This setting causes vmkfstools -J getuuid command to return error leading to Unknown state in Veritas Cluster Server.

 

Solution

Verify the UUID check is failing by running the following command on the ESX host where the VMWareDisks resource cannot probe.

1. Edit with .vmdk path configured in VMWareDisks resource.

2. Apply the patch (ESXi 6.0 Express Patch(EP) 6 or ESXi 6.0 Update 3) provided by VMware as a permanent solution.

Note: If a customer is using NetBackup, then disabling change block tracking would effectively take away some competitive advantage of NetBackup where it can morph incremental backup into full back and backup only used blocks.

Etrack : 3865850