I (and I expect many others) made the experience that shutting down the Raspberry Pi without using the shutdown command ("hard kill") often results in data loss on the SD-Card and therefore in unbootable devices. Or as written here:
I think this makes the Raspberry Pi for many purposes usless. Most people (me included) want a raspberry that does sth. in the background and that can be turned on and off whenever needed. E.g. if the Raspberry Pi is used as a additional media-device with your TV: If I go to bed I simply switch off the extension lead where all devices are connected (Raspberry, TV, Receiver, ...). I dont want to log first into the Raspberry Pi and to write "sudo shutdown ...". So I need a "hard kill" functionality.http://www.raspberrypi.org/phpBB3/viewt ... 28&t=58151:
Lastly, if you finally have managed to boot your PI for the fist time, (I recommend you try it the first time with Raspbian) make sure to do a proper shutdown.
Not following this procedure may lead to corruption of the cards contents.
What are possible solutions to avoid this? My ideas:
1.) Always booting with a filesystem check and automatic repair
Would it be possible to boot with a filesystem check performed? Sth. like this:
Code: Select all
sudo /usr/sbin/fsck.ext4 -f /dev/sdcx
2.) Using an external Harddrive / SSD
The SD-Card will always be necessary to boot. However, maybe it is possible to store all other stuff on a "real" Harddisk which is more stable? Or is the problem of corrupt filesystem entries not connected to the SD-Card but to the filesystem itself?
Do you have further ideas? Thanks for helping