Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Probably this is not the best forum to ask as it is not related to Slackware, but I will ask anyway.
Are your Raspberry Pi devices stable?
I invested a lot of time to set up a VPN Server on my Pi but as I lack any spare time I hardly ever switch it on. Now I see that my Filesystem is totally corrupted. I could have messed up my Filesystem when I mounted the SD Card on my old PC to disable the ssh service until I update it. Or else I might be using a faulty SD Card. I am skeptical that the SD Card as a Hard disk was a wise design solution, so I would like to ask you if any of you have similar stability problems on your RPi device.
I'm using a RasPi as a webcam server for about 1˝ years.
First I had it running with only the boot partition on the SD card and the system on an USB-HDD which worked fine first, but after a while (half a year ago) it turned out to be unstable (I suppose that was due to an issue in the power supply for the HDD). So I installed the complete system (SlackwareARM) on a SD card and now it's stable.
(Touch wood & fingers crossed) No problem so far with my two Pis (pies?). A model A & a B, used for general-messing-about-with, nothing specific. Slackwarearm and Raspbian, on Transcend 16 GB class 10 cards.
I'm *responsible* for approximately 50 RPi installs (most running raspbmc, a few openelec) and I've *learned* that, as previously stated, the no. 1 culprit is power supply, and secondly, the SD card is going to corrupt/fail. Hence, boot from the SD card (and have a few spares kicking around), but run everything else from usb (preferably usb-hdd.)
Thus far I've had no bad boards, and perhaps 8-10 SD cards go south (excluding the one's I've deliberately abused through testing), and 3 usb-sticks corrupt over time (out of 40). None of the 6 usb-hdd has gone south yet.
Thanks to the LQo admins for silently shifting my question from the Slackware ARM subforum to where it belongs, and thanks to all that posted their replies.
My Pi is not overclocked. I have fsck'ed the root partition with a new Laptop and at least it boots. The Power Supply is on a UPS but I will try to have closer look at my Power Supply specs and performance.
Start out with sizing your Rpi power needs and the connected devices. I use a 2Amp 4 port USB power supply wart for the Rpi. I use another identical 2Amp 4 port USB power wart for peripheral needs. Most Pi users fail to select a class 10 SD and that too can cause issues over time. Spend a few more bucks and get a good SD. I use SlackwareARM on my Pi. I have been moving to my new residence & LAB so things are in limbo for awhile. I can start over with my LAB layout.
I have been working on my breadboard interfaces for the Pi.
Mines somewhat stable. If the power blinks it can appear to lock up, no keyboard or mouse input afterwards. All my usb things that come off of it's usb port(s) are attached to a powered usb hub(s). Running debian jessie (armel) at the moment and have had it < 2 weeks. Uptime 1 day 17 hours. I started to venture down the gentoo path, but when it started to compile a gcc update and a day later it was still compiling it (which was 28 of like 45 pending updates), I opted to not go down that path until I have a 2GHz+ quad core arm type device with a sata port. So probably 2015.
I finally got povray v18.104.22.168 stable to compile and run. I was trying with the git version and that was a fail, but the prebuild.sh from the git version was needed to get the stable version play nice with automake v1.14, so not a complete waste. I fully intend to clone my install to other SDHC cards once I have it the way I like it. So when it fails (and SDHC cards will) I can keep on chugging with all my installed bits less a few recent things.
I like it so far, like a laptop from the 2002-era. Probably more powerful than I expected, but the fbdev video make it feel slower than it is. It's got me rethinking a few things as silent and non-space heater computing has certainly got my interest atm. It gets so cold in my room with the x86 desktop off. Meanwhile a lot of the x86 machines seem to be adding car parts (radiators).