Try to use overlayfs under raspi-config, I’ve been running some raspberry pis for years with that (mostly on offsite locations where fixing dead sd cards is not possible)
Updating the pis is a little more work but in some use cases it’s worth it
I think something like BTRFS might be a better solution as overlayfs seems to freeze the system image state. Something which is copy on write (COW) seems like it would be more resilient and still provide an RW file system. To do it right would probably be a combination of the two with the data partition BTRFS and the system image partition overlayfs.
Yeah that sounds like a good solution. I think arch based pikvm does something similar. (no reboot necessary to enable rw)
For those pis that need to write stuff, I usually mount a network drive and use that while having the overlayfs enabled. So far haven’t had any issues, only one pi died after 3 years due to faulty power supply.
Try to use overlayfs under
raspi-config, I’ve been running some raspberry pis for years with that (mostly on offsite locations where fixing dead sd cards is not possible)Updating the pis is a little more work but in some use cases it’s worth it
I think something like BTRFS might be a better solution as overlayfs seems to freeze the system image state. Something which is copy on write (COW) seems like it would be more resilient and still provide an RW file system. To do it right would probably be a combination of the two with the data partition BTRFS and the system image partition overlayfs.
Yeah that sounds like a good solution. I think arch based pikvm does something similar. (no reboot necessary to enable rw)
For those pis that need to write stuff, I usually mount a network drive and use that while having the overlayfs enabled. So far haven’t had any issues, only one pi died after 3 years due to faulty power supply.