After running bitcoind (as part of myNode) for 6 monhths with no issue, I got this error:

Fatal LevelDB error: Corruption: checksum mismatch: /home/bitcoin/.bitcoin/indexes/txindex/257701.log

At that point it would have been great to truncate the blockchain to some previously known good block and start loading blocks from that point (instead of starting from scratch which takes nearly a week). Since the integrity of the blockchain is maintained continuously from the genesis block on, I don't see that there would be any risk (or too great of a difficulty) in doing this. Yet it does not appear that there is any tool available to do such a truncation -- is this simply because no one has bothered to create and release such a tool, or would truncating the blockchain create some security risk that I'm not aware of?

1 Answer 1


There is no need to truncate it. You can just start Bitcoin Core with the -reindex option. If you do, it'll throw away the UTXO set and other databases, and rebuild it from the blocks you have on disk (which will be kept), up to the point where they're corrupt. It'll take a while (possibly nearly as long as synchronizing in the first place), but it won't redownload valid blocks you already have.

  • thanks, that makes sense, but it doesn't fit my scenario. When I tried -reindex I would get another error message asking me to to -reindex -- stuck in an infinte loop more or less. So it seems there must be something about the LevelDB corruption that I experienced that prevented -reindex from working. (At that point I used the 'Reset Blockchain' command on myNode which wiped out the entire installation and started the Initial Block Download. That was painful, but better than being stuck in that error loop.) I wonder if there was some other way to deal with the situation...
    – ckapilla
    Oct 4, 2021 at 21:33
  • 1
    If you're getting repeated errors, your hardware is most likely broken (overheating, memory errors, disk issues, ... Bitcoin fulls nodes tend to stress hardware far more than most applications). Oct 4, 2021 at 21:37
  • I'm hoping it was not permanently broken, but temporarily overheated -- I guess time will tell...
    – ckapilla
    Oct 4, 2021 at 21:57
  • Well if you get the problem again after a reindex, it's not a one-time thing. Oct 4, 2021 at 22:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.