Is it possible that you’re running out of disk or swap? Can you do: sudo df -h and check your space allocations?
Filesystem Size Used Avail Use% Mounted on
/dev/root 15G 2.8G 11G 21% /
devtmpfs 796M 0 796M 0% /dev
tmpfs 926M 0 926M 0% /dev/shm
tmpfs 926M 98M 828M 11% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 926M 0 926M 0% /sys/fs/cgroup
/dev/mmcblk0p1 253M 30M 223M 12% /boot
/dev/sda1 938G 487G 404G 55% /mnt/data
overlay 938G 487G 404G 55% /var/lib/docker/overlay2/40468787708c1ec73 e858d36df2c6c6c1f19794787bb70b03d7dd590c449d808/merged
overlay 938G 487G 404G 55% /var/lib/docker/overlay2/8b5671871cfd1ca3d 59d19cd020f04a4fe2fa1361ade85958839b15c034620dd/merged
tmpfs 186M 0 186M 0% /run/user/1000
overlay 938G 487G 404G 55% /var/lib/docker/overlay2/b2cc4a577569ddcf0 5efa80de46019a2d1098ab4c9886f8072c25edd6338dc32/merged
overlay 938G 487G 404G 55% /var/lib/docker/overlay2/4193b315a427e4e32 13a9a71e16b6bcd21eb66da6bbbe27468500f1fa7811f82/merged
overlay 938G 487G 404G 55% /var/lib/docker/overlay2/e4925b82398bce6ea 87fb61153fd94a64235411fa76a1707f694be9d4656cb19/merged
overlay 938G 487G 404G 55% /var/lib/docker/overlay2/b11cfa7acd8123fcf 36972257c8347549acf2e9b230c627bd5df52e470efafe3/merged
overlay 938G 487G 404G 55% /var/lib/docker/overlay2/eedc3f90b9571073a 53ecd654415c239ef71feb81cfaa05fed7ead9cc0b66ea1/merged
overlay 938G 487G 404G 55% /var/lib/docker/overlay2/a9fd37bf62937ffcc 1fdebb4dfa5ec763818eaeecd24c0346ff60dc62bacac89/merged
overlay 938G 487G 404G 55% /var/lib/docker/overlay2/388e595388657c958 d1ebd1eee927b1949e88391d1db61d901bc87068fa5dce5/merged
overlay 938G 487G 404G 55% /var/lib/docker/overlay2/55a7d8f68bfccfa4c 538d5418df52bba628a0533752d7f5ac70ff052823b02ed/merged
overlay 938G 487G 404G 55% /var/lib/docker/overlay2/a7e378b9a2dbcfe8c d2a3d893a9c651a45dd9d6a59c317cc1772e75ab6a6dfb5/merged
overlay 938G 487G 404G 55% /var/lib/docker/overlay2/2f3abd37017b688b5 64d9d24918905e5fc59c438b993bbb0ecac7f00cb5c412a/merged
umbrel@umbrel:~ $
I think that I have the same issue.
The dashboard says ‘synchronizing’, and no progress is shown.
When I open the development tools on my browser, I see the following failed call’s:
sync: error 500, with message: “Unable to obtain peer info”
btc: error 500, with message “Must unlock wallet”
Do other people see this also?
Also, when I check the lnd logs (docker logs lnd | more) I see this message:
2021-06-17 17:09:07.338 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.
2021-06-17 17:09:15.488 [INF] BTCN: DNS discovery failed on seed x49.seed.bitcoin.jonasschnelli.ch: tor host is unreachable
Do other people have the same messages?
And I also tried the suggestion of the missing settings.json, but that did not help me.
I just wiped the whole installation and all data.
After installing it again, the system seems to work correctly again.
I have done a number of reflashes on the SD card but I’m not willing to wipe my SSD as it had completed syncing before the dashboard failed. I don’t want to lose all that time.
My log says it can’t parse /data/.bitcoin/settings.json. Any ideas where this /data/ directory is supposed to be?
Never mind, I got it. Rather than create those files I deleted them and now I am syncing again.
I have this exact same issue. Is SSD a MUST do part of the setup? I can download the blockchain and it starts showing the blocks syncing and then after a day or so I get the loading dashboard with no info…
That’s essentially what I concluded, it works much better, faster on SSD. I did however have some issues with my partition sizes where I was running out of space on the mount where I had confirmation stores.