VMware vSphere ESXi 6.x
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x
Error | Cause | Resolution |
Failed to lock the file
or
One or more disks are busy
|
To prevent concurrent changes to critical virtual machine files and file systems, ESXi/ESX hosts establish locks on these files. In certain circumstances, these locks may not be released when the virtual machine is powered off, thereby causing this error, when the virtual machine is powered on later in the cluster. |
To resolve this issue, see Investigating virtual machine file locks on ESXi hosts.
|
A required file was not found
or
The system cannot find the file specified
|
This issue occurs if a virtual disk file or its snapshot disk is not present at the path specified in the virtual machine's configuration file. |
Ensure that the missing virtual disk file is restored at the path specified.
Ensure that the virtual disk files configured for the virtual machine were not accidentally deleted or moved to a different location and that the datastores containing these virtual disks are accessible and mounted at the correct locations. For more information, see Verifying ESXi virtual machine file names
To see if it is applicable to your setup, see Powering on a virtual machine on an upgraded host fails with the error: File [VMFS volume] VM-name/VM-name.vmdk was not found
|
Input/output error | This issue occurs if ESXi host has a problem accessing the underlying storage devices or data stores. |
Troubleshoot and resolve any issues with the underlying storage devices:
|
The parent virtual disk has been modified since the child was created.
or
The content ID of the parent virtual disk does not match the corresponding parent content ID in the child
|
This issue occurs when snapshots are in a bad state, either through manual intervention or through a system failure. |
To resolve this issue, resolve the CID mismatch error.
For more information, see "The parent virtual disk has been modified since the child was created" error
|
Consolidate virtual disk files Error msg.snapshot.error-FAIL | VM consolidation failed during the backup process and it will invoke an error, this kind of requires manual consolidation Consolidate Snapshots | |
There is not enough space on the file system for the selected operation |
Free up space on the datastore(s) holding the virtual machine configuration files and virtual disks.
Alternatively, increase the size of the datastore on which the virtual machine is located. For more information, see the vSphere Storage guide.
|
VMware Skyline Health Diagnostics for vSphere - FAQ