Please donate any unused Raspberry's to a local school, they would be more than happy to have it.axkibe wrote:The first card I used was one I bought from RS as bundle. For the other I explicitly looked up the wiki to see which are supposed to be good.
The way samba4 uses hard links and ACL will make rsync backups fail anyway.
Dunno why SD cards are supposed to be less reliable. The SSD hard drive in my notebook made zero issues so far.
Sorry but I'm likely gonna dump the rasperry. Using it in a production environment was maybe a bad idea. Am now in the process of setting up just some old pentium as replacement.
I think James is trying (in his terribly English way) to say that most of the SDCard corruption problems have been fixed by firmware changes, by ensuring cards are not Chinese fakes and by ensuring that the power supply for a machine that runs 24x7 can reliably provide a steady 5V0 @ 1A (or better). He's experienced more SSD failure events than most and very few SDCard failures (if any).axkibe wrote:go figure ... what?
There are a lot of tutorials out there, but most of them quite old. Which way is the current and recommended to disable all log activity?shuckle wrote:Try to minimize all sd card writes. Use memory file systems and stop all logging.
I have been running 24/7 systems which die now and then and i have not seen corruptions for a long time.
OK, not overckocking. RPi is fast enough for my video playback needs.shuckle wrote:Also avoid overclocking if possible.
Very interesting indeed. Do you think my setup and particulary the omxplayer-sync and python dependancies will run on Alpine Linux?
Yes, I do think it would work. However, I think you would need to set up at least one Pi (or cross-compile environment on another computer) for development so you could compile any of these extra software packages which aren't already in the Alpine repositories. It might take a bit of time/effort to get familiar with using Alpine Linux. I have used it on my B+ and really like it, but I haven't been using my B+ very much these days. I think they have recently added Pi2 support. I'm actually about to test it out on my Pi2B. I'll let you know how that goes.mxa wrote:Very interesting indeed. Do you think my setup and particulary the omxplayer-sync and python dependancies will run on Alpine Linux?
Code: Select all
sudo apt-get remove dphys-swapfile
Code: Select all
/dev/mmcblk0p1 /boot vfat defaults,noatime 0 2 /dev/mmcblk0p2 / ext4 defaults,noatime 0 1 tmpfs /var/tmp/ tmpfs nodev,nosuid,size=50M 0 0 tmpfs /var/log/ tmpfsnodev,nosuid,size=10M 0 0
Code: Select all
/dev/mmcblk0p1 /boot vfat defaults,ro 0 2 /dev/mmcblk0p2 / ext4 defaults,ro,noatime 0 1
Yes, but the "disk" in this case is an SD card, and SD cards perform all sorts of wear-level and maintenance functions at various times - usually when they aren't busy doing something else. While performing those operations it will be shuffling data around and writing out buffers - data could still get corrupted if power is removed during those times.johnspackman wrote:Corruption is caused by power failures at the same time as the disk is being written to. If the power fails while the disk is not being written to, you're OK (assuming that your PSU is a suitably good quality etc)
Are you up to date? What does "uname -a" report?ronald71 wrote:I have 3 Pi boards. Pi1 and Pi2. All develop SD card errors after some time. Power is stable with battery attached to PSU so the power failure does not happen. Sometimes after some weeks when I execute shutdown -r the board simply doesn't wake up, sometimes loads to the certain point and stops. Reflashing the card with a backup by diskimager helps instantly and the card is brought back to the normal condition. Sometimes apt-get upgrade kills the card so I need to upgrade the PI twice. The card is not physically destroyed, the card has only garbage data on it.
This is very good computer but for home use, learning and for the Linux fans but not for the production environment. If you run a web or e-mail server for yourself this is OK, when you discover failure you can resurrect it from the image and it is back on track.
I had not only ext4 filesystem corruption but also the boot loader was corrupted. It happened on the oldest Pi and on the Pi2.