I got Umbrel on Raspi4 8GB with 1TB remaining disk space.
After doing the last upgrade to 1.7.2, I can visit the portal at umbrel.local but it becomes unresponsive after ~8 hrs of uptime.
I can ssh and trigger a reboot. I can then visit the portal again and see my node getting back to 100% synch and such. After a few hours, the portal becomes unresponsive again.
How to fix?
Check your BIOS settings and make sure they are set right for running Debian Linux!
Check current Boot Mode - BIOS Settings
In your Boot tab, look at your “Set Boot Priority” list. UEFI is present: Your 2nd Boot option is explicitly listed as [UEFI]. This confirms your BIOS supports and is currently recognizing UEFI boot devices. Mixed Mode: Having both a standard hard disk and a UEFI entry typically indicates a “mixed” or CSM mode, which allows the system to boot from both legacy (MBR) and modern (GPT) formatted drives.
To switch to a “pure” UEFI mode (often required for features like Secure Boot or Windows 11), you usually need to find and disable the CSM (Compatibility Support Module). In some versions of this Aptio utility, a Launch CSM setting appears directly under the “Boot Configuration” section (where you currently see “LAN Remote Boot”). If you don’t see it in the Boot tab, check the Advanced tab under Windows OS Configuration or BIOS UEFI/CSM Mode
I use a Raspberry 4. It has no BIOS.
What apps are you running?
Bitcoin node, Mempool, Lightning node, Electrs, Firefox, Invidious. CPU running at <60%, RAM 4GB out of 8GB, SSD still has 1TB free.
maybe 1.7.3 will solve your problem
“It also includes improved storage reliability on Raspberry Pi 4.”
I tried uninstalling/reinstalling mempool app, as it was especially sluggish. Uninstall succeeded, but reinstallation hung at 72%, followed by again loss of access via umbrel.local portal.
Rebooted again via ssh and tried to install the 1.7.3 upgrade, but that failed too.
Rebooted yet again via ssh, opened umbrel.local and right-clicked in each app to stop them. After every app had stopped, I tried again and succeeded at upgrading to 1.7.3.
On restart, access was much more responsive. I started each app one by one, and reinstalled mempool app.
Umbrel navigation is snappy as before and I’ll monitor if it becomes unresponsive again, but just on responsiveness, this seems to have improved things.
Having the same problem here.
Running Umbrel on an N150 mini PC, with 16GB memory and 2 TB NVME SSD. I only run Bitcoin core, Electrum and Mempool. The system is unresponsive after a random few hours. Not sure why. As soon as I pull the plug and put it back in, I see my node is back up and blockchain is synced. So it’s seems to be running good until it stops.
I have a Umbrel node next to it, which is a Raspberry Pi 4 and this node does not have that problem. It keeps on running, although it’s a lot slower ofcourse. I got the N150 as an upgrade, but so far it’s not when it keeps crashing.
There are 2 BIOS settings that need to be set properly to run on Debian Linux. I’ve posted about it on here and in the Discord or search for the settings via google search.
I have seen that indeed. Only cannot find that csm option in the bios. Also don’t understand why it runs fine first. It indexes the blockchain completely without issues and then suddenly becomes unresponsive.
were you able to upgrade to 1.7.3? If not, restart your umbrel, try right-clicking on all apps and stop each, then upgrade to 1.7.3. After reboot, right-click the apps to start them.
It’s not an upgrade. It’s a completely new Umbrel OS installation on a N150.
did you manage to upgrade Umbrel to v1.7.3?
Not sure who you are asking this. I switched to different hardware for Umbrel to resolve the problem. The N150 is now running Start9.
@JohnnDoe sorry it was to you and that’s one sure way to solve the issue. Glad you found a way.
No worries. 