After the vMotion "VM needs disk consolidation" warning message was gone. I restarted the vxpa service on the host and when reconnected to vCenter, it was showing Disk Consolidation is needed.
Although this isn't really a "fix" as such, and may not be of use to a production server, when I've been faced with issues like this in the past I find the easiest solution is just to use Vmware converter to v2v the machine, this provides an identical machine with a single vmdk per disk and is done with an agent within the VM, rather than at the hypervisor level, so it isn't aware of snapshots. Vsphere produced an alarm that a vm consolidation is needed. The issue we are seeing is that there is a corrupt OIB file from a job that was stuck and then canceled. This is a weird issue I can't seem to resolve. Shutdown the VM, and go to settings -> advanced -> edit the config file.To do it, connect to the host via SSH and run this command: SFC SCANNOW Is Stuck – Fixed via CHKDSK Command.Consolidation failed for disk node ‘scsi0:0’: Failed to lock the file.I'm facing a problem with the task manager.
Go to This PC, right-click on any drive, and choose "Properties". You need to disable the disk checking before it starts. com needs snapshot consolidation, but all automatic snapshot consolidation attempts have failed.
0 kommentar(er)
