# Elasticsearch doesn't recover data from NAS storage volume

**URL:** <https://discuss.elastic.co/t/elasticsearch-doesnt-recover-data-from-nas-storage-volume/234681>\
**Category:** Elasticsearch\
**Created:** [May 28, 2020, 7:42am UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-recover-data-from-nas-storage-volume/234681 "2020-05-28T07:42:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tmporary](https://avatars.discourse-cdn.com/v4/letter/t/7bcc69/32.png) [@tmporary](https://discuss.elastic.co/u/tmporary)\
**Post date:** [May 28, 2020, 7:42am UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-recover-data-from-nas-storage-volume/234681/1 "2020-05-28T07:42:28Z")

</div>

Hi,  
Our elasticsearch instance starts up fine and in the logs I can see that it found the mounted storage but it doesn't recover any indices info into the cluster.

`[2020-05-28T06:51:41,853][INFO][o.e.e.NodeEnvironment] [es_master] using [1] data paths, mounts [[/media/storage (NAME_OF_NAS)]], net usable_space [10.3gb], net total_space [10.4gb], types [nfs]`

`[2020-05-28T06:51:54,950][INFO][o.e.g.GatewayService] [es_master] recovered [0] indices into cluster_state`

We have almost everything set to defaults when it comes to config the only config properties we set outservles are:

```
cluster.name: cluster_name

node.name: esmaster
node.master: true
node.data: false

discovery.seed_hosts: address to master

cluster.initial_master_nodes: esmaster

network.host: 0.0.0.0

path.data: /media/storage/data

node.max_local_storage_nodes: 3

```

The same properties are set for our data node with the difference that it has assigned data role instead of master

Am I missing something or doing something wrong? Maybe there's some specific way how to set up Elastic in order for it to be able to retrieve data from network mounted nfs shared drive

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 28, 2020, 7:50am UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-recover-data-from-nas-storage-volume/234681/2 "2020-05-28T07:50:09Z")

</div>

I would recommend you have a look at [this post](https://discuss.elastic.co/t/why-nfs-is-to-be-avoided-for-data-directories/215240/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 28, 2020, 7:57am UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-recover-data-from-nas-storage-volume/234681/3 "2020-05-28T07:57:18Z")

</div>

I suspect this may be your problem:

> [@tmporary](#):
>
> `node.max_local_storage_nodes: 3`

Don't use this, it's a little dangerous and it's deprecated. From the [docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#max-local-storage-nodes):

> **WARNING** : Never run different node types (i.e. master, data) from the same data directory. This can lead to unexpected data loss.

Instead, give each node its own specific `data.path` underneath `/media/storage/data`

Also as per the post Christian linked, NFS can theoretically be configured to work correctly but it's easy to get it wrong without realising, and often doesn't perform too well.

---

<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:** [June 25, 2020, 7:57am UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-recover-data-from-nas-storage-volume/234681/4 "2020-06-25T07:57:20Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.