bitcoin: Corruption: block checksum mismatch

with bitcoind 0.11.0 on a 64bit Linux VPS (with simfs)

2015-08-06 05:53:59 Corruption: block checksum mismatch
2015-08-06 05:53:59 *** System error while flushing: Database corrupted
2015-08-06 05:53:59 Error: Error: A fatal internal error occured, see debug.log for details
2015-08-06 05:53:59 ERROR: ProcessNewBlock: ActivateBestChain failed
2015-08-06 05:53:59 opencon thread interrupt
2015-08-06 05:53:59 addcon thread interrupt
2015-08-06 05:53:59 msghand thread interrupt
2015-08-06 05:53:59 scheduler thread interrupt
2015-08-06 05:53:59 net thread interrupt
2015-08-06 05:53:59 Shutdown: In progress...
2015-08-06 05:54:00 StopNode()
2015-08-06 05:54:00 Corruption: block checksum mismatch
2015-08-06 05:54:00 *** System error while flushing: Database corrupted
2015-08-06 05:54:00 Error: Error: A fatal internal error occured, see debug.log for details
2015-08-06 05:54:00 Shutdown: done

This is occasionally happening after a -reindex on 0.11.0, as this was also previously happening on earlier releases. bitcoind.conf includes settings preventing transaction flooding:

minrelaytxfee=0.00005
limitfreerelay=5

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 43 (12 by maintainers)

Most upvoted comments

With bitcoind 0.11.1 on a 64-bit Linux PC I got the “Corruption: block checksum mismatch” error. I ran a full system check, which reported single bit data dependent corruption in one of the DIMMs. I think the LevelDB data was corrupted when cached in the DRAM memory and then got written back to disk. I replaced both DIMMs, ran with -reindex=1, and bitcoind has been running without error for a week.

trevelocity on Oct 28, 2015