Does anyone know what the next steps are to address this issue?
It’s a new build on a Raspberry Pi 4 with 8gb of ram and the recommended 1tb ssd with the recommended enclosure. Not sure what to do. Have restarted several times. Same error.
Please check the Troubleshooting guide and post here the link to the debug log.
Thanks! Here are thoes logs.
umbrel@umbrel:~/umbrel $ ~/umbrel/scripts/debug --upload
= Umbrel debug info =
Umbrel version
0.4.2
Flashed OS version
v0.4.2
Raspberry Pi Model
Revision : d03114
Serial : 100000009008fe6d
Model : Raspberry Pi 4 Model B Rev 1.4
Firmware
Aug 31 2021 14:52:47
Copyright © 2012 Broadcom
version 67615e950e1e28b92dfae6303cf7a8b879a8908f (clean) (release) (start)
Temperature
temp=37.4’C
Throttling
throttled=0x0
Memory usage
total used free shared buff/cache available
Mem: 7.8G 136M 7.4G 8.0M 275M 7.6G
Swap: 0B 0B 0B
total: 1.7%
system: 1.7%
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 235G 3.1G 223G 2% /
/dev/root 235G 3.1G 223G 2% /
Startup service logs
– Logs begin at Sat 2021-09-25 15:05:42 UTC, end at Sat 2021-09-25 21:22:16 UTC. –
Sep 25 15:05:53 umbrel systemd[1]: Dependency failed for Umbrel Startup Service.
Sep 25 15:05:53 umbrel systemd[1]: umbrel-startup.service: Job umbrel-startup.service/start failed with result ‘dependency’.
External storage service logs
– Logs begin at Sat 2021-09-25 15:05:42 UTC, end at Sat 2021-09-25 21:22:16 UTC. –
Sep 25 15:05:46 umbrel systemd[1]: Starting External Storage Mounter…
Sep 25 15:05:46 umbrel external storage mounter[472]: Running external storage mount script…
Sep 25 15:05:47 umbrel external storage mounter[472]: Found device “CT1000MX 500SSD1”
Sep 25 15:05:47 umbrel external storage mounter[472]: Blacklisting USB device IDs against UAS driver…
Sep 25 15:05:47 umbrel external storage mounter[472]: Rebinding USB drivers…
Sep 25 15:05:47 umbrel external storage mounter[472]: Checking USB devices are back…
Sep 25 15:05:47 umbrel external storage mounter[472]: Waiting for USB devices…
Sep 25 15:05:48 umbrel external storage mounter[472]: Waiting for USB devices…
Sep 25 15:05:49 umbrel external storage mounter[472]: Checking if the device is ext4…
Sep 25 15:05:49 umbrel external storage mounter[472]: No, it’s not ext4
Sep 25 15:05:49 umbrel external storage mounter[472]: Formatting device…
Sep 25 15:05:49 umbrel external storage mounter[472]: /dev/sda: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54
Sep 25 15:05:49 umbrel external storage mounter[472]: /dev/sda: 8 bytes were erased at offset 0xe8e0db5e00 (gpt): 45 46 49 20 50 41 52 54
Sep 25 15:05:49 umbrel external storage mounter[472]: /dev/sda: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa
Sep 25 15:05:49 umbrel external storage mounter[472]: /dev/sda: calling ioctl to re-read partition table: Success
Sep 25 15:05:50 umbrel external storage mounter[472]: mke2fs 1.44.5 (15-Dec-2018)
Sep 25 15:05:50 umbrel external storage mounter[472]: Creating filesystem with 244190208 4k blocks and 61054976 inodes
Sep 25 15:05:50 umbrel external storage mounter[472]: Filesystem UUID: 8976c132-f699-42dd-9b82-304d4493bc22
Sep 25 15:05:50 umbrel external storage mounter[472]: Superblock backups stored on blocks:
Sep 25 15:05:50 umbrel external storage mounter[472]: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
Sep 25 15:05:50 umbrel external storage mounter[472]: 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
Sep 25 15:05:50 umbrel external storage mounter[472]: 102400000, 214990848
Sep 25 15:05:50 umbrel external storage mounter[472]: [65B blob data]
Sep 25 15:05:50 umbrel external storage mounter[472]: [62B blob data]
Sep 25 15:05:52 umbrel external storage mounter[472]: Creating journal (262144 blocks): done
Sep 25 15:05:53 umbrel external storage mounter[472]: [148B blob data]
Sep 25 15:05:53 umbrel systemd[1]: umbrel-external-storage.service: Main process exited, code=exited, status=1/FAILURE
Sep 25 15:05:53 umbrel systemd[1]: umbrel-external-storage.service: Failed with result ‘exit-code’.
Sep 25 15:05:53 umbrel systemd[1]: Failed to start External Storage Mounter.
External storage SD card update service logs
– Logs begin at Sat 2021-09-25 15:05:42 UTC, end at Sat 2021-09-25 21:22:16 UTC. –
Sep 25 15:05:53 umbrel systemd[1]: Dependency failed for External Storage SDcard Updater.
Sep 25 15:05:53 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
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
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 ====
You have either no external drive connected to your Raspberry Pi or the drive is not being detected.
Please shutdown your Raspberry Pi (‘sudo shutdown’), then plug the SSD into the other USB3 port.
After you’ve finished that, boot your Raspberry Pi back up. If it still still doesn’t work,
you can contact us on Telegram (t.me/getumbrel) and share the output of this script.
You can also share these links instead:
tail: cannot open ‘/home/umbrel/umbrel/scripts/…/logs/memory-monitor.log’ for reading: No such file or directory
tail: cannot open ‘logs/karen.log’ for reading: No such file or directory
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
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
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
https://umbrel-paste.vercel.app/57c59259c3049e1d6b9df1adbc77940a
umbrel@umbrel:~/umbrel $
So I attached the SSD drive enclosure to a Windows 10 machine via USB and formatted the drive as NTFS using Disk Management. That appears to solve the issue. Thanks!
Wrong. Never do that, formatting in NTFS. Just erase the partition is enough.
Umbrel is using ext4 format not NTFS.
See Troubleshooting manual section “My external disk drive is not mounting, what can I do?”