Hello,
I have 3 systems in my computer (Windows 10, Fedora 41 KDE and Kde Neon). Suddenly, since 2 days I can’t access to my Dropbox folder in my Windows partition from Fedora : the folder is represented as a link in Dolphin instead of a folder. When pointed with the mouse cursor, Dolphin displays some “unsupported reparse tag 0x9000f01a” text. All is well from Windows or KDE Neon… any idea ?
thanks !
Added f41
This can be caused by the ntfs-3g driver not supporting certain types of reparse points.
Under Windows, you can try recreating the Dropbox database, and check if this fixes the issue.
However, the issue could return, so you might want to consider using Dropbox under Linux as well. It requires double the storage, but might save you of headaches, while increasing performance by using a native filesystem.
Note: Windows 24H2 update will force your disk to be encrypted.
Apparently you can turn that off, but only after the install encrypted everything.
I’m still on 23H2 and waiting for this to hit my setup. This is from what I have read here and on the internet, no direct experience yet 
1 Like
Thanks for the reply. How can I get support for ntfs-3g ? I don’t find anything in their github.
Only on new installations and when doing the installation from an online activated Microsoft account. An existing Windows installation won’t suddenly get encrypted.
1 Like
I am not sure if ntfs-3g driver (see man ntfs-3g for details), or rather ntfs3, which is baked into the kernel, is being used by default when mounting NTFS partitions (at least when using the auto file system type).
You could try using one, and then the other file system type in /etc/fstab, and see if it makes any difference. Remember to use the nofail flag, in case something is wrong.
In case you choose not to reboot after each change in /etc/fstab, remember to run systemctl daemon-reload before each mount -a command.
Well i don’t know how to do thoses tests. It works juste fine in KDE Neon.
By testing I meant changing the file system type in your mount options. In case your partition is added to /etc/fstab, the entry for the NTFS partition might look similar to this:
/dev/disk/by-uuid/1234567890ABCDEF /mnt/win auto nosuid,nodev,nofail 0 0
The file system type comes right after the mount point, and it is auto in the example above. That should be replaced with ntfs-3g, or with ntfs3, respectively, then either run sudo systemctl daemon-reload and sudo mount -a afterwards, or reboot, and verify if the issue is still there. Again, remember to use the nofail flag.
If, on the other hand, the partition is not added to /etc/fstab, but rather mounted from the file manager, then it should be unmounted and remounted with mount -t option (see man mount for details).
The disk is mounted via Dolphin and the file system is “fuseblk”.
In KDE Neon, the file system is “ntfs3”…
Can you tell Dolphin what filesystem should it consider when mounting a device partition?
If not, then try umounting your Windows partition and then mount again with the command mount -t ntfs3 /your/device /your/mountpoint and check if it fixes the issue.
I could effectively mount the partition with your command (adding sudo in the beginning), thank you. I guess i should add it to /etc/fstab instead of reliying to the mount in Dolphin for this. I don’t know why it is different.
1 Like
Happy to hear it worked.
Yes, that would be the next step. Don’t forget the nofail flag.
Actually it is not ok, the partition is added read-only.
Try rebooting after making the changes in /etc/fstab.
Alternatively, you could also try replacing nosuid with user/group/mask permissions, e.g.:
uid=youruser,gid=yourgroup,umask=644,nodev,nofail