# Restore of elasticsearch data fails with CorruptIndexException\[checksum failed (hardware problem?)

**URL:** https://discuss.elastic.co/t/restore-of-elasticsearch-data-fails-with-corruptindexexception-checksum-failed-hardware-problem/261619
**Category:** Elasticsearch
**Tags:** snapshot-and-restore
**Created:** [January 20, 2021, 7:57am UTC](https://discuss.elastic.co/t/restore-of-elasticsearch-data-fails-with-corruptindexexception-checksum-failed-hardware-problem/261619 "2021-01-20T07:57:18Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [January 20, 2021, 11:07am UTC](https://discuss.elastic.co/t/restore-of-elasticsearch-data-fails-with-corruptindexexception-checksum-failed-hardware-problem/261619/4 "2021-01-20T11:07:02Z")

</div>

> [@akshatsharma](#):
>
> How can the backup content change?

These things happen, there's lots of possibilities. Wikipedia has an article that gives some more background on [silent corruption on disks](https://en.wikipedia.org/wiki/Data_corruption#Silent); a user here [recently reported corruption due to bad RAM](https://discuss.elastic.co/t/lucene-commit-failed-checksum-failed-while-indexing/253215/4). We recently found a [kernel bug](https://www.elastic.co/blog/canonical-elastic-and-google-team-up-to-prevent-data-corruption-in-linux) that causes corruption. I've also seen corruption introduced by [bad/buggy storage controllers](https://community.perforce.com/s/article/2410).

---

_[View the full topic](https://discuss.elastic.co/t/restore-of-elasticsearch-data-fails-with-corruptindexexception-checksum-failed-hardware-problem/261619)._