You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was of the idea that the EFS volume would be created once and it will get attached to any created EC2 instance, keeping all data intact in case of EC2 instance termination, but this did not happen.
The screenshot of my Auto Scaling group tells the story, the first run was on 10/16 and the instances got terminated at 10/26 and a new one was delployed.
Now if we see the current volumes created we see the the only one created at 10/26 (same date as the new instance deployment
So it seems that the volume is getting recreated as well.
Sadly I think I lost the old world we were playing, but hopefully someone knows how to fix it so this doesn't happen to other players
The text was updated successfully, but these errors were encountered:
hey @wsetws, your world should be located in /opt/minecraft which should be mounted via EFS df -h should show an "fs-xxxxxx.efs.ap-xxx.amazonaws.com:/" mounted as "/opt/minecraft"
I was of the idea that the EFS volume would be created once and it will get attached to any created EC2 instance, keeping all data intact in case of EC2 instance termination, but this did not happen.
The screenshot of my Auto Scaling group tells the story, the first run was on 10/16 and the instances got terminated at 10/26 and a new one was delployed.
Now if we see the current volumes created we see the the only one created at 10/26 (same date as the new instance deployment
So it seems that the volume is getting recreated as well.
Sadly I think I lost the old world we were playing, but hopefully someone knows how to fix it so this doesn't happen to other players
The text was updated successfully, but these errors were encountered: