Unable to mount ntfs HDD

solus_me

Axios They updated ntfs this update might see if that cures your problem.

Or may be this is the issue. I can't identify.
I made a clean reinstall recently in a hope to stop the vanish of files - same situation.

I do update rarely since I work on Solus and it is my daily bases OS also. When it is stable as I like, I don't want unwanted changes to the programs and the OS, which interfere and stops my work. It takes me time to identify the problem and find a solution. That is why I update rarely. Also I keep my HOME folder on a different partition, because of the above reasons. May be it is a conflict between - old configuration files in Home folder, with new identity in the operating system, but file system management have no place in HOME folder configuration files where resides user references, or am I wrong?

I use Solus for long time after I left Windows. I like it and I don't want to look for other linux distros.

Axios Maybe something got broked in switching of all the file managers if that's poss.

May be, I don't know.

Axios

solus_me I found this that resembles your problem was kind of interesting
but I think the devs would have to comment on it not sure how they handle Ntfs.

https://github.com/storaged-project/udisks/issues/1190

solus_me

Axios
Yes, I've read that.
I don't think removing the dirty flag with "ntfsfix -d" is a good idea. It could accumulate more problems to the file system when we don't know what is causing it.
But thanks anyway.

Axios

solus_me No Problem was not advocating of doing anything there more or less
just info.
Windows was good at telling you if a volume was dirty especially on plug in drives and if it said ok
I would believe it.

solus_me

Axios
Yes. Do not offend please. I'm very grateful for the attention. I'm just thinking out loud (out written) 😃

You are right. When Windows doesn't find anything, the problem is within Solus and the NTFS file system.
But what? How to diagnose this? That is the question.

Axios

solus_me Was not offending sorry if it came across that way.

solus_me

Ok, so...
Completely formatted HDD with zeros, checked for bad sectors with chkdsk /f /r under windows, freshly formated under NTFS, then newly installed and updated Solus Budgie (after the repo's little incident) - still the same result&
"wrong fs type, bad option, bad superblock....".
ntfsfix is sayng:

sudo ntfsfix --no-action /dev/sda5
ounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sda5 was processed successfully.

solus_me

sudo ntfsfix --no-action /dev/sda5
ounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sda5 was processed successfully.

dmesg is sayng:

sda5: It is recommened to use chkdsk.
ntfs3: sda5: volume is dirty and "force" flag is not set!

when manually mounting the partition:

sudo mount /dev/sda5 /mount/media

successful and with no complains.

What is interesting is that "ntfs3" is managing the file system not "ntfs-3g". As far as I can understand. Many people in other distros are complaining also from "ntfs3" corrupting their data and hard disks.

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

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

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

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

« Previous Page Next Page »