Copy wont tell u whether the vmdk is corrupted or not. If copy is not working then seems to be problem in the storage. If vmdk is corrupted you will not be able to power on the VM. I would say check with your storage vendor to see if there is any problem. As I said before 0x3 0x11 0x0 is not a good sign.
I checked your kernel log again, its filled with this sense code also I see abort for that datastore. Which is also not a good sign. I'm not sure how some VMs successfully migrated.
If you can power off the VM, can u try this command and post the error message
vmkfstools –v 0 –t 0 <vm.vmdk>
