# Weird behavior after server reboot

**URL:** <https://discuss.elastic.co/t/weird-behavior-after-server-reboot/192765>\
**Category:** Elasticsearch\
**Created:** [July 29, 2019, 7:36pm UTC](https://discuss.elastic.co/t/weird-behavior-after-server-reboot/192765 "2019-07-29T19:36:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![leeyu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leeyu/32/48561_2.png) [@leeyu](https://discuss.elastic.co/u/leeyu)\
**Post date:** [July 29, 2019, 7:36pm UTC](https://discuss.elastic.co/t/weird-behavior-after-server-reboot/192765/1 "2019-07-29T19:36:11Z")

</div>

Hi all,

I am currently running elasticsearch 7.2 on an ubuntu server.

And I faced some weird behavior that I don't know what to do.

Here is some background  
I change the default data path to a newly added hard drive.  
And everything works fine.

And here is what happened.

old data: the old data located in the default data path before I change the path.  
new data: the data I modified after I change the path.  
updated data: the data I modified after the data disappear.

1. 

action: update from 7.1.1 to 7.2 & reboot  
event: the whole elaticsearh folder in the new hard drive is gone.  
data in the folder: nothing.

1. 

action: rsync the old data to the new folder  
data in the folder: old data.

1. 

action: update the data  
data in the folder: updated data

1. 

action: reboot  
event: updated data is gone and the data in the folder is back to old data  
data in the folder: old data

But after the I reboot a few times but there is no data lost again.

I am very confused so any suggestions will be welcomed.

---

<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:** [August 26, 2019, 7:36pm UTC](https://discuss.elastic.co/t/weird-behavior-after-server-reboot/192765/2 "2019-08-26T19:36:18Z")

</div>

Closed on August 26, 2019, 7:36pm UTC

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