failed to sync after upgrade to 0.1.0-alpha.5

[0xSt1ng3R]

Describe the bug

1. Yesterday our reth node got stuck on 17867059, the same issue as in Stopped Syncing at Block 17867060 #4107.
2. Today, we upgraded to 0.1.0-alpha.5 with the fix(trie): dangling storage hashes #4108 fix.
3. The reth node failed to sync fully.
4. Tried to unwind a couple of blocks (reth stage unwind to-block 17860000) - but failed like in Skip state root check in stage unwind command #4114.
5. Logs attached - they are after the unwind.

Steps to reproduce

reth node --authrpc.jwtsecret /root/jwt.hex --authrpc.addr 127.0.0.1 --authrpc.port 8551 --http --http.addr 127.0.0.1 --http.port 8545 --http.api all --ws --ws.addr 127.0.0.1 --ws.port 8546 --ws.api all --ipcpath /tmp/reth.ipc --rpc-max-connections 1024 --rpc-max-subscriptions-per-connection 1024 --rpc-max-tracing-requests 1024 --log.persistent --log.filter info -vvv

lighthouse --network mainnet beacon --execution-endpoint http://localhost:8551 --execution-jwt /root/jwt.hex --http --logfile /tmp/lighthouse.log

Node logs

reth logs, lighthouse logs

Platform(s)

Linux (x86)

What version/commit are you on?

reth Version: 0.1.0-alpha.5
Commit SHA: b823cc01
Build Timestamp: 2023-08-09T07:52:03.903854775Z
Build Features: default,jemalloc
Build Profile: maxperf

What database version are you on?

Current database version: 1
Local database version: 1

If you've built Reth from source, provide the full command you used

LD_PRELOAD=/usr/local/lib/libjemalloc.so RUSTFLAGS="-C target-cpu=native" cargo build --profile maxperf --features jemalloc

Code of Conduct

• I agree to follow the Code of Conduct

[mattsse]

we still had a bug in this commit b823cc0 ,

the fix was added #4126

[0xSt1ng3R]

upgraded to 31d1288, but still have the same problem.
reth logs, lighthouse logs.

[0xSt1ng3R]

looks like 6622f53 solved it!