Yellow HAOS EMMC vs M.2

Configuration
,
1

Looking for some assistance with my Yellow, I know it’s not being manufactured anymore, though I’m hoping to get some support for it.

Every time I update HAOS, I need to restore my entire instance from backup.

I do have a CM5 with the onboard EMMC (not in use), and an M.2 SSD running HAOS.

My suspicion here is that the HAOS update is getting installed on the EMMC and not on the M.2, then when it reboots, it’s defaulting to the EMMC, and since it’s now bootable, it doesn’t look for an OS on the M.2.

I’d like some help getting to the bottom of this, and hopefully eliminating the issue, so I can at least get a year of use out of the Yellow before moving to some other supported & maintained platform.

Please assume I know my way around the innards of Linux, the kernel, and low level engineering, I work with similar systems for a living, and am happy to get my hands dirty. More than happy to connect a serial console and get into it; with hopes that we can reach a working resolution, and I can update the OS without a restore.

What logs or info would anyone need to get started?

2

With image based installation methods, it’s typically not good if you effectively write the same image (with the same filesystems UUIDs) to different media connected to the same system. Therefore I’d probably probably clear the internal eMMC completely (in the sense of wipefs -a /dev/mmc...) and then restoring (also rewriting) only the M.2 SSD first. Maybe it helps - disclaimer, this is just shooting int the dark for a quite likely issue, but I don’t have personal experience with the yellow or the RPi ecosystem, so maybe it isn’t a problem here.