Bitcoin-qt stuck at 284170 block for a week #4125

issue mariobgr opened this issue on May 5, 2014

mariobgr commented at 1:21 AM on May 5, 2014: none

Hi, I downloaded the Bitcoin Core v0.9.1.0-g026a939-beta (64-bit) and started the syncing about a week ago. For the first day and a half, the process went all the way to 12 weeks, but it got stuck there. The active connections are 38, everything looks good... except the syncing process

You can take a look at the log file here - http://mariobgr.com/debug.log

.
rebroad commented at 2:18 AM on May 5, 2014: contributor

would have been useful if the debug.log had included the parts from before you forked.
mariobgr commented at 2:38 AM on May 5, 2014: none

I restarted the client before posting the issue, sorry. I have no idea where to look for old logs...
laanwj added the label Bug on May 5, 2014

laanwj commented at 7:35 AM on May 5, 2014: member

2014-05-04 20:47:03 CheckForkWarningConditions: Warning: Large valid fork found
  forking the chain at height 284170 (0000000000000001ca4532061c5410c6acaf8fb47119b5ada2e9d421dacfed54)
  lasting to height 299128 (0000000000000000502bb5f16c22ee26d66479a285d79fa33c48212e8cf8d0bd).
Chain state database corruption likely.

So it thinks that the main chain is a fork. All new blocks that it receives are seen to be part of this fork, instead of the most-work chain. I wonder that it thinks to be the best chain, then?

Well,

2014-05-02 18:36:58 LoadBlockIndexDB(): hashBestChain=0000000000000001ca4532061c5410c6acaf8fb47119b5ada2e9d421dacfed54 height=284170 date=2014-02-04 19:53:15 progress=0.599675

So it is on the main chain, not even on a perceived fork. No idea what went wrong here...

rebroad commented at 9:14 AM on May 5, 2014: contributor

Might this be the same issue as #2726?
sipa commented at 1:27 PM on May 5, 2014: member

Yes, seems to be the case. Not that #2726 is a single issue really - it's just "chain validation fails for some unexplained reason".
laanwj commented at 9:24 AM on May 6, 2014: member

#4064 looks very similar as well
laanwj added the label UTXO Db and Indexes on May 6, 2014
mariobgr commented at 10:27 PM on May 6, 2014: none

Could be. I tried running with -reindex -par=1 and it got stuck at 15 weeks (instead of 12). CMD game me an I\O error (corrupted db) and crashed. Same thing on my laptop (completely different hardware). Should I try different version (32 bit perhaps) ?
noxxim commented at 8:32 AM on May 13, 2014: none

I got stucked in November 2013. Reindex with par=1 fixed it.
laanwj closed this on May 18, 2015
DrahtBot locked this on Sep 8, 2021

Contributors

Labels

Bug UTXO Db and Indexes

Linked (view graph)

#5645 "Large valid fork found" , stuck at block 322082