# Index corruption with .tim file checksum mismatch **URL:** \ **Category:** Elasticsearch\ **Created:** [March 7, 2019, 8:38am UTC](https://discuss.elastic.co/t/index-corruption-with-tim-file-checksum-mismatch/171253 "2019-03-07T08:38:13Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [March 7, 2019, 2:36pm UTC](https://discuss.elastic.co/t/index-corruption-with-tim-file-checksum-mismatch/171253/4 "2019-03-07T14:36:36Z")
> [@Rushikesh\_Pathak](#): > > Is there any know scenario in which this might occur? Yes, the most common scenario is a hardware problem. Sometimes it's the disk, sometimes a failing RAID controller or a flaky SAN. Occasionally it's a [bug in a filesystem implementation](https://discuss.elastic.co/t/underlying-file-changed-by-an-external-force/137555/4), particularly if you're not [using local disks](https://www.elastic.co/guide/en/elasticsearch/guide/current/hardware.html#_disks). Since you're using virtualisation it could also be an issue in the host OS or the hypervisor. There's a lot of places in between Elasticsearch and the disk in which things can go wrong, and unfortunately from Elasticsearch's point of view it can't tell you any more: they bytes it wrote weren't the bytes it read back again. --- _[View the full topic](https://discuss.elastic.co/t/index-corruption-with-tim-file-checksum-mismatch/171253)._