I'm no data rescue specialist. However, what you can try - after backing up all the VM's current files of course - is to expand the first extend to its correct size (using e.g. the dd utility and appending zeroes to the file). The try to boot the VM from a live CD/ISO to see what can be done. Alternatively you could crate a snapshot (after resizing the extent) to ensure the current .vmdk files won't get touched (and to be able to revert to it if necessary) and then try to power on the VM and see what can be rescued with this approach.
André