# Red status caused by stuck initializing\_shards

**URL:** https://discuss.elastic.co/t/red-status-caused-by-stuck-initializing-shards/135177
**Category:** Elasticsearch
**Created:** [June 8, 2018, 3:46pm UTC](https://discuss.elastic.co/t/red-status-caused-by-stuck-initializing-shards/135177 "2018-06-08T15:46:24Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)
#### Post date: [June 21, 2018, 2:20pm UTC](https://discuss.elastic.co/t/red-status-caused-by-stuck-initializing-shards/135177/12 "2018-06-21T14:20:25Z")

</div>

The logs here is showing that shard `2` of index `index_2018.01.21` is corrupted. But there might be others as well.

You could try what is described here: [Corrupted elastic index](https://discuss.elastic.co/t/corrupted-elastic-index/135932/2) but if there is an underlying hardware issue then it won't help much.

---

_[View the full topic](https://discuss.elastic.co/t/red-status-caused-by-stuck-initializing-shards/135177)._