I am not entirely certain, but I would guess that either the bootup or shutdown process(es) are getting interrupted/corrupt, and perhaps a file is not getting written to properly that is used for the bootup initialization?
Iām finding my VM (under Proxmox) reboots having taken the steps above. I see a sys log message mentioning āfailed to start QEMU agentā. I havenāt updated my instance for some time now. Iām not sure what could be causing this failure.
In case it helps anyone, the problem for me was caused because the disk was full. I enlarged the VMs disk within Proxmox, followed steps above, and HA came back up.
Hello Guys and thanks! this is my first post here. Today had same problem.
Following the mbielech5 procedure it seems to start but after some strings loading it restarts again and go back to Autoboot Screen. Theres no way . I use VMware in windows 10. I thought to reinstall all again but i need my HA backup and dont know how to get it if i cant start VMā¦ Had a lot of scenes setted and addons, i dont wanna start again from 0. Any suggestion?
is not free! with VMFS Recovery i found the HA backup i need inside the vmdk but to save it it asks for registered version!! How can i extract it from the vmdk file without paying?
I assume you have tried to reboot, windows, And also make sure windows is updated ā¦ Specially if you havenāt configure windows Anti-malware to exclude the disk you have your WM- .vmdk and .vmem files.
EDIT: Anti-malware and Anti-virus systems do āpeakā in ācompressed/containerā files , and windows give A.S if itās your Home-Surveillance system files
Windows Antimalware can lock( During itās āSearch/Checkā ) the .vmdk or .vmem files, can usually occur during boot of the image
Not that i know this is related, but could be worth a try, and to have in mind ā¦ i.e there is no reason for either antimalware or antivirus programs to ācheckā these files, or the whole drive for that matter, itās just a big risk
PS: if it doesnāt help, and the .vmdk is not corrupt, you can open it with 7-zip
You find your files in 7.hassos-data.img /supervisor ā¦ just double-click on .img