was more informative than the other two times this quite unusual list-broken-files message was seen.
Not seeing in advance what will happen is a little uncomfortable, but you can possibly find out later by
The COMPARE command if things are intact enough to run. Start-over is also good, but loses history.
I’m not sure how to debug your error message unless you can get in deep, or it’s reproducible. Maybe Creating a bug report and posting a link to it would help an expert, but I think the database format isn’t directly testable with that command, because it has to look at your backup files which I won’t ask for…
One way to possibly get some information detail is to add a –log-file=<path>, and run for another error.