# Shards failure - recovery possible?

**URL:** https://discuss.elastic.co/t/shards-failure-recovery-possible/231834
**Category:** Elasticsearch
**Created:** [May 9, 2020, 11:00am UTC](https://discuss.elastic.co/t/shards-failure-recovery-possible/231834 "2020-05-09T11:00:35Z")
**Posts on this page:** 1
**Showing post:** 2

<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: [May 9, 2020, 1:09pm UTC](https://discuss.elastic.co/t/shards-failure-recovery-possible/231834/2 "2020-05-09T13:09:59Z")

</div>

This probably relates your other recent post:

> [@Possibilities of increasing data security in elasticsearch - power failures \[?\]](https://discuss.elastic.co/t/possibilities-of-increasing-data-security-in-elasticsearch-power-failures/231839):
>
> Hi, Relatively simple question about the configuration of elasticsearch with respect to specific data security. Are there any possibilities to configure an elasticsearch cluster so that in case of a power failure there are no additional data losses? What security models when not all nodes have redundant power supply? Is there anything we can do? Of course backup is backup. But I'm looking for a quick solution in elasticsearch.

Looks like your storage system does not, in fact, implement `fsync()` correctly.

What's the _whole_ response from the allocation explain API? It looks like all copies of this shard are broken. Does this index have replicas?

---

_[View the full topic](https://discuss.elastic.co/t/shards-failure-recovery-possible/231834)._