I've run into an odd problem with a VMWare host that underwent several hard reboots yesterday. Most all of the VMs are booting up fine but a few can not be powered on. The host is running ESXi 5.1 799733 The error that pops from the vsphere client is:
An error was received from the ESX host while powering on VM black.
Cannot open the configuration file /vmfs/volumes/50a27883-8c4cae8e-a3fc-002590524262/black/black.vmx.
An error occurred while creating temporary file for /vmfs/volumes/50a27883-8c4cae8e-a3fc-002590524262/black/black.vmx: The file already exists
The file does of course exist. what's unique about the dirs that have these problematic VMs is that the vmx file name with the tilde extension is in an odd state.
/vmfs/volumes/50a27883-8c4cae8e-a3fc-002590524262/black # ls
ls: ./black.vmx~: No such file or directory
black-3ead7995.vswp black.nvram black.vmsd black.vmxf vmware.log
black-flat.vmdk black.vmdk black.vmx vmware-1.log
I've searched around and have not seen this exact issue mentioned elsewhere. Any idea as to what I could try?
Thanks!