I have several partitions that I do not want mounted at boot time.
The fstab entry is of the format
UUID=… uuidvalue /scratch1 ext4 defaults,noatime,noauto,user 0 0
UUID=… uuidvalue /backup ext4 defaults,noatime,noauto,user 0 0
Though it says noauto,user the partitions get mounted at boot.
I am wondering if anyone else experiences this bug,
My work around is to just manually umount the two partitions at login time. I should not have to do that.
it will be mounted if possible on boot , before login
if you want to mount theses UUID on login ,
you should use a condition systemd-unit on login for that ( and then UUID are /run/media/UUID )
Disk device recognition Manjaro uses udev (see Arch Wiki) to load devices at boot time. The loading of devices is arbitrary and therefore you cannot predict which device will be available at a given path. But static device names do exist and you can...
Reading time: 3 mins 🕑
Likes: 7 ❤
Entries with noauto, mean,
do not mount the partition at boot time.
entries with user, mean that without needing root level access, a user can mount and unmount the partition.
The reason the partitions are not mounted is for safety. One mounts a backup for a restore from backup or to add to the backups.
One does not want the backups mounted all the time.
do not forget that systemd is running on boot also for fsck , mount partitions and so
Works properly with other distros. They are not mounted at boot time and are not checked at boot time.
I believe that with the mount command, the disk partition is checked (fsck) for consistency.
Just out of curiosity, shouldn’t fsck be run prior to mounting a partition?
Just in case this is a systemd-related issue, it might be worth trying
UUID=… uuidvalue /scratch1 ext4 noatime,noauto,x-systemd.automount 0 0
and see if that helps.