I just installed the new ISO, and I can’t access the ntfs Storage partition w/o entering password. I remember this was an issue with my original install, but I thought it was supposed to be fixed on this release.
So, how can I change the permissions so I don’t have to enter a password every time?
Just be cautious that adding the ntfs partition to fstab may break your boot process!
I have the same issue and tried adding the partition in fstab first. Unfortunately this led to the OS booting into rescue mode. I guess one somehow needs to make sure that the ntfs driver is available during boot time, change the grub loader command? Haven’t had time to look into this yet though.
I agree, main reason for me to mount the partition was to get rid of the message showing up after every boot which @keith mentioned in his opening thread.
I would much rather avoid getting that popup instead of auto-mounting if that’s possible.
Hm, I don’t want to hijack this thread but I realize my response was misleading. Really all I want is for the OS to not bother mounting this partition.
It’s dormant, a backup just in case, and I haven’t booted Win10 in months,.
So it’s not the popup itself which is annoying, a different popup wouldn’t help, but rather the fact that I keep on getting asked to unlock this partition.
And right now the only way I figured out to get rid of this question was to give the OS what it wants by auto mounting followed by hiding the drive in Dolphin.
Maybe removing the ntrfs-3g driver would quiet things, but every now and then I need to work with ntfs formated USB drives, so not an option either.
If you use the noauto option in fstab you will not be asked for a password and your partition/drive will also not be mounted.
It can then be accessed in Thunar or other file managers simply by clicking on it. Until then your ntfs-drive will not be actually mounted!
Unfortunately no, this was one of the things I tried fairly early on and just tried again. The moment I add noauto to the fstab entry, the “authentication required” popup shows up after the system is up and running.
No entry in fstab -> authentication request shows up
fstab entry with noauto -> authentication request shows up
fstab entry without noauto -> All quiet, partition is mounted
My initial suspicion was that maybe Plasma or Dolphin somehow remember drives which were open at some stage and keep on trying to reopen upon launch, but I couldn’t figure out where such a thing may be captured.
But like I said, I don’t want to hijack this thread, I have a solution, albeit not ideal because what’s not used should not be mounted, but it’s sufficient for me.
(of course you’d have to adjust the mount point, uuid, uid and gid for your user)
If this doesn’t work then there is definitely something off about your system. All my systems (different Arch, Debian, Gentoo distros) all honor noauto if ntfs partitions could potentially be accessed. I have actually never encountered and therefore thought about the problem you’re having; it just works.
(Edit: Wrote the above before doing a quick search!)
Your suspicion about some process (KDE/Dolphin?) trying to (re)open the drive may be correct.
Made the change, but still get the “Authentication required”!
It seems that the “user” option is not supported out of the box because when I try to mount as user manually I get the below:
Unprivileged user can not mount NTFS block devices using the external FUSE
library. Either mount the volume as root, or rebuild NTFS-3G with integrated
FUSE support and make it setuid root. Please see more information at
I had a look at /usr/share/polkit1/actions but not sure what to do with the list. I’ll read up some more on this subject but in the meantime I will just mount as as root in fstab (default 0 0) and be done with it.
ntfs-3g-fuse AUR package description: Stable read and write NTFS driver and ntfsprogs. This package will allow normal users to mount NTFS Volumes.
#1 You could try to nstall ntfs-3g-fuse from AUR and maybe also make it setuid root with sudo chmod +s /bin/ntfs-3g
(I think it will still be ‘ntfs-3g’ even after installing ntfs-3g-fuse, but I could be wrong.)