SUMMARY If ntfs-3g is not installed, and Linux 5.15 ntfs3 (the new Paragon NTFS driver) is present, Dolphin tries to mount NTFS partition, but mounts with unknown to ntfs3 parameter - 'windows_names' STEPS TO REPRODUCE 1. Remove ntfs-3g FUSE driver 2. Load ntfs3 module from Linux 5.15+ 3. Mount NTFS formatted partition via Dolphin OBSERVED RESULT Mount fails with: An error occurred while accessing 'Home', the system responded: The requested operation has failed: Error mounting /dev/sda4 at /run/media/linux/Data: Unknown error when mounting /dev/sda4 EXPECTED RESULT Mount partition and access like any other partition. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux w/ Linux 5.15.1 from sources, and Linux 5.15.2 from repo KDE Plasma Version: 5.23.3-1 KDE Frameworks Version: 5.87.0-1 Qt Version: 5.15.2+kde+r254-1 Dolphin Version: 21.08.3-1 ADDITIONAL INFORMATION It appears that the new NTFS driver does not support 'windows_names' parameter. Dolphin tries to mount with it. It appears that the new driver has no such option and fails to mount. From dmesg after attempt to mount any NTFS partition via Dolphin: [ 194.448588] ntfs3: Unknown parameter 'windows_names'
Also having this issue, hopefully it gets resolved soon.
(Most of this info, the fix included, is courtesy of the nice people discussing it at https://github.com/storaged-project/udisks/pull/917) This isn't a KDE bug but a udisks2/libmount one and ultimately a ntfs3 one. It does indeed happen because the new ntfs3 driver does not support the 'windows_names' flag, for the time being at least (ntfs3 upstream have commented that it's a good and necessary flag for dual-booting with Windows, so in the near future they'll probably be looking into implementing it), but the flag is passed by default when trying to mount the filesystem via udisks2 (as Dolphin does in the background), so it will fail to mount. If you have udisks2 2.9.4+, as a temporary fix you can create the file /etc/udisks2/mount_options.conf with the following contents: [defaults] ntfs_defaults=uid=$UID,gid=$GID ...and you'll be set. For udisks 2.9.3 and earlier, because it lacks the necessary logic to recognize and use the ntfs3 driver in the first place, you apparently can "patch" the support in by also creating the file /etc/udev/rules.d/ntfs3.rules with the following contents: SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="ntfs", ENV{ID_FS_TYPE}="ntfs3" In this case, /etc/udisks2/mount_options.conf should also include some extra stuff added with udisks2 2.9.4 for ntfs3 to work properly: [defaults] ntfs_defaults=uid=$UID,gid=$GID ntfs_allow=uid=$UID,gid=$GID,umask,dmask,fmask,locale,norecover,ignore_case,windows_names,compression,nocompression,big_writes,nls,nohidden,sys_immutable,sparse,showmeta,prealloc Do keep in mind that these fixes will force-disable the 'windows_names' flag, which has the potential to cause you some pain if you dual-boot with Windows and mount the NTFS partitions. Anyway, hopefully this mess will be resolved upstream soon, by either ntfs3 implementing 'windows_names' or at least udisks2 (or even better libmount) implementing these overrides by default.
I can't mount a usb flash drive with ntfs3 kernel driver, Dolphin says: "An error occurred while accessing '28,9 GiB Removable Media', the system responded: The requested operation has failed: Error mounting /dev/sdd1 at /media/111D369D6BDE9734: Filesystem type ntfs3,ntfs not configured in kernel." Operating System: Arch Linux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.11-zen1-1-zen (64-bit) Graphics Platform: Wayland
I, too, have this issue; can't mount ntfs partition in dolphin. It does mount just fine via terminal, though. Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: X11
This issue is fixed on my end. Recently mounted two ntfs3 drives from Dolphin with no problem. Operating System: NixOS 23.11 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.9 Kernel Version: 6.4.4-cachyos (64-bit)
Nobody is replying "not fixed for me", so I think this can be closed. (Especially since this was an issue on udisks end)
Not fixed for me.
Just hit the same thing with Kubuntu 24.04 and the udisks workaround does not help, even after restarting the udisks2 systemd service. Turns out the underlying reason was that the partition was marked dirty (seen in dmesg), so running `ntfsfix -d` on it made it all dandy again.