michaelscheung

Okay after running `integration stage_trie —reset` node, I have again encountered the same error ``` EROR[08-23|03:39:23.004] [9/16 IntermediateHashes] Wrong trie root of block 32008831: 20639276ae2cd71b0f04af0977f6a4e66a97f651ddcfc5adc2e4564210ce01e7, expected (from header): 6095bf311356aaf1c6bd44f79149f829e51f3040e0c5b5f0e781a677781d1a89. Block...

Apologies here it is ``` user@UbuntuAmd:/mnt/raid_array/erigon/erigon-fynn-z$ ./build/bin/integration print_stages --datadir="/mnt/md4/erigon/polygon/erigon/datadir" --chain="bor-mainnet" Note: prune_at doesn't mean 'all data before were deleted' - it just mean stage.Prune function were run to this block....

Yes, at least I tried to, but I was unable to unwind stage_trie. Even if I reset and redid the entire step, it would encounter the same error. Also, I've...

My polygon node synchronized from backup seems to have been stuck on some kind of queue for the past few days. I don't remember seeing this before, so I wonder...

Update: I was able to achieve full synchronization using `erigon version 2022.08.1-alpha-7dabdc3` on a backup I took two months ago. So the bug appears to be something that was introduced...

This issue persist even with the latest release `erigon version 2022.09.1-alpha-4067b7c4` I had to revert to `erigon version 2022.99.99-dev-a02c71c0` (slightly after [v2022.08.01](https://github.com/ledgerwatch/erigon/tree/v2022.08.01) with VRS fix) to get it to synchronize...

> I concur with your point. That is the sense I have gotten from the situation by enumeration of the facts. > > I think AWS (as a company) needs...