I am running HA OS on a pi4 and I boot from an ssd.
We all have been there, for one reason or another every update seems to break boot from ssd, and it basically comes down to luck from what I can se. I see people that didn’t have this probelm on some updates where it happened to me and I had no problems with updates that where a pain for a lot of people.
Is there something I can do to make this predictable? Looking at the github I already see some people complaining about this happening
Last time I had this happen to me I just had to set up the eeprom once again and start with a new instance, then backup my old istance. At this point I kind of know what’s happening and I can fix it fairly easily but the whole process still is a 2hour deal out of either my sunday or my sleep schedule
Well, yes, that would work, but I kind of like being up to date. I mean my experience has been fairly straightforward but if I happen to need help I don’t want to be the guy with a year old instance that eventually updated and has half of his stuff not working anymore. Also right now I don’t expose my istance because of unrealted reasons, but I want to do that in the future as accessing HA from remote is useful to me
The experience has nothing to do with the OS. Update everything else. It is similar to running Home Assistant on a NUC, Debian, ect. It is above the OS.
I see… Since my istance is already on an ssd, I am guessing I would have to bring back the boot order to sd first, then migrate my configuration on an sd then do the steps shown in the link you posted.
Functionally would this be any different from what I have right now? Mostly I am thinking, would creating snapshots be any different?
Also I guess the boot times will not be as fast right?
And I am still confused as why would booting from an ssd be so cumbersome to break with every is update
In operation, nothing will change, all will function the same way, boot time should not really be that affected.
SSD’s and their controllers vastly differentiate, while it sounds cool an “easy” it’s really not, and also not recommended, the link I posted is the recommended way to use an SSD with a pi.
I and a lot of others could not get the SD / SSD working with the PI 4 on OSs above 5.4. Many GitHub issues open. Current directions were to stay on 5.4 or below.
SD Boot/SSD Storage indeed sounds like the most sensible solution.
Like @bschatzow said, I also had issues migrating back to SD Boot. Tried like 5 times to be sure that everything ran correctly, but it never worked.
Am now back in SSD Boot until I decide to try again.
I have Hass OS an ssd with boot order sd and then usb. I have no SD card installed, hence it boots from USB. I am confused - how does this break when I update the OS?
I see… installing on SD card (and booting from it) and moving data to SSD as suggested in the installation survives an OS update? Or has this also be done every single time?
Hm… my Raspbian Supervised install NEVER had issues before. I was planning on using HassOS for my brother since I thought it was even more stable, but I might have been wrong about that then.
Mine had been very stable with no issues until the changes made going from 5.4 to 5.5 and beyond. The developers have claimed many reasons (pi4 boot method, controllers, SSD, etc). No one has responded to what they changed and how it effected many people. If you choose a PI4 for your brother go with the 8 G version as most people using this with the SSD are not having any issues. There are many Github open issues with freeze issues and the PI. The open issues go back to November of last year. Mine is very stable as long as I don’t update the OS. There is a major 6.x update being worked on. Hopefully when this is released a fix for the issues will be incorporated.
Many people with the issues moved to a Debian os/ supervised Home Assistant. Their system is very stable also. Not sure if this is a good option for you brother?
