New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sd card corruption and error transferring data #444
Comments
There has been a lot of discussion and investigation of SD card corruption, and although the results were not entirely conclusive we have learnt a few things:
The most obvious thing to try is to switch to using the sdhost interface. As it says above, just add |
Hi Phil, Just to add an information, I have a Raspberry B, with Raspbian GNU/Linux 7 Kernel 3.12.23+ and If it's possible I would ask your feedback about the corrupted SD cards: Many thanks |
Hi Phil, |
The sdhost driver uses the second, Broadcom-developed SD card interface on the BCM2835. It has some quirks and issues (sharing the core clock is one of them, requiring slightly more CPU support is another) but so does the Arasan (mmc) interface, and for some cards sdhost seems to work better than mmc, plus with a more flexible clock divider you can hit 50MHz from a 250MHz core clock (the mmc block is limited to an even divider, so you are stuck at 41.6MHz) and get a slight speed-up. |
@zimmy73 has your issue been resolved? Then please close this issue. Thanks. |
@popcornmix please consider closing this issue |
Hello all,
I'm experiencing problems on more than 10 Raspberry B+, Raspbian GNU/Linux 7,
running mrtg, check_mk agent and nothing else,
sd card kingston 8GB class10 (SDC10/8GBSP)
Here is the mount command:
/dev/root on / type ext4 (rw,noatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=218304k,nr_inodes=54576,mode=755)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=44516k,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=89020k)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
/dev/mmcblk0p1 on /boot type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
none on /var/log type tmpfs (rw,noatime,size=1024k)
none on /var/tmp type tmpfs (rw,noatime,size=1024k)
none on /tmp type tmpfs (rw,noatime,size=1024k)
as you can see the /boot partition is ro, and the /var and /tmp are in-memory filesystem;
swap is disabled
With kernel 3.18.11+, after more or less 20-30 days of good running I have noticed that
they started to have problems in succession, reporting error data transfering on the kern.log file.
mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
After a reboot, all the raspberry devices were not able to start, nothing displayed on the HDMI output and the red and green
leds always on ... the sd card was corrupted and I was not able to built it from scratch because it resulted not readable
both from linux and windows.
Now I have done a raspi-update on an "still working" raspberry, loading kernel 4.0.6+, I'm waiting, hoping that the problem was related to
the kernel modules.
Do you know something about this issue?
Do you have suggestions for me?
Any help would be appreciated.
Many thanks
The text was updated successfully, but these errors were encountered: