Failed to recover wallets, corruptions, and unable to reset

I experienced a bad power outage, and i had to restore it from the seed.
I tried several things, but ended up with broad corruption on my process.
let me walk through the process. My current debug log is at the end of the post.
Thanks for your help.

After the sync, i found zero balance, then i tried rescan UTXO using command line below. but my wallet began to synchronizing forever

"Step 2 - execute the following command to rescan wallet’s UTXOs:
sed -i "s/\[Application Options\]/\[Application Options\]\nreset-wallet-transactions=true/g;" ~/umbrel/lnd/lnd.conf && sudo reboot
Step 3 - Wait some time so LND can rescan all wallet’s UTXOs. If it solve the issue, run this to stop it from rescanning on a future restart:
sed -i "s/reset-wallet-transactions=true//g;" ~/umbrel/lnd/lnd.conf && sudo reboot "

some parts of debug log at that moment.

middleware | umbrel-middleware
middleware | Unable to get wallet balance, failed to connect to all addresses
middleware | /v1/lnd/wallet/btc
middleware | LndError: Unable to get wallet balance

electrs | [2021-12-12T12:46:54.665Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-12-12T12:46:55.668Z INFO electrs::daemon] waiting for RPC warmup: Loading P2P addresses…

bitcoin | 2021-12-12T12:49:12Z Socks5() connect to 176.125.230.17:8333 failed: general failure

lnd | failed to load config: /data/.lnd/lnd.conf:40: malformed key=value (W[[Application Options])lnd | failed to load config: /data/.lnd/lnd.conf:40: malformed key=value (W[[Application Options])

I decided to reset my umbrel without scrapping the whole blockchain data. using this commands line.

sudo systemctl stop umbrel-startup && sudo rm -rf ~/umbrel/lnd/!(lnd.conf) && sudo rm -f ~/umbrel/db/user.json && sudo rm -f ~/umbrel/db/umbrel-seed/seed && sudo systemctl start umbrel-startup

even after 7 hours, umbrel’s welcome page shows ‘loading’
so I tried to get a debug log, but something unexpected. it doesn’t look like to be reset.

  1. I could ssh in with my old password, not moneyprintergobrrr.

  2. I got these error messages
    Attaching to middleware, manager
    middleware | ENOENT: no such file or directory, open ‘/lnd/tls.cert’

bitcoin | 2021-12-14T22:11:49Z New outbound peer connected: version: 70016, blocks=714174, peer=94 (block-relay-only)
bitcoin | 2021-12-14T22:12:33Z Socks5() connect to yg6o54ia4dnihv5c7bpzbtdy66uhrktkx5q4egt3ardvhzdr2azu4nad.onion:8333 failed: host unreachable

Attaching to lnd
lnd | failed to load config: /data/.lnd/lnd.conf:40: malformed key=value (W[[Application Options])

this is my current debug log. (I removed some redundancy b/c body limit)

= Umbrel debug info =

Umbrel version

0.4.10

Flashed OS version

v0.4.10

Raspberry Pi Model

Revision : c03114
Serial : 1000000089bd6c37
Model : Raspberry Pi 4 Model B Rev 1.4

Firmware

Dec 1 2021 15:01:54
Copyright © 2012 Broadcom
version 71bd3109023a0c8575585ba87cbb374d2eeb038f (clean) (release) (start)

External storage service logs

– Logs begin at Mon 2021-12-13 17:06:41 UTC, end at Tue 2021-12-14 23:50:39 UTC. –
Dec 13 17:06:48 umbrel systemd[1]: Starting External Storage Mounter…
Dec 13 17:06:48 umbrel external storage mounter[505]: Running external storage mount script…
Dec 13 17:06:51 umbrel external storage mounter[505]: Found device “Samsung PSSD T7 Touch”
Dec 13 17:06:51 umbrel external storage mounter[505]: Blacklisting USB device IDs against UAS driver…
Dec 13 17:06:51 umbrel external storage mounter[505]: Rebinding USB drivers…
Dec 13 17:06:51 umbrel external storage mounter[505]: Checking USB devices are back…
Dec 13 17:06:51 umbrel external storage mounter[505]: Waiting for USB devices…
Dec 13 17:06:52 umbrel external storage mounter[505]: Waiting for USB devices…
Dec 13 17:06:53 umbrel external storage mounter[505]: Checking if the device is ext4…
Dec 13 17:06:55 umbrel external storage mounter[505]: Yes, it is ext4
Dec 13 17:06:55 umbrel external storage mounter[505]: Checking if device contains an Umbrel install…
Dec 13 17:06:55 umbrel external storage mounter[505]: Yes, it contains an Umbrel install
Dec 13 17:06:55 umbrel external storage mounter[505]: Bind mounting external storage over local Umbrel installation…
Dec 13 17:06:55 umbrel external storage mounter[505]: Bind mounting external storage over local Docker data dir…
Dec 13 17:06:55 umbrel external storage mounter[505]: Bind mounting external storage to /swap
Dec 13 17:06:55 umbrel external storage mounter[505]: Bind mounting SD card root at /sd-card…
Dec 13 17:06:55 umbrel external storage mounter[505]: Checking Umbrel root is now on external storage…
Dec 13 17:06:58 umbrel external storage mounter[505]: Checking /var/lib/docker is now on external storage…
Dec 13 17:06:58 umbrel external storage mounter[505]: Checking /swap is now on external storage…
Dec 13 17:06:58 umbrel external storage mounter[505]: Setting up swapfile
Dec 13 17:06:58 umbrel external storage mounter[505]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
Dec 13 17:06:58 umbrel external storage mounter[505]: no label, UUID=d827449d-1e86-480d-bde3-ab3ea7d108ae
Dec 13 17:06:59 umbrel external storage mounter[505]: Checking SD Card root is bind mounted at /sd-root…
Dec 13 17:06:59 umbrel external storage mounter[505]: Starting external drive mount monitor…
Dec 13 17:06:59 umbrel external storage mounter[505]: Mount script completed successfully!
Dec 13 17:06:59 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Mon 2021-12-13 17:06:41 UTC, end at Tue 2021-12-14 23:50:39 UTC. –
Dec 13 17:07:07 umbrel systemd[1]: Starting External Storage SDcard Updater…
Dec 13 17:07:07 umbrel external storage updater[967]: Checking if SD card Umbrel is newer than external storage…
Dec 13 17:07:07 umbrel external storage updater[967]: No, SD version is not newer, exiting.
Dec 13 17:07:07 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

=======================================
========= Stage: Post-update ==========

== End Update Script 02-run.sh ==

== Begin Update Script 03-run.sh ==

=======================================
=============== UPDATE ================

=========== Stage: Success ============

Removing backup
Successfully installed Umbrel v0.4.10
== End Update Script 03-run.sh ==

Deleting cloned repository
Removing lock
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
karen is running in /home/umbrel/umbrel/events
Got signal:
karen is getting triggered!
Got signal:
karen is getting triggered!
./karen: line 68: /home/umbrel/umbrel/events/triggers/: Is a directory
./karen: line 68: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: debug
karen is getting triggered!
Debug result file generated
karen is running in /home/umbrel/umbrel/events
Got signal:
karen is getting triggered!
Got signal:
karen is getting triggered!
./karen: line 68: /home/umbrel/umbrel/events/triggers/: Is a directory
./karen: line 68: /home/umbrel/umbrel/events/triggers/: Is a directory

Umbrel logs

Attaching to middleware, manager
middleware | ENOENT: no such file or directory, open ‘/lnd/tls.cert’
middleware | /v1/lnd/info/status
middleware | Error: ENOENT: no such file or directory, open ‘/lnd/tls.cert’
middleware | ::ffff:10.21.21.2 - - [Tue, 14 Dec 2021 23:51:21 GMT] “GET /v1/lnd/info/status HTTP/1.0” 500 57 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36”
middleware |
middleware | umbrel-middleware
middleware | ENOENT: no such file or directory, open ‘/lnd/tls.cert’
middleware | /v1/lnd/info/status
middleware | Error: ENOENT: no such file or directory, open ‘/lnd/tls.cert’
middleware | ::ffff:10.21.21.2 - - [Tue, 14 Dec 2021 23:51:22 GMT] “GET /v1/lnd/info/status HTTP/1.0” 500 57 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36”
middleware |
middleware | umbrel-middleware
middleware | ENOENT: no such file or directory, open ‘/lnd/tls.cert’
middleware | /v1/lnd/info/status
middleware | Error: ENOENT: no such file or directory, open ‘/lnd/tls.cert’
middleware | ::ffff:10.21.21.2 - - [Tue, 14 Dec 2021 23:51:23 GMT] “GET /v1/lnd/info/status HTTP/1.0” 500 57 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36”
middleware |
middleware | umbrel-middleware
middleware | ENOENT: no such file or directory, open ‘/lnd/tls.cert’
middleware | /v1/lnd/info/status
middleware | Error: ENOENT: no such file or directory, open ‘/lnd/tls.cert’
manager | ::ffff:10.21.21.2 - - [Tue, 14 Dec 2021 23:33:29 GMT] “GET /v1/system/update-status HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 14 Dec 2021 23:33:31 GMT] “GET /ping HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36”
manager |
manager | umbrel-manager

Bitcoin Core logs

Attaching to bitcoin
bitcoin | 2021-12-14T22:11:49Z New outbound peer connected: version: 70016, blocks=714174, peer=94 (block-relay-only)
bitcoin | 2021-12-14T22:12:33Z Socks5() connect to yg6o54ia4dnihv5c7bpzbtdy66uhrktkx5q4egt3ardvhzdr2azu4nad.onion:8333 failed: host unreachable
bitcoin | 2021-12-14T22:13:19Z New outbound peer connected: version: 70016, blocks=714174, peer=95 (block-relay-only)
bitcoin | 2021-12-14T22:14:48Z New outbound peer connected: version: 70016, blocks=714174, peer=97 (block-relay-only)
bitcoin | 2021-12-14T22:24:06Z New outbound peer connected: version: 70015, blocks=714174, peer=99 (block-relay-only)
bitcoin | 2021-12-14T22:30:54Z UpdateTip: new best=000000000000000000085fdc889506f714f7b4cb931943b23bd100da8c7086bc height=714175 version=0x20600000 log2_work=93.229461 tx=694973326 date=‘2021-12-14T22:30:24Z’ progress=1.000000 cache=39.2MiB(285547txo)
bitcoin | 2021-12-14T22:39:10Z New outbound peer connected: version: 70016, blocks=714175, peer=100 (block-relay-only)
bitcoin | 2021-12-14T22:44:13Z Socks5() connect to y4exexee256yibouatijex6b7u5uj5lqt55swliid7h7nb3othxgbhid.onion:8333 failed: host unreachable
bitcoin | 2021-12-14T22:45:02Z UpdateTip: new best=00000000000000000007dcf0c0fd8dfe65e42e29559e9f4ea736fd11fc009437 height=714176 version=0x20e00004 log2_work=93.229474 tx=694976723 date=‘2021-12-14T22:44:55Z’ progress=1.000000 cache=40.5MiB(296635txo)
bitcoin | 2021-12-14T22:56:48Z Socks5() connect to 213.91.236.220:8333 failed: general failure
bitcoin | 2021-12-14T22:58:18Z UpdateTip: new best=00000000000000000002dafbcb2730ff9ed05b043df4ad739ccb4b414559d95b height=714177 version=0x20836004 log2_work=93.229487 tx=694979495 date=‘2021-12-14T22:58:09Z’ progress=1.000000 cache=41.5MiB(304776txo)
bitcoin | 2021-12-14T22:58:53Z Socks5() connect to 120.74.20.225:8333 failed: general failure
bitcoin | 2021-12-14T23:02:18Z Socks5() connect to 193.176.86.102:8333 failed: TTL expired
bitcoin | 2021-12-14T23:03:07Z Socks5() connect to 146.52.148.160:8333 failed: general failure
bitcoin | 2021-12-14T23:07:09Z Socks5() connect to 2600:6c40:4300:3700::110:8333 failed: general failure
bitcoin | 2021-12-14T23:12:07Z New outbound peer connected: version: 70015, blocks=714177, peer=104 (block-relay-only)
bitcoin | 2021-12-14T23:15:35Z Socks5() connect to 84.38.187.236:8333 failed: general failure
bitcoin | 2021-12-14T23:22:30Z New outbound peer connected: version: 70016, blocks=714177, peer=107 (block-relay-only)
bitcoin | 2021-12-14T23:24:55Z UpdateTip: new best=00000000000000000000b82393eb6390159ecdb987cd96c6b0c29e9ebb8f4e7c height=714178 version=0x20000004 log2_work=93.229500 tx=694982985 date=‘2021-12-14T23:24:51Z’ progress=1.000000 cache=43.2MiB(318308txo)
bitcoin | 2021-12-14T23:31:42Z UpdateTip: new best=00000000000000000005253176cc2a86bf51ab8d9a1bfeef4999bacd789e3631 height=714179 version=0x20004004 log2_work=93.229513 tx=694985603 date=‘2021-12-14T23:31:03Z’ progress=1.000000 cache=44.0MiB(324904txo)
bitcoin | 2021-12-14T23:33:12Z New outbound peer connected: version: 70016, blocks=714179, peer=112 (block-relay-only)
bitcoin | 2021-12-14T23:37:55Z Socks5() connect to 78.154.161.132:8333 failed: general failure
bitcoin | 2021-12-14T23:41:01Z UpdateTip: new best=0000000000000000000b3ad1bc1ba2539d5421fc50bb2b2a81d4520c17f09642 height=714180 version=0x20000004 log2_work=93.229526 tx=694988400 date=‘2021-12-14T23:40:41Z’ progress=1.000000 cache=44.7MiB(330390txo)
bitcoin | 2021-12-14T23:41:24Z UpdateTip: new best=00000000000000000004ebe2f9bff281cb944d2f18ba9576b0597d97aa07c13e height=714181 version=0x27ffe004 log2_work=93.229539 tx=694991459 date=‘2021-12-14T23:41:04Z’ progress=1.000000 cache=45.0MiB(332937txo)
bitcoin | 2021-12-14T23:43:14Z UpdateTip: new best=00000000000000000006f6ebdb6800d819fb5c3b0ae2716ad6afb0ffe350a56f height=714182 version=0x20b16000 log2_work=93.229552 tx=694995452 date=‘2021-12-14T23:42:46Z’ progress=1.000000 cache=45.6MiB(338271txo)
bitcoin | 2021-12-14T23:45:19Z UpdateTip: new best=00000000000000000008b0696117aee37b0ea799fad38481ea4abb9a333c1683 height=714183 version=0x20400000 log2_work=93.229565 tx=694999716 date=‘2021-12-14T23:44:48Z’ progress=1.000000 cache=46.4MiB(344649txo)
bitcoin | 2021-12-14T23:46:05Z New outbound peer connected: version: 70015, blocks=714183, peer=113 (block-relay-only)
bitcoin | 2021-12-14T23:47:45Z UpdateTip: new best=000000000000000000026bf2a0ece06f8a9a0ff83e587ea437d8a86da8bceae4 height=714184 version=0x20200000 log2_work=93.229578 tx=695001696 date=‘2021-12-14T23:47:29Z’ progress=1.000000 cache=46.5MiB(345717txo)
bitcoin | 2021-12-14T23:48:38Z New outbound peer connected: version: 70016, blocks=714184, peer=114 (block-relay-only)
bitcoin | 2021-12-14T23:49:50Z Socks5() connect to 2a01:4f8:191:422c::2:8333 failed: general failure

LND logs

Attaching to lnd
lnd | failed to load config: /data/.lnd/lnd.conf:40: malformed key=value (W[[Application Options])
lnd | failed to load config: /data/.lnd/lnd.conf:40: malformed key=value (W[[Application Options])
lnd | failed to load config: /data/.lnd/lnd.conf:40: malformed key=value (W[[Application Options])
lnd | failed to load config: /data/.lnd/lnd.conf:40: malformed key=value (W[[Application Options])

electrs logs

Attaching to electrs
electrs | [2021-12-14T23:11:32.770Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 121, 34, 185, 97, 13, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 202, 105, 45, 18, 32, 141] }
electrs | [2021-12-14T23:14:31.065Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 218, 36, 185, 97, 9, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 109, 123, 213, 130, 32, 141] }
electrs | [2021-12-14T23:16:23.035Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 102, 37, 185, 97, 9, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 164, 68, 105, 133, 32, 141] }
electrs | [2021-12-14T23:20:17.008Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 159, 37, 185, 97, 13, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 201, 99, 15, 32, 141] }
electrs | [2021-12-14T23:22:46.157Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 19, 39, 185, 97, 13, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 24, 180, 65, 76, 32, 141] }
electrs | [2021-12-14T23:24:29.623Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 81, 37, 185, 97, 9, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 94, 209, 115, 52, 32, 141] }
electrs | [2021-12-14T23:24:55.548Z INFO electrs::index] indexing 1 blocks: [714178…714178]
electrs | [2021-12-14T23:24:55.684Z INFO electrs::chain] chain updated: tip=00000000000000000000b82393eb6390159ecdb987cd96c6b0c29e9ebb8f4e7c, height=714178
electrs | [2021-12-14T23:25:33.063Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 189, 39, 185, 97, 9, 4, 0, 0, 0, 0, 0, 0, 42, 1, 4, 248, 2, 33, 67, 150, 0, 0, 0, 0, 0, 0, 0, 2, 32, 141] }
electrs | [2021-12-14T23:29:05.185Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 11, 40, 185, 97, 13, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 35, 189, 42, 216, 32, 141] }
electrs | [2021-12-14T23:30:25.203Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 164, 40, 185, 97, 9, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 35, 203, 4, 36, 32, 141] }
electrs | [2021-12-14T23:31:43.170Z INFO electrs::index] indexing 1 blocks: [714179…714179]
electrs | [2021-12-14T23:31:43.392Z INFO electrs::chain] chain updated: tip=00000000000000000005253176cc2a86bf51ab8d9a1bfeef4999bacd789e3631, height=714179
electrs | [2021-12-14T23:35:03.725Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [2, 83, 40, 185, 97, 9, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 173, 205, 92, 150, 214, 21, 72, 40, 185, 97, 9, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 188, 138, 88, 14, 32, 141] }
electrs | [2021-12-14T23:37:11.295Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 234, 40, 185, 97, 8, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 49, 156, 252, 236, 32, 141] }
electrs | [2021-12-14T23:38:34.507Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 103, 42, 185, 97, 9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 188, 166, 7, 133, 32, 141] }
electrs | [2021-12-14T23:39:10.552Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [2, 194, 41, 185, 97, 8, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 8, 210, 203, 247, 32, 141, 207, 41, 185, 97, 9, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 220, 250, 63, 248, 32, 141] }
electrs | [2021-12-14T23:41:01.372Z INFO electrs::index] indexing 1 blocks: [714180…714180]
electrs | [2021-12-14T23:41:01.495Z INFO electrs::chain] chain updated: tip=0000000000000000000b3ad1bc1ba2539d5421fc50bb2b2a81d4520c17f09642, height=714180
electrs | [2021-12-14T23:41:25.312Z INFO electrs::index] indexing 1 blocks: [714181…714181]
electrs | [2021-12-14T23:41:25.435Z INFO electrs::chain] chain updated: tip=00000000000000000004ebe2f9bff281cb944d2f18ba9576b0597d97aa07c13e, height=714181
electrs | [2021-12-14T23:43:09.350Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 160, 43, 185, 97, 9, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 220, 75, 229, 132, 32, 191] }
electrs | [2021-12-14T23:43:14.732Z INFO electrs::index] indexing 1 blocks: [714182…714182]
electrs | [2021-12-14T23:43:14.862Z INFO electrs::chain] chain updated: tip=00000000000000000006f6ebdb6800d819fb5c3b0ae2716ad6afb0ffe350a56f, height=714182
electrs | [2021-12-14T23:43:54.521Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 199, 41, 185, 97, 13, 4, 0, 0, 0, 0, 0, 0, 38, 3, 112, 129, 39, 0, 234, 240, 28, 161, 77, 55, 111, 85, 80, 61, 32, 141] }
electrs | [2021-12-14T23:45:19.708Z INFO electrs::index] indexing 1 blocks: [714183…714183]
electrs | [2021-12-14T23:45:19.847Z INFO electrs::chain] chain updated: tip=00000000000000000008b0696117aee37b0ea799fad38481ea4abb9a333c1683, height=714183
electrs | [2021-12-14T23:47:45.926Z INFO electrs::index] indexing 1 blocks: [714184…714184]
electrs | [2021-12-14T23:47:46.039Z INFO electrs::chain] chain updated: tip=000000000000000000026bf2a0ece06f8a9a0ff83e587ea437d8a86da8bceae4, height=714184
electrs | [2021-12-14T23:49:50.062Z WARN electrs::p2p] unexpected message: Unknown { command: CommandString(“addr”), payload: [1, 134, 45, 185, 97, 9, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 144, 91, 93, 126, 32, 141] }

Tor logs

Attaching to tor, umbrel_app_2_tor_1, umbrel_app_3_tor_1, umbrel_app_tor_1
app_2_tor_1 | Dec 14 16:50:03.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
app_2_tor_1 | Dec 14 16:50:03.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
app_2_tor_1 | Dec 14 16:50:04.000 [notice] Bootstrapped 100% (done): Done
app_2_tor_1 | Dec 14 16:50:21.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 103 buildtimes.
app_2_tor_1 | Dec 14 16:50:23.000 [notice] Guard TorZabehlice ($3D5D6178C44537E3692853B344385F6572A55767) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 103/151. Use counts are 63/63. 103 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
app_2_tor_1 | Dec 14 16:50:23.000 [warn] Guard TorZabehlice ($3D5D6178C44537E3692853B344385F6572A55767) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 103/207. Use counts are 63/63. 103 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
app_2_tor_1 | Dec 14 22:49:49.000 [notice] Heartbeat: Tor’s uptime is 6:00 hours, with 71 circuits open. I’ve sent 16.76 MB and received 10.33 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 12 connections with IPv4 and 0 with IPv6.
app_2_tor_1 | Dec 14 22:49:49.000 [notice] While bootstrapping, fetched this many bytes: 612780 (consensus network-status fetch); 14134 (authority cert fetch); 4530323 (microdescriptor fetch)
app_2_tor_1 | Dec 14 22:49:49.000 [notice] While not bootstrapping, fetched this many bytes: 156381 (consensus network-status fetch); 106278 (microdescriptor fetch)
app_2_tor_1 | Dec 14 22:49:49.000 [notice] Our onion services received 0 v2 and 0 v3 INTRODUCE2 cells and attempted to launch 0 rendezvous circuits.
tor | Dec 14 22:44:13.000 [notice] Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
tor | Dec 14 22:49:50.000 [notice] Heartbeat: Tor’s uptime is 6:00 hours, with 79 circuits open. I’ve sent 118.96 MB and received 123.24 MB. I’ve received 277 connections on IPv4 and 0 on IPv6. I’ve made 11 connections with IPv4 and 0 with IPv6.
tor | Dec 14 22:49:50.000 [notice] While bootstrapping, fetched this many bytes: 612780 (consensus network-status fetch); 13144 (authority cert fetch); 4985550 (microdescriptor fetch)
tor | Dec 14 22:49:50.000 [notice] While not bootstrapping, fetched this many bytes: 156870 (consensus network-status fetch); 107407 (microdescriptor fetch)
tor | Dec 14 22:49:50.000 [notice] Average packaged cell fullness: 33.406%. TLS write overhead: 3%
tor | Dec 14 22:49:50.000 [notice] Our onion services received 0 v2 and 0 v3 INTRODUCE2 cells and attempted to launch 0 rendezvous circuits.
tor | Dec 14 22:56:48.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Dec 14 22:58:53.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Dec 14 23:03:07.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Dec 14 23:15:35.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
app_3_tor_1 | Dec 14 16:50:03.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
app_3_tor_1 | Dec 14 16:50:03.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
app_3_tor_1 | Dec 14 16:50:04.000 [notice] Bootstrapped 100% (done): Done
app_3_tor_1 | Dec 14 16:50:18.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 111 buildtimes.
app_3_tor_1 | Dec 14 16:50:25.000 [notice] Guard masterchief ($99EC64FE9EF0E0ECEC3E125A2327C2779C1E7947) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 112/161. Use counts are 72/72. 112 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
app_3_tor_1 | Dec 14 16:50:26.000 [warn] Guard masterchief ($99EC64FE9EF0E0ECEC3E125A2327C2779C1E7947) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 112/225. Use counts are 72/72. 112 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
app_3_tor_1 | Dec 14 22:49:49.000 [notice] Heartbeat: Tor’s uptime is 6:00 hours, with 99 circuits open. I’ve sent 19.53 MB and received 11.92 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 14 connections with IPv4 and 0 with IPv6.
app_3_tor_1 | Dec 14 22:49:49.000 [notice] While bootstrapping, fetched this many bytes: 612780 (consensus network-status fetch); 14134 (authority cert fetch); 4865080 (microdescriptor fetch)
app_3_tor_1 | Dec 14 22:49:49.000 [notice] While not bootstrapping, fetched this many bytes: 136402 (consensus network-status fetch); 90326 (microdescriptor fetch)
app_3_tor_1 | Dec 14 22:49:49.000 [notice] Our onion services received 0 v2 and 0 v3 INTRODUCE2 cells and attempted to launch 0 rendezvous circuits.
app_tor_1 | Dec 14 16:50:05.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
app_tor_1 | Dec 14 16:50:05.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
app_tor_1 | Dec 14 16:50:06.000 [notice] Bootstrapped 100% (done): Done
app_tor_1 | Dec 14 16:50:23.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 101 buildtimes.
app_tor_1 | Dec 14 16:50:24.000 [notice] Guard cubieserver ($BAE10387321FDD3279EA44320720B919777FE640) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 101/151. Use counts are 62/62. 101 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
app_tor_1 | Dec 14 16:50:24.000 [warn] Guard cubieserver ($BAE10387321FDD3279EA44320720B919777FE640) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 102/205. Use counts are 63/63. 102 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
app_tor_1 | Dec 14 22:49:50.000 [notice] Heartbeat: Tor’s uptime is 6:00 hours, with 78 circuits open. I’ve sent 14.92 MB and received 10.77 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 19 connections with IPv4 and 0 with IPv6.
app_tor_1 | Dec 14 22:49:50.000 [notice] While bootstrapping, fetched this many bytes: 612780 (consensus network-status fetch); 14134 (authority cert fetch); 4985704 (microdescriptor fetch)
app_tor_1 | Dec 14 22:49:50.000 [notice] While not bootstrapping, fetched this many bytes: 129191 (consensus network-status fetch); 101156 (microdescriptor fetch)
app_tor_1 | Dec 14 22:49:50.000 [notice] Our onion services received 0 v2 and 0 v3 INTRODUCE2 cells and attempted to launch 0 rendezvous circuits.
================
==== Result ====
================
The debug script did not automatically detect any issues with your Umbrel.

Hey @louneskmt, pinging you on this one - I had him run the command:

sudo systemctl stop umbrel-startup && sudo rm -rf ~/umbrel/lnd/!(lnd.conf) && sudo rm -f ~/umbrel/db/user.json && sudo rm -f ~/umbrel/db/umbrel-seed/seed && sudo systemctl start umbrel-startup

Looks like his bitcoin is resyncing, not sure if the other errors are an issue or if it’s just a waiting game at this point.

fyi, my current debug log still shows the same. may it be related to the recent version issue?

We did discover an issue with 4.10 that is causing issues for some new installations - can you try reformatting your drive, and also reflashing your SD card back down to v4.9?

May i try reflashing my SD card with v4.9 before reformatting the drive?
If i have to reformat the drive(which means I have to download the blockchain again), can you give me some direction to do it?
I heard Windows OS doesn’t recognize Ext4, so I am not sure its a proper way to execute reformat using my laptop. I may have to do it through SSH terminal.
Any instruction is very much appreciated. Thank you.

Actually, try ssh’ing and running this command, our devs said it might help:

docker pull getumbrel/dashboard:v0.3.31 && sed -i “s/v0.3.30@sha256:b784e7796e60ba23770b552f99950db4640008fe4f5eebf2731bea8198e66665/v0.3.31/g;” ~/umbrel/docker-compose.yml && sudo systemctl restart umbrel-startup

If that doesn’t work, then yes, reflash to 4.9, to reformat, just stick your drive into your PC, right click the drive and click “format” (doesn’t really matter what you format it to, you mostly just want the data off of it) - umbrel will detect and reformat it back to ext4 as part of its startup process.