You are not logged in.
Dear friends
I have already posted this topic in the forum of archlinux.de, but could not get my problem solved. Perhaps there's a better chance in this forum due to a larger member base? I hope you don't mind my posting the same topic in a different Archlinx forum.
Situation:
Dual boot with Windows 10. Archlinux kernel is 5.17.9-arch1-1.
On the internal SSD, there's a separate NTFS data partition, shared between Windows 10 and Archlinux. Partition format: NTFS version 3.1, LFS version 2.0.
Quick start is deactivated in Windows 10
Entry for this partion in /etc/fstab:
UUID=UUID_OF_PARTITON /media/daten ntfs3 rw,noatime 0 2
Partition mounts ok, reading and writing works for all users.
BUT:
Problem:
findmnt --verify /media/daten
results in
[E] ntfs3 does not match with on-disk ntfs
Observations:
Changing the partition type of the NTFS partition from "Microsoft basic data" to "Linux filesystem" results in no error message with findmnt --verify. But the partition does not show up in the Windows 10 file explorer if the partition type is "Linux filesystem".
Therefore, changing the partition type is no solution for me.
When mounting the partition manually with
mount -t ntfs3 -o rw,noatime UUID=UUID_OF_PARTITON /media/daten
findmnt --verify /media/daten
results in
Success, no errors or warnings detected
Questions:
What do I have to enter in /etc/fstab in order to avoid the error message?
Or can the error message be safely ignored, without being confronted with an increased risk of data corruption or data loss?
I have searched for this topic in the web, but without success. Would it make sense posting a mail directly to the address mentioned in https://www.kernel.org/doc/html/latest/ … ntfs3.html?
Many thanks!
Rolf
Last edited by rfab (2022-05-23 12:13:04)
Offline
The first question would be why are you running findmnt --verify at all?
If I had to guess, findmnt may have not been updated for the ntfs3 driver.
Online
Dear Scimmia
Thanks for your quick reply!
I thought I could run findmnt --verify just in order to make sure everything is ok. But of course you're right, should the command not have been updated for the ntfs3 driver yet, it produces more worries than reassurance ...
Perhaps it's enough to be reassured if the entry in /etc/fstab does not produce any error messages when booting up the system?
Anyway, to be on the safe side and to avoid the error message, I have created a systemd service which mounts the partition on startup.
Best regards
Rolf
Last edited by rfab (2022-05-22 16:30:04)
Offline