-
Notifications
You must be signed in to change notification settings - Fork 19.6k
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
Unexpected trie node error BAD BLOCK #29781
Comments
Yes, definitely! (as in: yes, it definitely can be, not that it definitely is). The NVMe holding the state is the interesting one, which can lead to this type of corruption. I would advise to do a disk health check, check for corrupted bits. Drives do degrade over time, and four years of heavy mainnet-node operation takes its toll. |
Just to confirm that you use |
Could be relevant with #29436 |
The correct node blob should be
|
Could you please try to run these commands?
These information might be useful for debugging. |
The account mutations between block 19860215 to block 19871213 with address-hash-prefix
|
Yes I confirm that I've used Here are the logs from the commands you posted above:
|
Thanks, i have verified all the children are hash-matched. Namely only this particular fullNode is missing. do you have the logs when you resync your geth by any chance? |
Btw you can try this command to fix your corrupted database. |
System information
Geth version: 1.14.3
CL client & version: prysm@v5.0.3
OS & Version: Ubuntu 22.04.4
Actual behaviour
My node has suddenly stopped syncing yesterday. I tried to fix it by removing the state (kept the ancient) and resyncing. It was working fine for a few hours but then the same error appeared again.
Could this be a hardware issue? The node has been running without any issues for more than 4 years now. Just in case if that's important... I use separate hard drives for state and ancients. State is on the NVMe, ancients are on a regular SSD.
Backtrace
The text was updated successfully, but these errors were encountered: