Hi, guys.
Here is the situation what happened by history.
1-The vm stopped working because of low disk space on host.
2-Shutted down the vm.
3-Tried to move files to other storage.
4-Low disk space on second storage and moving files stopped with error.
5-Some *.vmdk files renamed automatically to *-flat.vmdk and *-sesparse.vmdk files.
=== Not sure about missing files. ===
6-Tried to move already moved files back to old storage. Error occured === cant access files. parent permission ===
7-Tried to download files to local computer. Renamed to normal *.vmdk and tried to map over vmware workstation to get windows files and folders from. Couldn't read the file.
8-Tried to repair *vmdk file with vmdk kernal repair tool. Error occured like === highly corrupted file ===.
Any possibility to recover the previous version of vm?
No backups. 🙊
You’ve created your post in a very unusual area of the forum considering the subject matter, which VMware product were you originally using to host the VM?
Thanks for kind reply.
Could you please navigate me to the right url to ask for a help with existing situation.
The host was running on ESXi-6.7 .
I’ve now reported your thread so moderators should take a look at it and decide which is the correct area, you’ll know if it’s moved by checking the path just above your opening comment.
Thanks a lot Scott!
Kindly waiting for reply.
That sounds scary and means that you try to evaluate the situation by looking at the Datastorebrowser !!!!
Please note:
as soon as VMs are misbehaving, or you are running out of free space - you must immediatly stop using the DatastoreBrowser.
Datastorebrowser does not display the content of a VM-directory correctly.
It illegally displays name.vmdk + name-flat.vmdk as if they were just a single file. It also displays the size of the vmdk-files incorrectly ....
Please connect with WinSCP
show a screenshot of all files in the VMs directory.
Make sure that all names are completely displayed - may need to resize columns to acchieve that.