Spin up new Nexus instance from scratch - Task Execute Data Repair Plan stops after 0 seconds

We were running an instance of Nexus for some years until we ran into severe database corruption some months after successful migration from OrientDB to H2.

Since then this instance was running in read-only mode, we were able to set.

Last week I tried to set up a new instance with a PostgreSQL database. Everything worked fine according to the guide.

Now I had the idea to restore the database completely from the blob store.

I moved the blob store from the old Nexus instance to the new one and ran the task “Recalculate blob store storage”. Once I did this for the docker and once for the maven blob store.

UI shows that it was successful and the correct size is shown:

But when running the task “Repair - Execute Data Repair Plan” it just says OK, with a runtime of 0 seconds.
I configured the task “Repair - Data Repair Plan”, selected the correct blob store and manually recreated the repositories which were present in the broken instance.

What can I do to make the Repair task work?