The first thing I would do is make a backup of all of the VM's files.

Does it actually say "...0001.vmdk" or is that you editing for privacy? If it's the actual message, before you start fiddling with the disks, you might want to check the vmx and files.

Having done that, this thread may help - you may be able to change the vmdk files to make Fusion think the parent hasn't changed and hope that it hasn't actually changed that much. Then copy all the data off, check it, and start with a fresh VM since you don't know how badly the original is corrupted. Also try searching in other forums, since this isn't Fusion-specific.

Hello... I picked up this thread and helped me fix an issue i was having. So, thanks many moons later! Nick