[SOLVED] M1 not booting from eMMC

[tompod]

I am trying to install Home Assistant OS on my new M1 but I do not get it to boot from eMMC. This is what I did so far:

2. Installed a Samsung NVMe in the M1.
2. Updated Petitboot to version 20230328 by placing "spiboot.img" on a microSD card and rebooting the M1. It found the new image and installed it. I did not use "spiupdate_odroidm1_20220304.img.xz" because it did not create an additional FAT partition through the balena etcher image process where I cloud place "spiboot.img". So I just tried to FAT format a microSD card by myself an put the spiboot.img onto it and booted the M1. Petitboot found the new image and updated it.
3. Removed microSD card.
4. Put Home Assistant OS image on the eMMC with balena ether and mounted the eMMC in the M1.

When I boot the M1 Petitboot is showing up in version 20230328 but Petitboot is stuck in "waiting for device discovery" fowever. No other menu items like show configuration or show system info work as well. When I boot the M1 with the recovery switch pressed Home Assistant OS is starting up from the eMMC without problems. Home Assistant OS is also able to see the NVMe.

When I remove the eMMC, Petitboot starts up and all menu items are usable.

Did anyone experience and solve the same problem? Why is Petitboot stuck in discovering devices and all menu itens are disfunctional? Is there an issue as I did not use "spiupdate_odroidm1_20220304.img.xz"?

Any help is very much appreciated.

[mad_ady]

So, do you want to run HAOS from the emmc with the NVME drive as extra storage? If yes, you'll need to leave emmc in and bypass petitboot from the switch. Once HAOS is installed (on the emmc) you can use the web gui to format and use the NVME drive. It will be used for volatile storage, data collection, etc. But the main OS will still boot from emmc.
The HA team did not release any image capable to boot only from NVME via petitboot.

However, plan B allows you to run HA from nvme, without an emmc. It involves installing Debian to nvme and installing HomeAssistant supervised on top.

[Markinton]

I had the same problem and solved it, see
viewtopic.php?p=370637#p370637

[tompod]

So, do you want to run HAOS from the emmc with the NVME drive as extra storage? If yes, you'll need to leave emmc in and bypass petitboot from the switch. Once HAOS is installed (on the emmc) you can use the web gui to format and use the NVME drive. It will be used for volatile storage, data collection, etc. But the main OS will still boot from emmc.
The HA team did not release any image capable to boot only from NVME via petitboot.

However, plan B allows you to run HA from nvme, without an emmc. It involves installing Debian to nvme and installing HomeAssistant supervised on top.

The NVME is not the problem. The M1 refuses to detect the eMMC automatically. If I bypass Petitboot by pressing the recovery switch, Home Assistant OS is booting fine from the eMMC. Petitboot is completely disfunctional when the eMMC is plugged in. None of the system menues work and Petitboot hangs while discovering devices.

[tobetter]

So, do you want to run HAOS from the emmc with the NVME drive as extra storage? If yes, you'll need to leave emmc in and bypass petitboot from the switch. Once HAOS is installed (on the emmc) you can use the web gui to format and use the NVME drive. It will be used for volatile storage, data collection, etc. But the main OS will still boot from emmc.
The HA team did not release any image capable to boot only from NVME via petitboot.

However, plan B allows you to run HA from nvme, without an emmc. It involves installing Debian to nvme and installing HomeAssistant supervised on top.

The NVME is not the problem. The M1 refuses to detect the eMMC automatically. If I bypass Petitboot by pressing the recovery switch, Home Assistant OS is booting fine from the eMMC. Petitboot is completely disfunctional when the eMMC is plugged in. None of the system menues work and Petitboot hangs while discovering devices.

You must update the Petitboot with "spiupdate_odroidm1_20220304.img.xz" as instructed HAOS Wiki, otherwise it won't boot from eMMC except the recovery switch is pressed.

[tompod]

So, do you want to run HAOS from the emmc with the NVME drive as extra storage? If yes, you'll need to leave emmc in and bypass petitboot from the switch. Once HAOS is installed (on the emmc) you can use the web gui to format and use the NVME drive. It will be used for volatile storage, data collection, etc. But the main OS will still boot from emmc.
The HA team did not release any image capable to boot only from NVME via petitboot.

However, plan B allows you to run HA from nvme, without an emmc. It involves installing Debian to nvme and installing HomeAssistant supervised on top.

The NVME is not the problem. The M1 refuses to detect the eMMC automatically. If I bypass Petitboot by pressing the recovery switch, Home Assistant OS is booting fine from the eMMC. Petitboot is completely disfunctional when the eMMC is plugged in. None of the system menues work and Petitboot hangs while discovering devices.

You must update the Petitboot with "spiupdate_odroidm1_20220304.img.xz" as instructed HAOS Wiki, otherwise it won't boot from eMMC except the recovery switch is pressed.

Does "spiupdate_odroidm1_20220304.img.xz" do anything else than updating Petitboot? Petitboot updated itself to the latest version (with eMMC support) when I copied the new image file to an microSD. I did this without "spiupdate_odroidm1_20220304.img.xz" because on my Windows 11 PC the imager did not create a visible FAT partition, where I could copy the image file to as written in the description.

[tobetter]

So, do you want to run HAOS from the emmc with the NVME drive as extra storage? If yes, you'll need to leave emmc in and bypass petitboot from the switch. Once HAOS is installed (on the emmc) you can use the web gui to format and use the NVME drive. It will be used for volatile storage, data collection, etc. But the main OS will still boot from emmc.
The HA team did not release any image capable to boot only from NVME via petitboot.

However, plan B allows you to run HA from nvme, without an emmc. It involves installing Debian to nvme and installing HomeAssistant supervised on top.

The NVME is not the problem. The M1 refuses to detect the eMMC automatically. If I bypass Petitboot by pressing the recovery switch, Home Assistant OS is booting fine from the eMMC. Petitboot is completely disfunctional when the eMMC is plugged in. None of the system menues work and Petitboot hangs while discovering devices.

You must update the Petitboot with "spiupdate_odroidm1_20220304.img.xz" as instructed HAOS Wiki, otherwise it won't boot from eMMC except the recovery switch is pressed.

Does "spiupdate_odroidm1_20220304.img.xz" do anything else than updating Petitboot? Petitboot updated itself to the latest version (with eMMC support) when I copied the new image file to an microSD. I did this without "spiupdate_odroidm1_20220304.img.xz" because on my Windows 11 PC the imager did not create a visible FAT partition, where I could copy the image file to as written in the description.

FYI, viewtopic.php?p=370632#p370632

[tompod]

Problem solved. I installed Ubuntu on the NVMe which was also in the odroid m1 system for later use as the home assistant data disk.

With that I could access the patition on the microSD card prepared by etcher and copy "spiboot.img" onto it. Booted the Odroid M1 from the microSD without the eMMC installed and the petitboot update worked fine. Reinstalled the eMMC and the system is booting into Home Assitant without any further issues. Thank you for your help!