Issue Description: I have been having this issue with my raspberry pi running dietPi where it seems to lock up and I cannot SSH / access any of the services on it. The interesting part is that the interface seems to be up and I can still ping it on the local network but shows no video output. usually I get about 3-6 days before the issue appears again.

I am not really sure where to start to diagnose this issue. Any help would be appreciated!

Things Tried:

Reduced operating temp by getting a fan. I want to say this improved the length in between this issue appearing but don’t really have any hard evidence.

uninstalled unused services

Limited active torrents in QbitTorrent

EDIT: Small thing to mention is that the CPU load is usually really high - like not uncommon for the load to be between 8-10 but I have seen it as high as 24.

Temporary fix:

Power cycle - everything comes up again in less than a minute.

Raspberry Pi 3B v2

OS: DietPi

Services:

Lidarr

Radarr

Sonarr

Prowlarr

Qbittorrent

Mullvad VPN - WireGaurd

SSH

Virtual Insanity
link
fedilink
English
21Y

Have had this issue myself asking with other DD card related issues.

I can’t understand why the pi foundation persist with using SD as the only physically practical storage option.

They’re looking post the point of needing a way to snap on reliable EMMC storage, as a default, in a way that doesn’t leave a cable or something permanently plugged into a USB port.

Sure, USB is a fine option, but I hate that it’s only an option and not a designed default.

Most of us only need 8GB or so for the OS, 8GB or good quality durable EMMC should hardly cost anything.

Other tiny computers and even economy notebooks and Chromebooks already use this.

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 180 users / day
  • 393 users / week
  • 1.04K users / month
  • 3.76K users / 6 months
  • 1 subscriber
  • 3.92K Posts
  • 79.5K Comments
  • Modlog