<p>I have seen a related question here: <a href="https://bitcoin.stackexchange.com/questions/60709/when-should-i-use-reindex-chainstate-and-when-reindex">When should I use -reindex-chainstate and when -reindex</a> &lt;-- Read this for more info.</p>

<p>You could try  </p>

<blockquote>
  <p>-reindex-chainstate</p>
</blockquote>

<p>If that doesn't work then try</p>

<blockquote>
  <p>-reindex</p>
</blockquote>

<p>Quoted from the linked question: </p>

<blockquote>
  <p>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.</p>
</blockquote>

CC BY-SA 4.0
2018-08-09T13:45:03.727Z
2018-08-09T13:45:03.727Z
Rouse
<p>My full node daemon (bitcoind) crashed due to a disk read failure. The error is as follows:</p>

<p><a href="https://i.sstatic.net/ohhdV.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/ohhdV.png" alt="enter image description here"></a></p>

<p>"Deserialize or I/O error - CAutoFile::read: fread failed" etc.</p>

<p>How do I recover from this error? I don't want to have to download the whole database again.</p>

CC BY-SA 3.0
2017-03-29T11:04:28.190Z
I 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 + `bitcoind` and the problem reappeared. In the end I had to change hardware, reinstall OS + `bitcoind`.
Sven Williamson
CC BY-SA 3.0
2017-03-29T11:05:40.717Z
The good news is: `v0.14.0` is mightly quick compared to previous versions.
Sven Williamson
<bitcoind><error>
How do I recover from a disk read error (fread failed)?
Harry Pillsbury
# How do I recover from a disk read error (fread failed)?

(Asked by: username_0 on 2017-03-29)

My full node daemon (bitcoind) crashed due to a disk read failure. The error is as follows:

[![enter image description here](https://i.sstatic.net/ohhdV.png)](https://i.sstatic.net/ohhdV.png)

"Deserialize or I/O error - CAutoFile::read: fread failed" etc.

How do I recover from this error? I don't want to have to download the whole database again.

**Tags:** bitcoind, error

> **Comments:**
> **username_1**: I 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 + `bitcoind` and the problem reappeared. In the end I had to change hardware, reinstall OS + `bitcoind`.  
> **username_1**: The good news is: `v0.14.0` is mightly quick compared to previous versions.  

---

## 1 answers

### Answer by username_2 on 2018-08-09. Score: 1

I have seen a related question here: [When should I use -reindex-chainstate and when -reindex](https://bitcoin.stackexchange.com/questions/60709/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.


---

