Umbrel after a few days is unresponsive

Support and Troubleshooting
1

In the recent few days I notice my umbrel goes down on my RPI5.
Instead of a green LED it changes to ORANGE. To recover, I have to poweroff the RPI5 and restart.
This is happening every two days at present. It was running fine for weeks before that.
I havn’t changed anything on the system.
Is this a known issue? I don’t even know what an orange light means on the RPI5 ..
Thanks.

1 Like
2

check disk space and cpu. these are basic health checks… like vital signs for humans.

To ensure your Raspberry Pi (running Umbrel on umbrelOS) is healthy, you need to check memory (RAM), disk space, and basic system status.

Step-by-Step Basic Health Checks for Your Raspberry Pi

  1. Access Your Raspberry Pi via SSH:
  • Open a terminal on your computer (Terminal on Mac/Linux, Command Prompt/PowerShell on Windows).
  • Connect to your Pi:

ssh umbrel@umbrel.local

  • If umbrel.local doesn’t work, use the Pi’s IP address (e.g., ssh umbrel@192.168.x.x). Find the IP in your router or Umbrel dashboard (http://umbrel.local).
  • Enter your Umbrel password (same as the dashboard login).
  1. Check Memory (RAM) Usage:
  • Run:

free -h

  • What to Look For:
    • Output shows total, used, free, and available memory in human-readable format (e.g., MB or GB).
    • Focus on available (under the Mem row). If it’s less than 100 MB, your Pi is low on RAM, which could cause issues.
    • Fix if Low: Stop non-essential apps via the Umbrel dashboard (e.g., pause Mempool or Electrs temporarily) or reboot:

sudo reboot
3. Check Disk Space:

  • Run:

df -h

  • What to Look For:
    • Output lists disk usage for each filesystem (e.g., SD card and external drive if used).
    • Look for the filesystem where Umbrel stores data (often /dev/sda1 for an external drive or / for the SD card).
    • Check the Avail column. You need at least 1-2 GB free for app updates. If Use% is 90% or higher, you’re critically low.
    • Fix if Low: Remove unused Docker images:

sudo docker image prune

Or delete old logs:

sudo find /var/log -type f -delete

If using an external drive, ensure it’s mounted (visible in df -h).
4. Check System Load (CPU Health):

  • Run:

uptime

  • What to Look For:
    • Output shows the current time, how long the Pi has been running, and three load averages (e.g., 0.50, 0.60, 0.70).
    • These numbers represent CPU load over 1, 5, and 15 minutes. For a Raspberry Pi (typically 4 cores), loads below 2.0 are healthy. If above 4.0, the Pi is overloaded.
    • Fix if High: Stop heavy apps (e.g., Bitcoin Core syncing) via the Umbrel dashboard or reboot:

sudo reboot
5. Check Running Containers:

  • Run:

sudo docker ps

  • What to Look For:
    • Lists all running Docker containers (Umbrel apps like BTC RPC Explorer, Bitcoin Core, etc.).
    • Ensure your key apps (e.g., btc-rpc-explorer_web_1, bitcoin_bitcoind_1) are listed under NAMES with Up under STATUS.
    • If an app is missing or shows Restarting, it’s unhealthy and may need a restart:

sudo docker-compose restart btc-rpc-explorer

Run this from ~/umbrel (use cd ~/umbrel first).

Why These Checks Matter

  • Memory: Low RAM can crash or cause apps to fail.
  • Disk: No free space prevents Docker and system from normal operations.
  • System Load: High CPU load slows down or disrupts.
  • Containers: Ensures Umbrel’s apps are running stably.

Tips for Success

  • Run Before and After Reboot: Do these checks twice and make note of the ‘healthy’ state
  • External Drive: If Umbrel uses an external drive for Bitcoin data, ensure it’s connected and shows in df -h.
  • Reboot if Unsure: A reboot often clears minor issues but isn’t a real solution:

sudo reboot

  • Dashboard Check: After SSH checks, glance at the Umbrel dashboard (http://umbrel.local) to confirm apps are online and Bitcoin Core is synced.

My Take: These commands are like checking your car’s oil and tires before a trip—basic but critical. A Raspberry Pi running Umbrel can choke on low memory or disk space, especially with Bitcoin’s blockchain hogging resources. If you see red flags (e.g., 50 MB RAM available or 95% disk usage), fix them first or your box will keep failing.

3

All good checks. I think the SD card went bad and they will have to image another.

4

When you get an orange light, I don’t think I could ssh in from memory.
The storage is a 128Gb sata drive connected via USB3

5

I have had this same issue.

6

I have the exact same issue, and I can’t explain it. My main question is how do I get data up to when it crashes? I suspect I would have to do some regular “every 10 sec cron” job to find out what happens that leads to this. I have a 16gb N150 mini-pc, not a raspberry pi. My raspberry pi 4 works fine, but I remember years ago having a similar issue that somehow resolved itself.

This also happens when I only had core running nothing else. I recently installed elements (liquid) and it fully synced last night, and during the night, again it’s now unresponsive.

The only error I have is an issue with my wifi (which I don’t use). I get the following error reoccurring endlessly

Blockquote “[218927.818728] pcieport 0000:00:1c.0: AER: Multiple Corrected error message received from 0000:01:00.0
[218927.818744] rtw_8821ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[218927.818746] rtw_8821ce 0000:01:00.0: device [10ec:c821] error status/mask=00000001/0000e000
[218927.818748] rtw_8821ce 0000:01:00.0: [ 0] RxErr (First)
[218928.035038] pcieport 0000:00:1c.0: AER: Multiple Corrected error message received from 0000:01:00.0
[218928.035058] rtw_8821ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[218928.035060] rtw_8821ce 0000:01:00.0: device [10ec:c821] error status/mask=00000001/0000e000
[218928.035062] rtw_8821ce 0000:01:00.0: [ 0] RxErr (First)”

ChatGPT says the above error is just a wifi error and isn’t much more than an annoyance considering I don’t use the wifi.

The only solution is to plug out the device and plug it back in and turn the power on. If I ping it from another device on the network, it fails say 80% of the packets (ie most) but occasionally some packets get returned.

One thing that’s turned out to be different this time is that after rebooting, the elements is doing a rendexing. Not redownloading the liquid blockchain, as it’s all still on the computer, but going through the blockchain again. Just noticed it’s on 4% done. But never had that with Bitcoin. This doesn’t bother me as I’m only tinkering with elements, I don’t actually need it, but just something that’s worth mentioning.

7

So last night I set up an automation to record in 15 min intervals key stats to see what is happening when it freezes, and today, i notice my LND restarted…No explanations why. I went to the logs I made, and this is what I showed…

I have made in bold the exact point where the node rebooted at ===== 2025-06-09 10:45:50 =====

But unfortunately, I personally don’t see anything out of the ordinary. It just rebooted without explanation.

Log Code
LOG_FILE=“/home/umbrel/system_Monitor.log”
DATE=$(date ‘+%Y-%m-%d %H:%M:%S’)

Log CPU (top 3 processes if >80% CPU)

echo “===== $DATE =====” >> “$LOG_FILE”
echo “CPU Top Consumers:” >> “$LOG_FILE”
ps -eo pid,user,%cpu,fname --sort=-%cpu | awk ‘$3 > 80’ | head -n 3 >> “$LOG_FILE”

Log Memory (top 3 processes)

echo “Memory Top Consumers:” >> “$LOG_FILE”
ps -eo pid,%mem,fname --sort=-%mem | head -n 3 >> “$LOG_FILE”

Log System Load & Free Memory

echo “Load Average:” >> “$LOG_FILE”
uptime | awk -F’load average: ’ ‘{print $2}’ >> “$LOG_FILE”
echo “Free Memory:” >> “$LOG_FILE”
free -h | grep “Mem:” >> “$LOG_FILE”
dmesg | grep -i “oom” >> “$LOG_FILE”
echo “Network Connections:” >> “$LOG_FILE”
ss -s | grep “estab” >> “$LOG_FILE”

This is the log results
Crash logs

===== 2025-06-09 10:42:28 =====
CPU Top Consumers:
Memory Top Consumers:
PID %MEM COMMAND
16076 33.6 bitcoind
18472 5.8 Fulcrum
Load Average:
0.27, 0.30, 0.33
Free Memory:
Mem:15Gi8.4Gi319Mi22Mi7.0Gi7.0Gi
Network Connections:
TCP: 408 (estab 9, closed 347, orphaned 1, timewait 0)
===== 2025-06-09 10:42:43 =====
CPU Top Consumers:
Memory Top Consumers:
PID %MEM COMMAND
16076 33.6 bitcoind
18472 5.8 Fulcrum
Load Average:
0.28, 0.30, 0.33
Free Memory:
Mem:15Gi8.4Gi325Mi22Mi7.0Gi7.0Gi
Network Connections:
TCP: 397 (estab 9, closed 336, orphaned 1, timewait 0)
===== 2025-06-09 10:42:58 =====
CPU Top Consumers:
868283 root 100 ps
Memory Top Consumers:
PID %MEM COMMAND
16076 33.7 bitcoind
18472 5.8 Fulcrum
Load Average:
0.22, 0.29, 0.33
Free Memory:
Mem:15Gi8.4Gi341Mi22Mi7.0Gi7.0Gi
Network Connections:
TCP: 412 (estab 9, closed 351, orphaned 1, timewait 0)
===== 2025-06-09 10:43:13 =====
CPU Top Consumers:
Memory Top Consumers:
PID %MEM COMMAND
16076 33.7 bitcoind
18472 5.8 Fulcrum
Load Average:
0.17, 0.27, 0.32
Free Memory:
Mem:15Gi8.4Gi357Mi22Mi7.0Gi7.0Gi
Network Connections:
TCP: 418 (estab 9, closed 357, orphaned 1, timewait 0)
===== 2025-06-09 10:43:28 =====
CPU Top Consumers:
Memory Top Consumers:
PID %MEM COMMAND
16076 33.8 bitcoind
18472 5.9 Fulcrum
Load Average:
0.34, 0.31, 0.33
Free Memory:
Mem:15Gi8.3Gi376Mi22Mi7.0Gi7.0Gi
Network Connections:
TCP: 415 (estab 9, closed 354, orphaned 1, timewait 0)
===== 2025-06-09 10:43:43 =====
CPU Top Consumers:
868763 root 100 ps
Memory Top Consumers:
PID %MEM COMMAND
16076 33.8 bitcoind
18472 5.8 Fulcrum
Load Average:
0.34, 0.31, 0.33
Free Memory:
Mem:15Gi8.3Gi356Mi22Mi7.0Gi7.0Gi
Network Connections:
TCP: 406 (estab 9, closed 345, orphaned 1, timewait 0)
===== 2025-06-09 10:43:58 =====
CPU Top Consumers:
868917 root 100 ps
Memory Top Consumers:
PID %MEM COMMAND
16076 33.8 bitcoind
18472 5.8 Fulcrum
Load Average:
0.27, 0.29, 0.33
Free Memory:
Mem:15Gi8.4Gi347Mi22Mi7.0Gi7.0Gi
Network Connections:
TCP: 415 (estab 9, closed 354, orphaned 1, timewait 0)
===== 2025-06-09 10:44:13 =====
CPU Top Consumers:
Memory Top Consumers:
PID %MEM COMMAND
16076 33.9 bitcoind
18472 5.8 Fulcrum
Load Average:
0.21, 0.28, 0.32
Free Memory:
Mem:15Gi8.4Gi320Mi22Mi7.0Gi7.0Gi
Network Connections:
TCP: 421 (estab 9, closed 360, orphaned 1, timewait 0)
===== 2025-06-09 10:44:28 =====
CPU Top Consumers:
Memory Top Consumers:
PID %MEM COMMAND
16076 33.8 bitcoind
18472 5.9 Fulcrum
Load Average:
0.23, 0.28, 0.32
Free Memory:
Mem:15Gi8.4Gi310Mi22Mi7.0Gi7.0Gi
Network Connections:
TCP: 423 (estab 9, closed 362, orphaned 1, timewait 0)
===== 2025-06-09 10:44:43 =====
CPU Top Consumers:
869398 umbrel 100 mariadb
Memory Top Consumers:
PID %MEM COMMAND
16076 33.8 bitcoind
18472 5.8 Fulcrum
Load Average:
0.18, 0.27, 0.32
Free Memory:
Mem:15Gi8.4Gi316Mi22Mi7.0Gi7.0Gi
Network Connections:
TCP: 437 (estab 9, closed 376, orphaned 3, timewait 0)
===== 2025-06-09 10:45:50 =====
CPU Top Consumers:
Memory Top Consumers:
PID %MEM COMMAND
1 0.0 systemd
233 0.0 systemd-
Load Average:
0.00, 0.00, 0.00
Free Memory:
Mem:15Gi530Mi14Gi1.2Mi259Mi14Gi
Network Connections:
TCP: 0 (estab 0, closed 0, orphaned 0, timewait 0)
===== 2025-06-09 10:46:05 =====
CPU Top Consumers:
Memory Top Consumers:
PID %MEM COMMAND
2574 0.9 bitcoind
2708 0.7 mysqld
Load Average:
1.29, 0.28, 0.09
Free Memory:
Mem:15Gi2.4Gi11Gi3.7Mi1.5Gi12Gi
Network Connections:
TCP: 127 (estab 3, closed 73, orphaned 0, timewait 0)
===== 2025-06-09 10:46:21 =====
CPU Top Consumers:
Memory Top Consumers:
PID %MEM COMMAND
2574 2.4 bitcoind
2207 2.0 lnd
Load Average:
10.79, 2.49, 0.82
Free Memory:
Mem:15Gi4.9Gi7.8Gi18Mi3.0Gi10Gi
Network Connections:
TCP: 216 (estab 3, closed 162, orphaned 0, timewait 0)
===== 2025-06-09 10:46:36 =====
CPU Top Consumers:
5723 umbrel 90.9 Fulcrum
Memory Top Consumers:
PID %MEM COMMAND
3479 1.5 node
5723 1.5 Fulcrum
Load Average:
20.26, 5.00, 1.67
Free Memory:
Mem:15Gi1.8Gi9.3Gi1.8Mi4.6Gi13Gi
Network Connections:
TCP: 30 (estab 0, closed 24, orphaned 0, timewait 1)
===== 2025-06-09 10:46:51 =====
CPU Top Consumers:
Memory Top Consumers:
PID %MEM COMMAND
3479 1.5 node
5576 1.3 next-rou
Load Average:
16.40, 4.90, 1.69
Free Memory:
Mem:15Gi1.5Gi9.2Gi1.7Mi5.0Gi13Gi
Network Connections:
TCP: 16 (estab 0, closed 12, orphaned 0, timewait 1)
===== 2025-06-09 10:47:06 =====
CPU Top Consumers:
Memory Top Consumers:
PID %MEM COMMAND
11071 1.6 mariadbd
6437 1.4 node
Load Average:
14.60, 5.04, 1.79
Free Memory:
Mem:15Gi2.6Gi7.6Gi3.2Mi5.5Gi12Gi
Network Connections:
TCP: 77 (estab 3, closed 38, orphaned 0, timewait 1)
===== 2025-06-09 10:47:22 =====
CPU Top Consumers:
Memory Top Consumers:
PID %MEM COMMAND
13927 2.7 bitcoind
15714 2.0 lnd
Load Average:
18.70, 6.43, 2.30
Free Memory:
Mem:15Gi5.0Gi4.9Gi21Mi5.9Gi10Gi
Network Connections:
TCP: 247 (estab 3, closed 190, orphaned 0, timewait 1)
===== 2025-06-09 10:47:37 =====
CPU Top Consumers:
18315 umbrel 89.8 gunicorn
18707 umbrel 82.0 node
Memory Top Consumers:
PID %MEM COMMAND
13927 12.5 bitcoind
14341 1.9 Fulcrum
Load Average:
16.54, 6.56, 2.40
Free Memory:
Mem:15Gi5.6Gi1.8Gi25Mi8.3Gi9.8Gi
Network Connections:
TCP: 391 (estab 5, closed 332, orphaned 0, timewait 0)
===== 2025-06-09 10:47:52 =====
CPU Top Consumers:
18883 root 100 ps
13927 umbrel 87.3 bitcoind
Memory Top Consumers:
PID %MEM COMMAND
13927 27.4 bitcoind
14341 4.6 Fulcrum
Load Average:
14.29, 6.56, 2.47
Free Memory:
Mem:15Gi5.9Gi190Mi25Mi9.7Gi9.5Gi
Network Connections:
TCP: 402 (estab 5, closed 343, orphaned 0, timewait 1)
===== 2025-06-09 10:48:07 =====
CPU Top Consumers:
13927 umbrel 108 bitcoind
Memory Top Consumers:
PID %MEM COMMAND
13927 26.8 bitcoind
14341 5.0 Fulcrum
Load Average:
12.32, 6.50, 2.52
Free Memory:
Mem:15Gi6.0Gi585Mi25Mi9.1Gi9.3Gi
Network Connections:
TCP: 404 (estab 5, closed 345, orphaned 0, timewait 1)
===== 2025-06-09 10:48:22 =====
CPU Top Consumers:
13927 umbrel 123 bitcoind
Memory Top Consumers:
PID %MEM COMMAND
13927 29.7 bitcoind
14341 4.7 Fulcrum
Load Average:
10.93, 6.57, 2.63
Free Memory:
Mem:15Gi6.2Gi273Mi25Mi9.2Gi9.1Gi
Network Connections:
TCP: 423 (estab 13, closed 356, orphaned 0, timewait 1)
===== 2025-06-09 10:48:37 =====
CPU Top Consumers:
13927 umbrel 137 bitcoind
Memory Top Consumers:
PID %MEM COMMAND
13927 30.3 bitcoind
14341 4.4 Fulcrum
Load Average:
10.26, 6.64, 2.71
Free Memory:
Mem:15Gi6.3Gi371Mi25Mi9.0Gi9.0Gi
Network Connections:
TCP: 430 (estab 13, closed 363, orphaned 0, timewait 1)
===== 2025-06-09 10:48:52 =====
CPU Top Consumers:
13927 umbrel 144 bitcoind
Memory Top Consumers:
PID %MEM COMMAND
13927 30.9 bitcoind
14341 4.5 Fulcrum
Load Average:
9.46, 6.64, 2.78
Free Memory:
Mem:15Gi6.3Gi309Mi25Mi9.1Gi9.1Gi
Network Connections:
TCP: 435 (estab 13, closed 368, orphaned 0, timewait 0)
===== 2025-06-09 10:49:07 =====
CPU Top Consumers:
13927 umbrel 148 bitcoind
19671 root 100 ps
Memory Top Consumers:
PID %MEM COMMAND
13927 25.8 bitcoind
14341 4.0 Fulcrum
Load Average:
8.15, 6.49, 2.79
Free Memory:
Mem:15Gi6.3Gi1.5Gi25Mi7.9Gi9.0Gi
Network Connections:
TCP: 446 (estab 13, closed 379, orphaned 0, timewait 0)
===== 2025-06-09 10:49:22 =====
CPU Top Consumers:
13927 umbrel 135 bitcoind
Memory Top Consumers:
PID %MEM COMMAND
13927 24.2 bitcoind
14341 3.6 Fulcrum
Load Average:
6.42, 6.19, 2.75
Free Memory:
Mem:15Gi6.4Gi821Mi25Mi8.5Gi9.0Gi
Network Connections:
TCP: 464 (estab 13, closed 397, orphaned 0, timewait 0)
===== 2025-06-09 10:49:37 =====
CPU Top Consumers:
13927 umbrel 128 bitcoind
Memory Top Consumers:
PID %MEM COMMAND
13927 19.4 bitcoind
14341 3.6 Fulcrum
Load Average:
5.36, 5.97, 2.73
Free Memory:
Mem:15Gi6.5Gi944Mi25Mi8.3Gi8.9Gi
Network Connections:
TCP: 463 (estab 13, closed 396, orphaned 0, timewait 0)
===== 2025-06-09 10:49:53 =====
CPU Top Consumers:
13927 umbrel 119 bitcoind
Memory Top Consumers:
PID %MEM COMMAND
13927 17.2 bitcoind
14341 3.5 Fulcrum
Load Average:
4.32, 5.71, 2.70
Free Memory:
Mem:15Gi6.5Gi840Mi25Mi8.4Gi8.9Gi
Network Connections:
TCP: 461 (estab 13, closed 394, orphaned 0, timewait 0)
===== 2025-06-09 10:50:08 =====
CPU Top Consumers:
13927 umbrel 112 bitcoind
20294 root 100 ps
Memory Top Consumers:
PID %MEM COMMAND
13927 15.2 bitcoind14341 3.5 Fulcrum
Load Average:
3.43, 5.44, 2.66
Free Memory:
Mem:15Gi6.5Gi899Mi25Mi8.4Gi8.9Gi
Network Connections:
TCP: 467 (estab 13, closed 400, orphaned 0, timewait 0)
===== 2025-06-09 10:50:23 =====
CPU Top Consumers:
13927 umbrel 105 bitcoind
20446 root 100 ps
Memory Top Consumers:
PID %MEM COMMAND
13927 16.5 bitcoind
14341 3.7 Fulcrum
Load Average:
3.03, 5.26, 2.64
Free Memory:
Mem:15Gi6.5Gi645Mi25Mi8.6Gi8.9Gi
Network Connections:
TCP: 476 (estab 13, closed 409, orphaned 0, timewait 0)
===== 2025-06-09 10:50:38 =====
CPU Top Consumers:
20588 root100 runc:[2:
13927 umbrel 98.3 bitcoind
Memory Top Consumers:
PID %MEM COMMAND
13927 16.5 bitcoind
14341 3.5 Fulcrum
Load Average:
2.43, 5.01, 2.61
Free Memory:
Mem:15Gi6.5Gi649Mi25Mi8.6Gi8.9Gi
Network Connections:
TCP: 481 (estab 13, closed 414, orphaned 0, timewait 0)

8

I do not have much to say, but this must be a huge file. It recorded every 15 seconds.

9

Not really. I have logrotate to limit it to 2mb max per day. Plus it’s only a tiny amount of data per line. But to keep it small, I subsequently split the data into different logs. One for copy, one for memory etc.

Either way, it’s crashed a few times since then but the logs don’t seem to point to anything specific except maybe something related to the wifi drivers. But it’s not solved which means no confirmation of what it is.

10

every 15 seconds, not minutes, why?

11

I initially was gonna have it at every 5 sec so I can capture the exact moment before it froze, but decided to not be so hyper…but a minute ago I felt would easily miss the exact moment and therefore any potential useful info.