Unknown filesystem type ‘ntfs3’

Since latest stable update VeraCrypt complains:

unknown filesystem type ‘ntfs3’

Non‑VeraCrypt disks are not affected. VeraCrypt volumes with other filesystems work fine as well.
I am still running ntfs-3g. After the automatic switch to ntfs3 in 2023, I had some issues on two disks, so I blacklisted ntfs3.
ntfs-3g has worked flawlessly for many years on a daily basis. I am aware of the “dirty flag” thing with ntfs-3g.

Because VeraCrypt and ntfs‑3g are not updated, what is causing the “unknown filesystem type ‘ntfs3’” error ?

$ mount.ntfs --version  
ntfs-3g 2022.10.3 external FUSE 29
$ ls /sbin/mount.ntfs* -l 
/sbin/mount.ntfs -> /usr/bin/ntfs-3g  
/sbin/mount.ntfs-3g -> /usr/bin/ntfs-3g

In one case I managed to mount VeraCrypt with ntfs-3g.

$ veracrypt --filesystem=none ...
$ sudo mount -t ntfs-3g /dev/loop0 ...
$ udisksctl mount -b /dev/sda

When mounting an NTFS volume it shows up as type fuseblk.

$ udisksctl mount -t ntfs-3g -b /dev/sda

Throws :

Error mounting /dev/sda: GDBus.Error:org.freedesktop.UDisks2.Error.OptionNotPermitted: Requested filesystem type ntfs-3g is neither well-known nor  
in /proc/filesystems nor in /etc/filesystems
$ cat /proc/filesystems 

Does not show any ntfs*.

ntfs‑3g does work, but in some cases it is no longer detected since the latest update.

I am using kernel 6.12.

I am aware that using ntfs is something one should avoid, but in my case it’s something i really depend on for compatibility reasons.

Thank you for any hints

Try referencing the filesystem type (ntfs) rather than the driver name; example:

sudo mount -t ntfs /dev/sdXY

And remember, we typically mount a partition (/dev/sdXY) with a filesystem, rather than the disk (/dev/sdX) itself.

2 Likes

ah. ok. its “ntfs” not “ntfs-3g”

udisksctl mount -t ntfs -b /dev/sda1
veracrypt --filesystem=ntfs /dev/sda1 /media/veracrypt1

thank you very much !!!

any idea what is causing the unknown filesystem type 'ntfs3'
without --filesystem=ntfs ?

ntfs3 is not a filesystem type, so naturally it will be “unknown” – I imagine you still have it incorrectly use elsewhere; check your /etc/fstab, for example; you might also try again after a reboot.


I have also moved your posts to a dedicated topic as your issue seemingly has nothing to do with the Update.

Regards.

2 Likes

No, sorry – that was a misunderstanding.

ntfs3 has been black‑listed for years, so my system uses only ntfs-3g.
ntfs filesystems were automatically detected when mounting via udisksctl and VeraCrypt.

After the latest stable update, VeraCrypt no longer recognizes ntfs-3g !
It complains about an unknown filesystem type 'ntfs3'.
I have to point it manually.

So something changed in the last update.

There is nothing about ntfs, ntfs3, ntfs-3g in my fstab.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.