Before I upgraded to 11.2 I could normally mount my NTFS partition from an external harddrive no there is this error:
Error mounting: mount exited with exit code 32: mount:
unknown filesystem type 'ntfs'
If I mount via terminal with mount -t ntfs-3g it is working.
The same problem I had with my Truecrypt partition in NTFS, but there I could solve the
problem by changing the fstab entry to ntfs-3g.
But how can I solve this problem with an external harddrive, I don’t want to
mount every time over terminal.
I’ve seen this happen when the external drive is inappropriately mentioned in a user’s /etc/fstab (can help if drive is connected when 11.2 upgraded). Is the drive by chance mentioned there?
As usualy I am full of suspicion if I do understand what you mean when I read what you have written.
When you say: “…I could normaly mount …”, do you mean using a *mount *statement, or do you mean you let it be mounted by HAL (not doing the mount yourself)? I also suppose the disk is added to the system on the flight and not permanently connected.
You already answered oldcpu’s question, there is no entry for this partition in /etc/fstab. That means that HAL should normaly do the job of mounting when you conneect the device. During this, the system decides it is ntsf (I do not know exactly how this is done, sort of look and error). But then it seems that the system has no support for this fs type. It has apparently support for ntfs-3g, but there seems to be no clue for trying it as an alternative to ntfs.
The above is certainly no solution, but I hope it helps in narrowing down the possibilities.
In the meantime you could make it easier for yourself, by adding an entry into /etc/fstab. Of course with the corret ntfs-3g as fstype and with at least the *noauto *option (so the system will not try to mount it at boot). This will make your ‘mount by hand’ easier to type (you could even make an alias for it).
When I connect it try automatically to mount with the named error.
With normally mount I meant this:
mount -t ntfs-3g -o rw /dev/sdb1 /media
That is working.
But I thought there should be a solution, because before the upgrade it worked.
Yes the disk is just sometimes connected.
I admit that it should work as you state. I only tried to let your bypass be more comfortable.
BTW, you mount on /media. I will not say that you should not do that, but as HAL has the incurable habbit to mount **within (not on) /media (on places like /media/<disk_label> or /media/disk), I wonder if it is a good idea. The more because HAL creates also other files inside /media (like */media/.hal-mtab *and a lock file) and mounting something over it would make them unreachable. HAL (when another mass storage device is connected) wil then most probably try to create new ones on your ntfs-3g partition and mount stuff in there, which is not what you want I think.
Better mount it on some place of your choice outside /media, or somewhere inside* /media* (like* /media/stubborndisk*).
And do not forget to create that directory before you try to mount.
buugmenot wrote:
<snip>
> But I thought there should be a solution, because before the upgrade it
> worked.
> Yes the disk is just sometimes connected.
i agree that it ‘sounds like’ HAL is failing sometimes, which might
mean a timing conflict or something far beyond my understanding…no
matter what the cause i think you should log a bug report, because
apparently something changed between 11.1 and 11.2 that needs to be
corrected, again…