Mounting Drive to Particular Folder

[gavinjb]

Hi,

I am trying to mount an External HD Drive to a particular folder. I am configuring it in the KDE Disk and File Systems Control Panel If I configure by name if I connect any other when this drive is not connected I get an error as it tries to mount the drive under the same dev devise as ext3 so I thought I would try mounting by UUID, I have told it to mount to a particular folder and selected by UUID and it populates UUID the info, only problem is it seems that only root can mount this, as when I try to mount I get permissions denied error, but it works ok.

I have checked that permissions are set for anyone to mount/dismount the drive


Can anyone please help.


Thanks,


Gavin,

[SheeEttin]

Re: Mounting Drive to Particular Folder

Can you post the whole line?
Also, try adding the options "user,uid=1000,gid=1000".

Also, try not to use Disk & Filesystems. It's been known to mess things up.
As a matter of fact, why not post /etc/fstab to make sure it's not done that already?

[gavinjb]

Re: Mounting Drive to Particular Folder

Hi,

I have just gone into the fstab and added your suggestion to the end, but it still gave me a permission denied error, anyway here is the fstab record for this drive.

UUID=511bf33e-cf5d-4110-a6f3-8f9157d582de /media/Fomalhaut auto users,atime,noauto,rw,dev,exec,suid 0 0

Thanks,


Gavin,

[gavinjb]

Re: Mounting Drive to Particular Folder

I have just tried running ls -l /dev/disk/by-uuid to check I had the right UUID and it looks ok.

total 0
lrwxrwxrwx 1 root root 10 2007-09-30 10:26 0E4E-05D0 -> ../../sda1
lrwxrwxrwx 1 root root 10 2007-09-30 10:26 10b3cbf0-3504-4060-ac5a-ee077fc05f55 -> ../../sda3
lrwxrwxrwx 1 root root 10 2007-09-30 10:26 1f563aca-3504-4e15-ae4a-94f763b14395 -> ../../sda4
lrwxrwxrwx 1 root root 10 2007-09-30 10:26 50a05161-b06f-4d12-88a1-101731b18a9e -> ../../sda2
lrwxrwxrwx 1 root root 10 2007-09-30 10:07 511bf33e-cf5d-4110-a6f3-8f9157d582de -> ../../sdb1

The drive is /dev/sdb1.


Gavin,

[gavinjb]

Re: Mounting Drive to Particular Folder

After doing a bit of search, I think I have found an answer of sorts, it looks like I need to add an udev rule, so I found the following thread http://ubuntuforums.org/showthread.php?t=168221, the only problem is that when I run udevinfo -a -p $(udevinfo -q path -n /dev/sdb) I get entries beginning with ATTRS and not SYSFS as in the example and I also have no BUS entry.

udevinfo -a -p $(udevinfo -q path -n /dev/sdb)

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

 looking at device '/block/sdb':
  KERNEL=="sdb"
  SUBSYSTEM=="block"
  DRIVER==""
  ATTR{stat}=="   103   172   1150   604    6    2    64    12    0   596   616"
  ATTR{size}=="781422768"
  ATTR{removable}=="0"
  ATTR{range}=="16"
  ATTR{dev}=="8:16"

 looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3.1/1-3.1:1.0/host3/target3:0:0/3:0:0:0':
  KERNELS=="3:0:0:0"
  SUBSYSTEMS=="scsi"
  DRIVERS=="sd"
  ATTRS{ioerr_cnt}=="0x0"
  ATTRS{iodone_cnt}=="0x74"
  ATTRS{iorequest_cnt}=="0x74"
  ATTRS{iocounterbits}=="32"
  ATTRS{timeout}=="30"
  ATTRS{state}=="running"
  ATTRS{rev}=="WQ10"
  ATTRS{model}=="HD400LD     "
  ATTRS{vendor}=="SAMSUNG "
  ATTRS{scsi_level}=="3"
  ATTRS{type}=="0"
  ATTRS{queue_type}=="none"
  ATTRS{queue_depth}=="1"
  ATTRS{device_blocked}=="0"
  ATTRS{max_sectors}=="240"

 looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3.1/1-3.1:1.0/host3/target3:0:0':
  KERNELS=="target3:0:0"
  SUBSYSTEMS==""
  DRIVERS==""

 looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3.1/1-3.1:1.0/host3':
  KERNELS=="host3"
  SUBSYSTEMS==""
  DRIVERS==""

 looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3.1/1-3.1:1.0':
  KERNELS=="1-3.1:1.0"
  SUBSYSTEMS=="usb"
  DRIVERS=="usb-storage"
  ATTRS{modalias}=="usb:v07ABpFCFEd0001dc00dsc00dp00ic08isc06ip50"
  ATTRS{bInterfaceProtocol}=="50"
  ATTRS{bInterfaceSubClass}=="06"
  ATTRS{bInterfaceClass}=="08"
  ATTRS{bNumEndpoints}=="02"
  ATTRS{bAlternateSetting}==" 0"
  ATTRS{bInterfaceNumber}=="00"

 looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3.1':
  KERNELS=="1-3.1"
  SUBSYSTEMS=="usb"
  DRIVERS=="usb"
  ATTRS{serial}=="01BC0E47003A"
  ATTRS{product}=="Freecom Hard Drive"
  ATTRS{manufacturer}=="Freecom"
  ATTRS{maxchild}=="0"
  ATTRS{version}==" 2.00"
  ATTRS{devnum}=="6"
  ATTRS{speed}=="480"
  ATTRS{bMaxPacketSize0}=="64"
  ATTRS{bNumConfigurations}=="1"
  ATTRS{bDeviceProtocol}=="00"
  ATTRS{bDeviceSubClass}=="00"
  ATTRS{bDeviceClass}=="00"
  ATTRS{bcdDevice}=="0001"
  ATTRS{idProduct}=="fcfe"
  ATTRS{idVendor}=="07ab"
  ATTRS{bMaxPower}=="500mA"
  ATTRS{bmAttributes}=="c0"
  ATTRS{bConfigurationValue}=="1"
  ATTRS{bNumInterfaces}==" 1"
  ATTRS{configuration}==""

 looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb1/1-3':
  KERNELS=="1-3"
  SUBSYSTEMS=="usb"
  DRIVERS=="usb"
  ATTRS{product}=="USB2.0 Hub"
  ATTRS{maxchild}=="4"
  ATTRS{version}==" 2.00"
  ATTRS{devnum}=="2"
  ATTRS{speed}=="480"
  ATTRS{bMaxPacketSize0}=="64"
  ATTRS{bNumConfigurations}=="1"
  ATTRS{bDeviceProtocol}=="01"
  ATTRS{bDeviceSubClass}=="00"
  ATTRS{bDeviceClass}=="09"
  ATTRS{bcdDevice}=="0702"
  ATTRS{idProduct}=="0606"
  ATTRS{idVendor}=="05e3"
  ATTRS{bMaxPower}=="100mA"
  ATTRS{bmAttributes}=="e0"
  ATTRS{bConfigurationValue}=="1"
  ATTRS{bNumInterfaces}==" 1"
  ATTRS{configuration}==""

 looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb1':
  KERNELS=="usb1"
  SUBSYSTEMS=="usb"
  DRIVERS=="usb"
  ATTRS{serial}=="0000:00:1d.7"
  ATTRS{product}=="EHCI Host Controller"
  ATTRS{manufacturer}=="Linux 2.6.20-16-generic ehci_hcd"
  ATTRS{maxchild}=="8"
  ATTRS{version}==" 2.00"
  ATTRS{devnum}=="1"
  ATTRS{speed}=="480"
  ATTRS{bMaxPacketSize0}=="64"
  ATTRS{bNumConfigurations}=="1"
  ATTRS{bDeviceProtocol}=="01"
  ATTRS{bDeviceSubClass}=="00"
  ATTRS{bDeviceClass}=="09"
  ATTRS{bcdDevice}=="0206"
  ATTRS{idProduct}=="0000"
  ATTRS{idVendor}=="0000"
  ATTRS{bMaxPower}==" 0mA"
  ATTRS{bmAttributes}=="e0"
  ATTRS{bConfigurationValue}=="1"
  ATTRS{bNumInterfaces}==" 1"
  ATTRS{configuration}==""

 looking at parent device '/devices/pci0000:00/0000:00:1d.7':
  KERNELS=="0000:00:1d.7"
  SUBSYSTEMS=="pci"
  DRIVERS=="ehci_hcd"
  ATTRS{msi_bus}==""
  ATTRS{broken_parity_status}=="0"
  ATTRS{modalias}=="pci:v00008086d000027CCsv00001025sd00000094bc0Csc03i20"
  ATTRS{local_cpus}=="ff"
  ATTRS{irq}=="21"
  ATTRS{class}=="0x0c0320"
  ATTRS{subsystem_device}=="0x0094"
  ATTRS{subsystem_vendor}=="0x1025"
  ATTRS{device}=="0x27cc"
  ATTRS{vendor}=="0x8086"

 looking at parent device '/devices/pci0000:00':
  KERNELS=="pci0000:00"
  SUBSYSTEMS==""
  DRIVERS==""

As the drive only seems to mount as sd?1 what do I need to add as Kernel, also if as is suggested in tutorial of entering KERNEL="sd?1" would this interfere with my main HD with Linux on as sda1 is root.

NOTE:
Is there an easy way of giving a drive a label and from then on when mounting the drive it will appear as /media/labelname as this would solve all my problems easily.

Thanks,



Gavin,