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.
After a full system update, I was getting the same error while opening my internal NTFS partition; which was automatically mounted every time before the update.
sudo fsck -y /dev/<your partition name here>
sudo ntfsfix /dev/<your partition name here>
sudo mkdir -p /media/<name for it>
sudo mount /dev/sda1 /media/<same name in previous line>
fsck cannot check ntfs file systems - it’s not the right tool for the job
ntfsfix also cannot do what it’s name seems to promise
All it does it to remove the “dirty” bit from a file system that is marked as having errors or not cleanly unmounted.
The effect is that you can then mount it again and can continue using it - but any error that was there is still there.
You have effectively done the equivalent of covering the “Check Engine” light in your car and pretend that it is not on and the reason for it being on is no longer present.
The only real way to check and fix ntfs file systems is to use native Windows tools.
btw, I have an internal ssd in my laptop, where 2 partitions are ext4 and one is NTFS. Is there any way to use the chkdsk without installing windows or without removing the ssd and connecting it to other laptop? @Nachlese
i can mount my external HDD with mount command too, but i can’t mount using dolphin
I have used chkdsk in Windows sistem, but it does not solve my problem, i dont have any bad sector when i use chkdsk. i tried ntfsfix and it did not work
If you suspect bad sectors, you need to use a slightly different command with chkdsk:
chkdsk x: /r /x
Note that chkdsk x: /f does not check for bad sectors.
Note: Substitute the X for your actual drive letter in Windows – chkdsk must be performed from an elevated command prompt. For more specific information please see the chkdsk documentation at Microsoft.
ntfsfix is not recommended for NTFS filesystems, and in any case, does not do what you expected it might have.
Everything you need is on the following page. All you need do is read and understand it.
When using the /r switch, the functionality of the /f switch is already included; so this means it’s unnecessary; all that’s needed is:
chkdsk (x:) /r /x
…in order to scan for and repair the filesystem, and also check for and repair bad sectors. Nonetheless, that was 4 hours well spent, especially as it solved your issue.
Cheers.
fsck should not ever be run on an NTFS filesystem.
ntfsfix does not repair an NTFS filesystem - using it will clear the dirty bit and usually prevent chkdsk from doing its job.
Understandable, because you did not actually fix anything with the commands you used. You cleared the dirty bit – but that does not repair an NTFS volume at all – to do that, you absolutely must use chkdsk from within a Windows environment.
Well, again, that was not a fix of any kind. The link is a basic walkthrough on how to auto mount various filesystem volumes, in this case using the /etc/fstab file.
For what it’s worth, the instructions seem consistent with the intended purpose; though there are arguably better ways to do this using systemd mount / automount units.
The OP hasn’t bothered to report back to offer any closure on their original issue, though it seems likely that the [Primer] NTFS on Linux link would have also offered the solution for their problem.
Therefore marking the appropriate post as the solution for all concerned. Cheers.
- 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.