Have you tried to run the repair tool again? This reference says that the repair tool will repair the issue. I generally tell my clients to run the verify, then repair manually that which the tool can't correct with the repair option. After the manual repair, run the verify again and if no manual intervention is required then to run the repair tool. Once the repair tool is completed (it should report all issues repaired), I then recommend repeating the verify, repair sequence until the verify returns a clean report with no issues, as I have seen the repair option create a new issue that another verify then finds. Once the verify has come back clean, then perform the upgrade.
If the project is truly corrupted as yoou say then you will need to start again with a fresh repository and a freshly migrated project schema in the DB. If the upgrade just stopped/ failed but the project didn't corrupt, then you can try a few cycles of verify and repair to fix the issues. It may be that the BP_PARAMs (says 9 instances) may need to be removed prior to attempting the upgrade. You would need to remove them from the DB component more than likely. I would try the verify and repair again first before trying a new repository and project schema though.
Hope this helps,