Hi Everyone,
For years, the fstab file I created for mounting my drives worked perfectly.
But recently I installed a new nvme drive for my system and had to make a new fstab.
Despite checking it carefully, my system failed to boot.
This has left me with two questions:
1. Automount or custom fstab?
Currently I am using Dolphin to mount each drive when I need it, but this is troublesome and interferes with software that requires constant access to drives.
- a) Can I simply use the “Removable Devices” feature in KDE and select “Automatically mount removable media that has never been mounted before” and use that instead of creating a custom fstab? I had a lot of trouble with that 5 years ago and am wondering if its a better option now than creating a custom fstab.
- b) would it be better to use system mounts as described here: [root tip] Use systemd to mount ANY device
2. Checking my custom fstab.
I have re-examined my fstab. Before I try to use it, I would like to ask if experienced users could check it for me. fstab settings
I have included the commands used for the each drive, and a question. .
The results from sudo blkid are:
~ lsblk -o NAME,SIZE,TYPE,PARTTYPENAME,FSTYPE,MOUNTPOINT PIPE|1 ✘
NAME SIZE TYPE PARTTYPENAME FSTYPE MOUNTPOINT
sda 3.6T disk
└─sda1 3.6T part Linux filesystem ext4 /run/media/ray/HSdisk2
sdb 465.8G disk
└─sdb1 465.8G part Linux filesystem ext4
sdc 465.8G disk
├─sdc2 127.4G part Linux filesystem ext4
└─sdc4 333G part Linux filesystem ext4
sdd 931.5G disk
└─sdd1 931.5G part Linux filesystem ext4 /run/media/ray/SSD2
sde 119.2G disk
└─sde1 119.2G part Linux ext4 /run/media/ray/SSD4
sdf 3.6T disk
└─sdf1 3.6T part Linux filesystem ext4 /run/media/ray/HSdisk6
sdg 3.6T disk ext4 /run/media/ray/HSdisk5
sdh 3.6T disk
├─sdh1 128M part Microsoft reserved
└─sdh2 3.6T part Linux filesystem ext4 /run/media/ray/HSdisk4
sdi 3.6T disk
├─sdi1 128M part Microsoft reserved
└─sdi2 3.6T part Linux filesystem ext4 /run/media/ray/HSdisk3
nvme0n1 1.9T disk
├─nvme0n1p1 512M part EFI System vfat /boot/efi
├─nvme0n1p2 15.6G part Linux swap swap [SWAP]
├─nvme0n1p3 146.5G part Linux filesystem ext4 /
└─nvme0n1p4 1.7T part Linux filesystem ext4 /home
The results from sblk -o NAME,SIZE,TYPE,PARTTYPENAME,FSTYPE,MOUNTPOINT are:
NAME SIZE TYPE PARTTYPENAME FSTYPE MOUNTPOINT
sda 3.6T disk
└─sda1 3.6T part Linux filesystem ext4 /run/media/ray/HSdisk2
sdb 465.8G disk
└─sdb1 465.8G part Linux filesystem ext4
sdc 465.8G disk
├─sdc2 127.4G part Linux filesystem ext4
└─sdc4 333G part Linux filesystem ext4
sdd 931.5G disk
└─sdd1 931.5G part Linux filesystem ext4 /run/media/ray/SSD2
sde 119.2G disk
└─sde1 119.2G part Linux ext4 /run/media/ray/SSD4
sdf 3.6T disk
└─sdf1 3.6T part Linux filesystem ext4 /run/media/ray/HSdisk6
sdg 3.6T disk ext4 /run/media/ray/HSdisk5
sdh 3.6T disk
├─sdh1 128M part Microsoft reserved
└─sdh2 3.6T part Linux filesystem ext4 /run/media/ray/HSdisk4
sdi 3.6T disk
├─sdi1 128M part Microsoft reserved
└─sdi2 3.6T part Linux filesystem ext4 /run/media/ray/HSdisk3
nvme0n1 1.9T disk
├─nvme0n1p1 512M part EFI System vfat /boot/efi
├─nvme0n1p2 15.6G part Linux swap swap [SWAP]
├─nvme0n1p3 146.5G part Linux filesystem ext4 /
└─nvme0n1p4 1.7T part Linux filesystem ext4 /home
My planned FSTAB is as follows. I have included questions
This EFI-boot partition on Team nvme0n1p1.
UUID=F8E0-2D49 /boot/efi vfat umask=0077 0 2
Why does MTAB use a very different set of operators for the drive?
/boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
The root partition on Team NVME0n1p3.
UUID=20f477fc-e057-42fd-ab1b-4e5609669e8f / ext4 defaults,noatime 0 1
Why does MTAB use
/dev/nvme0n1p3 / ext4 rw,noatime 0 0
The home partition on Team NVME0n1p4.
UUID=4c7b91e3-a4e6-4f07-b0d8-13dc016d00fb /home ext4 defaults,noatime 0 2
Why does MTAP use
/dev/nvme0n1p4 /home ext4 rw,noatime 0 0
The swap partition on NVME0n1p2
UUID=f048a1ef-72c0-4e9f-9b10-0ef7d1cedabe none swap sw 0 0
The following mounts are all correct as far as I can ascertain
#HSDisk2.
UUID=b19c4f75-7b75-4738-8af6-b4de9dc440f9 /mnt/HSdisk2 auto nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=HSdisk2 0 2
Why does MTAB use
/dev/sda1 /run/media/ray/HSdisk2 ext4 rw,nosuid,nodev,relatime,errors=remount-ro 0 0
#HSdisk3
UUID=d6ae7839-1577-44cb-8816-973cc26ffd23 /mnt/HSdisk3 auto nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=HSdisk3 0 2
#HSdisk4
UUID=e6d88df5-3c6e-4327-afd8-7a0985e1c7bc /mnt/HSdisk4 auto nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=HSdisk4 0 2
#HSdisk5
UUID=e25ad8e0-b018-4eb8-bb5a-a70d638fb34e /mnt/HSdisk5 auto nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=HSdisk5 0 2
#HSDisk6
UUID=5b2d0e1b-0032-4783-b562-dea888cd9460 /mnt/HSdisk6 auto nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=HSdisk6 0 2
#SSD2 Seagate 1tb
UUID=275329e6-8180-4242-ae3b-f2a1544ca163 /mnt/SSD2 auto nosuid,nodev,nofail,noatime,x-gvfs-show,x-gvfs-name=SSD2 0 2
But MTAB shows
SSD2 ext4 rw,nosuid,nodev,relatime,errors=remount-ro 0 0
#SSD3 Samsung 500gb
UUID=92342aa3-b638-4efe-9a2e-c041258344af /mnt/SSD3 auto nosuid,nodev,nofail,noatime,x-gvfs-show,x-gvfs-name=SSD3 0 2
I would greatly appreciate advice on figuring this out!
A final question: why is this still necessary in 2022 for systems with many drives? It seems like a very awkward process that would detract many people from switching to Linux. Surely there is an easier solution. Thanks to all who can provide assistance.