write / no write partitions
GT
I have an external HD added to my laptop. I am a little confused though :
one partition, called /mnt/NEW_VOLUME works fine
the other, called /mnt/NEW_VOL2 does *not* allow writing, whether root or not !
I took a look at fstab and they are identical :
.
.
.
/dev/sda5 /mnt/NEWVOL2 vfat pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
/dev/sda2 /mnt/NEW_VOLUME vfat pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
.
.
.
also, both partitions have *identical* properties concerning access and share (current user, not even root!)
looks to me they are "twins" in terms of access properties. is there something I might be missing?
must be.
any help appreciated !
thanks
G
Walter Mautner
Isn't it a simple typo in your fstab missing the "_" at NEWVOL2?
--
vista policy violation: Microsoft optical mouse detected penguin patterns
on mousepad. Partition scan in progress to remove offending
incompatible products. Reactivate MS software.
Linux 2.6.14-mm1 [LinuxCounter#295241,ICQ#4918962]
GT
> GT wrote:
>
>> Hi everyone,
>> I have an external HD added to my laptop. I am a little confused though :
>> one partition, called /mnt/NEW_VOLUME works fine
>> the other, called /mnt/NEW_VOL2 does *not* allow writing, whether root or
>> not ! I took a look at fstab and they are identical :
>>
>> .
>> .
>> .
>> /dev/sda5 /mnt/NEWVOL2 vfat
>> pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
>> /dev/sda2 /mnt/NEW_VOLUME vfat
>> pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0 .
>> .
>> .
>>
>> also, both partitions have *identical* properties concerning access and
>> share (current user, not even root!) looks to me they are "twins" in terms
>> of access properties. is there something I might be missing? must be.
>>
> Isn't it a simple typo in your fstab missing the "_" at NEWVOL2?
>
'fraid not. that's what they're called !
David W. Hodgins
> Walter Mautner wrote:
>
>> GT wrote:
>>> the other, called /mnt/NEW_VOL2 does *not* allow writing, whether root or
>>> /dev/sda5 /mnt/NEWVOL2 vfat
>> Isn't it a simple typo in your fstab missing the "_" at NEWVOL2?
>
> 'fraid not. that's what they're called !
Which is correct? NEW_VOL2 or NEWVOL2? The mount point specified in
the fstab must be an existing directory, with the names spelled the same<g>.
Regards, Dave Hodgins
--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)
GT
> On Sat, 25 Feb 2006 18:17:26 -0500, GT <ra...@caramail.com> wrote:
>
>> Walter Mautner wrote:
>>
>>> GT wrote:
>
>>>> the other, called /mnt/NEW_VOL2 does *not* allow writing, whether root or
>>>> /dev/sda5 /mnt/NEWVOL2 vfat
>>> Isn't it a simple typo in your fstab missing the "_" at NEWVOL2?
>>
>> 'fraid not. that's what they're called !
>
> Which is correct? NEW_VOL2 or NEWVOL2? The mount point specified in
> the fstab must be an existing directory, with the names spelled the same<g>.
>
> Regards, Dave Hodgins
>
>
two partitions, one is NEWVOL2, the other NEW_VOLUME
fstab reflects this and so do the mount points
Walter Mautner
Damned, your mountpoint differs from the /etc/fstab entry, that's what we
wanted to tell:
>>>>> the other, called /mnt/NEW_VOL2 does *not* allow writing, whether root
and fstab entry
>>>>> /dev/sda5 /mnt/NEWVOL2 vfat
with a missing "_".
Everything clear?
GT
>
> Damned, your mountpoint differs from the /etc/fstab entry, that's what we
> wanted to tell:
>>>>>> the other, called /mnt/NEW_VOL2 does *not* allow writing, whether root
> and fstab entry
>>>>>> /dev/sda5 /mnt/NEWVOL2 vfat
> with a missing "_".
> Everything clear?
fstab :
/dev/sda5 /mnt/NEWVOL2 vfat pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
/dev/sda2 /mnt/NEW_VOLUME vfat pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
/dev/sda1 /mnt/removable ext3 pamconsole,exec,noauto,managed 0 0
mount points :
/mnt/NEWVOL2
/mnt/NEW_VOLUME
can't really be clearer I think.
or am I being particularly dumb and overlooking the obvious.... you be the judge
David W. Hodgins
> /dev/sda5 /mnt/NEWVOL2 vfat pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
> /dev/sda2 /mnt/NEW_VOLUME vfat pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
> /dev/sda1 /mnt/removable ext3 pamconsole,exec,noauto,managed 0 0
> mount points :
> /mnt/NEWVOL2
> /mnt/NEW_VOLUME
> can't really be clearer I think.
> or am I being particularly dumb and overlooking the obvious.... you be the judge
In your original article, you stated the mount point was /mnt/NEW_VOL2, not /mnt/NEWVOL2,
I've just done some checking, and while pamconsole appears to be frequently used, I
can't find anywhere that states what it does. It is not listed as an option in man mount.
Here's what I have in my fstab for my vfat partitions...
/dev/hda1 /mnt/hda1 vfat noauto,users,umask=0,iocharset=iso8859-15,codepage=850 0 0
/dev/hda5 /mnt/hda5 vfat noauto,users,umask=0,iocharset=iso8859-15,codepage=850 0 0
In my /mnt direcory, with the partitons not mounted, I have (from ls -l /mnt) ...
drwxr-xr-x 2 root root 48 Jan 1 15:31 hda1/
drwxr-xr-x 2 root root 48 Jan 1 15:31 hda5/
then when I mount them as a regular user, ...
[dave@hodgins ~]$ mount /mnt/hda1
[dave@hodgins ~]$ mount /mnt/hda5
[dave@hodgins ~]$ ls -l /mnt
<snip>
drwxrwxrwx 70 dave dave 12288 Dec 31 1969 hda1/
drwxrwxrwx 50 dave dave 8192 Dec 31 1969 hda5/
Why your's is working for one partition, and not the other, or what pamconsole does, I
don't know.
Try altering your fstab, and possibly /mnt/sda* directory permissions, to be similar to mine.
Walter Mautner
Next time better copy & paste from a terminal window into the posting.
I copied the lines from your initial posting, and it came different.
Now what are the results of "ls -ld" on /mnt/NEW*, before and after the
mount?
Walter Mautner
> On Mon, 27 Feb 2006 12:59:06 -0500, GT <ra...@caramail.com> wrote:
>
>> /dev/sda5 /mnt/NEWVOL2 vfat
>> pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
>> /dev/sda2 /mnt/NEW_VOLUME vfat
>> pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
>> /dev/sda1 /mnt/removable ext3
>> pamconsole,exec,noauto,managed 0 0 mount points :
>> /mnt/NEWVOL2
>> /mnt/NEW_VOLUME
>> can't really be clearer I think.
>> or am I being particularly dumb and overlooking the obvious.... you be
>> the judge
>
> In your original article, you stated the mount point was /mnt/NEW_VOL2,
> not /mnt/NEWVOL2,
>
> I've just done some checking, and while pamconsole appears to be
> frequently used, I
> can't find anywhere that states what it does. It is not listed as an
> option in man mount.
>
You find "something" about pamconsole in hald documentation. From what I
got, it grants permissions to mount to the console user only.
Now, for myself, I don't want barely documentd scripts mess around
with /etc/fstab, so made it immutable and use autofs instead, for mounting
known removables (in conjunction with udev rules). Autofs allows specifying
the usual mount options, as well as a timeout/automatic unmount.
GT
>> fstab :
>>
>> /dev/sda5 /mnt/NEWVOL2 vfat
>> pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
>> /dev/sda2 /mnt/NEW_VOLUME vfat
>> pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
>> /dev/sda1 /mnt/removable ext3
>> pamconsole,exec,noauto,managed 0 0
>>
>> mount points :
>>
>>
>> /mnt/NEWVOL2
>> /mnt/NEW_VOLUME
>>
>> can't really be clearer I think.
>> or am I being particularly dumb and overlooking the obvious.... you be the
>> judge
>
> Next time better copy & paste from a terminal window into the posting.
> I copied the lines from your initial posting, and it came different.
> Now what are the results of "ls -ld" on /mnt/NEW*, before and after the
> mount?
gotcha. good tip. thanks
right, this is the fstab (just in case some inconsistency in there screws things up)
[guillaume@roudoudou ~]$ more ../../etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/hda5 / ext3 noatime 1 1
/dev/hda7 /home ext3 noatime 1 2
/dev/hdb /mnt/cdrom auto
umask=0,user,iocharset=iso8859-15,codepage=850,noauto,ro,exec,users 0 0
/dev/hdc /mnt/cdrom2 auto
umask=0,user,iocharset=iso8859-15,codepage=850,noauto,ro,exec,users 0 0
/dev/hda2 /mnt/windows vfat umask=0,iocharset=iso8859-15,codepage=850 0 0
none /proc proc defaults 0 0
/dev/hda6 swap swap defaults 0 0
/dev/sda5 /mnt/NEWVOL2 vfat
pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
/dev/sda2 /mnt/NEW_VOLUME vfat
pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
/dev/sda1 /mnt/removable ext3 pamconsole,exec,noauto,managed
0 0
[guillaume@roudoudou ~]$ ls -ld /mnt/NEW*
drwxr-xr-x 36 guillaume guillaume 16384 jan 1 1970 /mnt/NEWVOL2/
drwxr-xr-x 62 guillaume guillaume 16384 jan 1 1970 /mnt/NEW_VOLUME/
[guillaume@roudoudou ~]$
now THIS (above) is of course AFTER mounting. I would umount them if I knew where to
find the mount command linux uses to mount them back. unless of course logging off
and back on again suffices.
can you help there ?
thanks
David W. Hodgins
> David W. Hodgins wrote:
>> I've just done some checking, and while pamconsole appears to be
>> frequently used, I
>> can't find anywhere that states what it does. It is not listed as an
>> option in man mount.
>>
> You find "something" about pamconsole in hald documentation. From what I
Thanks for the pointer. For future reference, from the hal documentation...
| Note the two new mount options pamconsole and managed. The
| former specifies that any (unprivileged) user sitting at the console may
| mount the file system. The latter, a no-op, specifies that this line was
| added by a program and not by the system administrator - hence the
| option managed is useful if the administrator has already manually
| added an entry since fstab-sync refuses to add an entry in that case.
Walter Mautner
....
>> Now what are the results of "ls -ld" on /mnt/NEW*, before and after the
>> mount?
>
> gotcha. good tip. thanks
>
> right, this is the fstab (just in case some inconsistency in there screws
> things up)
>
.....
> /dev/sda5 /mnt/NEWVOL2 vfat
> pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
> /dev/sda2 /mnt/NEW_VOLUME vfat
> pamconsole,exec,noauto,codepage=850,iocharset=iso8859-15,managed 0 0
> /dev/sda1 /mnt/removable ext3
> pamconsole,exec,noauto,managed 0 0
>
> [guillaume@roudoudou ~]$ ls -ld /mnt/NEW*
> drwxr-xr-x 36 guillaume guillaume 16384 jan 1 1970 /mnt/NEWVOL2/
> drwxr-xr-x 62 guillaume guillaume 16384 jan 1 1970 /mnt/NEW_VOLUME/
> [guillaume@roudoudou ~]$
>
> now THIS (above) is of course AFTER mounting. I would umount them if I
> knew where to find the mount command linux uses to mount them back. unless
> of course logging off and back on again suffices.
>
After mounting, both mountpoints show up with your username and full
permissions for you, so the "pamconsole" seems to work.
Now please post the content of /etc/mtab (at least the lines containing your
questioned partitions), and - from a windows boot (a dos bootfloppy will
not see the usb or firewire drive) - do a file system check (scandisk) on
the /dev/sda5 (higher drive letter in windows). You may want to take the
external disk to a windows pc for that purpose. Or download the dosfstools
package and run dosfsck/fsck.vfat.
For remounting, you can just use "mount /mnt/NEW_VOLUME" etc. as root. The
"noauto" tells mount not to consider the line on a "mount -a" request,
while pamconsole and managed will be ignored.
Do not forget to umount what you manually mounted.