I am trying to install HAOS 10 (Generic x86-64) using this image: haos_generic-x86-64-10.0.img.xz, but when I boot the USB drive I keep getting this message on kernel load:
[ *** ] A start job is running for HAOS swap (7min 18s / no limit)
The kernel does not load, it waits forever for the job to complete.
I tried with balena etcher and dd created USB drives but I got the same result. I also tried to add noresume bootloader parameter but without success.
Debian Live USB boots without any problem on the same system. The system consists of an ASRock J4125B-ITX with Intel Celeron J4125 CPU, 8GB of RAM and a 480GB SSD.
I would like to have HAOS installed on the SSD.
Are there any steps or prerequisites that I missed to install HAOS?
Will this PC be running Home Assistant only? (This is the only way I know to run HAOS). I don’t either need nor want to mess with virtual machines or docker images. (Yes, I know that HAOS is a Docker image, but the user does not have to manage it).
I have installed HAOS on a few mini-PCs including two Intel NUCs. What I do is to flash this image (Generic x86-64 - Home Assistant) directly on the SSD, then install it back into the NUC and- done.
Here is from my notes:
“The NUC image on the Home Assistant site is not bootable. Flash the image to your hdd/SSD directly. I used an M.2 USB adapter and flashed to the M.2 drive, and after reinstalling the M.2 into the NUC, Home Assistant boots.”
Is the HAOS distribution image not a bootable installer by design? I think I am having a similar issue where HAOS boots and runs from the USB but does not install into the computers media.
After a long wait I get the Home Assistant CLI. I was expecting something similar to an “Ubuntu Live USB” but maybe that’s not expected.