Hi @lmiki9 and welcome to the Manjaro community
This error usually indicates that the NTFS filesystem is damaged.
1. Fix the error using chkdsk
If an error exists on the NTFS filesystem, it should be corrected within a Windows environment; which can be achieved by launching an administrative command prompt and using the chkdsk command:
chkdsk /f x:
x: denotes the drive letter of the disk as it appears in Windows.
If a Windows installation is not available, chkdsk may also be run from a bootable Windows installer, or the downloadable Hiren’s BootCD PE; as one possible example.
2. Blacklist the ntfs3 kernel module, and use ntfs-3g (Optional)
Install ntfs-3g:
# Check whether the `ntfs-3g` package is installed
pacman -Qi ntfs-3g
# Install the `ntfs-3g` package, if needed
sudo pacman -S ntfs-3g
Blacklist ntfs3:
echo 'blacklist ntfs3' | sudo tee /etc/modprobe.d/disable-ntfs3.conf
- To reverse this decision at any time delete
disable-ntfs3.conf:
sudo rm /etc/modprobe.d/disable-ntfs3.conf
- The
ntfs-3g package may remain installed, if desired, as the ntfs3 kernel driver will take precedence if it is not blacklisted.
A note on blacklisting ntfs3 in favour of ntfs-3g:
The ntfs3 kernel driver can appear to fail if damage; or, rather, an indicator of damage; to an NTFS formatted drive is found (commonly referred to as a dirty bit).
ntfs-3g, however, ignores this dirty bit and mounts the NTFS partition, regardless.
Important to note is that the NTFS filesystem may still be damaged. ntfs-3g allows you to continue using your drive blissfully unaware that a problem still exists.
Blacklisting ntfs3 when it fails to mount an NTFS filesystem, and using ntfs-3g instead, can allow the partition to be mounted – but that’s all it does – any indicator of damage to the drive is completely ignored; and loss of data is possible.
Any actual damage to the NTFS filesystem still needs to be repaired using the methods previously outlined, in a Windows environment.
I hope this helps. Cheers.
