Page 1 of 1

Mostly solved. Card reader - some commands fail.

Posted: Mon Sep 15, 2008 11:49 am
by T J Tulley
System is in my signature. I am trying to make my Fufifilm DCR2-161 card reader usable.

At present when I connect it, (USB2) I get a box saying "You are not privileged to mount this volume".
/var/log/syslog tells me that it is identified as sdf1.
The command /dev $ ls -al shows that it belongs to root with permissions 660
When previously connected, a command /dev $ sudo chown -R theo /dev/sdf1 was successful, but the result of that disappeared after it was disconnected and re-connected. I hoped that it would result in automatic mounting.
I have now repeated that command, followed by: sudo mount /dev/sdf1 /media/Cardreader (where the destination has been created by a mkdir command).
The card reader is mounted, its icon appears in the desktop screen, and its properties show under the Volume tab that its Mount options are rw nosuid nodev noatime relatime uid=1000 default_permissions=allow_other.
In spite of the rw shown, when opened, its contained directory and files show properties 755.
Now I apply a command: / $ sudo chown -R theo:theo /media/Cardreader
The response is a multi-line report for every item contained in Cardreader: Operation not permitted.
Strangely, even after mounting, a new command /dev $ ls -al still shows sdf1 as belonging to me with permissions 660 - although the mounted ownership and partitions are root, 755.

Why is a sudo command not permitted? What can I do about it?
[Command problems remain].
How do I make this device auto-mount, belonging to me, with read-write permissions, when inserted?
[This question solved - see late posts].

Advice most gratefully received - I've been trying for a long time.

Re: Please help! Obstinate card reader - some commands fail.

Posted: Mon Sep 15, 2008 12:01 pm
by Fred
Theo,

Post the line in /mtab or /mnt, whichever Mint is using, for the mounted card reader. I have an errand I must run, but I will answer you question when I get back.

Fred

Re: Please help! Obstinate card reader - some commands fail.

Posted: Mon Sep 15, 2008 12:46 pm
by T J Tulley
Thanks, Fred: the line in /etc/mtab is:
/dev/sdf1 /media/Cardreader vfat rw 0 0

At present I have a line in /etc/fstab as follows:
/dev/sdf1 /media/Cardreader auto rw,uid=1000,nodev,relatime 0 0

but if the card reader is connected while booting, the system always hangs - landing after a long time in either BusyBox or Terranova. Then, if I remember correctly, I have to reset - [Ctrl]+[Alt]+[Del} doesn't work.

Thanks also for your reply to my post about Grub & the /boot partition.

Re: Please help! Obstinate card reader - some commands fail.

Posted: Wed Sep 17, 2008 2:04 am
by Fred
Theo,

Sorry I was so slow. It about slipped my mind. Age does that to you from time to time. :-)

First make a directory in /media called Cardreader if you don't already have one there.

sudo mkdir /media/Cardreader

Then put the below line in your fstab file in place of the one you currently have.

/dev/sdf1 /media/Cardreader vfat umask=0000,uid=1000,gid=1000,auto,rw,users 0 0

Reboot and see if that doesn't work better.

Fred

Re: Please help! Obstinate card reader - some commands fail.

Posted: Wed Sep 17, 2008 7:06 am
by T J Tulley
Thanks again, Fred. Yes - I know about age - celebrating my 90th next week with a close family party - had a large extended-family party in advance a month ago!

I created the required mount point long ago. I've inserted your new line in /etc/fstab - will see result when I boot tomorrow. I wonder whether that will allow boot with card reader connected - so far, it always hangs.

However, it is now mounted automatically after connection, and appears with all its contents belonging to me with permissions 777 - very encouraging. Previously it has reported "Cannot mount - you are not privileged - - - ". Mounted from terminal it used to appear belonging to root with inadequate permissions.

This apparently means that fstab is consulted for a new device, not only at boot.

I've just had a look at /var/log/syslog - that had just given itself a re-start, so the record is in the preceding /syslog.0 - there I see the usual long chronicle of new device added, full of repetitions, but no mention of reference to fstab. Syslog is a curious resource - doesn't record entry of commands, as one might expect.