The sdcard of a standard Raspbian installation will likely become unbootable with multiple and repeated power interruptions. Each time an unscheduled interruption happens, the filesystem will need to be rebuilt by playing back log files and possibly scanning the entire sdcard. If you are particularly unlucky, the wear leveling microcontroller in the sdcard itself could enter an inconsistent state. This is the opposite of a reset to a known-good initial state that you want when the system locks up.dirthurts wrote:I was wondering, has anyone actually damaged a Raspberry Pi by pulling the power?
Code: Select all
/dev/mmcblk0p2 / ext4 defaults,noatime,commit=1 0 1
If you read the whole thread I linked to earlier you will see after configuring things that the read-only nature of the root filesystem can be turned on and off by changing one or two lines in some configuration files that reside in the /boot partition.dirthurts wrote:So, if I want to make the card read-only, is there a way to reverse this later if I want to edit to it? How would one approach such a magical task as to make a card read only?
I typically run from an nfs mounted root fs. True you'll never corrupt the filesystem itself, but you can still break things by powering off at an inopportune time.Martin Frezman wrote:AIUI (having not actually tried it), if you boot from the network, you don't need to have any media at all on the local machine - i.e., no SD card, no USB (flash drive or hard drive). So, nothing to corrupt...
Yes, it's a much smaller issue. But make sure you don't yank the power on the nfs file server when you are writing files. It can suffer filesystem corruption just like the Pi...Martin Frezman wrote: But you got to admit that corrupted files are basically First World Problems compared to corrupting the fs itself. I.e., you should have a pretty good idea what you were doing when the power went out - and thus have a pretty good idea of what needs fixing.