I would be curious to see how the Disks app is mounting the volume.
This item looks related to your issue:
https://wiki.archlinux.org/title/NTFS-3G#Unsupported_reparse_point
Unsupported reparse point
When mounting an NTFS filesystem for Windows 10, and reading files or directories, you may
- see broken symbolic links to ‘unsupported reparse point’, or
- see the error message
cannot access some_file: Input/output error
(in this case you seeCould not load plugin /usr/lib64/ntfs-3g/ntfs-plugin-80000017.so: Success
in the journal).The reason for this are NTFS reparse points, used by Microsoft to extend the file system. NTFS-3G does not support some types of reparse points by default. NTFS-3G plugins may be used to provide compatibility with a part of the features defined by the following reparse points
- System compression: also known as “Compact OS”, this feature provides a stronger, executable-optimized type of conversion than NTFS’s old LZ77. Use the ntfs-3g-system-compression-gitAUR plugin for read-only support, or run
compact.exe /CompactOS:never
in Windows to disable.- Deduplicated files: this is a Windows Server 2012 feature providing block-level offline deduplication. Not yet packaged in AUR.
- OneDrive files: OneDrive files are stored as a special volume on Windows. The ntfs-3g-onedrive-binAUR plugin gives read-write access only for files marked “available locally”.
See this page for further details, and archive.org for downloads.
Setting that compact.exe /CompactOS:never
option in Windows seems like it might be worth a shot. Obviously the Disks app is using some other method; I’d still be curious to hear about that if you can find out what it is doing.