The storage space on one of the datastores of our ESXi 7.0 U3 server was full, so I needed to migrate one specific VM to another datastore on the same server.
After the migration, the VMDK descriptor was missing and I was unable to start the machine.
I looked up a method to recreate the file and did it by creating a temp vmdk via vmkfstools. Then I took the necessary steps to rename the VMDK file and point it to the still existing -flat file. vmkfstools -e shows the disk chain as consistent.
I can now find the VMDK again, but when I try to add it to the VM, the provided data for that disk is empty or plain wrong and I can't save the new config. Clicking on save just does nothing.
Unfortunately, the original VMDK is not backupped anywhere.
Is there any way to fix this? Am I missing some info in the VMDK file?
Yes, I followed the KB and I double checked the VMX against one that is working on the same host and datastore.
But I completely lucked out. The server was non-critical and the owner gave permission to just completely recreate the VM from scratch.
Thanks for the reply, though!