How can I force the usage of the new Kernel 7.1 NTFS driver on /etc/fstab?

General Help
1

Hi everyone!
I've been using ZorinOS 18.1 for the last couple of months, and I'm loving it!

I updated the kernel to 7.1.3 to use the new NTFS driver. And after updating it and loading the module, I was able to mount a partition using the command:

mount -i -t ntfs

But so far, everything I tried to automount the disks using /etc/fstab or Disk Utility keeps using the fuseblk driver.
Here is one default mounting point for my NTFS drives:

/dev/disk/by-uuid/D684897E848961BB /mnt/D684897E848961BB auto nosuid,nodev,nofail,x-gvfs-show 0 0

And here is the mounting point I'm changing:

/dev/disk/by-uuid/4CF24DE8F24DD6BC /mnt/4CF24DE8F24DD6BC ntfs defaults,uid=1000,gid=1000,dmask=022,fmask=133,windows_names,nofail\040\0400\040\0400,x-gvfs-show 0 0

Should I disable the fuseblk module? Or what should I do to have the system automatically use the new driver?
Thanks!

2

I found this maybe helpful

3

Hey, thanks for the info!

Yes, I also found this info and used it to mount the NTFS driver manually using the new driver:

# cat /proc/mounts | grep ntfs
/dev/sda2 /mnt/4CF24DE8F24DD6BC ntfs rw,relatime,umask=00,iocharset=utf8,case_sensitive,errors=continue,mft_zone_multiplier=1 0 0

but when mounted by /etc/fstab, it uses FUSEBLK

# cat /proc/mounts | grep fuse
fusectl /sys/fs/fuse/connections fusectl rw,nosuid,nodev,noexec,relatime 0 0
/dev/nvme0n1p3 /mnt/6450535C505333D0 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/sdc2 /mnt/B0E86ADDE86AA0F8 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0

Thanks

4

Hi and welcome.

I think rhe issue is that it will only work with Ubuntu 26.04 as Zorin is based on 24.04 which uses ntfs-3g, and your discovery of fuseblk indicates you cannot use ntfs3 which no longer requires 'fuse' to run from what I have read elsewhere.

5

Yes @swarfendor437 Ubuntu 26.04 does use that but of course i have all my drives setup for EXT4 as it works much better with linux as ntfs is a microslope creation for use with thier systems I no longer use thier stuff but i figured I would share what i found on the subject since i do tend to run Ubuntu 26.04 half the month doing zorin for one half then back to ubuntu for one half just seeing whats on the horizen for zorin 19 possibly?

6

Hey, thanks for your answer!
As I informed you before, I was able to use the NTFS driver to manually mount manually. It isn't working when the mounting points are done on reboot or "mount -a".
So my main question is: what do I need to do to get automount to use the NTFS driver?

Thanks

7

Np...if you can do me a favor and mark my answer as a solution so other dont think this needs help.... :grin:

8

But I still need help.
What do I need to do to have the new kernel 7.1 NTFS driver used when drivers are mounted by /etc/fstab ?
Is it impossible to get this result at this moment?
Thanks!

9

I suspect you can't because ntfs3 will be built for Ubuntu 26.04, more importantly, kernel 7.x upwards. Your version of Zorin is on 6.x and so will be using 'fuse' in order for ntfs-3g to work.

10

Oh i misunderstood..thought your got it working...ok

11

Hey, @swarfendor437
I'm on Zorin 18.1 core, and I updated the kernel to 7.1.3

12

OK, but you are still on Ubuntu 24.04, and this might be the issue. Let me check.

13

I decided to use Brave A.I. search result for speed:

" The inability to mount NTFS3 in Ubuntu 24.04 is typically caused by either the volume being marked as "dirty" (often due to Windows Fast Startup or hibernation) or a conflict with the older ntfs-3g driver.

1. Clear the Dirty Flag The ntfs3 kernel driver refuses to mount partitions with the dirty bit set. You must clear this flag manually before the fstab entry will work.

  • Run sudo ntfsfix -d /dev/sdXY (replace sdXY with your partition, e.g., sda1 ).
  • Alternatively, boot into Windows and disable Fast Startup in Power Options, then perform a full shutdown.

2. Verify Driver Configuration Ensure your /etc/fstab explicitly calls the correct driver type. In Ubuntu 24.04 , the ntfs type in fstab may default to the deprecated read-only driver or ntfs-3g depending on the system state.

  • Use ntfs3 as the filesystem type for the native kernel driver.
  • Add the nofail option to prevent boot failures if the drive is disconnected.

Recommended /etc/fstab Entry:

UUID=YOUR-UUID-HERE  /mount/point  ntfs3  defaults,uid=1000,gid=1000,iocharset=utf8,nofail  0  0

3. Handle Driver Conflicts If issues persist, there may be a conflict between ntfs3 and ntfs-3g .

  • Check dmesg | grep ntfs for specific error messages.
  • Some users report success by blacklisting the ntfs3 module if the native driver is buggy in their specific kernel version, reverting to ntfs-3g (FUSE-based) by using ntfs-3g as the filesystem type in fstab.
  • Ensure the ntfs-3g package is installed if you choose to fall back to the FUSE driver.

AI-generated answer. Please verify critical facts."

14

Thanks for all the info @swarfendor437

Just to be perfectly clear, I'm on Zorin Core 18.1 using Kernel 7.1.3, and I am able to mount all my NTFS storage.

What I want, and this was the reason for me to upgrade to the new kernel, is to mount using the new NTFS driver.

On my /etc/fstab I have:

/dev/disk/by-uuid/4CF24DE8F24DD6BC /mnt/4CF24DE8F24DD6BC ntfs defaults,uid=1000,gid=1000,dmask=022,fmask=133,windows_names,nofail,exec,x-gvfs-show 0 0

But, checking my /proc/mounts I see:

dev/sda2 /mnt/4CF24DE8F24DD6BC fuseblk rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0

If I umount it and mount with the command:

mount -i -t ntfs /dev/sda2 /mnt/4CF24DE8F24DD6BC

It then shows:

/dev/sda2 /mnt/4CF24DE8F24DD6BC ntfs rw,relatime,umask=00,iocharset=utf8,case_sensitive,errors=continue,mft_zone_multiplier=1 0 0

Thanks!

1 Like