<p>I have had my bitcoind turned off for a couple of months and I just turned it on again (bitcoind -daemon), and it seems to be reloading the entire block chain from scratch. Shouldn't it be loading only the blocks I am missing from the last two months? Why is it starting over from the beginning? Is there any way to get it to remember the blocks it already downloaded from before?</p>

<p><strong>UPDATE</strong></p>

<p>It seems to be increasing in blocks very rapidly, so possibly it is just reading through the blocks on disk and updating its memory?</p>

CC BY-SA 3.0
2017-02-09T17:25:00.467Z
Did you corrupt your directory `~/.bitcoin` in any way? Or did you add something like `txindex=1` to your config file? Short of these two events, as far as I understand it, `bitcoind` should not start over from the beginning.
Sven Williamson
CC BY-SA 3.0
2017-02-09T17:37:19.407Z
@SvenWilliamson My machine is configured to operate like a full node.
Harry Pillsbury
CC BY-SA 3.0
2017-02-11T18:24:42.697Z
"It seems to be reloading the entire chain from scratch" Can you elaborate on what makes you conclude this? How long does it take? What numbers for headers and blocks do you see in the `getblockchaininfo` RPC? Is it using a lot of CPU or I/O?
Pieter Wuille
<bitcoind><synchronization><daemon>
bitcoind reloads blockchain from scratch when it starts up?
Harry Pillsbury
# bitcoind reloads blockchain from scratch when it starts up?

(Asked by: username_0 on 2017-02-09)

I have had my bitcoind turned off for a couple of months and I just turned it on again (bitcoind -daemon), and it seems to be reloading the entire block chain from scratch. Shouldn't it be loading only the blocks I am missing from the last two months? Why is it starting over from the beginning? Is there any way to get it to remember the blocks it already downloaded from before?

**UPDATE**

It seems to be increasing in blocks very rapidly, so possibly it is just reading through the blocks on disk and updating its memory?

**Tags:** bitcoind, synchronization, daemon

> **Comments:**
> **username_1**: Did you corrupt your directory `~/.bitcoin` in any way? Or did you add something like `txindex=1` to your config file? Short of these two events, as far as I understand it, `bitcoind` should not start over from the beginning.  
> **username_0**: @username_1 My machine is configured to operate like a full node.  
> **username_2**: "It seems to be reloading the entire chain from scratch" Can you elaborate on what makes you conclude this? How long does it take? What numbers for headers and blocks do you see in the `getblockchaininfo` RPC? Is it using a lot of CPU or I/O?  

---

## 0 answers

