# Default index pattern is missing after ES data dir been moved
**URL:** https://discuss.elastic.co/t/default-index-pattern-is-missing-after-es-data-dir-been-moved/149837
**Category:** Kibana
**Created:** [September 25, 2018, 1:27pm UTC](https://discuss.elastic.co/t/default-index-pattern-is-missing-after-es-data-dir-been-moved/149837 "2018-09-25T13:27:49Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Andrew\_Liaskovski](https://discuss.elastic.co/u/Andrew_Liaskovski)
#### Post date: [September 25, 2018, 1:27pm UTC](https://discuss.elastic.co/t/default-index-pattern-is-missing-after-es-data-dir-been-moved/149837/1 "2018-09-25T13:27:49Z")
Hi all. I'm having this issue where the default index pattern is no longer default and Kibana needs user to "star" some pattern once again? It happens on my instance not only every time when I restart ELK stack, also it happens periodically.
Pre-conditions are:
Had worked properly up until EBS volume was changed. I had to restore it and copy ES data dir to other location. The reason is a long story )
Docker-compose, here is the volume mount -
- /opt/elasticsearch\_data/data:/usr/share/elasticsearch/data
before migration I had rexray ebs driver
elasticsearch\_data:
driver: rexray/ebs:latest
and mount
- elasticsearch\_data:/usr/share/elasticsearch/data
Now I have:
tree -L 4 /opt/elasticsearch\_data/data/
/opt/elasticsearch\_data/data/
└── nodes
└── 0
├── indices
│ ├── 0yuAlf28TRKJkLpx5whg7Q
│ ├── yVBDitDpQqeX2Dh4dUIQrA
│ └── zdg0ckv3QvCqtQsGGkndxw
├── node.lock
└── \_state
├── global-526.st
└── node-86.st
0yuAlf28TRKJkLpx5whg7Q is .kibana index and here is a tree for it
├── 0
│ ├── index
│ │ ├── \_6b\_1.liv
│ │ ├── \_6b.dii
│ │ ├── \_6b.dim
│ │ ├── \_6b.fdt
│ │ ├── \_6b.fdx
│ │ ├── \_6b.fnm
│ │ ├── \_6b\_Lucene50\_0.doc
│ │ ├── \_6b\_Lucene50\_0.pos
│ │ ├── \_6b\_Lucene50\_0.tim
│ │ ├── \_6b\_Lucene50\_0.tip
│ │ ├── \_6b\_Lucene70\_0.dvd
│ │ ├── \_6b\_Lucene70\_0.dvm
│ │ ├── \_6b.nvd
│ │ ├── \_6b.nvm
│ │ ├── \_6b.si
│ │ ├── \_6f.cfe
│ │ ├── \_6f.cfs
│ │ ├── \_6f.si
│ │ ├── \_6g.cfe
│ │ ├── \_6g.cfs
│ │ ├── \_6g.si
│ │ ├── segments\_1j
│ │ └── write.lock
│ ├── \_state
│ │ └── state-3.st
│ └── translog
│ ├── translog-25.ckp
│ ├── translog-25.tlog
│ ├── translog-26.ckp
│ ├── translog-26.tlog
│ ├── translog-27.ckp
│ ├── translog-27.tlog
│ ├── translog-28.ckp
│ ├── translog-28.tlog
│ ├── translog-29.ckp
│ ├── translog-29.tlog
│ ├── translog-30.ckp
│ ├── translog-30.tlog
│ ├── translog-31.tlog
│ └── translog.ckp
└── \_state
└── state-16.st
5 directories, 39 files
GET .kibana/config/\_search? shows me
{
"took": 0,
"timed\_out": false,
"\_shards": {
"total": 1,
"successful": 1,
"skipped": 0,
"failed": 0
},
"hits": {
"total": 0,
"max\_score": null,
"hits": []
}
}
```
Thank you for any assistance!
```
---
### Author:  [@Bargs](https://discuss.elastic.co/u/Bargs)
#### Post date: [September 25, 2018, 7:31pm UTC](https://discuss.elastic.co/t/default-index-pattern-is-missing-after-es-data-dir-been-moved/149837/2 "2018-09-25T19:31:37Z")
The default index pattern id is stored in the config document in the `.kibana` index. I see from the search results you posted that the config document is missing. It must be getting deleted periodically for some reason. I've only ever heard of issues with the config document when upgrading, and even then only at upgrade time, not on a periodic basis afterward. If you can't think of a reason why your environment might be causing this to happen I'd recommend creating an [issue on Github](https://github.com/elastic/kibana/issues/new?template=Bug_report.md).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 23, 2018, 7:31pm UTC](https://discuss.elastic.co/t/default-index-pattern-is-missing-after-es-data-dir-been-moved/149837/3 "2018-10-23T19:31:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.