You've canceled an important disk move operation which was a big no-no. As a result, you probably have data corruption. You're already aware not having a backup was your big mistake, but at this point other than opening a support request there may not be a solution.
There are a handful of people in the forum who can help repair disks - Wila posted some information in a recent thread about the ones to look for.
Unfortunately at the moment the easiest approach to this problem is this nasty workaround:
1. copy the VMDK file in question to a Windows machine that has Starwind V2V converter installed
2. try to read the VMDK with the V2V converter
3. if possible convert the VMDK to another format / or create a new VMDK with it
4. copy back to your Fusion host
5. cross fingers
Plan B: try to install an older version of vdiskmanager - last known good one is from Fusion 3.1
VMware Knowledge Base
thanks for the replys. Ive a new windows laptop, I will try copying over to that and I will report back.