JsonC Posted May 21, 2022 Share Posted May 21, 2022 (edited) Hello. so the shit hit the fan a few days ago. I started an update to 6.10, ofc i got a power cut probably before the update was finished. all that is sorted and unraid is up and running again, but i cant get my vm to start with homeassistant. i got 2 atm, one old qcow2 file with all my settings. that one freezes with an autoboot- text. After some tampering i tried to download a new file and start from scratch but on that file i get alot of pcie errors and a shell instead. I've tried a regular ubuntu-server vm and that one started and worked flawless. And this is the error from the old one. I really have no clue what to do since I've tried every possible setting i know off in the vm-creation section. Edited May 21, 2022 by JsonC Removed stuff that is not part of the issue Quote Link to comment
Solution ghost82 Posted May 21, 2022 Solution Share Posted May 21, 2022 37 minutes ago, JsonC said: And this is the error from the old one. See if this helps: https://forums.unraid.net/topic/123419-functionnal-vm-wont-boot-anymore-stuck-on-autoboot/ 1 Quote Link to comment
ghost82 Posted May 21, 2022 Share Posted May 21, 2022 40 minutes ago, JsonC said: haos_generic-aarch64-8.1.qcow2 About the new one I think you downloaded the wrong version, that is for arm64 architecture, you need x64. Quote Link to comment
JsonC Posted May 21, 2022 Author Share Posted May 21, 2022 5 minutes ago, ghost82 said: See if this helps: https://forums.unraid.net/topic/123419-functionnal-vm-wont-boot-anymore-stuck-on-autoboot/ This worked. i've spent like 2 hours on google and did not find that solution. thanks ALOT! ❤️ 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.