MyNode dumped out - can it be restarted and pickup where it left off whilst downloading the Blockchain

[Westy66]

Hello, can anyone offer assistance please

I am struggling to get up and running

Rasp Pi4 - 4gb RAM
2TB Exteral SSD Drive

When initialy downloading the current block chain, the system always hangs - usually around 855565 of 908086 currently

I have restarted this process 3 times now and each time ends in disappointment.

Is there anyway of restarting the system but having it pickup where it left off - currently, when I restart the PI it starts the whole process from the begining - mounting the drive, initializing it and then begins the lengthy download and validation process afresh

I have pulled the following error report from the bitcoin section
Bitcoin Status
Error
2025-08-04T17:49:25Z Verification progress: 0%
2025-08-04T17:49:25Z Verifying last 6 blocks at level 3
2025-08-04T17:49:25Z init message: Verifying blocks…
2025-08-04T17:49:25Z [Chainstate [ibd] @ height 884711 (00000000000000000000f3d0f824c872f42d5836c1c7715a0814603ca3b2e666)] resized coinstip cache to 865.2 MiB
2025-08-04T17:49:25Z [Chainstate [ibd] @ height 884711 (00000000000000000000f3d0f824c872f42d5836c1c7715a0814603ca3b2e666)] resized coinsdb cache to 8.0 MiB
2025-08-04T17:49:25Z Using obfuscation key for /home/bitcoin/.bitcoin/chainstate: 65a86e7252779687
2025-08-04T17:49:25Z Opened LevelDB successfully
2025-08-04T17:49:25Z Opening LevelDB in /home/bitcoin/.bitcoin/chainstate
2025-08-04T17:49:25Z Loaded best chain: hashBestChain=00000000000000000000f3d0f824c872f42d5836c1c7715a0814603ca3b2e666 height=884711 date=2025-02-21T12:08:28Z progress=0.925475
2025-08-04T17:49:24Z Using obfuscation key for /home/bitcoin/.bitcoin/chainstate: 65a86e7252779687
2025-08-04T17:49:24Z Opened LevelDB successfully
2025-08-04T17:49:20Z Opening LevelDB in /home/bitcoin/.bitcoin/chainstate
2025-08-04T17:49:20Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2025-08-04T17:49:16Z Checking all blk files are present...
2025-08-04T17:49:16Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=71, size=112800050, heights=885194...885328, time=2025-02-25...2025-02-26)
2025-08-04T17:49:16Z LoadBlockIndexDB: last block file = 4797
2025-08-04T17:49:01Z Using obfuscation key for /home/bitcoin/.bitcoin/blocks/index: 0000000000000000
2025-08-04T17:49:01Z Opened LevelDB successfully
2025-08-04T17:49:00Z Opening LevelDB in /home/bitcoin/.bitcoin/blocks/index
2025-08-04T17:49:00Z Setting nMinimumChainWork=000000000000000000000000000000000000000063c4ebd298db40af57541800
2025-08-04T17:49:00Z Assuming ancestors of block 0000000000000000000222b7554f29d843113c705659aa065524efc9cfa82ec1 have valid signatures.
2025-08-04T17:49:00Z init message: Loading block index…
2025-08-04T17:49:00Z * Using 865.2 MiB for in-memory UTXO set (plus up to 238.4 MiB of unused mempool space)
2025-08-04T17:49:00Z * Using 8.0 MiB for chain state database
2025-08-04T17:49:00Z * Using 124.8 MiB for transaction index database
2025-08-04T17:49:00Z * Using 2.0 MiB for block index database
2025-08-04T17:49:00Z Cache configuration:
2025-08-04T17:49:00Z Script verification uses 2 additional threads
2025-08-04T17:49:00Z SetNetworkActive: true
2025-08-04T17:49:00Z init message: Loading banlist…
2025-08-04T17:49:00Z Loaded 65598 addresses from peers.dat 639ms
2025-08-04T17:49:00Z init message: Loading P2P addresses…
2025-08-04T17:49:00Z Using /16 prefix for IP bucketing
2025-08-04T17:49:00Z Warning: Skipping -wallet path that doesn't exist. Failed to load database path '/home/bitcoin/.bitcoin/joinmarket_wallet.dat'. Path does not exist.
2025-08-04T17:49:00Z Warning: Skipping -wallet path that doesn't exist. Failed to load database path '/home/bitcoin/.bitcoin/wallet.dat'. Path does not exist.
2025-08-04T17:49:00Z init message: Verifying wallet(s)…
2025-08-04T17:49:00Z Using wallet directory /home/bitcoin/.bitcoin
2025-08-04T17:49:00Z Starting HTTP server with 4 worker threads
2025-08-04T17:49:00Z Using rpcauth authentication.
2025-08-04T17:49:00Z Generated RPC authentication cookie /home/bitcoin/.bitcoin/.cookie
2025-08-04T17:49:00Z Using random cookie authentication.
2025-08-04T17:49:00Z Binding RPC on address ::1 port 8332
2025-08-04T17:49:00Z WARNING: the RPC server is not safe to expose to untrusted networks such as the public internet
2025-08-04T17:49:00Z Binding RPC on address 0.0.0.0 port 8332
2025-08-04T17:49:00Z scheduler thread start
2025-08-04T17:49:00Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2025-08-04T17:49:00Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2025-08-04T17:49:00Z Using at most 40 automatic connections (1024 file descriptors available)
2025-08-04T17:49:00Z Command-line arg: printtoconsole=""
2025-08-04T17:49:00Z Command-line arg: pid="/home/bitcoin/.bitcoin/bitcoin.pid"
2025-08-04T17:49:00Z Command-line arg: deprecatedrpc="accounts"
2025-08-04T17:49:00Z Command-line arg: daemon=""
2025-08-04T17:49:00Z Command-line arg: conf="/home/bitcoin/.bitcoin/bitcoin.conf"
2025-08-04T17:49:00Z Config file arg: [test] wallet="joinmarket_wallet.dat"
2025-08-04T17:49:00Z Config file arg: [test] wallet="wallet.dat"
2025-08-04T17:49:00Z Config file arg: [main] wallet="joinmarket_wallet.dat"
2025-08-04T17:49:00Z Config file arg: [main] wallet="wallet.dat"
2025-08-04T17:49:00Z Config file arg: zmqpubrawtx="tcp://0.0.0.0:28333"
2025-08-04T17:49:00Z Config file arg: zmqpubrawblock="tcp://0.0.0.0:28332"
2025-08-04T17:49:00Z Config file arg: zmqpubhashblock="tcp://0.0.0.0:28334"
2025-08-04T17:49:00Z Config file arg: whitelist="bloomfilter@192.168.0.0/16"
2025-08-04T17:49:00Z Config file arg: whitelist="bloomfilter@10.0.0.0/8"
2025-08-04T17:49:00Z Config file arg: whitelist="download@192.168.0.0/16"
2025-08-04T17:49:00Z Config file arg: whitelist="download@10.0.0.0/8"
2025-08-04T17:49:00Z Config file arg: whitelist="[::1]"
2025-08-04T17:49:00Z Config file arg: whitelist="172.16.0.0/12"
2025-08-04T17:49:00Z Config file arg: whitelist="127.0.0.1"
2025-08-04T17:49:00Z Config file arg: txindex="1"
2025-08-04T17:49:00Z Config file arg: shrinkdebugfile="1"
2025-08-04T17:49:00Z Config file arg: server="1"
2025-08-04T17:49:00Z Config file arg: rpcworkqueue="32"
2025-08-04T17:49:00Z Config file arg: rpcport="8332"
2025-08-04T17:49:00Z Config file arg: rpcbind="[::1]"
2025-08-04T17:49:00Z Config file arg: rpcbind="0.0.0.0"
2025-08-04T17:49:00Z Config file arg: rpcauth=****
2025-08-04T17:49:00Z Config file arg: rpcallowip="192.168.0.0/16"
2025-08-04T17:49:00Z Config file arg: rpcallowip="172.16.0.0/12"
2025-08-04T17:49:00Z Config file arg: rpcallowip="10.0.0.0/8"
2025-08-04T17:49:00Z Config file arg: rpcallowip="[::1]"
2025-08-04T17:49:00Z Config file arg: rpcallowip="127.0.0.1"
2025-08-04T17:49:00Z Config file arg: par="-1"
2025-08-04T17:49:00Z Config file arg: onlynet="ipv4"
2025-08-04T17:49:00Z Config file arg: mempoolfullrbf="1"
2025-08-04T17:49:00Z Config file arg: maxuploadtarget="5000"
2025-08-04T17:49:00Z Config file arg: maxorphantx="10"
2025-08-04T17:49:00Z Config file arg: maxmempool="250"
2025-08-04T17:49:00Z Config file arg: maxconnections="40"
2025-08-04T17:49:00Z Config file arg: deprecatedrpc="create_bdb"
2025-08-04T17:49:00Z Config file arg: dbcache="1000"
2025-08-04T17:49:00Z Config file arg: daemon="1"
2025-08-04T17:49:00Z Config file arg: bind="0.0.0.0"
2025-08-04T17:49:00Z Config file arg: assumevalid="0000000000000000000222b7554f29d843113c705659aa065524efc9cfa82ec1"
2025-08-04T17:49:00Z Config file: /home/bitcoin/.bitcoin/bitcoin.conf
2025-08-04T17:49:00Z Using data directory /home/bitcoin/.bitcoin
2025-08-04T17:49:00Z Default data directory /home/bitcoin/.bitcoin
2025-08-04T17:48:59Z Using the 'standard' SHA256 implementation
2025-08-04T17:48:59Z Script verification uses 2 additional threads
2025-08-04T17:48:59Z InitParameterInteraction: parameter interaction: -bind set -> setting -listen=1
2025-08-04T17:48:59Z Bitcoin Core version v27.1.0 (release build)

If this is of any use.

I would be eternally greatfull for any positive help on this.

Cheers
Westy

[tehelsper]

That log doesn't show an error, but just above or below what you see may show one. This guide may help and you can log a support ticket for us to further investigate your setup. This isn't a software bug. Hope that helps!

https://mynodebtc.github.io/troubleshooting/bitcoin-error.html

mynodebtc.com/support

[Westy66]

Thank you very much for replying - I will look into the hardward then as a possible issue.

Cheers
Westy