bsc highestBlock stuck on old blocks

[qbittex]

i setup latest release and its stuck on highestBlock and currentblock

instance: Geth/v1.1.16-cb131fab/linux-amd64/go1.17.13

{ currentBlock: 20778855, healedBytecodeBytes: 0, healedBytecodes: 0, healedTrienodeBytes: 0, healedTrienodes: 0, healingBytecode: 0, healingTrienodes: 0, highestBlock: 20778920, startingBlock: 0, syncedAccountBytes: 268148753, syncedAccounts: 2335281, syncedBytecodeBytes: 206788504, syncedBytecodes: 26483, syncedStorage: 12188128, syncedStorageBytes: 2651009323 }

[cosinlink]

This is generally related to node performance and p2p peers quality, adding --tries-verify-mode=none to start command may help

[qbittex]

i still see this after add --tries-verify-mode=none my complate flag is

geth --config ./config.toml --datadir ./node --pprof.addr 0.0.0.0 --metrics --pprof --http --http.corsdomain "*" --diffsync --cache 18000 --tries-verify-mode=none

and block height show wrong

{ currentBlock: 0, healedBytecodeBytes: 0, healedBytecodes: 0, healedTrienodeBytes: 0, healedTrienodes: 0, healingBytecode: 0, healingTrienodes: 0, highestBlock: 21962155, startingBlock: 0, syncedAccountBytes: 30447145, syncedAccounts: 120989, syncedBytecodeBytes: 52097710, syncedBytecodes: 7232, syncedStorage: 1752514, syncedStorageBytes: 379855820 }

i use 128gb ram and 3 TB nvme server