New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fatal LevelDB error: Corruption: block checksum mismatch #21724
Comments
Sounds like a hardware or OS problem. |
@kristapsk I used to get this on an NVME drive that was overheating. Fixed that and haven't seen this since. |
It's a Gigabyte Brix with SATA HDD with nothing strange in a |
Was bitcoin compiled (i assume so since on Gentoo), try recompiling again? Also, make sure to run diagnostics on your system, there could be a hardware issue somewhere. If not with the HDD then maybe with memory? This is marcofalke's template for these type of issues :) Bitcoin Core makes heavy use of CPU, RAM, and disk IO. Hardware defects might only become visible when running Bitcoin Core. You might want to check your hardware for defects. memtest86 to check your RAM Source: https://bitcoin.stackexchange.com/a/12206 Edit: |
@jarolrod , thanks for the hints / links, will test the hardware. |
@kristapsk any update? |
Closing for now |
Did some hardware tests on a specific machine back in a May, haven't found any problems (but I don't remember details about everything I tested anymore). Was busy with other things, have decided to replace it with something more serious for mainnet. But will try to figure out what's wrong there at some point probably. It's ok to close this for now. |
I had this checksum LevelDB problem frequently in the last weeks, following this answer #10897 (comment) I managed to solve it, the HD I have been using to keep a copy of bitcoins blockchain is not working properly anymore, copying everything to a new HD and using it completely solve the errors. |
I read that comment, but not sure what I have to do run tests against my external. Do you have more instructions written somewhere? |
Had this problem with one long running node. Tried to restart bitcoind with
-debug=leveldb -reindex
, ended up with:Any hints how to debug this?
The text was updated successfully, but these errors were encountered: