The virtual machine failed to start, prompting "File cannot be locked"

[chenrui39]

The virtual machine cannot be powered on or migrated. All prompted that the file could not be locked.

The following is the error message：

When you power on the virtual machine hnzy_om02, you receive an error from the ESX host.

Unable to start virtual machine.

Module Disk failed to power on.

Could not open the disk "/vmfs/volumes/571760cf-29b3014c-eb8a-0cc47a669ade/hnzy_om02/hnzy_om02-000001.vmdk" or one of the snapshot disks it depends on.

Failed to lock file

Queryed the VMware.log found that the file "/vmfs/volumes/571760cf-29b3014c-eb8a-0cc47a669ade/hnzy_om02/hnzy_om02-000001.vmdk" is locked

The mac address of the locker was not found by the "

vmkfstools -D /vmfs/volumes/571760cf-29b3014c-eb8a-0cc47a669ade/hnzy_om02/hnzy_om02-000001.vmd

k" command.

Has anyone encountered the same problem?

[sjesse]

Are there any snapshots on that vm? If so I'd try removing all snapshots if that's possible

[continuum · Accepted solution]

Do you use any automatic backup tools like Veeam ?
If yes - check the log-files of that tool - it may still have the snapshot mounted.