-
Notifications
You must be signed in to change notification settings - Fork 4
Description
I've been using RPi for some home automation work, and have run into one issue that this project should consider.
Every once in a while a Pi becomes unbootable because of corruption on the SD card. This can happen because of improper shutdown on power loss, but also might result from a lot of writes to the SD card.
Sometimes an fsck will fix the card, but I've had a couple that I couldn't fix. If it can be fixed, there may be some data lost.
In a home setup you can make this less painful by making a backup image of each SD card, including all of the local configuration for the Pi, so that you can just crank out a new SD card if the old one dies.
In a remote setup this is obviously more of an issue.
Some things that I think could be done by MMRA to reduce problems (these wouldn't be mandatory for the public project, as they would increase costs):
- Explore booting from a USB device. This may still be experimental and might only work on a RPi 3, see this link: https://www.raspberrypi.org/blog/pi-3-booting-part-i-usb-mass-storage-boot/
- Store all the critical configuration on USB storage, so that if the card goes bad less is lost. Still requires someone to go to the site to swap the SD card.
- Make sure the PI power has some battery backup, reducing the chance for file corruption.
- (Probably not realistic) Have a failover Pi for each online one
There are other single-board computers that can boot from SATA drives, but this would drive up the costs a lot and none of these are nearly as standard as the RPi.