I can try to reproduce this with a Joris: does the crash happen while you are synchronizing/running, or after a stop/start?

If so, could you try running with -par=1 (to reduce risk for CPU problems, but I don't think that is the problem here, you'd get validation errors instead).

2015-08-06 Stop Node() 2015-08-06 Corruption: block checksum mismatch 2015-08-06 *** System error while flushing: Database corrupted 2015-08-06 Error: Error: A fatal internal error occured, see for details 2015-08-06 Shutdown: done These are disk corruption issues: leveldb keeps its own checksums of all data it writes, when it notices during (background) compaction that these mismatch it will return the error on the next flush.

There is no disk corruption from our side, because all our nodes use RAID array in which case disks is duplicated in the array and in case of any disk failure this disk is automatically removed from the array and node is working with other left disk until faulty hard disk replace.

To see what it actually stores - nothing at this point - you need to use a client.

You could now see what's in there (which right now is nothing).

It happens often enough that it's a thing, but uncommonly enough that I forget how to fix it each time.

So, FOR PROSPERITY: Then proooobably what happens was search_downloaded wonky or something such that the hash no longer came to be the correct thing.

2015-08-06 Corruption: block checksum mismatch 2015-08-06 *** System error while flushing: Database corrupted 2015-08-06 Error: Error: A fatal internal error occured, see for details 2015-08-06 ERROR: Process New Block: Activate Best Chain failed 2015-08-06 opencon thread interrupt 2015-08-06 addcon thread interrupt 2015-08-06 msghand thread interrupt 2015-08-06 scheduler thread interrupt 2015-08-06 net thread interrupt 2015-08-06 Shutdown: In progress...

You can do an update on it, to get it back as it is inside the repository.

After, you should copy the files being modified and that you did not managed to commit from the place where you moved your folder to the newly updated folder, do another Refresh and you should have the resources presented as modified.