تعمیر هارد دیسک مجازی

ممنون ولی هیچ کدام از مواردی که فرمودید مشکل رو حل نکرد راه حل دیگه ای هست دوستان ؟! 

اینجا توضیحات خوبی داده ، ببخشید همینجوری کپیشون می کنم !

 Cause :
File corruption is random in nature.
This issue might occur by various circumstances that include but are not limited to:
Hardware issues with the storage controller or storage device.
Connectivity issues between the ESX host and the storage device.
When the datastore containing the snapshot disks runs out of free disk space.
 

 Resolution :
To resolve this issue, use one of the options based on the symptom you are experiencing:
Create enough free space on the datastore where the snapshot disks are located:

Extend the particular VMFS datastore.
Migrate other virtual machines' files out of this datastore.

Commit the virtual machine snapshots: 
Verify that you have enough free space before proceeding.
If the snapshot configuration files are corrupt and do not display in Snapshot Manager, consolidate the snapshot disks manually by taking a consolidator snapshot or cloning the snapshot disks. For more information, see Committing snapshots when there are no snapshot entries in the snapshot manager (1002310). 
If the clone operation fails with a device or resource busy error message, the virtual machine is not powered off completely. You might see the error:

msg.hbacommon.corruptredo 
Click OK to power off the virtual machine and continue.
If the virtual machine is unable to proceed past this error, the virtual machine world must be terminated manually. 
Note: Manually terminating the virtual machine world terminates the virtual machine's processes. For more information, see Powering off an unresponsive virtual machine on an ESX host (1004340). Go to step 2 or power on the virtual machine according to the current status.

اسنپشات ها رو پاك كرديد؟