6 Replies Latest reply on Aug 5, 2018 5:07 AM by rajen450m

    Cannot Power on or relocate virtual machine - Virtual Machine disk descriptor file is missing

    rajen450m Hot Shot
    vExpert

      Virtual Machine disk descriptor file is missing:

       

      We performed vmotion of a virtual machine (VM1) and had a strange incident (errors) faced.

       

      Relocate virtual machine

      Status: The VM failed to resume on the destination during early power on.

       

      Error stack:

      The source detected that the destination failed to resume.

      The VM failed to resume on the destination during early power on.

       

       

      Power On virtual machine

      Status: File /vmfs/volumes/<datastore>/VM1/VM1.vmdk was not found

       

      Error stack:

      An error was received from the ESX host while powering on VM VM1

      Failed to start the virtual machine.

      Module 'Disk' power on failed.

      Cannot open the disk '/vmfs/volumes/<datastore id>/VM1/VM1.vmdk' or one of the snapshot disks it depends on.

      The system cannot find the file specified

      File system specific implementation of Lookup[file] failed

      File system specific implementation of Lookup[file] failed

      File system specific implementation of LookupAndOpen[file] failed

      File system specific implementation of Lookup[file] failed

      VMware ESX cannot find the virtual disk "/vmfs/volumes//<datastore>/VM1/VM1.vmdk ". Verify the path is valid and try again.

       

       

      When we browse to check the files in datastore>VM folder, there was no VM1.vmdk of the virtual machine and we can see VM1-flat.vmdk and VM1-ctk.vmdk files?????

       

      We have re-created the VM1.vmdk file and brought VM live in production (as mentioned in the link),

       

      My Question is:

      What could be the reason for vmdk descriptor file is missing???

      How all these days it was working fine without any issue??