Error while mounting ntfs drive.

[Crypdos]

After deleting the old mountpoint and specifying a new one, and reinstalling ntfs-3g it now works again. Weird.

Maybe the old mountpoint was instead conflicting with hdXY, or maybe it was ntfs-3g? Haha, anyways I'm glad it works now.

Thanks for the help.

[Crypdos]

Too soon to cheer ...

After 3 reboots it is now happening again, error: error while mounting /media/mediadrive.
This is the new mountpoint I made...

[oldfred]

Gparted will often have a yelllow or red icon on a partition with issues. Clicking (right click?) on icon may tell why it has issues. Often with NTFS it just suggests chkdsk.

From Disk Utility or Disks click on drive and on right side is Smart Data info on drive. Is it showing any issues. New drive should not but even new drives sometimes have issues.

[Crypdos]

Gparted is showing a green icon. Smart-Data says "drive is healthy". And chkdsk yesterday reported no errors too.
I don't think the drive or the filesystem is faulty. I think the problem lies purely in the booting process. When I mount the drive in a gnome terminal, there are no problems at all - it uses the specified fstab mountpoint and works correctly.

Could it be that the drive gets accessed by something before fstab can mount it?
from the boot.log:

Mount is denied because the NTFS volume is already exclusively opened.  The volume may be already mounted, or another software may use it which  could be identified for example by the help of the 'fuser' command.  
mountall: mount /media/hdd1 [897] terminated with status 16  
mountall: Filesystem could not be mounted: /media/hdd1

I pressed M at the errorscreen (manual recovery) and ran "fuser -vm /dev/sdb1" and "mount" and recorded the output:

root@Media-PC:~# fuser -vm /dev/sdb1
                     USER        PID ACCESS COMMAND
/dev/sdb1:           root     kernel swap  /dev/sda1
                     root     kernel mount /dev
                     root          1 F.... init
                     root        396 F.... upstart-udev-br
                     root        398 F.... udevd
                     root        575 F.... udevd
                     root        580 F.... udevd
                     root        806 F.... upstart-socket-
                     root        878 F.... lircd
                     root        916 F.... mount.ntfs
                     root        924 F.... sh
                     root        925 F.... initctl
                     root        933 F.... sh
                     root        934 F.... bash
                     root        944 F.... script
                     root        945 F.... script
root@Media-PC:~# mount
/dev/sda2 on / type ext4 (rw,noatime,discard,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /tmp type tmpfs (rw,noatime,mode=1777)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
/dev/sda3 on /home type ext4 (rw,noatime,discard)
/dev/sdb1 on /media/mediahdd type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096)
root@Media-PC:~# exit
exit

[oldfred]

Your error message is from your old mount, where is that from?

I thought this was not now used:
mountall: Filesystem could not be mounted: /media/hdd1

What is mounted:

/dev/sdb1 on /media/mediahdd type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,b lksize=4096)

[Crypdos]

Yes, this was the old mountpoint. Sorry I copied the error message from my opening post.

The fuser and mount output are recent. It seems that the HDD is already mounted at that point (during manual recovery - which is before gnome)?

[Crypdos]

bump

[oldfred]

Were you not mounting hdd1 with fstab but with something else like a script or udisks?
Or is entry in fstab still there for the hdd1?

It seems like you are still trying to mount the same drive twice which is not allowed.

[Crypdos]

Yes, that's exactly what I'm saying. Something accesses the drive before fstab does. At least that's what I'm thinking right now.

I didn't manually make a script to do this, maybe it is a program I installed that I forgot about. I removed all entries from fstab now.

[Crypdos]

When I remove the line from fstab completely, it still gets mounted during boot. It is then mounted with the label's name under /media/mediahdd. The label is mediahdd. When mounted this way I do not have write access.

So something other than fstab mounts the drive during boot. Even _before_ fstab, because fstab reports the error "Mount is denied because the NTFS volume is already exclusively opened. The volume may be already mounted, or another software may use it which could be identified for example by the help of the 'fuser' command."

WHAT MOUNTS MY PROGRAM BEFORE FSTAB DOES?