Keep getting errors after a while of syncing

tansanDOTeth commented at 4:11 am on June 26, 2023: none

Is there an existing issue for this?

I have searched the existing issues

Current behaviour

Spent the last few weeks trying to sync a full node and keep getting a wild error after making lots of progress. I had to restart at least 3 times, but decided to finally report it here.

2023-06-26T04:05:04Z LevelDB read failure: Corruption: block checksum mismatch: /Volumes/Crucial X8/BTC Blockchain Data/chainstate/031566.ldb 2023-06-26T04:05:04Z Fatal LevelDB error: Corruption: block checksum mismatch: /Volumes/Crucial X8/BTC Blockchain Data/chainstate/031566.ldb 2023-06-26T04:05:04Z You can use -debug=leveldb to get more complete diagnostic messages

Ran with -debug=leveldb

2023-06-26T04:28:09Z LevelDB read failure: Corruption: block checksum mismatch: /Volumes/Crucial X8/BTC Blockchain Data/chainstate/031566.ldb 2023-06-26T04:28:09Z Fatal LevelDB error: Corruption: block checksum mismatch: /Volumes/Crucial X8/BTC Blockchain Data/chainstate/031566.ldb 2023-06-26T04:28:09Z You can use -debug=leveldb to get more complete diagnostic messages 2023-06-26T04:28:09Z Error: Error reading from database, shutting down. 2023-06-26T04:28:11Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /Volumes/Crucial X8/BTC Blockchain Data/chainstate/031566.ldb

In a previous sync, I got this error:

Corruption: not an sstable (bad magic number)

Previous github issues documenting this error suggest to -reindex, but is there a way for me to progress my sync without having to -reindex every time?

Expected behaviour

I expected it to be fault tolerant and recover without my intervention.

Steps to reproduce

I don’t have a list of steps to reproduce it indefinitely, but it has kept me from syncing a full node.

Relevant log output

2023-06-26T04:05:04Z LevelDB read failure: Corruption: block checksum mismatch: /Volumes/Crucial X8/BTC Blockchain Data/chainstate/031566.ldb 2023-06-26T04:05:04Z Fatal LevelDB error: Corruption: block checksum mismatch: /Volumes/Crucial X8/BTC Blockchain Data/chainstate/031566.ldb 2023-06-26T04:05:04Z You can use -debug=leveldb to get more complete diagnostic messages

How did you obtain Bitcoin Core

Downloaded from the website. Bitcoin-Qt

What version of Bitcoin Core are you using?

v25.0.0

Operating system and version

Apple Silicon M1 MacOS Ventura Version 13.4

Machine specifications

16 GB RAM 1TB HD However, for the bitcoin node, I am using a new external 2TB SSD that I bought for just this

External was formatted as ExFAT

tansanDOTeth commented at 9:34 am on June 26, 2023: none

I tried reindexing since I posted this and I got this:

023-06-26T09:16:24Z UpdateTip: new best=00000000000000000c93572c7fcf0ccc927b5fb00039e90d1550327d6d83552f height=368600 version=0x00000003 log2_work=83.174292 tx=78966308 date=‘2015-08-06T04:29:51Z’ progress=0.093234 cache=380.0MiB(2905123txo) 2023-06-26T09:16:25Z UpdateTip: new best=00000000000000000be13a49f9c0852b6c2c773efc816afadf4b2328bebc1b0f height=368601 version=0x00000003 log2_work=83.174322 tx=78967060 date=‘2015-08-06T04:36:12Z’ progress=0.093235 cache=382.2MiB(2923322txo) 2023-06-26T09:16:25Z LevelDB read failure: Corruption: block checksum mismatch: /Volumes/Crucial X8/BTC Blockchain Data/chainstate/058415.ldb 2023-06-26T09:16:25Z Fatal LevelDB error: Corruption: block checksum mismatch: /Volumes/Crucial X8/BTC Blockchain Data/chainstate/058415.ldb 2023-06-26T09:16:25Z You can use -debug=leveldb to get more complete diagnostic messages 2023-06-26T09:16:25Z Error: Error reading from database, shutting down. 2023-06-26T09:33:19Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /Volumes/Crucial X8/BTC Blockchain Data/chainstate/058415.ldb

maflcko commented at 9:41 am on June 26, 2023: member

Has anyone ever put the leveldb directory successfully on an external drive, I am not sure if this is even supported by leveldb?

Edit: Alternatively, leveldb may not support your filesystem?

maflcko commented at 9:44 am on June 26, 2023: member

In the meantime you can test your storage device use smartctl or CrystalDiskInfo (or similar) to rule out any hardware defects.

tansanDOTeth commented at 9:46 am on June 26, 2023: none

In the meantime you can test your storage device use smartctl or CrystalDiskInfo to rule out any hardware defects.

I’ll give that a try and report back

tansanDOTeth commented at 11:11 am on June 26, 2023: none

Edit: Alternatively, leveldb may not support your filesystem?

Actually, my friend was telling me his external was formatted as APFS. Mine is currently formatted as ExFAT. Will try that and report back tomorrow.

tansanDOTeth commented at 10:01 am on June 28, 2023: none

Has anyone ever put the leveldb directory successfully on an external drive, I am not sure if this is even supported by leveldb?

Edit: Alternatively, leveldb may not support your filesystem?

This looks like the fix. I am at 35% now and haven’t had issues since reformatting as APFS. Seems like ExFAT is the culprit. I’m going to close this now, thank you!

tansanDOTeth closed this on Jun 28, 2023

bitcoin locked this on Jun 27, 2024

Keep getting errors after a while of syncing #27972