I currently start using different Raspberry Pis to monitor my (Wi-Fi) network. (OS: Raspbian)
Unfortunately one Pi often corrupts the SD Card and I definitely don't just plug off the power cable. It must be something else.
Since I'm starting to do this, I try different things to setup the pis. One is the manipulation of the /boot/config.txt
but only for video options (which was, together with a reboot, the last thing I did before the file system got corrupted the last time).
Here is why I want to change this:
Because the raspberry pis should do their work automated, I don't have a monitor plugged in all the time. I want to set the HDMI hot-plug on, so that I can check the Raspberry Pi even when there is a problem with the network and ssh won't work.
Since hdmi_safe=1
doesn't fit my monitor resolution that good, I changed the entries manually.
Here is my configuration:
Disable_overscan=0
Hdmi_force_hotplug=1
Hdmi_group=2
Hdmi_mode=28
Hdmi_drive=1
Config_hdmi_boost=4
The question:
Is it possible that I accidentally wrote something wrong into the config file, which lead to the corruption of the SD card or is there anything else which could cause this pi to corrupt the SD card? Sorry if this is a silly question/problem but Google didn't help me and I don't really know whats the problem because another pi didn't corrupt the file system even once.
By the way: the video configuration didn't even do what I want it to do. The console should have a resolution about 1280x800...
Update: I use the SanDisk 8GB Extreme Pro (Class 1) SD cards, and yes I did try different SD cards of this type.
Update2: I assume, that the card is corrupted, because either while I want to perform different commands or at boot up there are suddenly a lot of error messages, which come so fast, I even can't read them, and I won't be able to do anything else again but perform a new installation/write my backup again on the SD card. And I did try both options. The odd thing is, this happens (at least until now) only to one of my Raspberry Pis. And I put them all into cases right after unpacking it, so I don't assume the Pi is really damaged.
fsck
says it is so. If you are assuming it is corrupt for some other reason -- e.g. it won't boot properly -- there could be some other cause. You need to explicitly rule that out.