Artix Linux Forum

I did manage to get them working at one point, but when I reformatted a drive due to what I think was a filesystem error it stopped working.

       nofail
           Do not report errors for this device if it does not exist.

Pretty sure if you reformat ntfs the UUID will change.

Other than that turn on verbose logging in
/etc/rc.conf

Code: [Select]

rc_logger="YES"
rc_verbose="YES"

And check the log at
/var/log/rc.log
after booting

and check the output of dmesg maybe.

Do they mount if you issue

Code: [Select]

sudo mount --all

?

It is generally a bad idea to automount external (removable) hard drives, to a subdirectory of /home nonetheless. Just use the mount function of your DE, or, if you aren't using a DE, mount them manually as root when you need them.

Furthermore, if an ordinary user tries to mount an NTFS filesystem, the attempt will fail with the following error message:

Code: [Select]

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
http://tuxera.com/community/ntfs-3g-faq/#unprivileged

So the user option has no effect.

Why are you using nofail? It does the following:Reporting errors is very useful for diagnosing issues like the one from this thread.

Other than that, one of the main functions of /etc/fstab is exactly automounting. All filesystems which don't have the noauto option specified should be automounted, unless there were errors.

So I turned off

Code: [Select]

nofail

, and it seems that the system cannot find the devices via their UUIDS on boot? However running

Code: [Select]

mount -a

works after boot.

Most likely your initramfs isn't configured to load ntfs module, so it can't "see" the ntfs partitions at that stage of the boot process. Try including ntfs module in mkinitcpio.conf (https://wiki.archlinux.org/title/Mkinitcpio#Configuration) and rerunning mkinitcpio.

Module name is ntfs. Refer to the documentation for mkinitcpio (https://wiki.archlinux.org/title/Mkinitcpio).

That's interesting. When I add that to /etc/mkinitcpio.conf it gives an error message. Something about not finding the module or something. And when I run

Code: [Select]

modprobe -c | vim

and search for "ntfs," the only reference is to "fs_ntfs3" and what I assume is the alias of it, "ntfs3."

Note: it works fine when I edit in "ntfs3."

By "works fine" I mean that mkinitcpio works, but when I reboot the drives show an error and I can't even enter my window manager.

Code: [Select]

UUID="3F8573B3660DF881"             /home/al/mount/TRANSCEND1       ntfs    auto,uid=1000,gid=998,rw,relatime,nofail,user,exec,umask=000 0
  2

UUID="42C508CF71F9C321"         /home/al/mount/Toshiba          ntfs    auto,uid=1000,gid=998,rw,relatime,nofail,user,exec,umask=000 0      2

For ntfs3, you also need to change /etc/fstab entries so the file type is ntfs3 instead of just ntfs as above.

https://wiki.archlinux.org/title/NTFS#Explicit_file_system_type_required_to_mount

That page lists some additional troubleshooting steps if that still doesn't work.

Okay. Weird thing happened. It worked after running "sudo mkinitcpio -P" and "sudo update-grub." Gonna reboot to test if the fix is persistent.

Both troubleshooting steps don't seem to apply,

..., but I'm sure it'll work if I configure it again (which I won't as while it may work properly I have discovered it could lead to potential issues.)