Pick one of your VMDKs, if you have 2 drives, pick

Create a new VM, same spec as the other, same OS, same HDD size(s) - ram and CPU do not have to match, but do NOT install an OS and do NOT create a HDD for this, instead specify, I'll use an existing diskģ. If you want to get technical and try to boot this, follow the below at your own risks.Ģ. I advise you have a copy of this one way or another, all of the below I suggest are AT YOUR OWN risk if you proceed and do so without a backup.īefore you try any of the below, if your concern is getting the data out of the VM and rebuilding it is an option once the data is secure, right click the VMDK and mount it as a drive - extract your data and consider yourself lucky. I dont know what's in the snapshots, but you can only try to manually recover this. You've not answered about backups, so I'll assume you dont have one - and while this is important to you, this only highlights how important backups are if you dont have one. Lack of space, it being interrupted before completing the merge(s), speed, could all cause this.

Hard drive snapshot