I have a big trouble, my VM is not able to boot, always shows tihs message. I tried everything tha search on internet but any does not work.
There is way or method to scan and repair the file snapshot like chkdsk o any tools in order repair offline.
Greetings
this KB should help
Can you post a screenshot? What lead to this event? Do you have a backup of this VM?
Please attached the screenshot ,without seeing the error message it is difficult to suggest anything
I'm guessing you have some kind of back application (like veeam) and you are in state of consolidation needed ?
please attach screen shot of your error message and screenshot of your VM vmdks name and location.
Thanks for you anwsers, I attached the info you requested:
Hi,
Just to be sure , I need another screenshot of your VM settings.
Please Edit Settings your VM and point to the vmdk and capture the screen. (if there is more then 1 vmdk capture each of the vmdk )
Thanks.
How big is the delta flat file.?
can you run the below for redo log file for which the clone is failing
vmkfstools -q snapshot_ xxxxxx#.vmdk -v10 | less
One of the causes for redo corruption as per the KB is datastore space.. please check the same.
Also check if you can kill the Vm-world if the disk cloning fails even after VM power off.
If the redo log file is not large, you can think of discarding the same. point the vm back to the base disk and power on.
It looks like the VM's files were manually modified/recreated!?
Please provide details about what exactly has been done so far, and attach all of the metadata files (the files less than 10kB) along with the vmware*.log files (compressed in a zip file) to a reply post.
André
Greeting,
This the settings of main vmdk, another disk I create in order to save info there:
Hello Husaainbte,
The flat file size 200 GB and the delta file size 60 GB. There is space free on disk where is located the vm, I have 330 GB space free.
Still I dont run the comman tha you written, as soon as run I will attached the results.
What is meant " kill the Vm-world"?.
Thnask for you help.
If you have powered off the VM and then cloning the disk .. I wanted you to make sure there is no running vm-world which is locking the files.
Hello,
Yes, I powered off the VM and tried to cloning the disk but failed.
I do not what is vm-world, please can you explain.
Thanks
this KB should help
Which Version of ESX are you using? There is a known bug in ESX 6.0 where the guest OS gets corrupted
VMware ESXi 6.0 Update 3 Release Notes
Possible data corruption or loss when a guest OS issues SCSI unmap commands and an IO filter prevents the unmap operation
When a VM virtual disk is configured with IO filters and the guest OS issues SCSI unmap commands, the SCSI unmap commands might succeed even when one of the configured IO filters failed the operation. As a result, the state reflected in the VMDK diverges from that of the IO filter and data corruption or loss might be visible to the guest OS.
This issue is resolved in this release.
If your using ESX 6.5 and VMFS6 there are lot of reports of redo log corruption when snapshots are present.
