# Elasticsearch not showing indexes after VM update **URL:** \ **Category:** Elasticsearch\ **Created:** [February 10, 2021, 7:05pm UTC](https://discuss.elastic.co/t/elasticsearch-not-showing-indexes-after-vm-update/263925 "2021-02-10T19:05:40Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Giovanni\_Ferrari](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/giovanni_ferrari/32/83741_2.png) [@Giovanni\_Ferrari](https://discuss.elastic.co/u/Giovanni_Ferrari)\ **Post date:** [February 10, 2021, 7:05pm UTC](https://discuss.elastic.co/t/elasticsearch-not-showing-indexes-after-vm-update/263925/1 "2021-02-10T19:05:40Z")
Hello everyone! I installed a cluster composed by a single node in a VM, with a disk attached to it and used for data storage (path.data configuration). The problem I'm facing is that in case the VM is destroyed and rebuilt all the indexes are not visible anymore from kibana (while they are still present on the disk). Do you have any idea why this would happen and how I could handle it? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [February 14, 2021, 11:42pm UTC](https://discuss.elastic.co/t/elasticsearch-not-showing-indexes-after-vm-update/263925/2 "2021-02-14T23:42:33Z")
> [@Giovanni\_Ferrari](#): > > in case the VM is destroyed Can you elaborate more on what you mean by this? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 14, 2021, 11:42pm UTC](https://discuss.elastic.co/t/elasticsearch-not-showing-indexes-after-vm-update/263925/3 "2021-03-14T23:42:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.