New zcashd node syncing from scratch rejected valid block?

Here’s the messages from debug.log:

2024-01-21T16:33:54.914180Z INFO ProcessNewBlock: main: InvalidChainFound: invalid block=0000000000ec78332f0936f4c24fa98463a415c5447655e3dbe9e1bb257db996 height=1252580 log2_work=58.605282 date=2021-05-17 11:39:02
2024-01-21T16:33:54.914194Z INFO ProcessNewBlock: main: InvalidChainFound: current best=00000000007814ea6c6f4af9a466b24dedf0930c29b8570609825a3e749fb956 height=1252579 log2_work=58.60528 date=2021-05-17 11:35:35
2024-01-21T16:33:54.914201Z ERROR ProcessNewBlock: main: ConnectTip(): ConnectBlock 0000000000ec78332f0936f4c24fa98463a415c5447655e3dbe9e1bb257db996 failed
2024-01-21T16:33:54.914223Z INFO ProcessNewBlock: main: InvalidChainFound: invalid block=0000000000ec78332f0936f4c24fa98463a415c5447655e3dbe9e1bb257db996 height=1252580 log2_work=58.605282 date=2021-05-17 11:39:02
2024-01-21T16:33:54.914231Z INFO ProcessNewBlock: main: InvalidChainFound: current best=00000000007814ea6c6f4af9a466b24dedf0930c29b8570609825a3e749fb956 height=1252579 log2_work=58.60528 date=2021-05-17 11:35:35

How ever the block 0000000000ec78332f0936f4c24fa98463a415c5447655e3dbe9e1bb257db996 appears to be a valid block according to block explorers. My node is now stuck at height 1252579.

Running zcashd v5.8.0 compiled from github.

3 Likes

I’ll forward this but, unless this is issue specific to 5.8.0, the typical solution is to reindex.

1 Like

Attempted to reindex but now node stuck at different height with a bunch of ‘hashMerkleRoot mismatch’ errors.

Could this be a disk failure?

2 Likes