Last week I went to log into my umbrel node and got this message: System Service Failed. It was the first time I’d seen it. After some research and restarting my node several times, I thought maybe it was the ssd card. So I re-flashed it with the latest update and started up my node again. Now when I sign in with ssh umbrel@umbrel.local I get this?
Can someone help me fix my node so I can sign in again?
=====================
= Umbrel debug info =
Umbrel version
0.4.11
Flashed OS version
v0.4.11
Raspberry Pi Model
Revision : d03114
Serial : 10000000cabce193
Model : Raspberry Pi 4 Model B Rev 1.4
Firmware
Dec 1 2021 15:01:54
Copyright © 2012 Broadcom
version 71bd3109023a0c8575585ba87cbb374d2eeb038f (clean) (release) (start)
Temperature
temp=41.8’C
Throttling
throttled=0x0
Memory usage
total used free shared buff/cache available
Mem: 7.8G 127M 7.5G 8.0M 224M 7.6G
Swap: 0B 0B 0B
total: 1.6%
system: 1.6%
tor: 0%
lnd: 0%
electrs: 0%
bitcoin: 0%
Memory monitor logs
tail: cannot open ‘/home/umbrel/umbrel/scripts/…/logs/memory-monitor.log’ for reading: No such file or directory
Filesystem information
Filesystem Size Used Avail Use% Mounted on
/dev/root 30G 3.2G 25G 12% /
/dev/root 30G 3.2G 25G 12% /
Startup service logs
– Logs begin at Wed 2022-01-26 23:27:26 UTC, end at Thu 2022-01-27 00:21:05 UTC. –
Jan 26 23:27:45 umbrel systemd[1]: Dependency failed for Umbrel Startup Service.
Jan 26 23:27:45 umbrel systemd[1]: umbrel-startup.service: Job umbrel-startup.service/start failed with result ‘dependency’.
External storage service logs
– Logs begin at Wed 2022-01-26 23:27:26 UTC, end at Thu 2022-01-27 00:21:05 UTC. –
Jan 26 23:27:30 umbrel systemd[1]: Starting External Storage Mounter…
Jan 26 23:27:30 umbrel external storage mounter[488]: Running external storage mount script…
Jan 26 23:27:30 umbrel external storage mounter[488]: No block devices found
Jan 26 23:27:30 umbrel external storage mounter[488]: Waiting for 5 seconds before checking again…
Jan 26 23:27:35 umbrel external storage mounter[488]: Found device “SanDisk Extreme 55AE”
Jan 26 23:27:35 umbrel external storage mounter[488]: Blacklisting USB device IDs against UAS driver…
Jan 26 23:27:36 umbrel external storage mounter[488]: Rebinding USB drivers…
Jan 26 23:27:36 umbrel external storage mounter[488]: Checking USB devices are back…
Jan 26 23:27:36 umbrel external storage mounter[488]: Waiting for USB devices…
Jan 26 23:27:37 umbrel external storage mounter[488]: Waiting for USB devices…
Jan 26 23:27:38 umbrel external storage mounter[488]: Waiting for USB devices…
Jan 26 23:27:39 umbrel external storage mounter[488]: Waiting for USB devices…
Jan 26 23:27:40 umbrel external storage mounter[488]: Waiting for USB devices…
Jan 26 23:27:41 umbrel external storage mounter[488]: Waiting for USB devices…
Jan 26 23:27:42 umbrel external storage mounter[488]: Waiting for USB devices…
Jan 26 23:27:43 umbrel external storage mounter[488]: Waiting for USB devices…
Jan 26 23:27:44 umbrel external storage mounter[488]: Waiting for USB devices…
Jan 26 23:27:45 umbrel external storage mounter[488]: Checking if the device is ext4…
Jan 26 23:27:45 umbrel external storage mounter[488]: No, it’s not ext4
Jan 26 23:27:45 umbrel external storage mounter[488]: Formatting device…
Jan 26 23:27:45 umbrel external storage mounter[488]: wipefs: error: /dev/sda: probing initialization failed: No medium found
Jan 26 23:27:45 umbrel systemd[1]: umbrel-external-storage.service: Main process exited, code=exited, status=1/FAILURE
Jan 26 23:27:45 umbrel systemd[1]: umbrel-external-storage.service: Failed with result ‘exit-code’.
Jan 26 23:27:45 umbrel systemd[1]: Failed to start External Storage Mounter.
External storage SD card update service logs
– Logs begin at Wed 2022-01-26 23:27:26 UTC, end at Thu 2022-01-27 00:21:05 UTC. –
Jan 26 23:27:45 umbrel systemd[1]: Dependency failed for External Storage SDcard Updater.
Jan 26 23:27:45 umbrel systemd[1]: umbrel-external-storage-sdcard-update.service: Job umbrel-external-storage-sdcard-update.service/start failed with result ‘dependency’.
Karen logs
tail: cannot open ‘logs/karen.log’ for reading: No such file or directory
Docker containers
NAMES STATUS
Umbrel logs
ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
networks.default.ipam.config.subnet is invalid: should use the CIDR format
services.tor_proxy.ports contains an invalid type, it should be a number, or an object
services.bitcoin.ports contains an invalid type, it should be a number, or an object
services.electrs.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.nginx.ports contains an invalid type, it should be a number, or an object
services.lnd.ports value [‘9735:9735’, ‘:’, ‘:’] has non-unique elements
Bitcoin Core logs
ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
networks.default.ipam.config.subnet is invalid: should use the CIDR format
services.tor_proxy.ports contains an invalid type, it should be a number, or an object
services.bitcoin.ports contains an invalid type, it should be a number, or an object
services.electrs.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.nginx.ports contains an invalid type, it should be a number, or an object
services.lnd.ports value [‘9735:9735’, ‘:’, ‘:’] has non-unique elements
LND logs
ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
networks.default.ipam.config.subnet is invalid: should use the CIDR format
services.tor_proxy.ports contains an invalid type, it should be a number, or an object
services.bitcoin.ports contains an invalid type, it should be a number, or an object
services.electrs.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.nginx.ports contains an invalid type, it should be a number, or an object
services.lnd.ports value [‘9735:9735’, ‘:’, ‘:’] has non-unique elements
electrs logs
ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
networks.default.ipam.config.subnet is invalid: should use the CIDR format
services.tor_proxy.ports contains an invalid type, it should be a number, or an object
services.bitcoin.ports contains an invalid type, it should be a number, or an object
services.electrs.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.nginx.ports contains an invalid type, it should be a number, or an object
services.lnd.ports value [‘9735:9735’, ‘:’, ‘:’] has non-unique elements
Tor logs
ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
networks.default.ipam.config.subnet is invalid: should use the CIDR format
services.tor_proxy.ports contains an invalid type, it should be a number, or an object
services.bitcoin.ports contains an invalid type, it should be a number, or an object
services.electrs.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.nginx.ports contains an invalid type, it should be a number, or an object
services.lnd.ports value [‘9735:9735’, ‘:’, ‘:’] has non-unique elements
==== Result ====
The debug script did not automatically detect any issues with your Umbrel.
umbrel@umbrel:~ $ Connection to umbrel.local closed by remote host.
Connection to umbrel.local closed.