We've had a weird issue that I cannot explain and thought others may have some comments.
We've had 2 VM guests that appear to have suddenly powered off. Theres nothing in the Events list to say that anything has been done to those machines. They then refuse to power up with File not found or a Locked VMDK error. After a while of looking around, I was able to determine that the disk paths listed in the vmx file seemed to contain some invalid paths to the VMDK files. Fixing this up seemed to fix the issues and the VM started.
I did notice that the person who created these VMs has named a couple of the vmdk files the same, i.e. data.vmdk but in different paths on different datastores. Once of the servers had an issue with data.vmdk which existed twice on the VM guest but on different datastores. Could this have been the issue?
Is there a way for a vmx to suddenly change the paths to the vmdk files? Or the vmdk files to move suddenly?
