# Upgrade from 1.2.1 to 1.4.2 and indices/shards corrupted

**URL:** https://discuss.elastic.co/t/upgrade-from-1-2-1-to-1-4-2-and-indices-shards-corrupted/21890
**Category:** Elasticsearch
**Created:** [January 29, 2015, 12:56am UTC](https://discuss.elastic.co/t/upgrade-from-1-2-1-to-1-4-2-and-indices-shards-corrupted/21890 "2015-01-29T00:56:11Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Greg\_5](https://avatars.discourse-cdn.com/v4/letter/g/f475e1/32.png) [@Greg\_5](https://discuss.elastic.co/u/Greg_5)
#### Post date: [January 29, 2015, 12:56am UTC](https://discuss.elastic.co/t/upgrade-from-1-2-1-to-1-4-2-and-indices-shards-corrupted/21890/1 "2015-01-29T00:56:11Z")

</div>

Hello,

We upgraded from 1.2.1 to 1.4.2 and after the restart, some shards were in  
UNASSIGNED state because they was corrupted.  
Here is a log: [https://gist.github.com/anonymous/63a0e3f70a72bab37052](https://gist.github.com/anonymous/63a0e3f70a72bab37052) and  
"Failed to start shard, message  
[IndexShardGatewayRecoveryException[[events\_xxxxx][2] failed to fetch index  
version after copying it over]"

To solve this, we deleted \_checksums and corrupted\* files from the data  
directory.

After various node restart... some shard which were perfectly loaded  
previously became suddenly "Corrupted"... The problem occured also when i  
tried to increase the number of replica on an index with no replica. The  
primary and the replica became UNASSIGNED for the same reason.

I tried the command to force allocation but without success: trying to  
allocate a primary shard [events\_xxxx][2], which is disabled  
And i can't consider to set allow\_primary="true" if i lose my data. cf doc  
"might result in data loss". In which case there is no data loss ?

The cluster is now green but.. i'm afraid to restart it or to add replica  
to others indices.

Any idea about this issue ?

Thank you for you help

--  
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/0ba1ce67-c220-42cd-8df9-fafde50970e5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0ba1ce67-c220-42cd-8df9-fafde50970e5%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 6, 2017, 12:36am UTC](https://discuss.elastic.co/t/upgrade-from-1-2-1-to-1-4-2-and-indices-shards-corrupted/21890/2 "2017-07-06T00:36:02Z")

</div>


