NTFS failed?

English Install/Boot/Login
#1

Hello,
I’m having issues trying to mount an NTFS drive. I’ve installed ntfs-3g, and fuse. But whenever I boot, it displays “failed” next to the portion where its mounting the drives. Is there any workaround for this?

Thanks!

#2

This can occur when the ntfs partition is ‘dirty’. See this thread.

#3

A tad more on fixing the problem: Failed Mounts – Resetting the “dirty” bit
and there’s a workaround if you don’t reset the dirty bit – it’s the force option (it’s not the preferred option though): The force option

#4

Fixing the dirty bit actually fixes the mounting problem but some problem with ntfs volume could still be there. Possibly the volume has not been correctly unmounted. So i think it is the case to cure the problem with the file system booting windows and let it perform a scandisk

#5

@drtechmaster -

The above is all correct (except that it is chkdisk, not scandisk). Keep in mind that the ntfs-3g driver does not write to the ntfs journal. The ntfsfix utility will clear the bit and reset the journal, but AFAIK it does not run the journal against the filesystem. And, if there has been a data corruption under ntfs-3g and the dirty bit has been set, when you boot Windows the journal will be checked and processed if applicable, and the bit reset. BUT, the corruption will not be resolved because it was not trapped in the journal, and Windows at boot will not see that. So the absolute safest thing to do is to, after booting Windows, run chkdisk against the volume.

#6

Hello, thanks everyone. It appears to be functional in dolphin other than… I can’t write data to the drives. Should I try clearing the resetbit again? It appears to still return failed… Sad, but true.

Thanks!
At least I can read now! Better than nothing.

#7

You may have a permissions issue, which of course would have nothing to do with the dirty bit. The dirty bit will prevent a mount altogether. If the drive has mounted, albeit only for read, the bit has been cleared. Look into your fstab settings (there are example in other threads).

#8

Try to give permissions to the mount point. If you are not sure about it give the command ‘mount’ in a console as root. It will return all the devices and their mount points. Then always as root give the command 'chmod 777 <your-mount-point>. Otherwise you could give it the correct permissions using the yast partitioner

#9

This is not me being contentious – this is me asking a question:
Just a passing question: Doesn’t the ntfs-3g driver automagically (a) chmod recursively the permissions and (b) chown the ownership on the mount point, following the constraints set in the mounting command, regardless of what they were before the act of mounting? In that case, would that mean that to “chmod 777 <your-mount-point>” would not be meaningful?

#10

I simply suspect that even if the partition has been mounted with the correct permissions, the regular user could not have the rights to write to the directory where the partition has been mounted. In my last opensuse11 installation (for me,my family and my friends) i always had that issue. I know it is a dirty way but it’s also fast and simple in solving the problem. So this is based on experience, no other theoretical meanings. I would give a try. If it should not work simply nothing happens. Always great respect on you swerdna!

#11

I dunno what happened, but it works now! :slight_smile:
Apparently it was readwrite, but I’m not sure what happened. It’s not giving me failed either which is nice.

Thanks everyone!

#12

Hi again. Just to confirm that even if a file system is correctly mounted with r/w permissions for all, but the mount point is not writeable by the common user, there is no chance for him to write the disk, unless you don’t change the permission for the mount folder. Look here Need Write Access To My Harddisk - openSUSE Forums
.

#13

That reference is for an ext3 filesystem, quite a different situation from ntfs-3g. I just did this to test your statement in relation to ntfs-3g: An NTFS partition is set in my computer in fstab to mount in a directory on booting. I unmounted it and chmoded the directory to forbidden to all; i.e. it’s d---------. The line in fstab says to mount using ntfs-3g with owner root:users and permissions drwxrwxr-x
(fstab options are user,users,gid=users,umask=0002,locale=en_US.UTF-8)

On booting it mounts automagically, metamorphosing from d--------- to drwxrwxr-x, following the coding instruction the devs for ntfs-3g have written into the application called ntfs-3g, a very different situation to ext3.

It’s wrong IMHO to treat it like a typical Linux filesystem.

Just my 2 cents worth.