Hi
i installed AlmaLinux yesterday (AlmaLinux release 9.6 (Sage Margay)) and all went well. Rebooting was no issue. Yesterday I mounted my backup data nvme ssd on /srv/nvme and rebooted, but the process was interrupted with ‘You are in emergency mode’ warning and failed to continue.
I used nano and edited out the mounting of the nvme drive and the machine rebooted normally again.
Tried editing fstab to ‘/dev/nvme0n1p1’ format but that did the same.
After rebooting I can mount the drive with ‘Files’ and is accessible as normal.
The recommended way is to use the UUID to specify a filesystem as that should be persistent (and unique, except for software RAID mirrors, clones, multipaths, etc).
I do usually add
noauto,nofail,x-systemd.automount,x-systemd.idle-timeout=300
to options in fstab. That delays the mount to first access (after system is up).
The real question is why the mount fails?
Nope, your suggestion did not work.
After I reboot I do:
sudo mount UUID=3d6c41d6-1467-4238-a7ab-ef255eeedb3e /srv/nvme
and that works fine. Weird.
Installed ELRepo and latest kernel did not work either.
Installed Almalinux 10.0
Mounting of nvme ssd using fstab is back to normal.
1 Like