-
Notifications
You must be signed in to change notification settings - Fork 20.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
BAD BLOCK #26611
Labels
Comments
log:
|
This error indicates that your state database might be corrupted. This can be due to a software bug, or due to a hardware fault. It's not possible to diagnose what happened from the provided log file. Generally speaking, a corrupted state database only recoverable by re-syncing the node. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So there are other instances of this, but what seems to be missing is the root cause. It happened to me last night (log attached). Is it an SSD failure? A bit flip? Something else?
Right now, geth is re-syncing from scratch on my machine, which has been running flawlessly for a year+.
Cursory
smartctl
information seems to indicate things are ok, but I guess we can never really know?What can we do to stop this from happening or recover quicker without manual intervention?
geth.log
The text was updated successfully, but these errors were encountered: