Hello,
I have finally gotten a CM4 for my Home Assistant Yellow and can finally get it setup. I am coming over from a Blue but have decided to start with a completely clean setup on the Yellow.
I have an 500Gb Samsung NVMe drive that I was, after much finagling, able to get HA installed on. The CM4 has 4Gb of eMMC but I don’t want to use that. I’ve been happy using the system for a few days, config isn’t complete but I’m slowly moving things over… This morning when I was doing some config I noticed that there was a Home Assistant Operating System Update (10.0 IIRC) and decided to run that.
Now, I know what you’re going to say, I should have backed up, and you’re correct but I am not so far along in the new config that I was worried about it. I’m more concerned with the long term stability of the Yellow after experiencing this issue…
Anyway, I ran the update and waited for the Yellow to come back up. When it finally did I was directed to the onboarding page. Where I had to create an account, just as if I had freshly installed HA, no devices, no config. I looked and it seems that the update was installed on the eMMC of the CM4!
So, my question is, can I get back to the install on the NVMe? I don’t really care if I can’t, I’m ok with installing again but I’d like to know how to prevent this issue in the future. Did I do something wrong, am I missing something or is this a bug?
I do not want to use the eMMC, the ability to use proper NVMe storage was one of the main selling points of the Yellow for me.
Thanks,
Adam