Stuck on Reboot at HASSOS Boot Menu

[gdreelin]

Whiskerz007 I followed your setup of Proxmox on a NUC from DrZZz videos to the letter and all went great. I did the same thing for loading HASSIO on to Proxmox using your script and it beautifully added the container and all was good. I had to make a hardware change to add a USB but when I restarted the container it loads then shows a "HASSOS Boot Menu" which it just sits there. I tried autoboot and nothing. I chose option 2 and it reboots but goes right back to that menu again. Any idea on this? I deleted the container four times now and rebuilt HA from backups but each time I reboot the container in Proxmox it kills Hassio.

[gdreelin]

I think I figured out the issue. When I did the resize on the disk size I did not run those commands you had a the bottom and I thing it was screwing it all up. I am going to run more tests.

[gdreelin]

Well that did not work. Rebooted and got that same menu again. It only happens if you reboot the host not HA. Not sure what I am missing here.

[cannotdraw]

I had this same issue. I got frustrated with it, so I was about to just wipe the vm disk and the vm, when I think I went into the shell, and after various --help type menus, I found:

The Issue: Max number of failed boot attempts reached- causing system to halt/prevent further attempts to boot.

Boot System 0's information had a property that reads something like: 'Number of failed boot attempts=3' and 'Halt boot/Cancel boot if failed boot limit reached' ...or something to that effect anyway.

My Theory: I had set my hassos host VM to start 'On Boot' of the Proxmox host, however since I'm still new to Proxmox, and linux, I've reset the Proxmox host several times, 3+ of those reboots were either hard resets, power loss, or soft-reboots that stopped the VM before it had finished booting, resulting in hassos to incorrectly infer that the incomplete/failed boots were due to an issue with itself, as its unaware that it is running on a hypervisor. (probably because hassos itself is a 'supervisor')

My Solution: Edit the number of max failed boot attempts before halting. When I tried to do that, I think the edit help menu said something about being able to reset the failed boot count, ignore it, or just increase the number of failed boots. I did the latter I'm pretty sure, and increased the failed boot count that prevents further attempts to the max which I think I tried to set to 999, or 99.

My Apologies: Sorry in advance for not having a more accurate/detailed description, I was just so frustrated that day that I was just trying anything, and when I got it to boot after that I was so excited that I didn't think about it till just now that I saw your post. Also, as I'm new to Linux, Proxmox, and Hassos/David/HasselhoffOS/HomeAssistant/HA-stop laughing at me/hasselingmeOS I'm still very much at the base of a few learning curves. Hope this helps.

[whiskerz007]

Thank you for following up. This could be useful for someone else.

[RebbePod]

I'm having the same issue, @cannotdraw I don't understand your solution, where is the option to increase the fail boot attempts? I'm running proxmox on a old laptop running a Intel Pentium Dual T2410, which it doesn't seem to support KVM, could that be the issue? What happens by me is, my first time starting up the VM after running the script, it gets stuck and I had to shut it down, and then it runs but gets into the above issue

[cannotdraw]

tbh I don’t remember exactly how I got to that menu, all I know is that it was accessible from the prompt that the system had left me on when it failed to fully boot.

However, I eventually got into the same situation again, and was unable to resolve it, so I ended up just re-running the whiskerz007 script when a new version of HassOS was released and starting all over. I can tell u, it was well worth starting all over with version 3.9 I believe. What version are you currently on? The newer versions of HassOS such as 4.10 are a breeze to setup, way quicker in every stage of deployment and setup. Not to mention the overall stability that comes from a non-upgraded system and fresh-install.

How is your VM configured?

This is my vm is configured using UEFI and q35 for the bios and machine fields respectively

As for the lack of kvm support, yeah you def need that to run proxmox as far as I understand it.

On Jun 18, 2020, at 11:50, n1rvn notifications@github.com wrote:

I'm having the same issue, @cannotdraw https://github.com/cannotdraw I don't understand your solution, where is the option to increase the fail boot attempts? I'm running proxmox on a old laptop running a Intel Pentium Dual T2410, which it doesn't seem to support KVM, could that be the issue? What happens by me is, my first time starting up the VM after running the script, it gets stuck and I had to shut it down, and then it runs but gets into the above issue

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/whiskerz007/proxmox_hassos_install/issues/33#issuecomment-646164561, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGGJUJFN7NUNYU5XBIBRWMLRXJAT5ANCNFSM4I3QVJBQ.

[RebbePod]

I'm trying to set up a fresh install so i believe it's using HA 4.2. I guess it's not worth it considering my lack of KVM support

[cannotdraw]

Just run it on bare metal. To do so download the Intel-NUC version, as its just an x86-x64bit mini-machine, so the image should be compatible with any 64 bit x86 CPU. So anything Pentium4(prescott architecture) and up

The other option is to run it within VirtualBox which doesn’t require kvm support, and is compatible with whatever OS you happen to be running on your Pentium Dual (Windows, Linux, MacOS, etc)

The last option, and probably the best option actually would be to look into upgrading the CPU. The Pentium Dual T2410 is a Socket P mobile CPU. I believe I had an old Dell E1505 or something along those lines from that era (my favorite machine from that era except for the MacBookPro 3.1) anyway, I had one E1505 with a celeron, and another with a Pentium Dual or perhaps even a Core Solo. Anyway, I was able to upgrade both machines to a Core2Duo T7300 which is a 2.2GHz 3mb of l2 cache, and supports intel Virtualization Technology. I think its the most basic form of virtualization but should be enough to support kvm as long as you also update your bios and enable the virtualization option in the bios. Note: most times the Virtualization option will only appear in the bios when you have a cpu installed that is capable of supporting that function. If you look for it in your bios now the option probably won’t even appear since your current cpu doesn’t support it. I think I paid maybe $20 bucks back in the day for that CPU, and the second machine I bought one for I did that swap last year, and I found the CPU on eBay for about $6 free shipping. I even did the make an offer so I got it down to like $5 plus tax.

Its the easiest swap to do, and totally worth saving a perfectly good machine from the trash by making it a cheap proxmox server like ur trying to do it sounds like.

On Jun 18, 2020, at 15:42, n1rvn notifications@github.com wrote:

I'm trying to set up a fresh install so i believe it's using HA 4.2. I guess it's not worth it considering my lack of KVM support

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/whiskerz007/proxmox_hassos_install/issues/33#issuecomment-646295177, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGGJUJFENERPCL2QWYPKKLDRXJ337ANCNFSM4I3QVJBQ.

[RebbePod]

I appreciate the response, you reminded me that I had an old mac-book pro which surprisingly has 8GB RAM and kvm support, so I'm going to try setting that up with VirtualBox, will see how that goes.