0
I have seen a related question here: When should I use -reindex-chainstate and when -reindex <-- Read this for more info.
You could try
-reindex-chainstate
If that doesn't work then try
-reindex
Quoted from the linked question:
You should use -reindex only when you were running in pruning mode, or if you suspect the blocks on disk are actually corrupted. Otherwise, when you only suspect corruption of the chainstate (which is far more likely), use -reindex-chainstate.
1I had read failures myself in the course of last week. I think it is important for you to uncover the source of the problem: is it a bug in
bitcoind, a bug in the operating system, a corrupted file system (which may happen very easily when systems are shutdown abruptly), is it a hardware problem with a flaw in the hard disk? In my case, the OS did inform me of inconsistent file system, tried to repair things, but it got worse and worse. I then reinstalled the whole OS +bitcoindand the problem reappeared. In the end I had to change hardware, reinstall OS +bitcoind. – Sven Williamson – 2017-03-29T11:04:28.190The good news is:
v0.14.0is mightly quick compared to previous versions. – Sven Williamson – 2017-03-29T11:05:40.717