Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I had had a Windows VM having a second virtual drive configured as an independant volume placed on a second datastore on a VMWare ESXi 5 server.

Then I have removed the second drive by removing it in the guest Windows Volumes Management and then removing (with deletion) it in the VM properties in vSphere client.

Now the machine seems perfectly operational (I can still start, use and stop it) but I get false "File thevmname.vmx not found" error when I try to make a snapshot (the file is on its place and seems ok, I've checked).

How to fix this?

I have never done any cloning/copying/migration or whatever special yet. There is a related question but it doesn't seem the same case.

share|improve this question
Are there any existing snapshots in play? Does vCenter allow you to migrate the guest's data to another datastore? Does a clone succeed? – Simon Catlin Aug 21 '12 at 21:45
There are snapshots already. I have never migrated or cloned anything within this server yet. Moreover, I don't know how to migrate a VM to a different storage - couldn't find such an option in vSphere client. – Ivan Aug 21 '12 at 22:40

The solution I've found is here:

The strange part is that the VHD I've removed to break the snapshots was created as independent initially.

Still glad to know better solutions.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.