I’ve recently read about how to fix corrupted SD-cards in Raspberry Pis. Corruption can happen when the Pi is unexpectedly losing power during a write to the SD card.
To avoid corruption, you can change the (boot partition of the) SD to read-only, requiring either USB storage (flash/HDD/SSD) or a writable secondary partition on the SD card) if you need to save anything locally. The system itself will run fine without write access. Only your files could be at risk if you lose power mid-write.
You can also configure your system to boot from USB storage instead of SD card. Keeping the system partition read-only is probably still a good idea, if possible in your setup.
Modern versions of raspi-config offer a similar read-only overlayFS functionality out of the box! sudo raspi-config, go to Advanced Options, then enable the Overlay FS: Enable/Disable read-only filesystem feature.
It wasn’t ever an issue of power or corruption. It was hitting the rewrite limit of the SD card itself. I had it on a UPS with my other network equipment and maintained a 100% uptime other than intentional outages with clean reboots. Literally wrote so much log info the card would die. You could still read the card but writing would no longer function.
The suggestion to do a read-only setup would be optimal, I’d prefer it be ram based though as I wouldn’t have such dire need of logs that losing them during a power cycle would cause me any grief.
I stopped using my Pihole because it kept eating SD cards. If that wasn’t an issue would love to be using it still.
I can recommend
for that. It logs to RAM and only writes to the SD card once a day (or more/less, if you choose).
It’s a must while using PiHole imo.
You formatted your links as images. Markdown uses  for images, […](…) for links.
I appreciate the links to log2Ram. I’ll try when I get a new pi.
I’ve recently read about how to fix corrupted SD-cards in Raspberry Pis. Corruption can happen when the Pi is unexpectedly losing power during a write to the SD card.
To avoid corruption, you can change the (boot partition of the) SD to read-only, requiring either USB storage (flash/HDD/SSD) or a writable secondary partition on the SD card) if you need to save anything locally. The system itself will run fine without write access. Only your files could be at risk if you lose power mid-write.
You can also configure your system to boot from USB storage instead of SD card. Keeping the system partition read-only is probably still a good idea, if possible in your setup.
Source: Shane S. @ https://raspberrypi.stackexchange.com/questions/7978/how-can-i-prevent-my-pis-sd-card-from-getting-corrupted-so-often
It wasn’t ever an issue of power or corruption. It was hitting the rewrite limit of the SD card itself. I had it on a UPS with my other network equipment and maintained a 100% uptime other than intentional outages with clean reboots. Literally wrote so much log info the card would die. You could still read the card but writing would no longer function.
The suggestion to do a read-only setup would be optimal, I’d prefer it be ram based though as I wouldn’t have such dire need of logs that losing them during a power cycle would cause me any grief.
I had that issue too. Had to switch to running it on my NAS.
High endurance rated cards are good for that. Don’t risk using the cheap SD cards