do the following safety checks.
1) Check to make sure you have no snapshots
2) Check the setting for your VM configuration your your Hard disk(s) is assigned to a proper VMDK file name. Meaning it should NOT have your VMname ending with 000001.vmdk.
3) Browse the VM folder and take a look. If the reports indicates your VM has a zombie file, you should see one or more VMname.000001.vmdk. The report will tell you if you have more than one.
The simple fix, All you have to do is run a Storage vMotion of the VM over to another LUN. Once the move is complete, whatever is left over in the original source LUN can be deleted if you know you don't need those VMDK files.Nawals1 person found this helpful
maybe the vm has a snapshot - and before snapshot was created there was a cd mounted ?
Yes, It could be. You just check if not in used you can remove it.Nawals
If RVTools detect is as zombie is cause that .vmdk is not present in any virtual machine configuration, but for safety, move that .vmdk to a temp folder in your datastore and wait some days before delete it.
Thank you all I will give it a try and I will let you know