Wallet cannot sync

[PSLLSP]

I reported this problem in the past and I see it again. I cannot sync wallet, I use wallet for Linux. I started with wallet that was not synced for 5 months. I tried to sync it today. I started with old wallet, v1.1.6 and it worked fine until block-chain history reached date 2020-10-04. At that date synchronization process was stopped. I realized I have to upgrade my wallet, so I downloaded wallet v1.2.1 and started sync process with new wallet client. But synchronization process is deadlocked at one block and I cannot continue. I have to delete whole block-chain and start sync process from block 0, I have to delete and download more than 4GB of data... :-( This bug is easy to replicate, I met this condition several times in the past and it is still not fixed.

This is tail of debug.log file from wallet v1.2.1, it rejects invalid header (that is block with date 2020-10-04):

2020-11-29T09:57:14Z Loaded best chain: hashBestChain=00000000000001899573ccfaa99c8d58d44514c1d59bd3f59dcf0aac372f904f height=329175 date=2020-10-04T17:45:02Z progress=0.981318
2020-11-29T09:57:14Z init message: Rewinding blocks...
2020-11-29T09:57:14Z init message: Verifying blocks...
2020-11-29T09:57:14Z Verifying last 6 blocks at level 3
2020-11-29T09:57:14Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2020-11-29T09:57:14Z No coin database inconsistencies in last 6 blocks (6 transactions)
2020-11-29T09:57:14Z  block index            3602ms
2020-11-29T09:57:14Z init message: Loading wallet...
...
2020-11-29T09:57:28Z 1 addresses found from DNS seeds
2020-11-29T09:57:28Z dnsseed thread exit
2020-11-29T09:57:30Z New outbound peer connected: version: 70022, blocks=368309, peer=2
2020-11-29T09:57:31Z New outbound peer connected: version: 70022, blocks=368309, peer=3
2020-11-29T09:57:32Z New outbound peer connected: version: 70022, blocks=368309, peer=4
2020-11-29T09:57:58Z New outbound peer connected: version: 70021, blocks=329175, peer=5
2020-11-29T09:57:59Z New outbound peer connected: version: 70022, blocks=368309, peer=6
2020-11-29T09:58:51Z New outbound peer connected: version: 70021, blocks=329175, peer=7
2020-11-29T09:59:32Z New outbound peer connected: version: 70021, blocks=329175, peer=8
2020-11-29T10:02:08Z ERROR: AcceptBlockHeader: block 000000000000003a71ad2f6d1f7d7da07d59ce22cff5c2c1e51da6c21c625b4f is marked invalid
2020-11-29T10:02:08Z ERROR: invalid header received
2020-11-29T10:05:25Z New outbound peer connected: version: 70022, blocks=368315, peer=9
2020-11-29T10:07:32Z ERROR: AcceptBlockHeader: block 000000000000003a71ad2f6d1f7d7da07d59ce22cff5c2c1e51da6c21c625b4f is marked invalid
2020-11-29T10:07:32Z ERROR: invalid header received
2020-11-29T10:08:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 630 seconds ago)
2020-11-29T10:08:30Z New outbound peer connected: version: 70022, blocks=368318, peer=11
2020-11-29T10:10:22Z ERROR: AcceptBlockHeader: block 000000000000003a71ad2f6d1f7d7da07d59ce22cff5c2c1e51da6c21c625b4f is marked invalid
2020-11-29T10:10:22Z ERROR: invalid header received
2020-11-29T10:10:36Z socket recv error  (104)
2020-11-29T10:11:21Z socket recv error  (104)
2020-11-29T10:12:42Z New outbound peer connected: version: 70021, blocks=329175, peer=14
2020-11-29T10:13:03Z Timeout downloading headers from peer=1, disconnecting
2020-11-29T10:13:12Z New outbound peer connected: version: 70022, blocks=368320, peer=15
2020-11-29T10:14:45Z New outbound peer connected: version: 70021, blocks=329175, peer=16
...
2020-11-29T12:52:25Z New outbound peer connected: version: 70022, blocks=368398, peer=84
2020-11-29T12:53:41Z socket recv error  (104)
2020-11-29T12:55:16Z ERROR: AcceptBlockHeader: block 000000000000003a71ad2f6d1f7d7da07d59ce22cff5c2c1e51da6c21c625b4f is marked invalid
2020-11-29T12:55:16Z ERROR: invalid header received
2020-11-29T12:55:16Z ERROR: AcceptBlockHeader: block 000000000000003a71ad2f6d1f7d7da07d59ce22cff5c2c1e51da6c21c625b4f is marked invalid
2020-11-29T12:55:16Z ERROR: invalid header received
2020-11-29T12:55:41Z ERROR: AcceptBlockHeader: block 000000000000003a71ad2f6d1f7d7da07d59ce22cff5c2c1e51da6c21c625b4f is marked invalid
2020-11-29T12:55:41Z ERROR: invalid header received
2020-11-29T12:56:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10710 seconds ago)

[matiasSXchange]

HI, I'm facing the exactly same problem. Any solution?
Already tried:
clearbanned
reconsiderblock <blockhash>
It didn't work.

[proteanx]

HI, I'm facing the exactly same problem. Any solution? Already tried: clearbanned reconsiderblock <blockhash> It didn't work.

This is caused by an improper shutdown. The quickest solution if reconsiderblock does not work is to delete the chainstate and rewards directories (not the blocks directory) and let it rebuild the chain index on boot.