I always mount my external hard drives without opening a terminal and typing a command with sudo.
I still mount other external HHD just by clicking the button on the notification when you insert the USB or by the context menu right-clicking its name in Dolphin (KDE). Never had that error.
Then you use udisks2 as backend. ntfs3 is the default there. And yes the error is somewhat misleading, but it has to do with ntfs being in a dirty state from windows.
There are 2 drivers: ntfs-3g and ntfs3. Both are different
ntfs-3g
userspace driver
force remove dirty bit by default
has default option which is called recover and this removes the dirty bit instantly.
ntfs3
kernelspace driver
doesn’t remove dirty bit by default
has an equivalent parameter to recover option: force. That means it will ignore the dirty bit, but disabled by default.
Note that both approaches can be dangerous, since this dirty bit is meant for checking the FS on the next mounting process, so usually on Windows. Linux does not and is not able to check the consistency of your data when using ntfs.
What I understand you are saying is that your NTFS drive no longer mounts automatically as it did before, due to the error you described above.
Using ntfs3 that error is by design; it’s a security measure; a warning to correct possible damage that was detected. Until that is done, ntfs3will actively refuse to mount that volume.
Perhaps this article will give you some insight into NTFS and how it works (and doesn’t work) with Linux. Please, read it and understand:
Another (temporary) solution might be to revert to an earlier kernel (6.6 for example).
Regarding the comment from @Nachlese - It may seem unlikely that all three volumes would develop an error simultaneously, but it’s certainly not impossible if (for example) the machine had a forced hard reset.
Indirectly, perhaps.
Are you sure your NTFS file systems are indeed clean? Free of errors.
Better check using Windows chkdsk.
Only then look for other causes.