Troubleshoot virtual disk lock conditions that prevent VM power operations, consolidation or file access.
Start with Identify the affected VMDK and work through the six diagnostic checks in order.
Record results before changing configuration and validate the original symptom after each controlled change.
Quick checks
Start with the basic checks in this runbook before moving to deeper troubleshooting.
- Confirm the affected service or component is available.
- Check recent configuration or connectivity changes.
- Run the relevant commands and compare the result with the expected state.
Identify the affected VMDK
Record the VM, datastore and exact VMDK path from the error before changing the environment.
Check VM and snapshot state
Check for active snapshots, consolidation warnings and concurrent VM operations.
Identify lock ownership
Use supported ESXi diagnostic methods to identify which host or process holds the file lock.
Check host state
Determine whether another ESXi host or process still has the VM or disk open.
Preserve the VM files
Do not manually delete VMDK, lock or snapshot files simply to clear an error. Preserve evidence first.
Verify the VM operation
After resolving the lock owner, retry the affected operation and verify the virtual disk remains consistent.
Useful commands
Run these checks from an appropriate administrative session and replace example values with your environment.
Lock check
vmkfstools -D /vmfs/volumes/<datastore>/<vm>/<disk>.vmdkOpen files
lsof | grep <vmdk-name>Quick troubleshooting path
Use this sequence to isolate the failing dependency before changing production configuration.
- Identify the affected VMDK → Record the VM, datastore and exact VMDK path from the error before changing the environment.
- Check VM and snapshot state → Check for active snapshots, consolidation warnings and concurrent VM operations.
- Identify lock ownership → Use supported ESXi diagnostic methods to identify which host or process holds the file lock.
- Check host state → Determine whether another ESXi host or process still has the VM or disk open.
- Preserve the VM files → Do not manually delete VMDK, lock or snapshot files simply to clear an error. Preserve evidence first.
- Verify the VM operation → After resolving the lock owner, retry the affected operation and verify the virtual disk remains consistent.
What good troubleshooting looks like
Good infrastructure troubleshooting is evidence-driven. Capture the original state, test the dependency that can prove or disprove your hypothesis, make the smallest safe change and repeat the original test.
Symptom → hypothesis → direct test → result → controlled change → validation → documentation