Good that you reported back. You wouldn't have had the issue if there would be only 1 image for HAOS Aarc64, but instead, they (or many organizations) create or have to create dedicated images for every board or variant of board or brand or vendor.resolved - I'm embarassed to say this whole time I for some reason had in my head that this was a raspberry pi 5, and it's a pi 4 8gb, not a pi5 8gb.
my apologies, that's such a silly mistake.
but I guess if anyone else is having strange issues like this you may want to re-verify that your model is what you think it is.
Compare to x86, only 1 'image' or 1 'thing' to download/do. HA does or needs the same hypocrisy as RPL, even worse. For RPi5, they only include the 16k pages kernel (and DTBs) (kernel_2712.img). So a RPi4 can't find kernel8.img, standard 64-bit 4k pages kernel everywhere also in normal generic distros. RPi5 can simply work/use that 4k kernel,8.img so a single image for RPi would do. The trade-off is just a joke if you consider the whole HA thing. The OS is custom buildroot, all very compressed and small, but the data it generates is huge. I was just shocked that there is no easy way of down-sampling old time-series data. So '32GB is minimum' is stated. I have an HA test instance that I limit to 6GB space. It is supervised on top of standard Debian (in a KVM), not custom OS with A/B Ext4. I block access to outside internet, so then it stays small. Else watch it pile up old versions etc etc.
Statistics: Posted by redvli — Wed Sep 03, 2025 6:22 am