bitcoin core slow sync today?

[gabrio81]

hi guys

it seems to have worked, it was syncing all day, now left at 25 weeks behind, so far so good... hopefully also the newest transactions will work OK

Great to hear! Let us know when you get up to 100%.

it's complete now, finished and all back to normal.

[Martin SK]

Hey.
I have a problem, that I found fit to post here.
Since yesterday my note only shows headers to be 508757. Before it got "synced" it showed the correct headers 536424 as of writing this post

Your help will be much appreciated.

Code:

pi@btccore:~ $ bitcoin-cli getblockchaininfo
{
  "chain": "main",
  "blocks": 508757,
  "headers": 508757,
  "bestblockhash": "00000000000000000021b78e0d404649b4b91e3104e4ef2310e38563c7347722",
  "difficulty": 2874674234415.941,
  "mediantime": 1518400210,
  "verificationprogress": 0.8450131626940209,
  "initialblockdownload": true,
  "chainwork": "00000000000000000000000000000000000000000112b04f78f51cecbb145970",
  "size_on_disk": 890825462,
  "pruned": true,
  "pruneheight": 508092,
  "automatic_pruning": true,
  "prune_target_size": 1048576000,
  "softforks": [
    {
      "id": "bip34",
      "version": 2,
      "reject": {
        "status": true
      }
    },
    {
      "id": "bip66",
      "version": 3,
      "reject": {
        "status": true
      }
    },
    {
      "id": "bip65",
      "version": 4,
      "reject": {
        "status": true
      }
    }
  ],
  "bip9_softforks": {
    "csv": {
      "status": "active",
      "startTime": 1462060800,
      "timeout": 1493596800,
      "since": 419328
    },
    "segwit": {
      "status": "active",
      "startTime": 1479168000,
      "timeout": 1510704000,
      "since": 481824
    }
  },
  "warnings": ""
}

best regards!

[gabrio81]

Hi

You might try what worked for me... bear in mind it will reindex the chain which took about 2 days in total. First pass goes fast then the next one takes longer.

I did the "deleting the most recent blk*.dat and rev*.dat files"

[Martin SK]

Hi

You might try what worked for me... bear in mind it will reindex the chain which took about 2 days in total. First pass goes fast then the next one takes longer.

I did the "deleting the most recent blk*.dat and rev*.dat files"

Ok. I two days isn't that long compared to the time it takes to first sync with the network.
I read through the whole post and can find the information I'll need there. Otherwise I'll return for help.

Thanks

[Martin SK]

Hey,

where do I find the most recent blk*.dat and rev*.dat files??

I run Bitcoind (wallet only through terminal)
Thanks.

[gabrio81]

Hey,

where do I find the most recent blk*.dat and rev*.dat files??

I run Bitcoind (wallet only through terminal)
Thanks.

they are in the /blocks folder if you are running bitcoin core. not sure whether or not Bitcoind is part of bitcoin core though.

[Martin SK]

Hey,

where do I find the most recent blk*.dat and rev*.dat files??

I run Bitcoind (wallet only through terminal)
Thanks.

they are in the /blocks folder if you are running bitcoin core. not sure whether or not Bitcoind is part of bitcoin core though.

It is. It's just BTC-core without the graphic user interface. Anyways, I just corrupted the SD-card, so I'm running a recent backup. So I never got to try the proposed solution.

[Developerx11]

 -reindex-chainstate should work in most of cases

[bob123]

-reindex-chainstate should work in most of cases

-reindex-chainstate does wipe the chainstate + rebuilds it.
This is helpful if your chainstate got somehow corrupted.

But if the block index is corrupted, this command won't help you. You'll need to use -reindex instead.
-reindex does wipe the chainstate and the blockindex and rebuilds both of them (Chainstate is being built by validating blocks in the block index).


Both are unrelated to the time it takes for core to synch.
This is mostly dependend on the hardware (especially hard drive and CPU) and the network rate.