# GET\_REPAIR failed because of invalid signature

**URL:** <https://forum.storj.io/t/get-repair-failed-because-of-invalid-signature/16122>\
**Category:** troubleshooting\
**Created:** [November 12, 2021, 9:11am UTC](https://forum.storj.io/t/get-repair-failed-because-of-invalid-signature/16122 "2021-11-12T09:11:40Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [November 14, 2021, 4:58pm UTC](https://forum.storj.io/t/get-repair-failed-because-of-invalid-signature/16122/27 "2021-11-14T16:58:11Z")

</div>

The audit can be affected by `GET_AUDIT` and `GET_REPAIR` in three ways:

1. data is deleted
2. 3x 5-minutes timeouts for the same piece
3. data is corrupted.

The first one is visible in the logs as “file not found”. The second is visible too - you should measure time between “download started” and “downloaded” (see [Got Disqualified from saltlake - #97 by Alexey](https://forum.storj.io/t/topic/14848/97)). The third one cannot be visible in the logs (it will be downloaded as usual), but sometimes visible, see [[storagenode] pieces error: PieceHeader framing field claims impossible size of XXX bytes · Issue #4194 · storj/storj · GitHub](https://github.com/storj/storj/issues/4194)

---

_[View the full topic](https://forum.storj.io/t/get-repair-failed-because-of-invalid-signature/16122)._
