Try a different power supply
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I've owned and deployed a lot of pi, every model, and in my experience when I have similar instability as you described its related to the sdcard. Either the sdcard itself or the tray soldered to the pi. I had one pi that would corrupt the sdcard without fail after 2 months and I played with bending the sdcard metal tray inward a little to help press the card better into the contacts and the problem went away. Try fiddling with the sdcard holder or different sdcards.
Thank you for the tip, I'll check it out, if the Pi runs unstable again. Just surprised, it sounds that it happened often to you... Since I upgraded to better sd-cards, I never had sd-card trouble again for nearly a decade now. (And I am constantly running multiple Pis 24/7 as servers)
Have you checked the logs in /var/logs?
dmesg and journalctl -k, found only entries after reboot, that the shutdown was not clean. Any specific logs where I could find more?
Unless the info is out of date (which is likely) kern.log syslog or messeges.
Thanks. I could neither find a file /var/log/kern.log nor did find /var/log | grep -i mess have a match.
I have a pi 4 server that hangs up after a few days. Tried to track down what was causing it but didn't go to extremes. Most expedient solution was to force a reboot.
Have a cron job that reboots the pi at 3:00 AM each day. Easy work around, lazy was better.
The issue is that it is simply not built with reliability as a high priority so probably some hardware component shits itself too much after a while.There is a reason every reasonable company that needs a server to run reliably in production uses something orders of magnitude more expensive than a rpi.
You lucked out with your previous experiences, but many others did not, or the industry would not pay the price of a rpi a month to run a machine with the specs of a rpi.
That said, if you don't need the reliability some easy hacks like a reboot cronjob or systemd timer, or trying to turn off unneeded services or peripherals could give you 90% of an industrial server's reliability