Thanks for uploading the logs. They are very informative.
Unfortunately, this vmdk's metadata is very corrupted. Normally the SparseChecker will try to patch up common metadata errors, such as the kind that happen when you pull the plug on your computer or crash Fusion, but these are not those kind of errors. It looks like someone was scribbling randomly over your metadata -- possibly there were two VMs that managed to get ahold of the same disk? There should be locking to prevent this, so it would be a bug. Can you describe what happened to the VM before it became unbootable?
It is very unlikely that you can recover this VM to a bootable state. Even if you can patch up the metadata, it is likely that the data on disk will be incosistent. Do you have important data you need to retrieve from this VM? It is possible to manually patch up the disk so you can attach it to another VM and run a data recovery program on it, though it will take some effort.
If you have snapshots of the VM, reverting to an older version is likely to work.
Let me know if there is anything I can help with.
-Eric
