bitcoin: Stuck in Endless Pre-Syncing Headers Loop

Expected behavior Pre-Sync Headers Like Normal.

Actual behavior

2022-10-26T07:34:14Z Pre-synchronizing blockheaders, height: 748853 (~98.55%)
2022-10-26T07:34:16Z Pre-synchronizing blockheaders, height: 226853 (~31.00%)

Unaffected by restating program.

2022-10-26T07:34:14Z Pre-synchronizing blockheaders, height: 748853 (~98.55%)
2022-10-26T07:34:16Z Pre-synchronizing blockheaders, height: 226853 (~31.00%)

To reproduce

I think that this is a one-off sort of error:

Here is a backup of my .bitcoin folder. https://drive.proton.me/urls/V04QAGG998#GlCnfHpkWW7F

~The files before blk00047.dat and rev00047.dat are omitted, and need to be copied in from another source.~ As sipa says, the blk files are not deterministic. - Will upload the full .bitcoin folder so people can reproduce…

Here is the 4.6gb full backup of my .bitcoin folder: https://drive.proton.me/urls/JA11NDEA14#GeG83qrpmvtt

System information

Fedora 37 Silverblue Running in Toolbox.

Bitcoin Core: 28cf75697186ea8e473e120a643994bdf8237d6c

About this issue

  • Original URL
  • State: open
  • Created 4 years ago
  • Comments: 21 (13 by maintainers)

Most upvoted comments

I’m seeing this with v25.0.0 as well 😕

2023-06-20T11:09:46Z Pre-synchronizing blockheaders, height: 782560 (~98.44%)
2023-06-20T11:09:49Z Pre-synchronizing blockheaders, height: 738560 (~93.00%)

What are the recommendations on fixing this?

detect this corruption and self fix/reindex from the point of corruption.

I am not sure this will be an improvement, because:

  • It will turn an endless per-sync loop into an endless reindex loop (at least for some).
  • If there is an issue with the hardware, it would be better to diagnose and fix it, instead of continuing. Otherwise the issue will possibly be silently ignored and re-appear in the future.

My recommendation would be to check which configs of your hardware run into this problem and then try to determine and fix the root cause.