Site Tools


vmware:troubleshooting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
vmware:troubleshooting [2021/01/07 11:03] lunetikkvmware:troubleshooting [2021/09/16 17:17] lunetikk
Line 121: Line 121:
 __Fix:__ \\ __Fix:__ \\
  
-Connect to your ESX host via ssh and restart the management agents+Connect to your ESX host via SSH and restart the management agents
 <code> <code>
 /etc/init.d/hostd restart /etc/init.d/hostd restart
Line 129: Line 129:
 You should be able to create or remove the snapshot afterwards You should be able to create or remove the snapshot afterwards
  
-[[https://kb.vmware.com/s/article/1027707|https://kb.vmware.com/s/article/1027707]]+[[https://kb.vmware.com/s/article/1027707|VMware KB 1027707 - Invalid state]]\\ 
 +[[https://kb.vmware.com/s/article/1003490|VMware KB 1003490 - Restart management agents]]\\ 
 +[[https://kb.vmware.com/s/article/2004746|VMware KB 2004746 - Activate SSH]]\\
  
 ==== No coredump target has been configured ==== ==== No coredump target has been configured ====
Line 229: Line 231:
 To fix the logrotate/cron, check [[https://kb.vmware.com/s/article/2149278|VMware KB 2149278]] To fix the logrotate/cron, check [[https://kb.vmware.com/s/article/2149278|VMware KB 2149278]]
  
-==== The operation is not allowed in the current state ====+==== Restore from different datastore ====
  
-Remove-Snapshot  The operation for the entity "HOSTNAME" failed with the following message: "The operation is not allowed in the current state."+A VM is broken and needs to be restored. To do so you need to copy the VM from the backup datastore to your productive one \\
  
 __Reason:__ \\ __Reason:__ \\
--+You dont want to run VMs from your backup datastore \\
  
 __Fix:__ \\ __Fix:__ \\
 +Connect to your esx host via ssh and copy the files with "cp" or "vmkfstools"\\
 +Make sure you either rename your old .vmdk + flatfile to .old or your restore to something different (rename flat in .vmdk)
 +<code bash>
 +cp -a myvm.vmdk /vmfs/volumes/prod_datastore/myvm/myvm.vmdk
 +cp -a myvm-flat.vmdk /vmfs/volumes/prod_datastore/myvm/myvm-flat.vmdk
 +</code>
  
-Connect to the ESX-host via SSH and restart the management agents +With vmkfstools you dont need to edit the flat name inside .vmdk, the tool does this for you if you choose another name 
- +<code bash
-<code> +vmkfstools -i myvm.vmdk /vmfs/volumes/prod_datastore/myvm/myvm.vmdk
-/etc/init.d/hostd restart +
-/etc/init.d/vpxa restart+
 </code> </code>
  
-[[https://kb.vmware.com/s/article/1027707|VMware KB 1027707 - Invalid state]] +\\
-[[https://kb.vmware.com/s/article/1003490|VMware KB 1003490 - Restart management agents]] +
-[[https://kb.vmware.com/s/article/2004746|VMware KB 2004746 - Activate SSH]] +
vmware/troubleshooting.txt · Last modified: 2022/09/03 16:27 by lunetikk