Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Rebuilding block database after corruption behaves strangely #8523
After clicking OK I get:
Which appears to be a bug. When I now click OK Bitcoin Core crashes:
After restarting it I get:
At this point nothing changes when I restart again.
The log says:
2016-08-16 12:52:42 Bitcoin version v0.12.1 (2016-04-11 13:01:43 +0200)
Hope this helps find the problem.
I now delete
I've got a lead for what the assertion is about. I just restored a saved
The chainstate and blocks directories are independent, and you are allowed to copy both from different sources. However, the blocks database cannot be older than the chainstate. This means that the latest block seen by the chainstate-sourcing instance must be present in the blocks directory.
Windows v0.13.0, this happened twice after two electricity cuts: first message above (corrupted, do you want...), OK, then it started to rebuild the blocks and chainstate from the beginning, another electricity cut during this process after a few days, and again, restarted from the beginning, good to wait for 10 days again...
Of course electricity cuts and no protection against could be seen as abnormal and I could install bitcoin qt on my servers instead, but, still, this does not look normal (unless the drive got damaged but it does not seem to be the case), it should be able to recover
A workaround is probably to backup the blockchain directory and restart from it if something happens, this brings again the #8738 subject