System service failed - 5g home internet router problem?

Hi.

I just got my node assembled and plugged in since yesterday. I have been getting “Error: System service failed” when trying to access it from my desktop browser (Brave). I am thinking the problem is possibly with my T-Mobile 5g home internet, which when I set it up warned me that accessing devices on the local network would be different than normal. I have already tried to find information on that from T-Mobile and called their support and they were not able to help right away, though the issue has been escalated. I can see the device is connected on my router dashboard and it shows the IP address, which when I type in to the browser takes me to the same error screen as umbrel.local.

Or it could be something to do with the external SSD. I have bolded the relevant lines in the debug log below, though I don’t know exactly how to interpret what I’m reading. Any help would be appreciated. Thanks.

= Umbrel debug info =

Umbrel version

0.4.9

Flashed OS version

v0.4.9

Raspberry Pi Model

Revision : c03111
Serial : 100000000f2ee198
Model : Raspberry Pi 4 Model B Rev 1.1

Firmware

Oct 29 2021 10:47:33
Copyright © 2012 Broadcom
version b8a114e5a9877e91ca8f26d1a5ce904b2ad3cf13 (clean) (release) (start)

Temperature

temp=45.7’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 3.8G 125M 3.5G 8.0M 209M 3.6G
Swap: 0B 0B 0B

total: 3.3%
system: 3.3%
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 29G 1.7G 27G 6% /
/dev/root 29G 1.7G 27G 6% /

Startup service logs

– Logs begin at Fri 2021-12-17 17:55:40 UTC, end at Fri 2021-12-17 20:48:47 UTC. –
Dec 17 17:55:47 umbrel systemd[1]: Dependency failed for Umbrel Startup Service.
Dec 17 17:55:47 umbrel systemd[1]: umbrel-startup.service: Job umbrel-startup.service/start failed with result ‘dependency’.

External storage service logs

– Logs begin at Fri 2021-12-17 17:55:40 UTC, end at Fri 2021-12-17 20:48:47 UTC. –
Dec 17 17:55:44 umbrel systemd[1]: Starting External Storage Mounter…
Dec 17 17:55:44 umbrel external storage mounter[484]: Running external storage mount script…
Dec 17 17:55:44 umbrel external storage mounter[484]: Found device “Argon Forty”
Dec 17 17:55:44 umbrel external storage mounter[484]: Blacklisting USB device IDs against UAS driver…
Dec 17 17:55:44 umbrel external storage mounter[484]: Rebinding USB drivers…
Dec 17 17:55:44 umbrel external storage mounter[484]: Checking USB devices are back…
Dec 17 17:55:44 umbrel external storage mounter[484]: Waiting for USB devices…
Dec 17 17:55:45 umbrel external storage mounter[484]: Waiting for USB devices…
Dec 17 17:55:46 umbrel external storage mounter[484]: Checking if the device is ext4…
Dec 17 17:55:47 umbrel external storage mounter[484]: No, it’s not ext4
Dec 17 17:55:47 umbrel external storage mounter[484]: Formatting device…
Dec 17 17:55:47 umbrel external storage mounter[484]: wipefs: error: /dev/sda: probing initialization failed: No medium found
Dec 17 17:55:47 umbrel systemd[1]: umbrel-external-storage.service: Main process exited, code=exited, status=1/FAILURE
Dec 17 17:55:47 umbrel systemd[1]: umbrel-external-storage.service: Failed with result ‘exit-code’.
Dec 17 17:55:47 umbrel systemd[1]: Failed to start External Storage Mounter.

External storage SD card update service logs

– Logs begin at Fri 2021-12-17 17:55:40 UTC, end at Fri 2021-12-17 20:48:47 UTC. –
Dec 17 17:55:47 umbrel systemd[1]: Dependency failed for External Storage SDcard Updater.
Dec 17 17:55:47 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.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.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.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.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.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.

Hi,
Seems corrupted files in SSD, this afecting Tor and other parts.
I will ask to you the traditional “do you use official power supply?” and “do your usb cables to the SSD seems good quality, they fit firmly to conectors?” because I learned the hard way they are the main problem source for file corruption…

I do have an official power supply, but the SSD did not fit smoothly in the slot. Damn, I’ll take a look at that.

Look the usb cable itself, if it fit loosely its a problem. This need some testing, I got a Motorola cable very bad, and others no brand very good… And flexible usb cables cables are more reliable than more rigid ones.

If it’s a hardware thing, I think it has something to do with the SSD. The enclosure I got fits only the super small SSDs shaped like a stick of RAM with the connectors on the end. Well the SSD I got fits so that all the chips are face down and it sticks out at an angle because there isn’t enough space. I can push it down and screw it in, but that might be effecting the connection. If I could have flipped it over it would be fine, but the notch is on the wrong side then. Ugh, this is a real bummer.

Test the board out off the shell… Test another usb cables if possible. After a instal, try some restarts and some shutdowns, if they succeed smoothly, conections are reliable.

I got a new Pi enclosure and a separate SSD enclosure (the recommended ones from this site) and also used a different full size SSD I had. It’s working now and I’m downloading the ledger! Thanks for your help LG.