Vmware cannot delete file flat.vmdk

It doesn't remove them. Also tried the remove from disk option as well. This is the error it returns - and the drive is still listed. Failed to reconfigure virtual machine Systems28 - Veeam. I still have the drive. It's thin so only shows GB but that is it, Looking over the link you send me.

When I try to power on the station I still get this. I searched the VMX file and there is nothing left pointing to Systems72 so there must be another setting,. I did learn something. OK now that Veeam is back online I need to reinstall vCenter. Since the Veeam VM "thinks" it's already controlled by vCenter think that will give me much issue?

I am not certain how Veeam was installed that it is displaying this message If you already have a running vCenter, I would expect that you wouldn't want to deploy another one, I don't know how it would help correct it if it was associated with a broken one anyway.

Get answers from your peers along with millions of IT pros who visit Spiceworks. I'm working with ESXi 6.

Edited Jan 19, at UTC. Best Answer. JasonValentine This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. VMware expert. I don't know if this will help you. View this "Best Answer" in the replies below ». Popular Topics in VMware. Spiceworks Help Desk. Problem is when you create snapshot it creates delta files wich are used as "incremental files" to separate files before and after snapshot.

VM host then makes VM see these files as one disk. If you delete one from the chain you will corrupt the data! This may take a while so be patient else you will corupt the vmdk. If there are still files after this operation you will need to consolidate.

To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Each one is a different size When I go check the setting of the machine, it says that the hard drive is test Popular Topics in VMware. Below is the workaround we performed to quickly allow us to P2V the physical server. Your email address will not be published. How are you deleting the. VMDK file? If removing the VM from disk it will in fact remove all files and folder associated with the VM.

I deleted the file from SSH. Not sure if that might be the issue or not, but i will try it when I get home this evening on my home lab as well. Thank you very must you saved me, after the material virtual update 9 to 10, the DIsk 1 size take 0 MB usual 50 GB In a friday newer do a action on prod a friday! This worked like a charm! Thanks a million! This was a life saver. The one thing that might be of useful info is that we have had a rebuild of the VCENTRE server, which was a windows based to the appliance based, my thoughts are did this faulty vcentre have something still open with these servers when it failed?

It's indeed possible to rename and move. The point in time when you run into issues with renamed, or moved files is when you power-cycle the VM, i. That's why I actually though of files that are still in use, e.

However, what's strange is the vmfsfilelockinfo result. What you may want to check, is whether you see any helpful entries in the log files e. Other than this, try to contact VMTN user continuum , who may be able to help in such a case. I have tried today to rename the vmdk file and reboot the server is should be attached to.