Deriver system is resetting - failed to fetch blob sidecars for slot 9946383 block 0x4f792564095af9fa5d2e36c112afe0eaecc2080abdcbc01fd5241bd88dd2fc25:20737555

Bug Description
Op-node failed to fetch blobs: failed to get blob sidecars for L1BlockRef.
Steps to Reproduce

Try to sync mainet
Op-node is stuck on this error.
Expected behavior
It should sync without error

Environment Information:
Op-node and op-geth are deployed using docker-compose. Prysm and Geth are also deployed on same machine.

Op-node version is v1.11.2
Op-geth version is v1.101500.1

geth version is ethereum/client-go:v1.15.2
prysm version is beacon-chain:v5.3.0

P.S. geth is not fully synced, only prysm - but I don't think this causes this sync stuck on op-node.

Do you have any alternative for Beacon node that contain all blockchain data? (Maybe some flags could fix this?)
I also did some research and sync from scratch of Prysm does not guarantee my beacon node will have all the necessary data. Thank you!

Start by reproducing the sync failure with the stated op-node v1.11.2, op-geth v1.101500.1, Prysm v5.3.0, and Docker Compose setup. Investigate the op-node blob-sidecar fetch path and the reported L1 block reference, then verify that syncing proceeds without the reset or fetch error.

Written by the indexing model from the issue text.