Node suddenly stops [Batch hash mismatch]

[1aBcD1234aBcD1]

System information

Geth version: scroll-v5.7.0
OS & Version: Ubuntu with docker version 25.0.2, build 29cf629

Actual behaviour

After syncing some chain data I get the following:

scroll_node-1  | 2024-09-12T09:41:30.978855228Z INFO [09-12|09:41:30.978] Imported new chain segment               blocks=5   txs=103 mgas=31.532  elapsed=1.906s    mgasps=16.541 number=9,220,961 hash=ac5d2d..5ec07c dirty=0.00B ignored=1
scroll_node-1  | 2024-09-12T09:41:33.377937798Z INFO [09-12|09:41:33.377] Imported new chain segment               blocks=1   txs=16  mgas=4.218   elapsed=359.341ms mgasps=11.739 number=9,220,962 hash=c8e33f..8b2b9a dirty=0.00B
scroll_node-1  | 2024-09-12T09:41:34.394634670Z INFO [09-12|09:41:34.394] Imported new chain segment               blocks=1   txs=15  mgas=3.917   elapsed=252.392ms mgasps=15.519 number=9,220,963 hash=5b0443..2f9095 dirty=0.00B
scroll_node-1  | 2024-09-12T09:41:35.081636317Z ERROR[09-12|09:41:35.081] Batch hash mismatch                      batch index=308,540 start block=8,569,372 end block=8,569,429 parent batch hash=0x8bf40b5406245677958d3240194004478141364f0621f4c76da3b8d86dfe3b0a parent TotalL1MessagePopped=927,611 l1 finalized batch hash=0xac0d1baac7a803f541d43e1c9b4fb07307fb68ba5a6cf490206ab33739bffe83 l2 batch hash=0x771cde487fb70c3fd51bb7939a787de3c9bae6804f63fb6aa4ac163cba2b9d98

After that I get an error that starts that starts with chunks and is followed by a print of a ton of older blocks. Starting from block 8569372

[backtrace]

When submitting logs: please submit them as text and not screenshots.

[colinlyguo]

Thank you for reporting this issue and providing the log details. Could you share your node's full log output in a text file? And some additional information:

• Which L1 endpoint (or service provider) are you using for your node synchronization?
• At what block height did you start syncing your node?