Home Assistant supervised install on nvme with 6.2 kernel

[glenno]

Ive been running the M1 since April '22 on Debian 10 and its been really stable. I have wanted to move Home Assistant over onto it to take advantage of the durability and performance of the nvme drive.

I had some requirements:
New kernel (preferable 6.x)
New distribution (Debian 10 is just about EOL)
Boot & Root on nvme drive (didnt want to rely on a sd card)
Home Assistant Supervised based installation (fully managed)

After lots of mucking around and dead ends, it turns out the process was really simple in the end. So I wanted to document it so others could use these steps if they need.

• Use Petitboot netboot to install Debian 11 following the bouncing ball (udhcp, netboot_default, exit)

• Install package from the repo "sudo apt-get install linux-image-6.2.0-odroid-arm64". At the time of writing Debian 11 is booting with a 5.x kernel. And 6.2 is in the repo. This will change over time.

• Confirm the machine is stable and doing what you need it to do.

• Follow these instructions to install HA https://peyanski.com/how-to-install-hom ... pendencies

Hope that helps someone else! Obviously we will soon have 6.x vanilla kernels landing in all the distributions which will make this post irrelevant. But in the meantime...

[odroid]

Thank you for sharing the nice and useful instruction.


I have two quick questions before trying it by myself.

<1> Which HA os-agent package did you install?
Was that os-agent_1.4.1_linux_aarch64.deb working fine?

<2> Which machine type did you select when you configured the homeassistant-supervised package?
There is no "ODROID-M1" since HomeAssistan dev team has not supported the M1 board yet.

Screenshot from 2023-02-01 18-08-11.png (34.27 KiB) Viewed 1586 times

[mad_ady]

I'm personally running the odroid-c2 variant on an Odroid N1. It may matter if you're planning on using GPIOs directly from within HA.

[glenno]

Thank you for sharing the nice and useful instruction.


I have two quick questions before trying it by myself.

<1> Which HA os-agent package did you install?
Was that os-agent_1.4.1_linux_aarch64.deb working fine?

<2> Which machine type did you select when you configured the homeassistant-supervised package?
There is no "ODROID-M1" since HomeAssistan dev team has not supported the M1 board yet.
Screenshot from 2023-02-01 18-08-11.png

Yes I used that version of the agent and select the qemuarm64 option.

[glenno]

Thought I would report back after almost a month running the M1 with Home Assistant and my other needs.

Home Assistant Supervised install has been going great. The performance of the NVME drive is outstanding. I can create complex graphs looking at my energy stats and they draw in seconds rather than minutes in the XU4 with an sdcard! iotop shows maximum disk read of 33MB/s and the 4 cpu's run at about 160% (out of 400%) which im pretty happy with. HA updates and add-ons install without issue.

Debian 11 is nice and stable with 6.2 kernel - 6.2.0-202301311607 from the http://ppa.linuxfactory.or.kr/ repo. I run the unit headless, but during setup the HDMI in text console works fine. Only issue is the changing MAC address each reboot, so ive just set a static IP address and will see whether this gets resolved down the track.

Ive installed other apps I had running on other Hardkernel SBC's including SBFSpot to log and upload my solar inverter stats, pla-util to track the performance of my ethernet-over-power adapters, and Smokeping looking at network latency.

Thanks to everyone who has helped make this board and kernel as stable as it is!

[odroid]

Thank you for sharing your successful experiences.
When you have time, please let me know your average RAM usage.

[glenno]

Thank you for sharing your successful experiences.
When you have time, please let me know your average RAM usage.

Hope this helps

Siting idle doing its thing:
MiB Mem : 7449.0 total, 3716.0 free, 1166.0 used, 2567.1 buff/cache

After running a large Home Assistant graphing query
MiB Mem : 7449.0 total, 3033.1 free, 1274.6 used, 3141.4 buff/cache

[odroid]

Thank you for the numbers.
I think a 4GB model will be sufficient for my use cases.

[glenno]

Thank you for the numbers.
I think a 4GB model will be sufficient for my use cases.

Nahhh. always need more!

Bill Gates in 1981 - 640k is enough
HA in 2023 - 8GB is what you need



Especially as without using HAOS you're free to use the M1 for whatever else you want.

[istanbulls]

The latest Home Assistant OS 10 supports the Hardkernel ODROID-M1 single board computer officially!
https://www.home-assistant.io/blog/2023 ... -odroid-m1

[glenno]

YES! This is great to see. Pity my patience was about 2months too short Hah!.

Anyway im still happy running mine unsupported with Docker and doing its other duties. Its interesting the official HAOS is on a 6.1 kernel v's 6.2. But either way its great for adoption of the M1 platform.

[Markinton]

I installed Home Assistant 10.1 on my Odroid M1 8GB, Pettitboot updated to 20230328 via PB-update command in Pettitboot so I can boot from eMMC. First test Home Assistant 10 with a SD-card, went wel. After flashing the 64G eMMC module Home Assistant won't boot from eMMC. It work's when I boot from SD-card. The HA hardware info shows no SD-card and the mmcblk0 /dev/disk/by-id/mmc-CJTD4R_0xc76e5228 as Bootdevice. Any idea why I can not boot directly from eMMC?

[tobetter]

I installed Home Assistant 10.1 on my Odroid M1 8GB, Pettitboot updated to 20230328 via PB-update command in Pettitboot so I can boot from eMMC. First test Home Assistant 10 with a SD-card, went wel. After flashing the 64G eMMC module Home Assistant won't boot from eMMC. It work's when I boot from SD-card. The HA hardware info shows no SD-card and the mmcblk0 /dev/disk/by-id/mmc-CJTD4R_0xc76e5228 as Bootdevice. Any idea why I can not boot directly from eMMC?

I've flashed HAOS image 10.1 for ODROID-M1 to eMMC and after updating the Petitboot to the version v20230328. Without SD card, only eMMC is attached to ODROID-M1, it boots to HAOS - No Petitboot.
https://github.com/home-assistant/opera ... 0.1.img.xz

[Markinton]

I installed Home Assistant 10.1 on my Odroid M1 8GB, Pettitboot updated to 20230328 via PB-update command in Pettitboot so I can boot from eMMC. First test Home Assistant 10 with a SD-card, went wel. After flashing the 64G eMMC module Home Assistant won't boot from eMMC. It work's when I boot from SD-card. The HA hardware info shows no SD-card and the mmcblk0 /dev/disk/by-id/mmc-CJTD4R_0xc76e5228 as Bootdevice. Any idea why I can not boot directly from eMMC?

I've flashed HAOS image 10.1 for ODROID-M1 to eMMC and after updating the Petitboot to the version v20230328. Without SD card, only eMMC is attached to ODROID-M1, it boots to HAOS - No Petitboot.
https://github.com/home-assistant/opera ... 0.1.img.xz

I've did the same, first update the Pettitboot to version 20230328 (on the Pettitboot page that version is shown), Pettiboot update with the PB-update command. Flashed the HAOS image 10.1 for ODROID-M1 to eMMC. Without SD-card inserted (only eMMC) the boot stocks in the Pettitboot screen. With the SD-card inserted it boots from eMMC....

https://github.com/home-assistant/opera ... roid-m1.md

[tobetter]

I installed Home Assistant 10.1 on my Odroid M1 8GB, Pettitboot updated to 20230328 via PB-update command in Pettitboot so I can boot from eMMC. First test Home Assistant 10 with a SD-card, went wel. After flashing the 64G eMMC module Home Assistant won't boot from eMMC. It work's when I boot from SD-card. The HA hardware info shows no SD-card and the mmcblk0 /dev/disk/by-id/mmc-CJTD4R_0xc76e5228 as Bootdevice. Any idea why I can not boot directly from eMMC?

I've flashed HAOS image 10.1 for ODROID-M1 to eMMC and after updating the Petitboot to the version v20230328. Without SD card, only eMMC is attached to ODROID-M1, it boots to HAOS - No Petitboot.
https://github.com/home-assistant/opera ... 0.1.img.xz

I've did the same, first update the Pettitboot to version 20230328 (on the Pettitboot page that version is shown), Pettiboot update with the PB-update command. Flashed the HAOS image 10.1 for ODROID-M1 to eMMC. Without SD-card inserted (only eMMC) the boot stocks in the Pettitboot screen. With the SD-card inserted it boots from eMMC....

https://github.com/home-assistant/opera ... roid-m1.md

Follow up the instruction to update the Petitboot even if you have the version 20230328 of Petitboot.

[Markinton]

I installed Home Assistant 10.1 on my Odroid M1 8GB, Pettitboot updated to 20230328 via PB-update command in Pettitboot so I can boot from eMMC. First test Home Assistant 10 with a SD-card, went wel. After flashing the 64G eMMC module Home Assistant won't boot from eMMC. It work's when I boot from SD-card. The HA hardware info shows no SD-card and the mmcblk0 /dev/disk/by-id/mmc-CJTD4R_0xc76e5228 as Bootdevice. Any idea why I can not boot directly from eMMC?

I've flashed HAOS image 10.1 for ODROID-M1 to eMMC and after updating the Petitboot to the version v20230328. Without SD card, only eMMC is attached to ODROID-M1, it boots to HAOS - No Petitboot.
https://github.com/home-assistant/opera ... 0.1.img.xz

I've did the same, first update the Pettitboot to version 20230328 (on the Pettitboot page that version is shown), Pettiboot update with the PB-update command. Flashed the HAOS image 10.1 for ODROID-M1 to eMMC. Without SD-card inserted (only eMMC) the boot stocks in the Pettitboot screen. With the SD-card inserted it boots from eMMC....

https://github.com/home-assistant/opera ... roid-m1.md

Follow up the instruction to update the Petitboot even if you have the version 20230328 of Petitboot.

I tried to follow the instruction to update the Petitboot, I managed to flash the SD-card with the spiupdate_odroidm1_20220304.img.xz file with balenaEtcher. I use MacOS and can's access the content of the SD-card to paste the spiboot.img file onto the FAT partition of that same SD card. Any id how to access the SD-card with Mac OS or solve that problem? That's the reason I used PB-update to update Petitboot, witch not working....

[tobetter]

I installed Home Assistant 10.1 on my Odroid M1 8GB, Pettitboot updated to 20230328 via PB-update command in Pettitboot so I can boot from eMMC. First test Home Assistant 10 with a SD-card, went wel. After flashing the 64G eMMC module Home Assistant won't boot from eMMC. It work's when I boot from SD-card. The HA hardware info shows no SD-card and the mmcblk0 /dev/disk/by-id/mmc-CJTD4R_0xc76e5228 as Bootdevice. Any idea why I can not boot directly from eMMC?

I've flashed HAOS image 10.1 for ODROID-M1 to eMMC and after updating the Petitboot to the version v20230328. Without SD card, only eMMC is attached to ODROID-M1, it boots to HAOS - No Petitboot.
https://github.com/home-assistant/opera ... 0.1.img.xz

I've did the same, first update the Pettitboot to version 20230328 (on the Pettitboot page that version is shown), Pettiboot update with the PB-update command. Flashed the HAOS image 10.1 for ODROID-M1 to eMMC. Without SD-card inserted (only eMMC) the boot stocks in the Pettitboot screen. With the SD-card inserted it boots from eMMC....

https://github.com/home-assistant/opera ... roid-m1.md

Follow up the instruction to update the Petitboot even if you have the version 20230328 of Petitboot.

I tried to follow the instruction to update the Petitboot, I managed to flash the SD-card with the spiupdate_odroidm1_20220304.img.xz file with balenaEtcher. I use MacOS and can's access the content of the SD-card to paste the spiboot.img file onto the FAT partition of that same SD card. Any id how to access the SD-card with Mac OS or solve that problem? That's the reason I used PB-update to update Petitboot, witch not working....

Power up your ODROID-M1 without any storage, then insert the SD card which is flashed with spiupdate_odroidm1_20220304.img.xz. In the command line of Petitboot, run ums /dev/mmcblk1 after attaching the micro USB cable with your PC, the micro USB port is under the USB host port. Then check your Mac OS if it shows the SD card as USB storage.

[Markinton]

I installed Home Assistant 10.1 on my Odroid M1 8GB, Pettitboot updated to 20230328 via PB-update command in Pettitboot so I can boot from eMMC. First test Home Assistant 10 with a SD-card, went wel. After flashing the 64G eMMC module Home Assistant won't boot from eMMC. It work's when I boot from SD-card. The HA hardware info shows no SD-card and the mmcblk0 /dev/disk/by-id/mmc-CJTD4R_0xc76e5228 as Bootdevice. Any idea why I can not boot directly from eMMC?

I've flashed HAOS image 10.1 for ODROID-M1 to eMMC and after updating the Petitboot to the version v20230328. Without SD card, only eMMC is attached to ODROID-M1, it boots to HAOS - No Petitboot.
https://github.com/home-assistant/opera ... 0.1.img.xz

I've did the same, first update the Pettitboot to version 20230328 (on the Pettitboot page that version is shown), Pettiboot update with the PB-update command. Flashed the HAOS image 10.1 for ODROID-M1 to eMMC. Without SD-card inserted (only eMMC) the boot stocks in the Pettitboot screen. With the SD-card inserted it boots from eMMC....

https://github.com/home-assistant/opera ... roid-m1.md

Follow up the instruction to update the Petitboot even if you have the version 20230328 of Petitboot.

I tried to follow the instruction to update the Petitboot, I managed to flash the SD-card with the spiupdate_odroidm1_20220304.img.xz file with balenaEtcher. I use MacOS and can's access the content of the SD-card to paste the spiboot.img file onto the FAT partition of that same SD card. Any id how to access the SD-card with Mac OS or solve that problem? That's the reason I used PB-update to update Petitboot, witch not working....

Power up your ODROID-M1 without any storage, then insert the SD card which is flashed with spiupdate_odroidm1_20220304.img.xz. In the command line of Petitboot, run ums /dev/mmcblk1 after attaching the micro USB cable with your PC, the micro USB port is under the USB host port. Then check your Mac OS if it shows the SD card as USB storage.

After the command ums /dev/mmdblk1 I get a message on my Mac that it unable to read the attaches drive.. the same error message as SD-card in card reader direct on Mac. Why is PB-update not the solution? It managed to get Petitboot to version 20230328.

[tobetter]

After the command ums /dev/mmdblk1 I get a message on my Mac that it unable to read the attaches drive.. the same error message as SD-card in card reader direct on Mac. Why is PB-update not the solution? It managed to get Petitboot to version 20230328.

There is some part which is not able to be updated via network update, so you need to follow up the instruction of HA documentation.
If you do not have any other OS, then try Ubuntu Live System in the Petitboot. Run netboot_default after udhcpc in the command line, then select "Ubuntu Live System" boot entry in the Petitboot screen, that will load simple Ubuntu server through the network on ODROID-M1 itself. Then you could access the partitions of SD card and copy spiboot.img to it as instructed.

[Markinton]

After the command ums /dev/mmdblk1 I get a message on my Mac that it unable to read the attaches drive.. the same error message as SD-card in card reader direct on Mac. Why is PB-update not the solution? It managed to get Petitboot to version 20230328.

There is some part which is not able to be updated via network update, so you need to follow up the instruction of HA documentation.
If you do not have any other OS, then try Ubuntu Live System in the Petitboot. Run netboot_default after udhcpc in the command line, then select "Ubuntu Live System" boot entry in the Petitboot screen, that will load simple Ubuntu server through the network on ODROID-M1 itself. Then you could access the partitions of SD card and copy spiboot.img to it as instructed.

What filesystem type is on the SD-card? I have a Raspberry Pi 400 and a Microsoft Windows PC, both are unable to read the content of the SD-card.

[tobetter]

After the command ums /dev/mmdblk1 I get a message on my Mac that it unable to read the attaches drive.. the same error message as SD-card in card reader direct on Mac. Why is PB-update not the solution? It managed to get Petitboot to version 20230328.

There is some part which is not able to be updated via network update, so you need to follow up the instruction of HA documentation.
If you do not have any other OS, then try Ubuntu Live System in the Petitboot. Run netboot_default after udhcpc in the command line, then select "Ubuntu Live System" boot entry in the Petitboot screen, that will load simple Ubuntu server through the network on ODROID-M1 itself. Then you could access the partitions of SD card and copy spiboot.img to it as instructed.

What filesystem type is on the SD-card? I have a Raspberry Pi 400 and a Microsoft Windows PC, both are unable to read the content of the SD-card.

If you mean after flashing the spiupdate_odroidm1_20220304.img.xz, it's definitely FAT.

[Markinton]

After the command ums /dev/mmdblk1 I get a message on my Mac that it unable to read the attaches drive.. the same error message as SD-card in card reader direct on Mac. Why is PB-update not the solution? It managed to get Petitboot to version 20230328.

There is some part which is not able to be updated via network update, so you need to follow up the instruction of HA documentation.
If you do not have any other OS, then try Ubuntu Live System in the Petitboot. Run netboot_default after udhcpc in the command line, then select "Ubuntu Live System" boot entry in the Petitboot screen, that will load simple Ubuntu server through the network on ODROID-M1 itself. Then you could access the partitions of SD card and copy spiboot.img to it as instructed.

What filesystem type is on the SD-card? I have a Raspberry Pi 400 and a Microsoft Windows PC, both are unable to read the content of the SD-card.

If you mean after flashing the spiupdate_odroidm1_20220304.img.xz, it's definitely FAT.

Finally it works! I managed to copy spiboot.img file to the SD-card on a Raspberry Pi 4 and flashed te right Petitboot to the M1. HA boots from eMMC! Thank you very much for your help!!!