after 3.5 host remediation, one VM will not start: "a file was not found"
{font:Arial}{size:2}{color:#000000}the error message is: "a file was not found". In addition to using update manager to remediate, I moved this host into an EVC cluster -- it is the first and only server in the new cluster currently. {color}{size}{font}
{font:Arial}{size:2}Below is an ls -l in the VM directory, and then also a CAT of the descriptor file. Any suggestions how to get this VM started again?{size}{font}
{font:Arial}{size:2}{color:#000000}[root@rp-esx1 rp-altium]# ls -l total 10486464 -rw------- 1 root root 21474836480 Jun 10 2008 rp-altium-flat.vmdk -rw------- 1 root root 8684 Feb 11 21:41 rp-altium.nvram -rw------- 1 root root 428 Jun 10 2008 rp-altium.vmdk -rw------- 1 root root 0 Jun 10 2008 rp-altium.vmsd -rw-r--r-- 1 root root 1827 Feb 12 09:10 rp-altium.vmx -rw------- 1 root root 264 Feb 12 09:10 rp-altium.vmxf -rw-r--r-- 1 root root 20217 Feb 12 09:08 vmware-10.log -rw-r--r-- 1 root root 20327 Feb 12 09:09 vmware-11.log -rw-r--r-- 1 root root 20217 Feb 11 23:02 vmware-6.log -rw-r--r-- 1 root root 20217 Feb 11 23:03 vmware-7.log -rw-r--r-- 1 root root 20217 Feb 12 08:02 vmware-8.log -rw-r--r-- 1 root root 20217 Feb 12 09:07 vmware-9.log -rw-r--r-- 1 root root 20443 Feb 12 09:10 vmware.log [root@rp-esx1 rp-altium]# {color}{size}{font}
________________________________________________ Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow" I do not support Workstation 16 at this time ...