# Backup issues following NAS crash - Hash mismatch

**URL:** <https://forum.duplicati.com/t/backup-issues-following-nas-crash-hash-mismatch/5303>\
**Category:** Support\
**Created:** [November 15, 2018, 7:08pm UTC](https://forum.duplicati.com/t/backup-issues-following-nas-crash-hash-mismatch/5303 "2018-11-15T19:08:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JonMikelV](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/439d5e/32.png) [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)\
**Post date:** [November 15, 2018, 7:46pm UTC](https://forum.duplicati.com/t/backup-issues-following-nas-crash-hash-mismatch/5303/2 "2018-11-15T19:46:32Z")

</div>

Ouch! I hope you were able to verify (and replace) that bad memory!

At this point I think you pretty much just need to purge the bad version (in your case 5). I could be wrong, so feel free to wait for a second opinion - but if I’m wrig then hopefully this will help:

> [@How to list / purge broken files](https://forum.duplicati.com/t/how-to-list-purge-broken-files/3884):
>
> This is a first crack at helping people understand what will happen with list-broken-files and purge-broken-files commands. It is by no means complete, but it IS a wiki, so feel free to add / update anything you feel might be useful to other users. slight_smile While Duplicati is very robust in handling errors (including missing destination files) there may come a time when you need to remove references to backup versions from your job. When this happens, the use of the list-broken-files …

* * *

I notice your “broken” version has a fairly old date (09/27/2018) on it - it’s odd that something other than the most recent backup (version 0) would be involved in any files transfers UNLESS a compact was going on - do you think that could have been the process running during the reboot?

---

_[View the full topic](https://forum.duplicati.com/t/backup-issues-following-nas-crash-hash-mismatch/5303)._
