(2024-05-22, 05:58 PM)TheDreadPirate Wrote: Reboot. It will apply the new mount parameters during boot up.
Yea I did that, and this was a result after sudo mount -a
ntfs-3g-mount: failed to access mountpoint /media/mutka/Exos1: No such file or directory
mount: /media/mutka/Seagatetwo: mount point does not exist.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=593b83f6-03bf-4388-bef1-424af1e22c05 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=8248-C7D1 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
/dev/sda2 /media/mutka/Exos1 ntfs defaults 0 0
/dev/sdb2 /media/mutka/Seagatetwo exfat defaults 0 0
/dev/sdc2 /media/mutka/seagate ntfs defaults 0 0
this is what the fstab file looks like. does UUID things interfere? Tried also with putting hash infront of them