You are not logged in.
Pages: 1
I want to have my NTFS drives mounted without requesting password every reboot, and I've tried all I could find. Mounting in fstab, gnome-disks auto-mount, polkit. Nothing seems to work. I have ntfs-3g and fuse installed.
If I do
sudo mount /dev/sda2 /mnt/mountDirI get
mount: /mnt/mountDir: unknown filesystem type 'ntfs'.Same thing happens with fstab of which my lines are:
UUID=XXXXXXX /run/media/BackUp ntfs uid=1000,gid=1000,dmask=022,fmask=133 0 0
UUID=YYYYYYY /run/media/GamesSSD ntfs uid=1000,gid=1000,dmask=022,fmask=133 0 0And when I do that it basically fails on boot and tells me to check systemctl status run-media-BackUp.mount which gives the above error.
If I do this:
https://cdn.imgchest.com/files/84apcxqzme4.png
then when I reboot and go to file manager and click the disk it will ask for password as usual but gives this error:
https://cdn.imgchest.com/files/l4necaberr4.png
I also tried the first answer here:
https://askubuntu.com/questions/1029399 … partitions
Had no effect whatsoever.
I've no idea what else to do.
Last edited by lpv (2024-02-12 09:20:26)
Offline
Request ntfs-3g explicitly or use ntfs3 for the in-kernel driver instead of ntfs-3g
Offline
Request ntfs-3g explicitly or use ntfs3 for the in-kernel driver instead of ntfs-3g
Do you mean this:
If you want to use ntfs3 as the default driver for ntfs partitions, such udev rule does the trick:
/etc/udev/rules.d/ntfs3_by_default.rules
SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="ntfs", ENV{ID_FS_TYPE}="ntfs3"I forgot to mention I also tried that to no avail.
Offline
Yes and no, apparently this rule isn't read correctly, so just explicitly use ntfs3 in your fstab instead of ntfs
Offline
Yes and no, apparently this rule isn't read correctly, so just explicitly use ntfs3 in your fstab instead of ntfs
Wow you guys are geniuses. I did not expect to solve this one so easily after trying "everything". Thank you so much!
Offline
You'd probably still want to find out why your ntfs symlink is broken, what's your output for
stat /bin/mount.ntfs
pacman -Qkk ntfs-3gOffline
You'd probably still want to find out why your ntfs symlink is broken, what's your output for
stat /bin/mount.ntfs pacman -Qkk ntfs-3g
I'm embarassed. ntfs-3g was not installed. I don't know how I did that as it was the first thing I tried. I swear I remember installing it, obviously since I tried everything I could find. My apologies..
Last edited by lpv (2024-02-11 20:06:43)
Offline
Aside from the solution - auto-mounting something called "backup" sounds like a bad idea!
Imagine some bad code runs a rm -rf / as root - this will also clean your backup as its mounted.
You should rethink about having some fallback always mounted write-access. At least decrease the risk by mout read-only.
Offline
Aside from the solution - auto-mounting something called "backup" sounds like a bad idea!
Imagine some bad code runs a rm -rf / as root - this will also clean your backup as its mounted.
You should rethink about having some fallback always mounted write-access. At least decrease the risk by mout read-only.
I had another main disk and this backup drive was it's backup but the main was faulty so I put it aside. I need to buy a new disk. However even in worst-case someone rm -rf's my disk probly I'll probably only be missing some games given I have the old faulty disk. Yeh faulty doesn't sound too good but it works.
Thanks for the heads up!
Last edited by lpv (2024-02-12 08:20:03)
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Pages: 1