Author

Topic: Bitcoin Core Node Sync constantly fails at 97% (Read 105 times)

?
Activity: -
Merit: -

~~~
If he deletes chainstate folder, his pruned node will have to re-download the whole blockchain again.
I don't think the chainstate folder on a pruned node requires the entire blockchain to be again downloaded if op deletes only a chain state folder. No? Yes, but only requires if he delete block's folder.
hero member
Activity: 714
Merit: 1010
Crypto Swap Exchange
With only 8GB RAM your node can't hold the chainstate fully in memory and has to do a lot of I/O to your HDD (painfully slow at random access I/O) to properly build the UTXO set which is stored in the chainstate folder. Full sync on HDD without lots of RAM will be snail slow and your HDD won't like the workload. A synced chainstate folder is about 12GB large.

Have you checked if your HDD is still OK? By which interface is your HDD connected to your node?


Is it intentional that you have a pruned node which doesn't store more than 2GB of block data? You could store an unpruned blockchain on your 1TB HDD if it's not used for anything else.


~~~
If he deletes chainstate folder, his pruned node will have to re-download the whole blockchain again. Apparently the same is needed when he deletes the blocks folder.
?
Activity: -
Merit: -
[2025-01-17T17:05:57Z LevelDB read failure: Corruption: block checksum mismatch: D:\BTCNode_Blockchain\chainstate/2510441.ldb

Clearly shown the error is of block checksum mismatch.

Go to cmd in your pc, run it as a administrator and then run this command
Code:
rmdir /S /Q "D:\BTCNode_Blockchain\chainstate"

After entering this, your chainstate folder will be cleared and then restart bitcoin core, will work properly. Also, you can clear blocks folder same as clearing of chainstate data but with this another command in your command promt.
Code:
rmdir /S /Q "D:\BTCNode_Blockchain\blocks"
[/s]
legendary
Activity: 3500
Merit: 3237
Happy New year 🤗
As you can see on the logs, you have a chainstate or database corruption.
I think you can just delete that folder for chainstate and then shutdown the Bitcoin core and reopen it again; it should resync and generate a new database.

If it doesn't work, you can try using this command below through CMD or terminal. This won't need to redownload the blocks but to erase the chainstate and recreate a new one.

Code:
-reindex-chainstate
brand new
Activity: 0
Merit: 0
I synced for a fews weeks now. Its around 97% , when i open it, it progresses some 0,xx% butt then always fails after a minute or so, i get an
error saying:
"Error reading from database, shutting down."

What can i do? Any advice?
thank you guys in advance.

Posting the contents of the log file where it starts reporting errors would help. The name of the file is debug.log and it is located in bitcoin core's data directory.

Absolutely, here you are:


2025-01-17T17:05:55Z UpdateTip: new best=000000000000000000020ab79b52e94d7c67418063923b80e31c3d6b94d37d76 height=873702 version=0x200b4000 log2_work=95.312933 tx=1128647187 date='2024-12-07T22:16:18Z' progress=0.979447 cache=123.4MiB(925993txo)
2025-01-17T17:05:55Z Loading 0 mempool transactions from file...
2025-01-17T17:05:55Z Imported mempool transactions from file: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2025-01-17T17:05:55Z initload thread exit
2025-01-17T17:05:55Z Synchronizing blockheaders, height: 879660 (~100.00%)
2025-01-17T17:05:56Z UpdateTip: new best=000000000000000000017f29f8a59f8e2cf4a9e6952b80bb1bf7413c183d800a height=873703 version=0x36000000 log2_work=95.312946 tx=1128649037 date='2024-12-07T22:24:54Z' progress=0.979450 cache=124.2MiB(933100txo)
2025-01-17T17:05:57Z LevelDB read failure: Corruption: block checksum mismatch: D:\BTCNode_Blockchain\chainstate/2510441.ldb
2025-01-17T17:05:57Z Fatal LevelDB error: Corruption: block checksum mismatch: D:\BTCNode_Blockchain\chainstate/2510441.ldb
2025-01-17T17:05:57Z You can use -debug=leveldb to get more complete diagnostic messages
2025-01-17T17:05:57Z [error] Error reading from database, shutting down.
2025-01-17T17:05:58Z [error] Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: D:\BTCNode_Blockchain\chainstate/2510441.ldb

2025-01-19T17:02:20Z Bitcoin Core version v28.1.0 (release build)
2025-01-19T17:02:20Z Qt 5.15.14 (static), plugin=windows
2025-01-19T17:02:20Z Static plugins:
2025-01-19T17:02:20Z  QWindowsIntegrationPlugin, version 331520
2025-01-19T17:02:20Z  QWindowsVistaStylePlugin, version 331520
2025-01-19T17:02:20Z Style: windowsvista / QWindowsVistaStyle
2025-01-19T17:02:20Z System: Windows 10 Version 2009, x86_64-little_endian-llp64
2025-01-19T17:02:20Z Screen: \\.\DISPLAY1 1280x1024, pixel ratio=1.0
2025-01-19T17:02:22Z Script verification uses 1 additional threads
2025-01-19T17:02:22Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2025-01-19T17:02:27Z Using RdRand as an additional entropy source
2025-01-19T17:02:27Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core noch nicht sicher beendet…"
2025-01-19T17:02:27Z Default data directory C:\Users\bro02\AppData\Local\Bitcoin
2025-01-19T17:02:27Z Using data directory D:\BTCNode_Blockchain
2025-01-19T17:02:27Z Config file: D:\BTCNode_Blockchain\bitcoin.conf (not found, skipping)
2025-01-19T17:02:27Z Setting file arg: prune = "1907"
2025-01-19T17:02:27Z Setting file arg: server = true
2025-01-19T17:02:27Z Setting file arg: upnp = true
2025-01-19T17:02:27Z Using at most 125 automatic connections (2048 file descriptors available)
2025-01-19T17:02:27Z scheduler thread start
2025-01-19T17:02:27Z Binding RPC on address ::1 port 8332
2025-01-19T17:02:27Z Binding RPC on address 127.0.0.1 port 8332
2025-01-19T17:02:27Z Using random cookie authentication.
2025-01-19T17:02:27Z Generated RPC authentication cookie D:\BTCNode_Blockchain\.cookie
2025-01-19T17:02:27Z Permissions used for cookie: rw-rw-rw-
2025-01-19T17:02:27Z Starting HTTP server with 4 worker threads
2025-01-19T17:02:27Z Using wallet directory D:\BTCNode_Blockchain
2025-01-19T17:02:27Z init message: Überprüfe Wallet(s)...
2025-01-19T17:02:27Z Using /16 prefix for IP bucketing
2025-01-19T17:02:27Z init message: Lade P2P-Adressen...
2025-01-19T17:02:29Z Loaded 65701 addresses from peers.dat  1309ms
2025-01-19T17:02:29Z init message: Lade Bannliste…
2025-01-19T17:02:29Z SetNetworkActive: true
2025-01-19T17:02:29Z Script verification uses 1 additional threads
2025-01-19T17:02:29Z Cache configuration:
2025-01-19T17:02:29Z * Using 2.0 MiB for block index database
2025-01-19T17:02:29Z * Using 8.0 MiB for chain state database
2025-01-19T17:02:29Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2025-01-19T17:02:29Z Using obfuscation key for blocksdir *.dat files (D:\BTCNode_Blockchain\blocks): 'd8b3906fc3bfc522'
2025-01-19T17:02:29Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2025-01-19T17:02:29Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2025-01-19T17:02:29Z init message: Lade Block-Index...
2025-01-19T17:02:29Z Assuming ancestors of block 000000000000000000011c5890365bdbe5d25b97ce0057589acaef4f1a57263f have valid signatures.
2025-01-19T17:02:29Z Setting nMinimumChainWork=000000000000000000000000000000000000000088e186b70e0862c193ec44d6
2025-01-19T17:02:29Z Prune configured to target 1907 MiB on disk for block and undo files.
2025-01-19T17:02:29Z Opening LevelDB in D:\BTCNode_Blockchain\blocks\index
2025-01-19T17:02:29Z Opened LevelDB successfully
2025-01-19T17:02:29Z Using obfuscation key for D:\BTCNode_Blockchain\blocks\index: 0000000000000000
2025-01-19T17:02:35Z Shutdown requested. Exiting.
2025-01-19T17:02:35Z Shutdown: In progress...
2025-01-19T17:02:35Z scheduler thread exit
2025-01-19T17:02:35Z Flushed fee estimates to fee_estimates.dat.
2025-01-19T17:02:35Z Shutdown: done
brand new
Activity: 0
Merit: 0
Hi guys,

i not that tech savvy. meaning i cant do anything CLI, but am a windows user for 15 years and know my way around there and a bit in building PCs.

So im new to this but i wanted to do my part for the network and run a full node on my thin client.

Specs:
Win 10
CPU G3420
8GB Ram
256SSD
and second drive 1TB HDD (Node on here)

28.1 Downloaded at https://bitcoincore.org/en/download/ and verified


I synced for a fews weeks now. Its around 97% , when i open it, it progresses some 0,xx% butt then always fails after a minute or so, i get an
error saying:
"Error reading from database, shutting down."

What can i do? Any advice?
thank you guys in advance.

Never heard of this problem previous but I do think, is because of insufficient storage available on 1TB harddisk which contains blockchain data in, how about space availability?

Thank you for responding!
Free Space is: 893GB
used space is: 21GB

(is that normal with 97% downloaded blockchain??)
?
Activity: -
Merit: -
Hi guys,

i not that tech savvy. meaning i cant do anything CLI, but am a windows user for 15 years and know my way around there and a bit in building PCs.

So im new to this but i wanted to do my part for the network and run a full node on my thin client.

Specs:
Win 10
CPU G3420
8GB Ram
256SSD
and second drive 1TB HDD (Node on here)

28.1 Downloaded at https://bitcoincore.org/en/download/ and verified


I synced for a fews weeks now. Its around 97% , when i open it, it progresses some 0,xx% butt then always fails after a minute or so, i get an
error saying:
"Error reading from database, shutting down."

What can i do? Any advice?
thank you guys in advance.

Never heard of this problem previous but I do think, is because of insufficient storage available on 1TB harddisk which contains blockchain data in, how about space availability?
legendary
Activity: 4522
Merit: 3426
I synced for a fews weeks now. Its around 97% , when i open it, it progresses some 0,xx% butt then always fails after a minute or so, i get an
error saying:
"Error reading from database, shutting down."

What can i do? Any advice?
thank you guys in advance.

Posting the contents of the log file where it starts reporting errors would help. The name of the file is debug.log and it is located in bitcoin core's data directory.
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!

Please stop just pasting AI generated text.

"Error reading from database, shutting down."

I didn't encounter this error, but the internet seems to agree that reindex is the first thing to try. See these links/answers:

* https://bitcoin.stackexchange.com/a/56551

* https://www.reddit.com/r/Bitcoin/comments/1g66w8y/btc_core_error_reading_from_database_shutting_down/



PS. I feel that this topic is more suited for Bitcoin Technical Support, you may want to move it there
brand new
Activity: 0
Merit: 0
Hi guys,

i not that tech savvy. meaning i cant do anything CLI, but am a windows user for 15 years and know my way around there and a bit in building PCs.

So im new to this but i wanted to do my part for the network and run a full node on my thin client.

Specs:
Win 10
CPU G3420
8GB Ram
256SSD
and second drive 1TB HDD (Node on here)

28.1 Downloaded at https://bitcoincore.org/en/download/ and verified


I synced for a fews weeks now. Its around 97% , when i open it, it progresses some 0,xx% butt then always fails after a minute or so, i get an
error saying:
"Error reading from database, shutting down."

What can i do? Any advice?
thank you guys in advance.
Jump to: