This is not a VMware issue at all. If there's an issue with the disk structure, it actually depends on what files/blocks are affected. In this case the virtual disk file (.vmdk) seems to be the "unlucky" file which had some of its data on the problematic blocks. Glad you got this fixed.
André