Unable to access ntfs directory

[ahurd]

Re: Unable to access ntfs directory

Here it is:
albert@ALBERT-desktop:~$ cd /media
albert@ALBERT-desktop:/media$ ls -la
total 40
drwxr-xr-x 10 root root 4096 2008-06-11 21:09 .
drwxr-xr-x 25 root root 4096 2008-06-11 18:11 ..
lrwxrwxrwx 1 root root 6 2008-03-22 10:58 cdrom -> cdrom0
drwxr-xr-x 2 root root 4096 2008-03-22 10:58 cdrom0
lrwxrwxrwx 1 root root 45 2008-03-22 10:59 .directory -> /etc/kubuntu-default-settings/directory-media
lrwxrwxrwx 1 root root 7 2008-03-22 10:58 floppy -> floppy0
drwxr-xr-x 2 root root 4096 2008-03-22 10:58 floppy0
-rw-r--r-- 1 root root 0 2008-06-11 21:09 .hal-mtab
lrwxrwxrwx 1 root root 42 2008-03-22 10:59 .hidden -> /etc/kubuntu-default-settings/hidden-media
drwxr-xr-x 2 root root 4096 2008-03-22 10:58 sda1
drwxr-xr-x 5 root root 4096 2008-03-22 10:00 sda10
drwxr-xr-x 2 root root 4096 2008-03-22 10:58 sda2
drwxr-xr-x 4 root root 4096 2008-03-10 10:20 sda6
drwxr-xr-x 6 root root 4096 2008-03-10 13:19 sda7
drwxr-xr-x 9 root root 4096 2008-03-23 11:29 sda9
albert@ALBERT-desktop:/media$

[toad]

Re: Unable to access ntfs directory

Thanks! It should be easy.

sudo umount /dev/sda1

sudo chown albert /media/sda1

sudo mount /dev/sda1

If you want sda1 to be writeable by other users as well, you need to do

sudo chgrg users /media/sda1

and

sudo chmod+w users /media/sda1

For an explanation see this thread http://kubuntuforums.net/forums/inde...;topicseen#new

[ahurd]

Re: Unable to access ntfs directory

Here are results of trying yr suggestion:

albert@ALBERT-desktop:~$ sudo umount /dev/sda1
[sudo] password for albert:
umount: /dev/sda1: not mounted
albert@ALBERT-desktop:~$ sudo chown albert /media/sda1
albert@ALBERT-desktop:~$ sudo mount /dev/sda1
mount: according to mtab, /dev/sda1 is already mounted on /media/sda1

The same error message about mount and mtab occurs when I try to look into /media/sda1, and has been occurring throughout.

[ahurd]

Re: Unable to access ntfs directory

I am told the following by someone on linuxquestions:
write in your mtab

/dev/sda2 /mnt/Directory ntfs-3g defaults 0 0

and reboot , it will always mount.

Problem: mtab appears empty in kate and I hesitate to write a line to it using kate. Is this safe anyway?

[dibl]

Re: Unable to access ntfs directory

No, that's an /etc/fstab entry, and for a non-root filesystem the last number should be a "2" not a zero.

Some LInuces use /mnt for mounting drives, but *buntu defaults to /media. So, for Kubuntu, the fstab entry would be

/dev/sda2 /media/{your directory] ntfs-3g defaults 0 2

You can make a directory (aka "mount point") in /media with the console command

sudo mkdir /media/mysda2drive

or whatever you want to name it. Then use that in the /etc/fstab mounting line.

[ahurd]

Re: Unable to access ntfs directory

With your proposed alteration of /etc/fstab and a reboot, I again get the error message that has been plaguing me:

mount: according to mtab, /dev/sda1 is already mounted on /media/sda1

and not able to see anything in this directory.

[dibl]

Re: Unable to access ntfs directory

Bummer -- we're kinda going around in circles here, huh?

/etc/mtab is a system file that is updated automatically by the "mount" command. It should show all devices that are mounted at any given moment, but the fact that your drive/partition is shown mounted in /etc/mtab should not be an "error" -- it should be a normal fact. Here is my current /etc/mtab:

dibl@cville:~$ cat /etc/mtab
/dev/sda1 / ext3 rw,noatime,errors=remount-ro 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
/sys /sys sysfs rw,noexec,nosuid,nodev 0 0
varrun /var/run tmpfs rw,noexec,nosuid,nodev,mode=0755 0 0
varlock /var/lock tmpfs rw,noexec,nosuid,nodev,mode=1777 0 0
udev /dev tmpfs rw,mode=0755 0 0
devshm /dev/shm tmpfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
lrm /lib/modules/2.6.24-18-generic/volatile tmpfs rw 0 0
/dev/sda2 /home ext3 rw,noatime,data=writeback 0 0
/dev/sda4 /media/images xfs rw,noatime,nodiratime,logbufs=8 0 0
/dev/sdb1 /media/disk0 ext3 rw,nosuid,nodev,noatime,data=writeback 0 0
/dev/sdc1 /media/backups xfs rw,noatime,nodiratime,logbufs=8 0 0
/dev/sdc2 /media/music xfs rw,noatime,nodiratime,logbufs=8 0 0
/dev/sdc3 /media/videos xfs rw,noatime,nodiratime,logbufs=8 0 0
/dev/sdd2 /media/disk1 ext3 rw,nosuid,nodev,noatime,data=writeback 0 0
/dev/sdd3 /media/disk2 ext3 rw,nosuid,nodev,noatime,data=writeback 0 0
/dev/sde1 /media/music_bak xfs rw,noatime,nodiratime,logbufs=8 0 0
securityfs /sys/kernel/security securityfs rw 0 0
none /proc/fs/vmblock/mountPoint vmblock rw 0 0

As you can see, it reflects the setup that I have in /etc/fstab:

dibl@cville:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>  <type> <options>    <dump> <pass>
proc      /proc      proc  defaults    0    0
# /dev/sda1
UUID=909106df-3f64-48f7-9860-17e04ae0f734    /        ext3  noatime,errors=remount-ro 0    1
# /dev/sda2
UUID=8244ac7e-8dba-4e51-b252-3033c4c97ea4    /home      ext3  noatime,data=writeback     0    2
# WDC_WD1500ADFD-0-WD-WMAP41478339-part4,    /dev/sda4
UUID=8bd15bd5-04df-437c-b5f8-25897e5ea7b0    /media/images  xfs   noatime,nodiratime,logbufs=8 0    2
# WDC_WD1500ADFD-0-WD-WMAP41142727-part1, /dev/sdb1
UUID=1a1ffa9b-a8f6-43e9-bb1f-fbc32934018b    /media/disk0  ext3  auto,users,exec,noatime,data=writeback    0    2
# WDC_WD7500AAKS-0-WD-WCAPT0030245-part1, /dev/sdc1
UUID=92c0453f-2a35-40d5-8013-b8870ed66127    /media/backups xfs   noatime,nodiratime,logbufs=8 0    2
# WDC_WD7500AAKS-0-WD-WCAPT0030245-part2, /dev/sdc2
UUID=f4e36b39-af7d-475c-8990-b2093f558295    /media/music  xfs   noatime,nodiratime,logbufs=8 0    2
# WDC_WD7500AAKS-0-WD-WCAPT0030245-part3, /dev/sdc3
UUID=eba33247-0dbb-482c-9351-81505a953864    /media/videos  xfs   noatime,nodiratime,logbufs=8 0    2
# WDC_WD1500AHFD-0-WD-WMAP41413403-part3, /dev/sdd2
UUID=5df77414-98e4-4241-b696-00001ad57fc9    /media/disk1  ext3  auto,users,exec,noatime,data=writeback    0    2
# WDC_WD1500AHFD-0-WD-WMAP41413403-part3, /dev/sdd3
UUID=e11635ae-7dae-45fa-9372-bdc70ef9ec6b    /media/disk2  ext3  auto,users,exec,noatime,data=writeback    0    2
# automatically added, Maxtor_6L200P0-L42WA14G-part1, /dev/sde1
UUID=e731c3cf-e2ff-4692-8353-ede2a3dcb85e    /media/music_bak    xfs   noatime,nodiratime,logbufs=8 0    2
# /dev/sdd1
UUID=f292aef5-76a6-4455-a4e0-b760e43126e5 none      swap  sw       0   0
/dev/scd0    /media/cdrom0  udf,iso9660 user,noauto,exec,utf8 0    0
/dev/fd0    /media/floppy0 auto  rw,user,noauto,exec,utf8 0    0

So, it should not be an error to see that /dev/sda2 is mounted at a mount point in /media and also in /etc/mtab, because that is normal.

That makes me wonder if there is something messed up in your system. Another thing that makes me wonder is that a hard drive or partition can only be mounted once, AFAIK, and yet earlier it appeared that your /dev/sda2 partition was mounted in multiple places. I dunno what's wrong there, exactly, but those are certainly some unusual error messages for what looks like a fairly normal hard drive setup. :P

[ahurd]

Re: Unable to access ntfs directory

I now have sda2 listed in fstab following your suggestion, and yet /dev/sda2 does not appear in mtab contrary to error message. It is true that I earlier tried to mount sda1 and saa2 in several places. Is there anything I can do now, like umount and mount. Will an upgrade solve the problem?

[dibl]

Re: Unable to access ntfs directory

I would not upgrade a system that was giving me this kind of trouble, personally. I'd rather do a clean new installation, and then carefully edit the /etc/fstab file, and I would only use Mount by UUID as the way to avoid those sneaky /dev/IDs changing when you plug in a USB drive.

[ahurd]

Re: Unable to access ntfs directory

Many thanks to all.