The write protect tab is an optional feature of the sdcard host, and does nothing on the Pi.mosu03ab wrote:The corruption also appears if the write protect is enabled by the physical tab. After underclocking by 33%, the corruptions seemed less frequent.
It's a firmware only fix (i.e. start.elf/fixup.dat not kernel.img). The fix appeared here:videostorm wrote:I actually need to know the specific version of GPU code/firmware that the fixes were applied. Also, if the fix was done in the linux kernel which version as well.
My OpenELEC install has been f2fs (on USB stick) for a few weeks. No problems so far.videostorm wrote:Have you done much experimenting with F2FS for the root partition? If so, any feedback on its stability verses ext4?
It's not that; sync just flushes the cache, which is something that happens automatically at the end of proper shutdown (ie with "sudo shutdown"). it's either a hardware issue (damaged card, dodgy psu, etc) or there is still a bug in raspbian where it does not wait for the card to finish it's own leveling before saying that it's safe to remove the power. In theory that bug has been fixed but if you have a reproducable test case (with a new card) the developers were swapping out kitKCE wrote:Have had the same results with two Kingston 8GB Class 4, which is what made me think it was my shutdown method.
gsh wrote: What's the error on the Pi look like?
Was the Pi shutdown correctly when this happened or is it likely to may have happened while the SD card was still actively doing something?
Code: Select all
!/bin/sh #Script to check FAT32 disk sudo umount /dev/mmcblk0p1 sleep 10 sudo dosfsck -w -r -l -a -v -t -V /dev/mmcblk0p1 sleep 10 sudo mount /dev/mmcblk0p1 exit 0
Users browsing this forum: lost and 36 guests