S3 backed repository missing chunks

Hello,

One of our repository is encountering issues duw to missing chunks. I ran a cvmfs_server check and got the following error:

[inspecting catalog] bb68eae71852bbac2eafb5851acb3f9f61292723-shake128 at /testing/1056695/sandybridge/software/XXX/2024-3/YYYYY-v6.7
CATALOG PROBLEMS OR OTHER ERRORS FOUND

Is there a way for me to recover the repository? We still have the original source of truth for the data in the repo.
Thanks!

The easiest way would be to use a stratum-1 replica or backup of the whole repository if that exists - is there one? The missing/corrupted files can just be replaced in the storage backend then.

A publication that removes and adds the files again may not work if the objects are corrupted.
Can you do a directory listing on that path if you mount the repository?

We don’t have a backup of the backend or a stratum-1 replica for that repo. I will do a recursive listing of the subdir and see what is missing.