# Strategy to recover from RAM corrupted blocks

**URL:** <https://forum.duplicati.com/t/strategy-to-recover-from-ram-corrupted-blocks/20611>\
**Category:** Support\
**Created:** [May 1, 2025, 8:07am UTC](https://forum.duplicati.com/t/strategy-to-recover-from-ram-corrupted-blocks/20611 "2025-05-01T08:07:48Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)\
**Post date:** [May 13, 2025, 2:39pm UTC](https://forum.duplicati.com/t/strategy-to-recover-from-ram-corrupted-blocks/20611/12 "2025-05-13T14:39:17Z")

</div>

> [@obones](#):
>
> I just got the update for 2.1.0.117

It just got replaced with 2.1.0.118. I’m not going to quote the whole change description, however I think you might be in the area that was found broken, and was just rewritten:

> [@Release: 2.1.0.118 (Canary) 2025-05-12](https://forum.duplicati.com/t/release-2-1-0-118-canary-2025-05-12/20666/1):
>
> This version has a number of minor fixes and a major rewrite of the the “repair” command.

I don’t know if the dev will come by to comment further on your 2.1.0.117 repair attempt.

---

_[View the full topic](https://forum.duplicati.com/t/strategy-to-recover-from-ram-corrupted-blocks/20611)._
