HELP: Umbrel Node Not Starting After Power Outage

Support and Troubleshooting
1

Hello Umbrel Community,

I am reaching out for help with an issue I’ve encountered with my Umbrel node running on a Raspberry Pi 4. Following a 36-hour power outage due to a storm, I have been unable to restart my Bitcoin node. :fearful: Despite re-flashing the SD card with the latest version of Umbrel, I am still greeted with an ‘Error system failed’ message upon trying to connect to Umbrel.

Here are the steps I have taken so far:

  • I re-flashed the SD card with the latest Umbrel OS.
  • Attempted to restart the node multiple times.
  • Checked the Docker service status, which indicated a failure to start.

I have attached the Docker service log below, which repeats the following messages:

Nov 08 10:31:45 umbrel systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Nov 08 10:31:45 umbrel systemd[1]: docker.service: Scheduled restart job, restart counter is at 5.
Nov 08 10:31:45 umbrel systemd[1]: Stopped Docker Application Container Engine.
Nov 08 10:31:45 umbrel systemd[1]: docker.service: Start request repeated too quickly.
Nov 08 10:31:45 umbrel systemd[1]: docker.service: Failed with result 'exit-code'.
Nov 08 10:31:45 umbrel systemd[1]: Failed to start Docker Application Container Engine.

I would greatly appreciate any guidance or suggestions on what steps to take next to resolve this issue and get my node back online.

Thank you in advance for your time and help. :pray:

Val

=====================
= Umbrel debug info =

Umbrel version

0.5.4

Flashed OS version

v0.5.4-patch-1

Raspberry Pi Model

Revision : d03115
Serial : 1000000042940270
Model : Raspberry Pi 4 Model B Rev 1.5

Firmware

May 9 2023 12:16:34
Copyright (c) 2012 Broadcom
version 30aa0d70ab280427ba04ebc718c81d4350b9d394 (clean) (release) (start)

Temperature

temp=36.5’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 7.8G 114M 6.6G 292M 1.1G 7.3G
Swap: 4.1G 0B 4.1G

total: 1.5%
system: 1.5%
thunderhub: 0%
ride-the-lightning: 0%
nostr-relay: 0%
lightning-terminal: 0%
lightning: 0%
electrs: 0%
bitcoin: 0%

Memory monitor logs

2023-11-05 05:49:04 Memory monitor running!
2023-11-05 05:49:17 Memory monitor running!
2023-11-05 05:49:30 Memory monitor running!
2023-11-05 05:49:48 Memory monitor running!
2023-11-05 05:50:00 Memory monitor running!
2023-11-05 05:50:13 Memory monitor running!
2023-11-05 05:50:25 Memory monitor running!
2023-11-05 05:50:38 Memory monitor running!
2023-11-05 05:50:57 Memory monitor running!
2023-11-05 05:51:09 Memory monitor running!

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 238G 6.9G 222G 4% /
/dev/sda1 1.8T 667G 1.1T 39% /home/umbrel/umbrel

2

Thanks describing your issue so well and including these logs- makes things a lot easier.
Fortunately this looks pretty promising since you can still boot Umbrel at least.

Please give the following a try:
SSH back into your Umbrel instance
and running the following

sudo systemctl stop docker && sudo rm -rf /var/lib/docker/* && sudo reboot

Let me know if that helps

1 Like
3

Hi Smolgrrr,

Thanks a lot for your help !

I executed your command, but the docker service is still not starting.

Here are logs

umbrel@umbrel:~ $ sudo systemctl status docker.service
[sudo] password for umbrel:

● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2023-11-08 15:27:19 UTC; 46s ago
     Docs: https://docs.docker.com
  Process: 10281 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=2
 Main PID: 10281 (code=exited, status=2)

Nov 08 15:27:19 umbrel systemd[1]: Failed to start Docker Application Container Engine.
Nov 08 15:27:29 umbrel systemd[1]: docker.service: Start request repeated too quickly.
Nov 08 15:27:29 umbrel systemd[1]: docker.service: Failed with result 'exit-code'.
Nov 08 15:27:29 umbrel systemd[1]: Failed to start Docker Application Container Engine.
Nov 08 15:27:42 umbrel systemd[1]: docker.service: Start request repeated too quickly.
Nov 08 15:27:42 umbrel systemd[1]: docker.service: Failed with result 'exit-code'.
Nov 08 15:27:42 umbrel systemd[1]: Failed to start Docker Application Container Engine.
Nov 08 15:27:54 umbrel systemd[1]: docker.service: Start request repeated too quickly.
Nov 08 15:27:54 umbrel systemd[1]: docker.service: Failed with result 'exit-code'.
Nov 08 15:27:54 umbrel systemd[1]: Failed to start Docker Application Container Engine.
lines 1-17/17 (END)```

Thanks again

Val
4

Hello Umbrel community,

I wanted to share an update on this issue.
I decided to proceed with a full reinstallation of Docker and my node is now back online. :partying_face:
Here are the steps I took :

1. Uninstall Docker :

sudo apt-get purge docker-ce docker-ce-cli containerd.io

2. Clean Unused Dependencies :

sudo apt-get autoremove

3. Remove Residual Configuration Files :

sudo rm -rf /var/lib/docker
sudo rm -rf /etc/docker

4. Update Package List :

sudo apt-get update

5. Reinstall Docker :

sudo apt-get install docker-ce docker-ce-cli containerd.io

6. Reboot the Raspberry Pi :

sudo reboot

My Umbrel node is back online. :hugs:
I hope this solution might help others who encounter similar issues, but remember to do your research and ask for opinions based on your specific situation before taking action.

Thanks,
Val

1 Like
5

Great to hear, and nice work!
Sorry I couldnt get back to you in time.

1 Like