Troubleshoot VMware virtual disk file locks, failed consolidation and inaccessible VMDK files without risking production VM data.
01 Confirm the exact locked file
06 Consolidation validation After the lock is cleared, consolidate from vCenter and monitor the task. Confirm snapshot state, guest accessibility and datastore capacity afterward.
Read the vCenter task details and identify the affected VMDK, delta disk or configuration file. Do not delete a VMDK because it appears old.
Confirm the exact locked file
Check for active VM operations
Verify snapshots, backup jobs, replication jobs, migrations and storage operations. Backup products can temporarily hold virtual disk files.
Identify the host holding the lock
Use vSphere task history and ESXi shell diagnostics where appropriate. Compare the VM registration and running host across the cluster.
Check datastore capacity
Confirm free space and inode/file availability. Consolidation can require additional temporary space even when the visible snapshot size seems small.
Validate stale registrations
A VM can remain registered on another host after an unexpected failure. Confirm the VM is not actively running elsewhere before changing registrations.
Consolidation validation
After the lock is cleared, consolidate from vCenter and monitor the task. Confirm snapshot state, guest accessibility and datastore capacity afterward.
Explore more TechRunbook guides
Continue with practical infrastructure troubleshooting, PowerShell scripts and operational runbooks.
Browse all articles →