# Help with corrupt repo

**URL:** <https://kopia.discourse.group/t/help-with-corrupt-repo/1247>\
**Category:** Support\
**Created:** [July 1, 2022, 2:09pm UTC](https://kopia.discourse.group/t/help-with-corrupt-repo/1247 "2022-07-01T14:09:19Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![tony09](https://avatars.discourse-cdn.com/v4/letter/t/7cd45c/32.png) [@tony09](https://kopia.discourse.group/u/tony09)\
**Post date:** [July 3, 2022, 3:02am UTC](https://kopia.discourse.group/t/help-with-corrupt-repo/1247/4 "2022-07-03T03:02:10Z")

</div>

> [@jkowalski](#):
>
> Then run `kopia index recover --parallel=10 --commit` and see if that recovers your repository.

I ended up removing all the files under the xn25 directory before I was able to connect and run an index recover. That seemed to have done the trick, and I was able to complete a round of snapshot create commands.

Thank you! In general, if I wanted to verify the integrity of the local repo before doing a sync, would a snapshot verify 100% be the only way?

Edit: found the answer to my question in this [related thread](https://kopia.discourse.group/t/best-method-to-ensure-valid-snapshots-snapshot-verify-vs-snapshot-fix-invalid-files/1217)

---

_[View the full topic](https://kopia.discourse.group/t/help-with-corrupt-repo/1247)._