New Umbrel setup - bitcoin core stuck syncing at 92%

Hi all
My Umbrel is up and running and I can access it fine. But the syncing of bitcoin core seems to have stopped at a certain block / %.
What can i do to confirm if there is an error, or if it is just now very slow?
I am copying a section of the log for reference.

=====================
= Umbrel debug info =

Temperature

temp=55.5’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 7.8G 923M 2.0G 17M 4.9G 6.8G
Swap: 4.1G 0B 4.1G

total: 11.8%
lnd: 5.7%
bitcoin: 4.6%
system: 0.8%
tor: 0.5%
electrs: 0.2%

External storage service logs

– Logs begin at Mon 2021-11-29 12:13:52 UTC, end at Mon 2021-11-29 17:32:39 UTC. –
Nov 29 12:13:57 umbrel systemd[1]: Starting External Storage Mounter…
Nov 29 12:13:57 umbrel external storage mounter[487]: Running external storage mount script…
Nov 29 12:13:57 umbrel external storage mounter[487]: Found device “USB3.0 Extemal HDD”
Nov 29 12:13:57 umbrel external storage mounter[487]: Blacklisting USB device IDs against UAS driver…
Nov 29 12:13:57 umbrel external storage mounter[487]: Rebinding USB drivers…
Nov 29 12:13:57 umbrel external storage mounter[487]: Checking USB devices are back…
Nov 29 12:13:57 umbrel external storage mounter[487]: Waiting for USB devices…
Nov 29 12:13:58 umbrel external storage mounter[487]: Waiting for USB devices…
Nov 29 12:13:59 umbrel external storage mounter[487]: Checking if the device is ext4…
Nov 29 12:14:00 umbrel external storage mounter[487]: Yes, it is ext4
Nov 29 12:14:00 umbrel external storage mounter[487]: Checking if device contains an Umbrel install…
Nov 29 12:14:00 umbrel external storage mounter[487]: Yes, it contains an Umbrel install
Nov 29 12:14:00 umbrel external storage mounter[487]: Bind mounting external storage over local Umbrel installation…
Nov 29 12:14:00 umbrel external storage mounter[487]: Bind mounting external storage over local Docker data dir…
Nov 29 12:14:00 umbrel external storage mounter[487]: Bind mounting external storage to /swap
Nov 29 12:14:00 umbrel external storage mounter[487]: Bind mounting SD card root at /sd-card…
Nov 29 12:14:00 umbrel external storage mounter[487]: Checking Umbrel root is now on external storage…
Nov 29 12:14:01 umbrel external storage mounter[487]: Checking /var/lib/docker is now on external storage…
Nov 29 12:14:01 umbrel external storage mounter[487]: Checking /swap is now on external storage…
Nov 29 12:14:01 umbrel external storage mounter[487]: Setting up swapfile
Nov 29 12:14:01 umbrel external storage mounter[487]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
Nov 29 12:14:01 umbrel external storage mounter[487]: no label, UUID=ee524974-4081-498f-8110-c48abe9f97c1
Nov 29 12:14:01 umbrel external storage mounter[487]: Checking SD Card root is bind mounted at /sd-root…
Nov 29 12:14:01 umbrel external storage mounter[487]: Starting external drive mount monitor…
Nov 29 12:14:01 umbrel external storage mounter[487]: Mount script completed successfully!
Nov 29 12:14:01 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Mon 2021-11-29 12:13:52 UTC, end at Mon 2021-11-29 17:32:39 UTC. –
Nov 29 12:14:12 umbrel systemd[1]: Starting External Storage SDcard Updater…
Nov 29 12:14:12 umbrel external storage updater[930]: Checking if SD card Umbrel is newer than external storage…
Nov 29 12:14:12 umbrel external storage updater[930]: No, SD version is not newer, exiting.
Nov 29 12:14:12 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

Stopping nginx … done
Stopping manager … done
Stopping dashboard … done
Stopping tor … done
Removing neutrino-switcher …
Removing middleware …
Removing bitcoin …
Removing nginx …
Removing lnd …
Removing manager …
Removing dashboard …
Removing umbrel_app_2_tor_1 …
Removing tor …
Removing electrs …
Removing umbrel_app_3_tor_1 …
Removing umbrel_app_tor_1 …
Removing dashboard … done
Removing bitcoin … done
Removing neutrino-switcher … done
Removing manager … done
Removing electrs … done
Removing umbrel_app_2_tor_1 … done
Removing nginx … done
Removing umbrel_app_tor_1 … done
Removing umbrel_app_3_tor_1 … done
Removing tor … done
Removing middleware … done
Removing lnd … done
Removing network umbrel_main_network
karen is running in /home/umbrel/umbrel/events
Got signal:
karen is getting triggered!
./karen: line 68: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal:
karen is getting triggered!
./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
Got signal: debug
karen is getting triggered!
Debug result file generated
Got signal: debug
karen is getting triggered!

Docker containers

NAMES STATUS
middleware Up 5 hours
neutrino-switcher Up 5 hours
bitcoin Up 15 seconds
lnd Up 5 hours
nginx Up 5 hours
manager Up 5 hours
umbrel_app_3_tor_1 Up 5 hours
umbrel_app_2_tor_1 Up 5 hours
tor Up 5 hours
electrs Up 2 seconds
dashboard Up 5 hours
umbrel_app_tor_1 Up 5 hours

Umbrel logs

Attaching to middleware, manager
manager | ::ffff:10.21.21.2 - - [Mon, 29 Nov 2021 17:32:26 GMT] “GET /v1/external/price HTTP/1.0” 200 312 “-” “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 - - [Mon, 29 Nov 2021 17:32:33 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 - - [Mon, 29 Nov 2021 17:32:36 GMT] “GET /v1/system/dashboard-hidden-service 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 - - [Mon, 29 Nov 2021 17:32:36 GMT] “GET /v1/system/uptime HTTP/1.0” 200 5 “-” “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 - - [Mon, 29 Nov 2021 17:32:36 GMT] “GET /v1/system/info 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 - - [Mon, 29 Nov 2021 17:32:36 GMT] “GET /v1/apps 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 - - [Mon, 29 Nov 2021 17:32:36 GMT] “GET /v1/apps?installed=1 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 - - [Mon, 29 Nov 2021 17:32:40 GMT] “POST /v1/system/debug HTTP/1.0” 200 17 “-” “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
middleware | at endReadableNT (_stream_readable.js:1241:12)
middleware | at /app/node_modules/async-listener/glue.js:188:31
middleware | at processTicksAndRejections (internal/process/task_queues.js:84:21)
middleware | ::ffff:10.21.21.2 - - [Mon, 29 Nov 2021 17:32:32 GMT] “GET /v1/bitcoind/info/sync HTTP/1.0” 500 28 “-” “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 | Unable to obtain peer info
middleware | /v1/bitcoind/info/sync
middleware | BitcoindError: Unable to obtain peer info
middleware | at /app/services/bitcoind.js:24:18
middleware | at IncomingMessage. (/app/node_modules/bitcoind-rpc/lib/index.js:107:7)
middleware | at IncomingMessage.emit (events.js:326:22)
middleware | at endReadableNT (_stream_readable.js:1241:12)
middleware | at /app/node_modules/async-listener/glue.js:188:31
middleware | at processTicksAndRejections (internal/process/task_queues.js:84:21)
middleware | ::ffff:10.21.21.2 - - [Mon, 29 Nov 2021 17:32:34 GMT] “GET /v1/bitcoind/info/sync HTTP/1.0” 500 28 “-” “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 | Unable to obtain peer info
middleware | /v1/bitcoind/info/sync
middleware | BitcoindError: Unable to obtain peer info
middleware | at /app/services/bitcoind.js:24:18
middleware | at IncomingMessage. (/app/node_modules/bitcoind-rpc/lib/index.js:107:7)
middleware | at IncomingMessage.emit (events.js:326:22)
middleware | at endReadableNT (_stream_readable.js:1241:12)
middleware | at /app/node_modules/async-listener/glue.js:188:31
middleware | at processTicksAndRejections (internal/process/task_queues.js:84:21)
middleware | ::ffff:10.21.21.2 - - [Mon, 29 Nov 2021 17:32:36 GMT] “GET /v1/bitcoind/info/sync HTTP/1.0” 500 28 “-” “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
manager | ::ffff:10.21.21.2 - - [Mon, 29 Nov 2021 17:32:41 GMT] “GET /v1/system/debug-result HTTP/1.0” 200 23 “-” “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 - - [Mon, 29 Nov 2021 17:32:42 GMT] “GET /v1/system/debug-result 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-11-29T17:32:26Z HTTP: creating work queue of depth 64
bitcoin | 2021-11-29T17:32:26Z Using random cookie authentication.
bitcoin | 2021-11-29T17:32:26Z Generated RPC authentication cookie /data/.bitcoin/.cookie
bitcoin | 2021-11-29T17:32:26Z Using rpcauth authentication.
bitcoin | 2021-11-29T17:32:26Z HTTP: starting 4 worker threads
bitcoin | 2021-11-29T17:32:26Z Using wallet directory /data/.bitcoin
bitcoin | 2021-11-29T17:32:26Z init message: Verifying wallet(s)…
bitcoin | 2021-11-29T17:32:26Z init message: Loading banlist…
bitcoin | 2021-11-29T17:32:26Z SetNetworkActive: true
bitcoin | 2021-11-29T17:32:26Z Using /16 prefix for IP bucketing
bitcoin | 2021-11-29T17:32:26Z Cache configuration:
bitcoin | 2021-11-29T17:32:26Z * Using 2.0 MiB for block index database
bitcoin | 2021-11-29T17:32:26Z * Using 24.8 MiB for transaction index database
bitcoin | 2021-11-29T17:32:26Z * Using 21.7 MiB for basic block filter index database
bitcoin | 2021-11-29T17:32:26Z * Using 8.0 MiB for chain state database
bitcoin | 2021-11-29T17:32:26Z * Using 143.6 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
bitcoin | 2021-11-29T17:32:26Z init message: Loading block index…
bitcoin | 2021-11-29T17:32:26Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
bitcoin | 2021-11-29T17:32:26Z Opening LevelDB in /data/.bitcoin/blocks/index
bitcoin | 2021-11-29T17:32:26Z Opened LevelDB successfully
bitcoin | 2021-11-29T17:32:26Z Using obfuscation key for /data/.bitcoin/blocks/index: 0000000000000000
bitcoin | 2021-11-29T17:32:40Z LoadBlockIndexDB: last block file = 2540
bitcoin | 2021-11-29T17:32:40Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=21, size=26294304, heights=679140…679512, time=2021-04-14…2021-04-16)
bitcoin | 2021-11-29T17:32:40Z Checking all blk files are present…
bitcoin | 2021-11-29T17:32:40Z Opening LevelDB in /data/.bitcoin/chainstate
bitcoin | 2021-11-29T17:32:40Z Opened LevelDB successfully
bitcoin | 2021-11-29T17:32:40Z Using obfuscation key for /data/.bitcoin/chainstate: b02ccb28e27b78fd
bitcoin | 2021-11-29T17:32:41Z Loaded best chain: hashBestChain=000000000000000000016f6493dd6d439d81ff8667e23f7dad8bd2d9ab5dc2ba height=679156 date=2021-04-14T08:47:23Z progress=0.926143
bitcoin | 2021-11-29T17:32:41Z init message: Verifying blocks…
bitcoin | 2021-11-29T17:32:41Z Verifying last 6 blocks at level 3

LND logs

Attaching to lnd
lnd | 2021-11-29 17:23:52.925 [INF] CRTR: Processed channels=0 updates=120 nodes=26 in last 59.998834904s
lnd | 2021-11-29 17:23:54.102 [INF] DISC: Broadcasting 216 new announcements in 18 sub batches
lnd | 2021-11-29 17:24:52.926 [INF] CRTR: Processed channels=0 updates=172 nodes=7 in last 1m0.000528055s
lnd | 2021-11-29 17:25:24.102 [INF] DISC: Broadcasting 265 new announcements in 18 sub batches
lnd | 2021-11-29 17:25:52.925 [INF] CRTR: Processed channels=0 updates=144 nodes=19 in last 59.998826665s
lnd | 2021-11-29 17:26:35.517 [INF] BTCN: Processed 1 block in the last 24m12.47s (height 711829, 2021-11-29 17:25:53 +0000 UTC)
lnd | 2021-11-29 17:26:35.520 [INF] BTCN: Attempting to fetch set of un-checkpointed filters at height=711829, hash=00000000000000000005e26d3f518c78568b11baa0afb8379c274f93f5f8107c
lnd | 2021-11-29 17:26:45.526 [INF] BTCN: Verified 1 filter header in the last 24m12.47s (height 711829, 2021-11-29 17:25:53 +0000 UTC)
lnd | 2021-11-29 17:26:46.236 [INF] NTFN: New block: height=711829, sha=00000000000000000005e26d3f518c78568b11baa0afb8379c274f93f5f8107c
lnd | 2021-11-29 17:26:46.236 [INF] UTXN: Attempting to graduate height=711829: num_kids=0, num_babies=0
lnd | 2021-11-29 17:26:52.926 [INF] CRTR: Processed channels=0 updates=132 nodes=26 in last 1m0.000589922s
lnd | 2021-11-29 17:26:54.102 [INF] DISC: Broadcasting 231 new announcements in 18 sub batches
lnd | 2021-11-29 17:27:52.926 [INF] CRTR: Processed channels=0 updates=119 nodes=6 in last 59.999537936s
lnd | 2021-11-29 17:28:24.102 [INF] DISC: Broadcasting 195 new announcements in 18 sub batches
lnd | 2021-11-29 17:28:52.925 [INF] CRTR: Processed channels=0 updates=114 nodes=7 in last 59.999322356s
lnd | 2021-11-29 17:29:20.401 [INF] BTCN: Processed 1 block in the last 2m44.88s (height 711830, 2021-11-29 17:28:32 +0000 UTC)
lnd | 2021-11-29 17:29:20.404 [INF] BTCN: Attempting to fetch set of un-checkpointed filters at height=711830, hash=000000000000000000098076b42f5333051673c05e863234caab200f7855d79b
lnd | 2021-11-29 17:29:30.409 [INF] BTCN: Verified 1 filter header in the last 2m44.88s (height 711830, 2021-11-29 17:28:32 +0000 UTC)
lnd | 2021-11-29 17:29:31.039 [INF] NTFN: New block: height=711830, sha=000000000000000000098076b42f5333051673c05e863234caab200f7855d79b
lnd | 2021-11-29 17:29:31.040 [INF] UTXN: Attempting to graduate height=711830: num_kids=0, num_babies=0
lnd | 2021-11-29 17:29:52.525 [INF] BTCN: Processed 1 block in the last 32.12s (height 711831, 2021-11-29 17:29:34 +0000 UTC)
lnd | 2021-11-29 17:29:52.528 [INF] BTCN: Attempting to fetch set of un-checkpointed filters at height=711831, hash=000000000000000000038ff8d484e366993ffe313df74ea3bd4117a614a6d43b
lnd | 2021-11-29 17:29:52.926 [INF] CRTR: Processed channels=0 updates=100 nodes=18 in last 1m0.000361395s
lnd | 2021-11-29 17:29:54.102 [INF] DISC: Broadcasting 171 new announcements in 18 sub batches
lnd | 2021-11-29 17:30:02.534 [INF] BTCN: Verified 1 filter header in the last 32.12s (height 711831, 2021-11-29 17:29:34 +0000 UTC)
lnd | 2021-11-29 17:30:03.165 [INF] NTFN: New block: height=711831, sha=000000000000000000038ff8d484e366993ffe313df74ea3bd4117a614a6d43b
lnd | 2021-11-29 17:30:03.165 [INF] UTXN: Attempting to graduate height=711831: num_kids=0, num_babies=0
lnd | 2021-11-29 17:30:52.925 [INF] CRTR: Processed channels=1 updates=142 nodes=5 in last 59.999162786s
lnd | 2021-11-29 17:31:24.102 [INF] DISC: Broadcasting 253 new announcements in 17 sub batches
lnd | 2021-11-29 17:31:52.925 [INF] CRTR: Processed channels=0 updates=204 nodes=13 in last 1m0.000107471s

electrs logs

Attaching to electrs
electrs | [2021-11-29T17:32:08.706Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-11-29T17:32:09.708Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-11-29T17:32:10.710Z INFO electrs::daemon] waiting for RPC warmup: Loading P2P addresses…
electrs | [2021-11-29T17:32:11.713Z INFO electrs::daemon] waiting for 32335 blocks to download (IBD)
electrs | [2021-11-29T17:32:12.715Z INFO electrs::daemon] waiting for 32335 blocks to download (IBD)
electrs | [2021-11-29T17:32:13.718Z INFO electrs::daemon] waiting for 32335 blocks to download (IBD)
electrs | [2021-11-29T17:32:14.721Z INFO electrs::daemon] waiting for 32675 blocks to download (IBD)
electrs | [2021-11-29T17:32:15.724Z INFO electrs::daemon] waiting for 32675 blocks to download (IBD)
electrs | [2021-11-29T17:32:16.728Z INFO electrs::daemon] waiting for 32675 blocks to download (IBD)
electrs | [2021-11-29T17:32:22.139Z INFO electrs::daemon] waiting for 32669 blocks to download (IBD)
electrs | [2021-11-29T17:32:38.142Z INFO electrs::db] closing DB at /data/db/bitcoin
electrs | Error: electrs failed
electrs |
electrs | Caused by:
electrs | 0: bitcoind RPC polling failed
electrs | 1: daemon not available
electrs | 2: JSON-RPC error: transport error: Didn’t receive response data in time, timed out.
electrs | Starting electrs 0.9.1 on aarch64 linux with Config { network: Bitcoin, db_path: “/data/db/bitcoin”, daemon_dir: “/data/.bitcoin”, daemon_auth: CookieFile("/data/.bitcoin/.cookie"), daemon_rpc_addr: V4(10.21.21.8:8332), daemon_p2p_addr: V4(10.21.21.8:8333), electrum_rpc_addr: V4(0.0.0.0:50001), monitoring_addr: V4(127.0.0.1:4224), wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: Some(200), reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, disable_electrum_rpc: false, server_banner: “Umbrel v0.4.9”, args: [] }
electrs | [2021-11-29T17:32:39.416Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
electrs | [2021-11-29T17:32:39.641Z INFO electrs::db] “/data/db/bitcoin”: 4817 SST files, 0.003877685 GB, 0.000000021 Grows
electrs | [2021-11-29T17:32:39.720Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-11-29T17:32:40.727Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-11-29T17:32:41.732Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-11-29T17:32:42.736Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-11-29T17:32:43.739Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-11-29T17:32:44.741Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-11-29T17:32:45.745Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-11-29T17:32:46.747Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-11-29T17:32:47.750Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-11-29T17:32:48.753Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…

Tor logs

Attaching to umbrel_app_3_tor_1, umbrel_app_2_tor_1, tor, umbrel_app_tor_1
tor | Nov 29 17:00:39.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Nov 29 17:02:03.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Nov 29 17:05:34.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Nov 29 17:12:52.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Nov 29 17:19:16.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Nov 29 17:22:37.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Nov 29 17:25:52.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Nov 29 17:30:18.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Nov 29 17:32:14.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
app_2_tor_1 | Nov 29 12:16:52.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
app_2_tor_1 | Nov 29 12:16:52.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
app_2_tor_1 | Nov 29 12:16:52.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
app_2_tor_1 | Nov 29 12:16:52.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
app_2_tor_1 | Nov 29 12:16:52.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
app_2_tor_1 | Nov 29 12:16:53.000 [notice] Bootstrapped 100% (done): Done
app_2_tor_1 | Nov 29 12:17:13.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 103 buildtimes.
app_2_tor_1 | Nov 29 12:17:14.000 [notice] Guard mharelay ($00B57BF614F7ED3051073B5D4526FF0B23AF217B) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 103/151. Use counts are 61/61. 103 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
app_2_tor_1 | Nov 29 12:17:14.000 [warn] Guard mharelay ($00B57BF614F7ED3051073B5D4526FF0B23AF217B) 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 61/61. 103 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
app_2_tor_1 | Nov 29 16:33:52.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 779 buildtimes.
app_3_tor_1 | Nov 29 12:16:57.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
app_3_tor_1 | Nov 29 12:16:57.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
app_3_tor_1 | Nov 29 12:16:57.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
app_3_tor_1 | Nov 29 12:16:58.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
app_3_tor_1 | Nov 29 12:16:58.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
app_3_tor_1 | Nov 29 12:16:58.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
app_3_tor_1 | Nov 29 12:16:58.000 [notice] Bootstrapped 100% (done): Done
app_3_tor_1 | Nov 29 12:17:16.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 110 buildtimes.
app_3_tor_1 | Nov 29 12:17:16.000 [notice] Guard Orodruin ($69D9E5F20FE3B0C872936BDE41D136A0F24D6995) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 109/156. Use counts are 69/69. 109 circuits completed, 0 were unusable, 0 collapsed, and 3 timed out. For reference, your timeout cutoff is 60 seconds.
app_3_tor_1 | Nov 29 12:17:16.000 [warn] Guard Orodruin ($69D9E5F20FE3B0C872936BDE41D136A0F24D6995) 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 109/219. Use counts are 69/69. 109 circuits completed, 0 were unusable, 0 collapsed, and 3 timed out. For reference, your timeout cutoff is 60 seconds.
app_tor_1 | Nov 29 12:16:54.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
app_tor_1 | Nov 29 12:16:54.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
app_tor_1 | Nov 29 12:16:54.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
app_tor_1 | Nov 29 12:16:54.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
app_tor_1 | Nov 29 12:16:54.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
app_tor_1 | Nov 29 12:16:54.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
app_tor_1 | Nov 29 12:16:54.000 [notice] Bootstrapped 100% (done): Done
app_tor_1 | Nov 29 12:17:14.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 100 buildtimes.
app_tor_1 | Nov 29 12:17:15.000 [notice] Guard gGDHjdcC6zAlM8k08lX ($11DF0017A43AF1F08825CD5D973297F81AB00FF3) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 99/151. Use counts are 61/61. 99 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
app_tor_1 | Nov 29 12:17:16.000 [warn] Guard gGDHjdcC6zAlM8k08lX ($11DF0017A43AF1F08825CD5D973297F81AB00FF3) 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 100/201. Use counts are 61/61. 100 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.

==== Result ====

The debug script did not automatically detect any issues with your Umbrel.

Txs

Most likely due to intense download of blocks your Tor connection get stuck.
Patience, it will get back by itself after a while.
This is the most hard part of sync, the last 10%, is getting really slow.
Don’t do anything, just wait.
only one thing can do is to monitor closely:
SSH into umbrel
cd umbrel
sudo docker-compose logs -f bitcoin

And just watch the blocks how are verified.
When you see the height=1.0000 then is done sync
After that will start to kick electrum, and will heavily index the blocks. Will be another 8-10h of max memory used.
BE PATIENT!
You can check then electrs logs
sudo docker-compose logs -f electrs
and see when is finished.
After that and ONLY after that start using your node.

PATIENCE IS THE KEY

See the error at the end

bitcoin | 2021-11-29T18:11:14Z P2P peers available. Skipped DNS seeding.
bitcoin | 2021-11-29T18:11:14Z dnsseed thread exit
bitcoin | 2021-11-29T18:11:14Z UpdateTip: new best=0000000000000000000bd6dea8ad6134bba7a932d57f7d509654574577cd38f7 height=679159 version=0x20000000 log2_work=92.809319 tx=633878991 date=‘2021-04-14T09:34:12Z’ progress=0.926148 cache=5.2MiB(38734txo)
bitcoin | 2021-11-29T18:11:15Z UpdateTip: new best=0000000000000000000ba4c8527b07ac7306653de4c071570af4a3eca8d665de height=679160 version=0x20000000 log2_work=92.809335 tx=633881946 date=‘2021-04-14T09:39:35Z’ progress=0.926153 cache=6.5MiB(49144txo)
bitcoin | 2021-11-29T18:11:16Z UpdateTip: new best=00000000000000000006c8b54dbd6df313a557f801ff27ee760840cbbae0de73 height=679161 version=0x20000000 log2_work=92.809352 tx=633882410 date=‘2021-04-14T09:40:11Z’ progress=0.926153 cache=7.4MiB(56474txo)
bitcoin | 2021-11-29T18:11:16Z UpdateTip: new best=00000000000000000002f20749b4aad191fe45f0d28588b5412e1e70e9804969 height=679162 version=0x20800000 log2_work=92.809368 tx=633885041 date=‘2021-04-14T09:53:45Z’ progress=0.926157 cache=9.2MiB(67118txo)
bitcoin | 2021-11-29T18:11:18Z UpdateTip: new best=000000000000000000082a8bbb9e49b54e89297162e71a11b1732f2a1ffcad4b height=679163 version=0x20004000 log2_work=92.809385 tx=633887004 date=‘2021-04-14T10:06:53Z’ progress=0.926160 cache=10.3MiB(76660txo)
bitcoin | 2021-11-29T18:11:19Z UpdateTip: new best=000000000000000000057a8a0878ab1091a221f274210e0942908f56c3e3185a height=679164 version=0x3fffc000 log2_work=92.809401 tx=633888185 date=‘2021-04-14T10:15:02Z’ progress=0.926162 cache=11.3MiB(84677txo)
bitcoin | 2021-11-29T18:11:19Z LevelDB read failure: Corruption: block checksum mismatch: /data/.bitcoin/chainstate/628457.ldb
bitcoin | 2021-11-29T18:11:19Z Fatal LevelDB error: Corruption: block checksum mismatch: /data/.bitcoin/chainstate/628457.ldb
bitcoin | 2021-11-29T18:11:19Z You can use -debug=leveldb to get more complete diagnostic messages
bitcoin | 2021-11-29T18:11:19Z Error: Error reading from database, shutting down.
bitcoin | 2021-11-29T18:11:19Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /data/.bitcoin/chainstate/628457.ldb
bitcoin | Error: Error reading from database, shutting down.
bitcoin exited with code 139
umbrel@umbrel:~/umbrel $

Ouch, that hurts.
maybe hardware failure, drive disconnected, bad voltage, cabling.
Or just start over and be sure you do not format that drive in NTFS, only ext4

thought there was a problem :frowning:
how do i start over ?.. i just connected the hard drive out of the box 1st time
Txs

even bran new drives can crash. An RPi machines this is usual due to bad voltage, bad power adapter, bad USB cabling, case etc
Just wipe the partition on that drive and tart as new process again.
Re-flash the mSD card also.
If there’s a data corruption this is the best way.

Thanks… real noob question - how do i wipe the partition on the drive … or reformat the drive…
i am accessing the umbrel node from windows 10 pc
i can access with SSH but don’t know what commands to use.
or if i can reformat as ext4 by connecting to my windows 10 pc?

Just take that external case, attach to windows, go to system partition tool, right click on that external drive, delete partition.
Don’t create another one, just delete it.

Thanks.
I already tried using AOMEI partition just now. It seems to have worked. My node is back up and running (I reflashed SD card also). Now syncing again from 0%