Finally got around to installing HA on my Potato only to get greeted with, “Hi thanks for installing, we’re deprecating this install…”
I’ve already got HA on a Synology Docker container and wanted to use add-ons so I turned to to the potato.
As much as I loathe a custom/locked down OS (ironically like the Synology) I’m wondering if there has been any testing with the HAOS images?
I tried " haos_generic-aarch64-16.1.img.xz" out of ignorant desperation but she don’t boot.
After flashing the image, try flashing the bootloader for the specific board using libretech-flash-tool. If it’s a generic UEFI ARM64 target, it should work if they didn’t change the ARM defconfig for kernel too much.
Thanks.
Unfortunately I think I’m doing something wrong.
Originally I had written the SD Card with win32imager, I then took it over to a linux Mint box to run the flash tool.
Before the tool, the card had 8 partitions that linux saw, after flash tool it had nada. Put it in the potato, it posts, but finds no bootable partition.
I then retried the image on Mint using USB Image Writer which gave me the same post-image write condition where I have sdb with 8 different sub volumes.
I tried pointing flash tool at sdb1 and it barked about it not being a valid target.
cmd I ran:
sudo ./lft.sh bl-flash aml-s905x-cc sdb
The board is labeled the above chipset v1 so I believe I’ve got the right board target.
Again the image I initially hit it with is haos_generic-aarch64-16.1.img.xz from here: Releases · home-assistant/operating-system · GitHub
It might be using GPT partition tables. If that’s the case, try erasing and flashing just the bootloader onto a MicroSD and flashing the generic image on a USB. The board will boot from MicroSD and load the OS from USB.
I understand where you’re going, but not sure how to get there.
I took a look at it using WinImage and there was only one partition available to look at:
So I’m not sure how to just write the boot partition; the thought I had was write one out and delete all but the boot so I took a look with fdisk and two things stood out. It’s listed as EFI and fdisk complained about the table size mismatch:
GPT PMBR size mismatch (12582911 != 15564799) will be corrected by write.
Device Start End Sectors Size Type
/dev/sdb1 2048 67583 65536 32M EFI System
/dev/sdb2 67584 116735 49152 24M Linux filesystem
/dev/sdb3 116736 641023 524288 256M Linux filesystem
/dev/sdb4 641024 690175 49152 24M Linux filesystem
/dev/sdb5 690176 1214463 524288 256M Linux filesystem
/dev/sdb6 1214464 1230847 16384 8M Linux filesystem
/dev/sdb7 1230848 1427455 196608 96M Linux filesystem
/dev/sdb8 1427456 4048895 2621440 1.3G Linux filesystem
So first I tried just saving so fdisk fixed the size. no post
Then I deleted all but sdb1. no post
I’m back to, “I’m doing this wrong” I think.
I think the suggestion was to
On boot, it should read the bootloader from the SD card. The bootloader will then go through its list of possible boot sources and should find the USB drive and boot your OS from there.
Thanks Tiki, I guess I just don’t understand what you’re getting at with #2 then.
ETA: I don’t know how to ‘write just a bootloader’
Use the libre flash tool to flash the bootloader to a blank SD card.
OH, what libre tried telling me in the very first post that I clearly wasn’t picking up on….got it.
It doesn’t ‘auto’ boot, it loads grub, efi_mgr scans and finds none, there’s a line about bootflow ‘’ and then booting with and dumps me on the grub command line.
From reading and errors I get it wants a kernel, what file is that? The first 2 partitions have:
-rwxr-xr-x 1 root root 27 Aug 13 05:00 cmdline.txt*
drwxr-xr-x 3 root root 2048 Aug 13 05:00 EFI/
/EFI/
total 20
drwxr-xr-x 3 root root 2048 Aug 13 05:00 ./
drwxr-xr-x 3 root root 16384 Dec 31 1969 ../
drwxr-xr-x 2 root root 2048 Aug 13 05:00 BOOT/
/EFI/BOOT/
total 798
drwxr-xr-x 2 root root 2048 Aug 13 05:00 ./
drwxr-xr-x 3 root root 2048 Aug 13 05:00 ../
-rwxr-xr-x 1 root root 806912 Aug 13 05:00 bootaa64.efi*
-rwxr-xr-x 1 root root 2216 Aug 13 05:00 grub.cfg*
-rwxr-xr-x 1 root root 1024 Aug 13 05:00 grubenv*
and
drwxrwxrwx 2 1001 128 28 Aug 13 05:00 ./
drwxr-xr-x 4 root root 4096 Aug 23 14:52 ../
-rw-r--r-- 1 1001 128 41847296 Aug 13 04:54 Image
All examples I see are referring to /vmlinuz which doesn’t exist that I’ve found.
Can you post a photo or a few photos of the boot error? It will help us let you know what the issue is.
Type normal in the grub console and see if it goes through. If not, grub is broken on the HA image.
Seems broke then or I’m using the wrong image.
16.2rc2 is out, I’ll give that a whirl.
ETA: Nope, same. I gotta be doing something wrong or have the wrong image.
Your best bet is to raise an issue on their repo and the put the link between this thread and that thread on both places. This helps us track and assist to fix the issue since HA is an external non-upstream project with respect to how they have their images configured.
Roger that, will do.
