The robustness of RaspiOS to an SSD boot device suddenly disappearing should be about nil. I've never seen an OS survive a vanishing root filesystem.
My predictions:
If the state of the platform as seen by the OS departs from the actual state of the hardware platform, that's trouble. For some categories of devices/protocols, trouble is expected and recovery is made to be graceful, e.g. networking or USB devices. For others, like a root filesystem, reliability is expected and recovery tends to be ugly.
In conclusion, I suppose I'd go the full embedded OS route. In terms of investment I'd say piCore is the lightest and Yocto the heaviest.
HTH
My predictions:
- With RaspiOS in standard mode, if the SSD goes away during a write, the OS will crash and the filesystem might get corrupt. If not during a write, then it should be a simple crash
- With RaspiOS in "read-only" mode, it should cause a simple crash every time
- With an embedded OS like piCore or built from frameworks like Yocto or Buildroot, the OS won't crash if you configure the system to run entirely in RAM. However in case the SSD disconnects during boot, the system will hang or crash (I'd use a watchdog to ensure reboot)
If the state of the platform as seen by the OS departs from the actual state of the hardware platform, that's trouble. For some categories of devices/protocols, trouble is expected and recovery is made to be graceful, e.g. networking or USB devices. For others, like a root filesystem, reliability is expected and recovery tends to be ugly.
In conclusion, I suppose I'd go the full embedded OS route. In terms of investment I'd say piCore is the lightest and Yocto the heaviest.
HTH
Statistics: Posted by epoch1970 — Thu Sep 19, 2024 12:40 pm