After power outage restated Umbrel , Bitcoin knots will run for a few seconds and stop tried start Bitcoin core it will show starting but not running
What does the log show?
2025-07-14T12:41:51Z Ignoring unknown configuration value datum
2025-07-14T12:41:51Z Included configuration file umbrel-bitcoin.conf
2025-07-14T12:41:51Z Bitcoin Knots version v28.1.knots20250305 (release build)
2025-07-14T12:41:51Z parameter interaction: -onlynet excludes IPv4 and IPv6 → setting -dnsseed=0
2025-07-14T12:41:51Z ParameterInteraction: parameter interaction: -walletimplicitsegwit=0 → setting -addresstype=legacy
2025-07-14T12:41:51Z Script verification uses 3 additional threads
2025-07-14T12:41:51Z Using the ‘sse4(1way),sse41(4way),avx2(8way)’ SHA256 implementation
2025-07-14T12:41:51Z Feeding 27925 bytes of environment data into RNG
2025-07-14T12:41:51Z Using RdSeed as an additional entropy source
2025-07-14T12:41:51Z Using RdRand as an additional entropy source
2025-07-14T12:41:52Z Default data directory /home/node/.bitcoin
2025-07-14T12:41:52Z Using data directory /data/bitcoin
2025-07-14T12:41:52Z Config file: /data/bitcoin/bitcoin.conf
2025-07-14T12:41:52Z R/W Config file: /data/bitcoin/bitcoin_rw.conf (not found, skipping)
2025-07-14T12:41:52Z Config file arg: acceptnonstddatacarrier=“0”
2025-07-14T12:41:52Z Config file arg: bantime=“86400”
2025-07-14T12:41:52Z Config file arg: blockfilterindex=“1”
2025-07-14T12:41:52Z Config file arg: blockmaxsize=“3985000”
2025-07-14T12:41:52Z Config file arg: blockmaxweight=“3985000”
2025-07-14T12:41:52Z Config file arg: blocknotify=“curl -s -m 5 http://datum_datum_1:21000/NOTIFY”
2025-07-14T12:41:52Z Config file arg: blockreconstructionextratxn=“1000000”
2025-07-14T12:41:52Z Config file arg: chain=“main”
2025-07-14T12:41:52Z Config file arg: coinstatsindex=“0”
2025-07-14T12:41:52Z Config file arg: datacarrier=“1”
2025-07-14T12:41:52Z Config file arg: datacarriercost=“1”
2025-07-14T12:41:52Z Config file arg: datacarriersize=“83”
2025-07-14T12:41:52Z Config file arg: dbcache=“450”
2025-07-14T12:41:52Z Config file arg: i2pacceptincoming=“0”
2025-07-14T12:41:52Z Config file arg: includeconf=“umbrel-bitcoin.conf”
2025-07-14T12:41:52Z Config file arg: listen=“1”
2025-07-14T12:41:52Z Config file arg: listenonion=“1”
2025-07-14T12:41:52Z Config file arg: maxconnections=“125”
2025-07-14T12:41:52Z Config file arg: maxmempool=“300”
2025-07-14T12:41:52Z Config file arg: maxorphantx=“100”
2025-07-14T12:41:52Z Config file arg: maxreceivebuffer=“5000”
2025-07-14T12:41:52Z Config file arg: maxsendbuffer=“1000”
2025-07-14T12:41:52Z Config file arg: maxuploadtarget=“0”
2025-07-14T12:41:52Z Config file arg: mempoolexpiry=“336”
2025-07-14T12:41:52Z Config file arg: onion=“10.21.22.12:9050”
2025-07-14T12:41:52Z Config file arg: onlynet=“onion”
2025-07-14T12:41:52Z Config file arg: peerblockfilters=“1”
2025-07-14T12:41:52Z Config file arg: peerbloomfilters=“0”
2025-07-14T12:41:52Z Config file arg: peertimeout=“60”
2025-07-14T12:41:52Z Config file arg: permitbaremultisig=“1”
2025-07-14T12:41:52Z Config file arg: permitbarepubkey=“0”
2025-07-14T12:41:52Z Config file arg: persistmempool=“1”
2025-07-14T12:41:52Z Config file arg: prune=“0”
2025-07-14T12:41:52Z Config file arg: rejectparasites=“1”
2025-07-14T12:41:52Z Config file arg: rejecttokens=“0”
2025-07-14T12:41:52Z Config file arg: rest=“0”
2025-07-14T12:41:52Z Config file arg: rpcallowip=“10.21.0.0/16”
2025-07-14T12:41:52Z Config file arg: rpcallowip=“127.0.0.1”
2025-07-14T12:41:52Z Config file arg: rpcauth=****
2025-07-14T12:41:52Z Config file arg: rpcworkqueue=“128”
2025-07-14T12:41:52Z Config file arg: timeout=“5000”
2025-07-14T12:41:52Z Config file arg: torcontrol=“10.21.22.12:9051”
2025-07-14T12:41:52Z Config file arg: torpassword=****
2025-07-14T12:41:52Z Config file arg: txindex=“1”
2025-07-14T12:41:52Z Config file arg: whitelist=“10.21.0.0/16”
2025-07-14T12:41:52Z Config file arg: whitelist=“127.0.0.1”
2025-07-14T12:41:52Z Config file arg: zmqpubhashblock=“tcp://0.0.0.0:48334”
2025-07-14T12:41:52Z Config file arg: zmqpubhashtx=“tcp://0.0.0.0:48336”
2025-07-14T12:41:52Z Config file arg: zmqpubrawblock=“tcp://0.0.0.0:48332”
2025-07-14T12:41:52Z Config file arg: zmqpubrawtx=“tcp://0.0.0.0:48333”
2025-07-14T12:41:52Z Config file arg: zmqpubsequence=“tcp://0.0.0.0:48335”
2025-07-14T12:41:52Z Config file arg: [main] bind=“0.0.0.0:9333”
2025-07-14T12:41:52Z Config file arg: [main] bind=“10.21.21.7:8334=onion”
2025-07-14T12:41:52Z Config file arg: [main] port=“9333”
2025-07-14T12:41:52Z Config file arg: [main] rpcbind=“10.21.21.7”
2025-07-14T12:41:52Z Config file arg: [main] rpcbind=“127.0.0.1”
2025-07-14T12:41:52Z Config file arg: [main] rpcport=“9332”
2025-07-14T12:41:52Z Setting file arg: wallet = [“”]
2025-07-14T12:41:52Z Command-line arg: datadir=“/data/bitcoin”
2025-07-14T12:41:52Z Command-line arg: deprecatedrpc=“create_bdb”
2025-07-14T12:41:52Z Using at most 125 automatic connections (1048576 file descriptors available)
2025-07-14T12:41:52Z scheduler thread start
2025-07-14T12:41:52Z Binding RPC on address 10.21.21.7 port 9332
2025-07-14T12:41:52Z Binding RPC on address 127.0.0.1 port 9332
2025-07-14T12:41:52Z Generated RPC authentication cookie /data/bitcoin/.cookie
2025-07-14T12:41:52Z Permissions used for cookie: rw-------
2025-07-14T12:41:52Z Using random cookie authentication.
Using rpcauth authentication.
2025-07-14T12:41:52Z Starting HTTP server with 16 worker threads
2025-07-14T12:41:52Z Using wallet directory /data/bitcoin
2025-07-14T12:41:52Z init message: Verifying wallet(s)…
2025-07-14T12:41:52Z Using SQLite Version 3.38.5
2025-07-14T12:41:52Z Using wallet /data/bitcoin
2025-07-14T12:41:52Z Using /16 prefix for IP bucketing
2025-07-14T12:41:52Z init message: Loading P2P addresses…
2025-07-14T12:41:52Z Loaded 78495 addresses from peers.dat 435ms
2025-07-14T12:41:52Z init message: Loading banlist…
2025-07-14T12:41:52Z SetNetworkActive: true
2025-07-14T12:41:52Z Script verification uses 3 additional threads
2025-07-14T12:41:52Z Cache configuration:
2025-07-14T12:41:52Z * Using 2.0 MiB for block index database
2025-07-14T12:41:52Z * Using 56.0 MiB for transaction index database
2025-07-14T12:41:52Z * Using 49.0 MiB for basic block filter index database
2025-07-14T12:41:52Z * Using 8.0 MiB for chain state database
2025-07-14T12:41:52Z * Flushing caches if available system memory drops below 10 MiB
2025-07-14T12:41:52Z * Using 335.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2025-07-14T12:41:52Z Using obfuscation key for blocksdir *.dat files (/data/bitcoin/blocks): ‘0000000000000000’
2025-07-14T12:41:52Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2025-07-14T12:41:52Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2025-07-14T12:41:52Z init message: Loading block index…
2025-07-14T12:41:52Z Assuming ancestors of block 000000000000000000006e926737e6a349f7581525ad36e743dfe5f4bc3abbb7 have valid signatures.
2025-07-14T12:41:52Z Setting nMinimumChainWork=0000000000000000000000000000000000000000b08ea5865bede3101629fa0e
2025-07-14T12:41:52Z Opening LevelDB in /data/bitcoin/blocks/index
2025-07-14T12:41:53Z Opened LevelDB successfully
2025-07-14T12:41:53Z Using obfuscation key for /data/bitcoin/blocks/index: 0000000000000000
2025-07-14T12:41:59Z LoadBlockIndexDB: last block file = 5022
2025-07-14T12:41:59Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=48, size=64626441, heights=904167…904683, time=2025-07-05…2025-07-09)
2025-07-14T12:41:59Z Checking all blk files are present…
2025-07-14T12:42:00Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2025-07-14T12:42:00Z Opening LevelDB in /data/bitcoin/chainstate
2025-07-14T12:42:02Z Opened LevelDB successfully
2025-07-14T12:42:03Z Using obfuscation key for /data/bitcoin/chainstate: 3f482632168d2e9a
2025-07-14T12:42:04Z : Error initializing block database.
Please restart with -reindex or -reindex-chainstate to recover.
2025-07-14T12:42:04Z [error] Aborted block database rebuild. Exiting.
2025-07-14T12:42:04Z Shutdown: In progress…
: Error initializing block database.
Please restart with -reindex or -reindex-chainstate to recover.
2025-07-14T12:42:04Z scheduler thread exit
2025-07-14T12:42:04Z Flushed fee estimates to fee_estimates.dat.
2025-07-14T12:42:05Z Shutdown: done
Core logs
umbrel_bitcoin_2025-07-14_14-21.log (136.2 KB)
Did you see this at the end?
I had a similar problem after an outage. Same message but couldn’t reindex the database.
I ended up having to unmounting my app data drive and having to run fsck to repair the file system.
It looks like your block index is okay, but your chainstate index is hosed. You can probably get away with just reindexing that.
Go to this screen:
Add the following override:
reindex-chainstate=1
Then, click “Save overrides,” and your node will restart to begin the operation. Monitor the logs.
If that solves the issue, delete the override from your node config and “Save overrides,” again.
If that doesn’t solve the problem, you can try a full reindex by replacing the above override with this one:
reindex=1
Then, click “Save overrides,” and your node will restart to begin the operation. Monitor the logs.
If that solves the issue, delete the override from your node config and “Save overrides,” again.
Nice visuals.