Please be more precise: what vmdk-type are you talking about ?
A descriptor vmdk, a flat.vmdk, a delta.vmdk, a sesparse-vmdk, a ctk-vmdk or a RDM-vmdk ?
Typical reason for a non cooperative vmdk-files are either I/O errors or bad descriptor.
To find out which option applies run
hexdump -C <full path to vmdk-file> | less
You either get a hexdump view, a message with I/O error or a message with bad descriptor.
To deal with a non-deleteable large vmdk-file you resize io almost zero-size withh dd and afterwards wipe the associated inode.
Not ideal and not documented but way better than living with the wasted space.
To deal with a non readable vmdk with the intention to copy or move it somewhere you typically need the help of a Linux-VM
In real life dealing with non-cooperative vmdks you never need a move operation.
If you want a useful suggestion I need a vmfs-header-dump and a screenshot of the results of the already mentioned hexdump-test.
Ulli
________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...