There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved.
If this issue is still relevant, please let us know by leaving a comment 👍
This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

The issue still persists regarding the documentation, suggesting the use of Balena Etcher.
Since the described way lead to errors and questionable behaviour, the documentation should be updated.
I'm more than happy to support to this, just tell me what to do.

Not stalled.

I had this exact issue. Flashing got to 32% for me, but as HAOS appeared to boot fine, it looked like the flashing completed, and perhaps it was just a graphics issue that meant the screen wasn't updating. In fact it absolutely didn't complete. The most noticeable issue was DNS not working properly, but adding DNS servers didn't fix it.
The problem appears to be with Balena Etcher. I tried multiple Live OS's, and various methods. In the end, following this guide actually worked:

https://community.home-assistant.io/t/how-to-install-home-assistant-on-generic-x86-64-using-live-os/567210

Note that this guide seems to install a different (older) version of Balena Etcher, and despite a number of errors during install, it works fine and writes the image to the disk without any errors.

Definitely worth mentioning it in the guide that if you do not see Balena Etcher flash to 100% and verify, then it likely hasn't worked, even though the OS may boot and look ok. I suspect there are quite a few people out there with slightly knackered installs due to this one.

@DamianosS I was able to reproduce the problem and this is really very curious 😅

So I think for one, it just seems that balenaEtcher is not a good fit for Ubuntu 22.04, at least when using the Live version. It requires libfuse2, and then crashes as it seems 🙈

The outcome of the whole situation is really interesting, it seems that balenaEtcher corrupted the CoreDNS binary inside the DNS plug-in on Home Assistant, which lead to those DNS issues people have reported 🤯 .

In any case, It think the better approach here is to use the built-in "Disks" utility of Ubuntu. The main reason the guide is using balenaEtcher is since it is available on all platform (in case people flash it from a host using USB-to-S-ATA adapter) and it supports verify (however, that is moot point since it crashes 🙈 ). So this means we have to split the guides in two separate flows.

USBimager does look interesting. What don't like too much is that it doesn't support AppImage and uses x11 by default on Linux.

@agners, I see your point. However, since the documentation suggests Ubuntu Live as the jump-off point, and Balena Etcher gives userd a hard time, shouldn’t it suggest the USBimager alternative?

@DamianosS USBImager would probably work too, but Ubuntu has a built-in tool called Disks which even can handle xz images directly. Initially we did not use that tool because it adds another flow to document. But given the problems, I think this is the best option as it doesn't require installing anything additionally.

@c0ffeeca7 created a PR adjusting the documentation in #29997.

Agree. If there’s a build-in tool, so the user wouldn’t need to download anything, it’s of course the preferable way! Thanks a lot, @agners!

Resolved by #29997