I'm using CachyOS (based on Arch), and while I can mount my NTFS drives through the Dolphin GUI without any issues, the problem is that I have to mount them manually every time I boot my computer. I can't use Dolphin's auto-mounting feature because it prompts for my admin password at every startup due to my login restrictions. I've tried using the fstab command to auto-mount the drives, and while this approach works to some extent, I'm facing issues with Steam games not launching when the drive is mounted this way. Is there something different that Dolphin does when it mounts drives? Here's the current fstab line I'm using:
UUID=XXXXXXXX /run/media/XXX/Samsung\040990\040pro\040PCIE\0404 ntfs-3g defaults,nofail 0 2
If anyone has suggestions or insights into what I might be missing, I'd appreciate the help!
2 Answers
After you mount with Dolphin, try checking the output of the `mount` command in the terminal. It will show you any special mount options being applied. You can use those to modify your `/etc/fstab` entry as the syntax closely aligns with the output from the `mount` command.
Your observation is spot on! The proper options really make a difference. Once I changed my fstab line to:
/run/media/XXX/Samsung\040990\040pro\040PCIE\0404 ntfs3 rw,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2 0 2
Everything started working perfectly. I can now write to the drive and launch my games without a hitch!
Just a heads up, you shouldn't use `/run/media/...` in your fstab. Instead, you should pick a static path, like `/media/yourchoice`, which is more reliable. Having it dynamic can lead to issues on reboot.
Why is that? I copied the path from Dolphin because it worked before. I'd prefer to keep it as is since other apps like Steam are set up with that location. But I did manage to solve some issues by tweaking the fstab options, as mentioned in my replies.
Thanks for the tip! From the mount command, I found out the following:
/run/media/XXX/Samsung 990 pro PCIE 4 type ntfs3 (rw,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2)
I noticed that it’s using ntfs3 instead of ntfs-3g. I had switched to ntfs-3g because I couldn't write to some files with ntfs3. I'll give the options you mentioned a shot with ntfs3 next.