<p>My computer got shut off due to a power outage and when I rebooted my bitcoin core it was stuck on connecting to peers. I was told to do a -reindex-chainstate with dbcache set as high as possible. Even with these high settings of dbcache=7000 and 16 core cpu, why does reindexing take more than 24+ hours? Also I'm not using a SSD, but a regular HDD. </p>

CC BY-SA 4.0
2018-10-05T20:17:30.470Z
What does "suck on connecting to peers" mean?  And what told you to do a reindex chainstate?
G. Maxwell
CC BY-SA 4.0
2018-10-05T22:06:47.637Z
Mr. Pieter told me to. see: https://bitcoin.stackexchange.com/questions/79760/its-october-2018-bitcoin-qt-reindex-chainstate-takes-forever-is-there-a-wa
Patoshi パトシ
CC BY-SA 4.0
2018-10-06T03:38:14.820Z
Nowhere in that are you told to reindex.
Claris
CC BY-SA 4.0
2018-10-06T03:40:35.823Z
Your right. he just mentions dbcache. I must have gotten it from another related question where someone had the same issue of connecting to peers. This happened right after my VM box got shut off unexpectedly.
Patoshi パトシ
CC BY-SA 4.0
2018-10-07T23:11:08.503Z
Do you have pruning turned on?
Pieter Wuille
CC BY-SA 4.0
2018-10-08T05:19:24.557Z
no i do not have pruning turned on.
Patoshi パトシ
<bitcoin-core><reindex>
Even with dbcache=7000 and 16 core processor. Why does -reindex-chainstate take more than 24+ hours?
Patoshi パトシ
# Even with dbcache=7000 and 16 core processor. Why does -reindex-chainstate take more than 24+ hours?

(Asked by: username_0 on 2018-10-05)

My computer got shut off due to a power outage and when I rebooted my bitcoin core it was stuck on connecting to peers. I was told to do a -reindex-chainstate with dbcache set as high as possible. Even with these high settings of dbcache=7000 and 16 core cpu, why does reindexing take more than 24+ hours? Also I'm not using a SSD, but a regular HDD.

**Tags:** bitcoin-core, reindex

> **Comments:**
> **username_1**: What does "suck on connecting to peers" mean?  And what told you to do a reindex chainstate?  
> **username_0**: Mr. username_3 told me to. see: https://bitcoin.stackexchange.com/questions/79760/its-october-2018-bitcoin-qt-reindex-chainstate-takes-forever-is-there-a-wa  
> **username_2**: Nowhere in that are you told to reindex.  
> **username_0**: Your right. he just mentions dbcache. I must have gotten it from another related question where someone had the same issue of connecting to peers. This happened right after my VM box got shut off unexpectedly.  
> **username_3**: Do you have pruning turned on?  
> **username_0**: no i do not have pruning turned on.  

---

## 0 answers

