Unable to mount ntfs HDD

alfisya

solus_me It is interesting that "ntfs3" is not in the repository, it is not installed in the system but it is managing the file systems??? As far as I can understand.

ntfs3 is part of ntfs-3g package

solus_me

Or may be ntfs3 is a kernel module.
Does anyone know how to blacklist kernel module or ntfs3 in Solus?

Axios

solus_me If you mount it manually does the file manager work properly
copy delete etc?
Also I would try formatting and setting up ntfs disk under linux and see if dirty flag goes away
(Trying to see if windows or linux sets dirty bit)

solus_me

Axios
When I did the test, it worked. You can use file manager to create, copy and delete files. Then manually unmounted it. At least it could help you to move data to some other place, if this is the case.

On your second thought, I don't advice. I lost data like that. I already tried formatting under linux in NTFS, but Windows in it's turn don't recognize the data in the partition. It counts something in size when you check the properties, but the partition is empty. Using Scan Tools and "chkdsk" doesn't help.

I don't know what is causing it. May is the "ntfs3". It was not like that as far as I can remember.

solus_me

Axios
It is from linux - ntfs3.
At least this is what I've got from a research.

Axios

solus_me When a volume is mounted dirty bit is set if its not cleanly unmounted
it does not get cleared (Info)
Something strange going on should not be any issues between Os what windows is it dual boot?

Will have to think on this one.

solus_me

Ok, I've tryied to blacklist ntfs3.

Created a file: disable-ntfs3.conf
and put it into: /etc/modprobe.d/
with content: blacklist ntfs3

I don't know is that the correct way in Solus, but it worked partially.
After restart, now the partition is mounting and unmounting seemingly ok.

dmesg, on other hande, is saying:
request_module fs-ntfs3 succeeded, but still no fs?

May be the system some how found a way to bypass it and the properties are saying Filesystem type: fuse, which is not correct. It doesn't recognize NTFS.

Removing the "blacklist" instantly gives the same result "wrong fs type....".

Any other ideas, guys?

Axios

solus_me My guess its not using ntfs3g after disabling ntfs3
What do you get if from terminal you do this
ls /sbin/mount.ntfs* -l

solus_me

Axios
I will tell you, when I get back home. Currently I'm on work. 🙂

solus_me

Axios My guess its not using ntfs3g after disabling ntfs3

Yes. It is not using ntfs-3g as default after disabling ntfs3.

solus_me

Axios What do you get if from terminal you do this
ls /sbin/mount.ntfs* -l

reports:

/sbin/mount.ntfs -> ../bin/ntfs-3g
/sbin/mount.ntfs-3g -> ../bin/ntfs-3g

there is lowntfs-3g also in the /sbin folder

Axios

solus_me That output is proper.
On that note I can not get this issue straight in my mind for some reason and to not cause more or going
in circles going to step aside but if I do run across something or that light bulb goes on I will post.

Lets us know what happens.
Note: I prob shouldnt have said straight but more like cant find a starting point all the same I guess.

solus_me

It is interesting that 'lsblk' recognizes the file system:

lsblk -f /dev/sda5
NAME FSTYPE FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda5 ntfs         New Volume D8826AFC826ADF0E

solus_me

Don't worry.
May be we should turn this issue to the devs?
I'm not experienced enough to solve it by myself.

Axios

I am posting this for information purposes.

Windows hibernation and fast restarting on win10 and win11
On computers which can be dual-booted into Windows or Linux, Windows has to be fully shut down before booting into Linux, otherwise the NTFS file systems on internal disks may be left in an inconsistent state and changes made by Linux may be ignored by Windows.

So, Windows may not be left in hibernation when starting Linux, in order to avoid inconsistencies. Moreover, the fast restart feature available on recent Windows systems has to be disabled. This can be achieved by issuing as an Administrator the Windows command which disables both hibernation and fast restarting :

powercfg /h off

solus_me

Many people in other distros are complaining like me from NTFS3,
which by their assessment isn't managing correctly the file system and causing data lose.

Due to research I found out that NTFS3 is flagging hard drives and their partitions frantically with "Dirty flags",
without proper report of the condition. The only thing that recommends is to be used "chkdsk" of Windows.

NTFS3 is supposed to replace NTFS-3G.
If read-only access - NTFS3 works fine, where writing - creates errors and corrupts HDD.

There is a bug found in the code in 2022 which causes a crash of the NTFS3 driver itself,
if compiled directly to the kernel, it crashes the whole system.

Refference to the bug article:
https://www.cyberark.com/resources/threat-research-blog/the-linux-kernel-and-the-cursed-driver

Refference to the bug report:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/ntfs3/attrib.c?id=6d5c9e79b726cc473d40e9cb60976dbe8e6696

There could be more bugs since the driver is not maintained by the owner, according to users and devs.

If you are experiencing lose of data in NTFS hard drive, and series of errors mounting NTFS drives or partitions,
may be this is your case.

Users suggest using FUSE kernel module with NTFS-3G for reading and writing data on NTFS
and blacklisting NTFS3 until the issues with it are resolved or removed from the kernel itself.

« Previous Page Next Page »