An error occurred while consolidating disks msg fileio lock
If you have a snapshot running that is not in Snapshot Manager, you can attempt to delete it in one of two ways.First, create a new snapshot using the v Sphere Client and delete all snapshots from the snapshot manager after the new one has been created.When you select an object in the left pane of the v Sphere Client, you can select the Storage View tab in the right pane and view storage information related to that object.One of the columns that you can view is Snapshot Space -- which is the total size of all snapshot-related files, including the -delta.vmdk, and files.But what do you do when your snapshots start acting funny?
When it completes, see if the delta files have been deleted. If the delta files weren't deleted, check the VMX file for the VM and locate the lines starting with scsi.
Update: According to many of the comments, a number of people are finding this post when searching for help with a VM that will not power on.
This post was written for a specific scenario related to missing snapshot files, but if you are merely trying to power on a VM that was working recently, you may be able to resolve the problem by simply delete any folders containing .
In part one of this series, I discussed how to use VMware snapshots.
In part two, I explained how to delete snapshots without wasting disk space.
After moving those files to a new location or deleting a snapshot file, attempting to boot the virtual machine returns the following error message: Cannot open the disk ‘XXXXXX.vmdk’ or one of the snapshot disks it depends on. I’ve found that following the steps below fixes the problem and allows me to boot the virtual machine as it existed at the time of creation.