You are not logged in.
Hi
I have WD an external Tb drive and this NTFS drive cannot be mounted in KDE Plasma. Howevery, I am able mount it in the terminal using the mount command. But when I use udiskctl, it fails:
sudo udisksctl mount -b /dev/sdb1
Error mounting /dev/sdb1: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sdb1 at /run/media/root/My Passport: fsconfig() failed: No such file or directoryIts the same error that KDE reported. I have ntfs-3g and udisks2 installed in my system. In addition, I tried to mount two USB sticks the first one contain the Arch Image and the other is formatted with NTFS and KDE was able to mount them.
Any comment or suggestion is welcome.
Thanks in advance
Last edited by XDimensioN0 (2025-08-25 12:53:27)
Offline
plasma/dolphin will use udisks and udisks default to ntfs3, not ntfs-3g, see https://wiki.archlinux.org/title/Udisks … nt_failing (the assertions about the defaults there are dated, look at the actual example config where you can find the module order)
HOWEVER: the cause for this is most likely because ntfs-3g is way more lenient when it comes to inconsistent filesystems.
You should sanitize this, https://wiki.archlinux.org/title/NTFS-3 … ilesystems and in doubt make sure that this isn't because of a dual boot condition(see 3rd link below) and otherwise always make sure to properly unmount ("safe remove" or so on windows) drives before powering them down.
Offline
I made a copy of udisks2.conf.example and uncommented the requested lines. But I still does not worked. In addition, I checked the log of udisks2 service and it reported this error:
Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdb': Unexpected sense data returned:
0000: f0 00 01 00 00 00 00 0a 00 00 00 00 00 1d 00 00 ................Offline
Uncommented what requested lines?
The defaults will not change just because you uncomment the default value.
What does the file look like?
Also I'd stress that
HOWEVER: the cause for this is most likely because ntfs-3g is way more lenient when it comes to inconsistent filesystems.
You should sanitize this, https://wiki.archlinux.org/title/NTFS-3 … ilesystems and in doubt make sure that this isn't because of a dual boot condition(see 3rd link below) and otherwise always make sure to properly unmount ("safe remove" or so on windows) drives before powering them down.
Changing the udisks default from ntfs3 to ntfs-3g will not make anything "work", it'll just allow you to gloss you over (most likely) the dirty bit being set.
Offline
I initially had these lines:
ntfs:ntfs3_defaults=uid=$UID,gid=$GID
ntfs:ntfs3_allow=uid=$UID,gid=$GID,umask,dmask,fmask,iocharset,discard,nodiscard,sparse,nosparse,hidden,nohidden,sys_immutable,nosys_immutable,showmeta,noshowmeta,prealloc,noprealloc,hide_dot_files,nohide_dot_files,windows_names,nocase,case
ntfs_drivers=ntfsAfter checking the file again, I realised that I needed to uncomment the
[defaults]line. So I did and now it works.
Offline
Ok, but I'll one last time stress that this is actually not the correctmostbestway to address this:
Also I'd stress that
seth wrote:HOWEVER: the cause for this is most likely because ntfs-3g is way more lenient when it comes to inconsistent filesystems.
You should sanitize this, https://wiki.archlinux.org/title/NTFS-3 … ilesystems and in doubt make sure that this isn't because of a dual boot condition(see 3rd link below) and otherwise always make sure to properly unmount ("safe remove" or so on windows) drives before powering them down.Changing the udisks default from ntfs3 to ntfs-3g will not make anything "work", it'll just allow you to gloss you over (most likely) the dirty bit being set.
Offline