# Badly corrupted index

**URL:** <https://discuss.elastic.co/t/badly-corrupted-index/21476>\
**Category:** Elasticsearch\
**Created:** [January 5, 2015, 11:02am UTC](https://discuss.elastic.co/t/badly-corrupted-index/21476 "2015-01-05T11:02:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmkgreen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jmkgreen/32/471_2.png) [@jmkgreen](https://discuss.elastic.co/u/jmkgreen)\
**Post date:** [January 5, 2015, 11:02am UTC](https://discuss.elastic.co/t/badly-corrupted-index/21476/1 "2015-01-05T11:02:52Z")

</div>

Our storage server threw it's toys of the pram. We got it back, and  
everything bar ElasticSearch is singing sweetly again.

On start, we get an IndexFormatTooNewException. Not many get that one, but  
CheckIndex appears to be worth a go, except that also barfs:

nicks@elasticsearch:/var/lib/elasticsearch/elasticsearch/nodes/0/indices/support/3/index$  
sudo java -cp /usr/share/elasticsearch/lib/lucene-core-4.8.1.jar  
-ea:org.apache.lucene... org.apache.lucene.index.CheckIndex . -fix  
Opening index @ .  
ERROR: could not read any segments file in directory  
org.apache.lucene.index.IndexFormatTooNewException: Format version is not  
supported (resource:  
BufferedChecksumIndexInput(MMapIndexInput(path="/var/lib/elasticsearch/elasticsearch/nodes/0/indices/support/3/index/segments.gen"))):  
1071082519 (needs to be between -2 and -3)  
at  
org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:803)  
at  
org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:710)  
at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:412)  
at  
org.apache.lucene.index.CheckIndex.checkIndex(CheckIndex.java:393)  
at org.apache.lucene.index.CheckIndex.main(CheckIndex.java:1967)

This has rendered our ES service offline. Any suggestions to fix it would  
be appreciated, we are uncertain how to proceed otherwise.

ES 1.2.1 from Debian packages. We are just (now) upgrading to 1.4 to see if  
this results in some progress.

James

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAMH6%2BaxYVvHEnjLocbeHh9v5pjReZ0aDds0aOtkjy1sDGmfY1w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2BaxYVvHEnjLocbeHh9v5pjReZ0aDds0aOtkjy1sDGmfY1w%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![unknownunknown](https://avatars.discourse-cdn.com/v4/letter/u/4da419/32.png) [@unknownunknown](https://discuss.elastic.co/u/unknownunknown)\
**Post date:** [October 5, 2016, 1:08pm UTC](https://discuss.elastic.co/t/badly-corrupted-index/21476/2 "2016-10-05T13:08:31Z")

</div>

Were you ever able to recover from this scenario?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 10:14pm UTC](https://discuss.elastic.co/t/badly-corrupted-index/21476/3 "2017-07-05T22:14:43Z")

</div>