I’ve had my share of battles with corrupt vmdk files, after the process of removing a snapshot crashed. Finally, I found a way to recover them through a VCB utility. Here’s the log that usually presents itself:

May 12 01:43:13.593: vmx| DISKLIB-DSCPTR: Failed to open extents for descriptor file in normal mode
May 12 01:43:13.593: vmx| DISKLIB-LINK : “/vmfs/volumes/49dc603e-af139aaa-7131-002219b6f201/VM1/VM1.vmdk” : failed to open (Device or resource busy).
May 12 01:43:13.593: vmx| DISKLIB-CHAIN : “/vmfs/volumes/49dc603e-af139aaa-7131-002219b6f201/VM1/VM1.vmdk” : failed to open (Device or resource busy).
May 12 01:43:13.594: vmx| DISKLIB-LIB : Failed to open ‘/vmfs/volumes/49dc603e-af139aaa-7131-002219b6f201/VM1/VM1.vmdk’ with flags 0xa (Device or resource busy).
May

Read more