VM is in power off state, unable to power on due to 'disks consolidation is needed' warning.
Below log entries are observed in the vmware.log file of the VM,
yyyy-mm-ddThh:mm:ss.270Z In(05)+ vmx - Power on failure messages: Locking conflict for file "xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx/vm-name-directory/diffenent_vm-name-flat.vmdk ". VMFS on-disk lock owner is host with MAC address xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx and VMFS lock mode 0x1.
yyyy-mm-ddThh:mm:ss.270Z In(05)+ vmx - File system specific implementation of OpenFile[file] failed
yyyy-mm-ddThh:mm:ss.270Z In(05)+ vmx - File system specific implementation of OpenFile[file] failed
yyyy-mm-ddThh:mm:ss.270Z In(05)+ vmx - File system specific implementation of OpenFile[file] failed
yyyy-mm-ddThh:mm:ss.270Z In(05)+ vmx - File system specific implementation of OpenFile[file] failed
yyyy-mm-ddThh:mm:ss.270Z In(05)+ vmx - File system specific implementation of OpenFile[file] failed
yyyy-mm-ddThh:mm:ss.270Z In(05)+ vmx - File system specific implementation of OpenFile[file] failed
yyyy-mm-ddThh:mm:ss.270Z In(05)+ vmx - Failed to lock the file
yyyy-mm-ddThh:mm:ss.270Z In(05)+ vmx - Cannot open the disk 'xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx/vm-name-directory/diffenent_vm-name-flat.vmdk ' or one of the snapshot disks it depends on.
vCenter 7.x, 8.x
ESXi 7.x, 8.x
The vmdk file mentioned in above error logs, belong to a different live VM.
The affected VM could be a backup proxy server hence it has a disk of different VM attached.
Go to 'Edit Settings' of the affected VM.
Identify the specific disk of different VM and perform 'Remove device'
Note : Make sure NOT to click 'Remove device and data' as it could cause data loss.
Re try the disk consolidation.