I rebooted a
m5d.xlarge EC2 instance running Ubuntu 16.04.5 LTS (xenial) using
Upon reboot, various drive mounts defined in
/etc/fstab did not line up with the device assignments given to them initially.
This caused various services to fail, which rely upon the drive mount with the assigned name containing specific data associated with that name.
In this case,
/data needed to contain what is normally expected to be in
/data, and not some other drive mount, like
lsblk helped with manually redefining the
/etc/fstab file to reflect the new device assignments and bringing services back online.
Problem: My worry is that rebooting will randomly reassign device labels to drive mounts, and this problem could or will occur again when the server requires rebooting.
Question: How do I ensure that drive mounts and their respective device paths are preserved between reboots, without needing manual (re)intervention?