2025-07-09T11:26:08Z Included configuration file umbrel-bitcoin.conf
2025-07-09T11:26:09Z Bitcoin Core version v29.0.0 (release build)
2025-07-09T11:26:09Z Using the ‘arm_shani(1way,2way)’ SHA256 implementation
2025-07-09T11:26:09Z Default data directory /home/node/.bitcoin
2025-07-09T11:26:09Z Using data directory /data/bitcoin
2025-07-09T11:26:09Z Config file: /data/bitcoin/bitcoin.conf
2025-07-09T11:26:09Z Config file arg: bantime=“86400”
2025-07-09T11:26:09Z Config file arg: blockfilterindex=“1”
2025-07-09T11:26:09Z Config file arg: chain=“main”
2025-07-09T11:26:09Z Config file arg: datacarrier=“1”
2025-07-09T11:26:09Z Config file arg: datacarriersize=“83”
2025-07-09T11:26:09Z Config file arg: dbcache=“450”
2025-07-09T11:26:09Z Config file arg: i2pacceptincoming=“0”
2025-07-09T11:26:09Z Config file arg: i2psam=“10.21.22.11:7656”
2025-07-09T11:26:09Z Config file arg: includeconf=“umbrel-bitcoin.conf”
2025-07-09T11:26:09Z Config file arg: listen=“1”
2025-07-09T11:26:09Z Config file arg: listenonion=“0”
2025-07-09T11:26:09Z Config file arg: maxconnections=“240”
2025-07-09T11:26:09Z Config file arg: maxmempool=“300”
2025-07-09T11:26:09Z Config file arg: maxorphantx=“100”
2025-07-09T11:26:09Z Config file arg: maxreceivebuffer=“5000”
2025-07-09T11:26:09Z Config file arg: maxsendbuffer=“1000”
2025-07-09T11:26:09Z Config file arg: maxuploadtarget=“0”
2025-07-09T11:26:09Z Config file arg: mempoolexpiry=“336”
2025-07-09T11:26:09Z Config file arg: onion=“10.21.22.10:9050”
2025-07-09T11:26:09Z Config file arg: onlynet=“ipv4”
2025-07-09T11:26:09Z Config file arg: onlynet=“ipv6”
2025-07-09T11:26:09Z Config file arg: onlynet=“onion”
2025-07-09T11:26:09Z Config file arg: onlynet=“i2p”
2025-07-09T11:26:09Z Config file arg: peerblockfilters=“1”
2025-07-09T11:26:09Z Config file arg: peerbloomfilters=“0”
2025-07-09T11:26:09Z Config file arg: peertimeout=“60”
2025-07-09T11:26:09Z Config file arg: permitbaremultisig=“1”
2025-07-09T11:26:09Z Config file arg: persistmempool=“1”
2025-07-09T11:26:09Z Config file arg: prune=“0”
2025-07-09T11:26:09Z Config file arg: rest=“0”
2025-07-09T11:26:09Z Config file arg: rpcallowip=“10.21.0.0/16”
2025-07-09T11:26:09Z Config file arg: rpcallowip=“127.0.0.1”
2025-07-09T11:26:09Z Config file arg: rpcauth=****
2025-07-09T11:26:09Z Config file arg: rpcworkqueue=“128”
2025-07-09T11:26:09Z Config file arg: timeout=“5000”
2025-07-09T11:26:09Z Config file arg: txindex=“1”
2025-07-09T11:26:09Z Config file arg: whitelist=“10.21.0.0/16”
2025-07-09T11:26:09Z Config file arg: whitelist=“127.0.0.1”
2025-07-09T11:26:09Z Config file arg: zmqpubhashblock=“tcp://0.0.0.0:28334”
2025-07-09T11:26:09Z Config file arg: zmqpubhashtx=“tcp://0.0.0.0:28336”
2025-07-09T11:26:09Z Config file arg: zmqpubrawblock=“tcp://0.0.0.0:28332”
2025-07-09T11:26:09Z Config file arg: zmqpubrawtx=“tcp://0.0.0.0:28333”
2025-07-09T11:26:09Z Config file arg: zmqpubsequence=“tcp://0.0.0.0:28335”
2025-07-09T11:26:09Z Config file arg: [main] bind=“0.0.0.0:8333”
2025-07-09T11:26:09Z Config file arg: [main] bind=“10.21.21.8:8334=onion”
2025-07-09T11:26:09Z Config file arg: [main] port=“8333”
2025-07-09T11:26:09Z Config file arg: [main] rpcbind=“10.21.21.8”
2025-07-09T11:26:09Z Config file arg: [main] rpcbind=“127.0.0.1”
2025-07-09T11:26:09Z Config file arg: [main] rpcport=“8332”
2025-07-09T11:26:09Z Command-line arg: datadir=“/data/bitcoin”
2025-07-09T11:26:09Z Command-line arg: deprecatedrpc=“create_bdb”
2025-07-09T11:26:09Z Using at most 240 automatic connections (1048576 file descriptors available)
2025-07-09T11:26:09Z scheduler thread start
2025-07-09T11:26:09Z Binding RPC on address 10.21.21.8 port 8332
2025-07-09T11:26:09Z Binding RPC on address 127.0.0.1 port 8332
2025-07-09T11:26:09Z Generated RPC authentication cookie /data/bitcoin/.cookie
2025-07-09T11:26:09Z Permissions used for cookie: rw-------
2025-07-09T11:26:09Z Using random cookie authentication.
2025-07-09T11:26:09Z Using rpcauth authentication.
2025-07-09T11:26:09Z Starting HTTP server with 16 worker threads
2025-07-09T11:26:09Z Using wallet directory /data/bitcoin
2025-07-09T11:26:09Z init message: Verifying wallet(s)…
2025-07-09T11:26:09Z Using /16 prefix for IP bucketing
2025-07-09T11:26:09Z init message: Loading P2P addresses…
2025-07-09T11:26:10Z Loaded 75617 addresses from peers.dat 999ms
2025-07-09T11:26:10Z init message: Loading banlist…
2025-07-09T11:26:10Z SetNetworkActive: true
2025-07-09T11:26:11Z Cache configuration:
2025-07-09T11:26:11Z * Using 2.0 MiB for block index database
2025-07-09T11:26:11Z * Using 56.2 MiB for transaction index database
2025-07-09T11:26:11Z * Using 49.2 MiB for basic block filter index database
2025-07-09T11:26:11Z * Using 8.0 MiB for chain state database
2025-07-09T11:26:11Z * Using 334.5 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2025-07-09T11:26:11Z Script verification uses 3 additional threads
2025-07-09T11:26:11Z Using obfuscation key for blocksdir *.dat files (/data/bitcoin/blocks): ‘68ac1d239cef10cc’
2025-07-09T11:26:11Z Opening LevelDB in /data/bitcoin/blocks/index
2025-07-09T11:26:12Z Opened LevelDB successfully
2025-07-09T11:26:12Z Using obfuscation key for /data/bitcoin/blocks/index: 0000000000000000
2025-07-09T11:26:12Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2025-07-09T11:26:12Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2025-07-09T11:26:12Z init message: Loading block index…
2025-07-09T11:26:12Z Assuming ancestors of block 00000000000000000001b658dd1120e82e66d2790811f89ede9742ada3ed6d77 have valid signatures.
2025-07-09T11:26:12Z Setting nMinimumChainWork=0000000000000000000000000000000000000000b1f3b93b65b16d035a82be84
2025-07-09T11:26:27Z LoadBlockIndexDB: last block file = 5021
2025-07-09T11:26:27Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=48, size=70034131, heights=904571…904618, time=2025-07-08…2025-07-08)
2025-07-09T11:26:27Z Checking all blk files are present…
2025-07-09T11:26:28Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2025-07-09T11:26:28Z Opening LevelDB in /data/bitcoin/chainstate
2025-07-09T11:26:29Z Opened LevelDB successfully
2025-07-09T11:26:29Z Using obfuscation key for /data/bitcoin/chainstate: e558bd46cbdc0b66
2025-07-09T11:26:29Z Loaded best chain: hashBestChain=0000000000000000000071eec85890b95d1ece46e6b5dcb25426819003cd1c3e height=904603 date=2025-07-08T13:21:15Z progress=0.999697
2025-07-09T11:26:29Z init message: Verifying blocks…
2025-07-09T11:26:29Z Verifying last 6 blocks at level 3
2025-07-09T11:26:29Z Verification progress: 0%
2025-07-09T11:27:51Z Verification progress: 16%
2025-07-09T11:29:03Z Verification progress: 33%
2025-07-09T11:29:49Z Verification progress: 50%
2025-07-09T11:30:10Z Verification progress: 66%
2025-07-09T11:30:35Z Verification progress: 83%
2025-07-09T11:31:11Z Verification progress: 99%
2025-07-09T11:31:11Z Verification: No coin database inconsistencies in last 6 blocks (16769 transactions)
2025-07-09T11:31:11Z Block index and chainstate loaded
2025-07-09T11:31:11Z Opening LevelDB in /data/bitcoin/indexes/txindex
2025-07-09T11:31:12Z Opened LevelDB successfully
2025-07-09T11:31:12Z Using obfuscation key for /data/bitcoin/indexes/txindex: 0000000000000000
2025-07-09T11:31:12Z Opening LevelDB in /data/bitcoin/indexes/blockfilter/basic/db
2025-07-09T11:31:12Z Opened LevelDB successfully
2025-07-09T11:31:12Z Using obfuscation key for /data/bitcoin/indexes/blockfilter/basic/db: 0000000000000000
2025-07-09T11:31:12Z [error] txindex: best block of the index not found. Please rebuild the index.
Error: txindex: best block of the index not found. Please rebuild the index.
2025-07-09T11:31:12Z Shutdown: In progress…
2025-07-09T11:31:12Z scheduler thread exit
2025-07-09T11:31:12Z Flushed fee estimates to fee_estimates.dat.
2025-07-09T11:31:13Z Shutdown: done
Where’s your question?
1 Like
My apologies. I didn’t realize the information had been posted. I was in the process of editing it and walked away for a meeting.
Q1) I think the issue is that I had a power outage, and that possibly corrupted the index. I have read through some similar, older posts, but wasn’t sure if they were the best way to approach the problem. Any recommendations? Running a Raspi 5, with 8 GB, 2T hard drive attached via USB. Any recommendations on where to start and course of action?
Q2) Also, if I need to rebuild the entire index (which I understand could take hours, days or weeks), can I simply download the entire index from the web or another trusted friend’s Umbrel to save time and bandwidth?
Lastly, is there CLI or Umbrel software to run a nightly backup of my entire Umbrel hard drive to another USB attached drive to avoid this situation?
Thanks
There is no GUI option to reindex, and I don’t know how you’d run it via bitcoin-cli with Umbrel. But there was a similar question to this here: Command for Reindex Blockchain
No, since your block-storage is unique, the verification need to be done by your own system on your own.
Believe me, a daily snapshot of a 1TB is not something you want your system to go through. What I would rather suggest: Once your block is in sync again, stop bitcoind, copy the whole folder with rsync (see the equivalent for Raspibolt here to another SSD on your computer (don’t attach another SSD to your umbrel, it does not have enough power) via network and put it to a shelf.
Whenever your SSD is toast in the future, you don’t need to do the full IBD, but start from where you did the last transfer. It’s probably always going to be a lot faster than a reindex or complete SSD crash. Those happen more often than you’d want to.