Bug #189220 “Usbmount not showing mounted partitions to mount” : Bugs : usbmount package : Ubuntu

Revision history for this message

Rogério Theodoro de Brito (rbrito) wrote on 2008-10-19:

#1

Hi, I am upstream for usbmount. Please, see bug #229883.

Do you have HAL running? Any gnome or kde thing automounting devices?

If not, could you please use the following command to see what udev would do with your device:

udevadm test --action=add /sys/class/block/sda1 (or whatever)

It generates *a lot* of output. Many screens, depending on the device.

Another good diagnostic tool would be the following:

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

Regards, Rogério Brito.

Revision history for this message

marc (marc-teclliure) wrote on 2008-10-31: Re: [Bug 189220] Re: Usbmount not showing mounted partitions to mount

#2

Download full text (8.7 KiB)

El dom, 19-10-2008 a las 14:54 +0000, Rogério Brito escribió:
> Hi, I am upstream for usbmount. Please, see bug #229883.
>
> Do you have HAL running? Any gnome or kde thing automounting devices?

Yes, i've HAL running. No GNOME or KDE installed.

> If not, could you please use the following command to see what udev
> would do with your device:
>
> udevadm test --action=add /sys/class/block/sda1 (or whatever)
>
> It generates *a lot* of output. Many screens, depending on the device.

root@sbg-ajuntament:~# udevadm test --action=add /sys/class/block/sdc1
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

parse_file: reading '/etc/udev/rules.d/05-options.rules' as rules file
parse_file: reading '/etc/udev/rules.d/05-udev-early.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/20-names.rules' as rules file
parse_file: reading '/etc/udev/rules.d/30-cdrom_id.rules' as rules file
parse_file: reading '/etc/udev/rules.d/40-basic-permissions.rules' as
rules file
parse_file: reading '/etc/udev/rules.d/40-permissions.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/45-fuse.rules' as rules file
parse_file: reading '/etc/udev/rules.d/60-persistent-input.rules' as
rules file
parse_file: reading '/etc/udev/rules.d/60-persistent-storage-tape.rules'
as rules file
parse_file: reading '/etc/udev/rules.d/60-persistent-storage.rules' as
rules file
parse_file: reading '/etc/udev/rules.d/60-symlinks.rules' as rules file
parse_file: reading '/etc/udev/rules.d/61-persistent-storage-edd.rules'
as rules file
parse_file: reading '/etc/udev/rules.d/65-mdadm.vol_id.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/70-persistent-cd.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/70-persistent-net.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/75-cd-aliases-generator.rules' as
rules file
parse_file: reading
'/etc/udev/rules.d/75-persistent-net-generator.rules' as rules file
parse_file: reading '/etc/udev/rules.d/80-programs.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-alsa.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-hdparm.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-hwclock.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-ifupdown.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-mdadm.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-pcmcia.rules' as rules file
parse_file: reading '/etc/udev/rules.d/90-modprobe.rules' as rules file
parse_file: reading '/etc/udev/rules.d/95-hal.rules' as rules file
parse_file: reading '/etc/udev/rules.d/95-udev-late.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z60_usbmount.rules' as rules file
unable to open device '/class/block/sdc1'

> Another good diagnostic tool would be the following:
>
> udevinfo -a -p $(udevinfo -q path -n /dev/sda1) (idem)

root@sbg-ajuntament:~# udevinfo -a -p $(udevinfo -q path -n /dev/sdc1)

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prin...

El dom, 19-10-2008 a las 14:54 +0000, Rogério Brito escribió: 
> Hi, I am upstream for usbmount. Please, see bug #229883.
> 
> Do you have HAL running? Any gnome or kde thing automounting devices?

Yes, i've HAL running. No GNOME or KDE installed.

> If not, could you please use the following command to see what udev
> would do with your device:
> 
> udevadm test --action=add /sys/class/block/sda1 (or whatever)
> 
> It generates *a lot* of output. Many screens, depending on the device.

root@sbg-ajuntament:~# udevadm test --action=add /sys/class/block/sdc1
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

parse_file: reading '/etc/udev/rules.d/05-options.rules' as rules file
parse_file: reading '/etc/udev/rules.d/05-udev-early.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/20-names.rules' as rules file
parse_file: reading '/etc/udev/rules.d/30-cdrom_id.rules' as rules file
parse_file: reading '/etc/udev/rules.d/40-basic-permissions.rules' as
rules file
parse_file: reading '/etc/udev/rules.d/40-permissions.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/45-fuse.rules' as rules file
parse_file: reading '/etc/udev/rules.d/60-persistent-input.rules' as
rules file
parse_file: reading '/etc/udev/rules.d/60-persistent-storage-tape.rules'
as rules file
parse_file: reading '/etc/udev/rules.d/60-persistent-storage.rules' as
rules file
parse_file: reading '/etc/udev/rules.d/60-symlinks.rules' as rules file
parse_file: reading '/etc/udev/rules.d/61-persistent-storage-edd.rules'
as rules file
parse_file: reading '/etc/udev/rules.d/65-mdadm.vol_id.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/70-persistent-cd.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/70-persistent-net.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/75-cd-aliases-generator.rules' as
rules file
parse_file: reading
'/etc/udev/rules.d/75-persistent-net-generator.rules' as rules file
parse_file: reading '/etc/udev/rules.d/80-programs.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-alsa.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-hdparm.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-hwclock.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-ifupdown.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-mdadm.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-pcmcia.rules' as rules file
parse_file: reading '/etc/udev/rules.d/90-modprobe.rules' as rules file
parse_file: reading '/etc/udev/rules.d/95-hal.rules' as rules file
parse_file: reading '/etc/udev/rules.d/95-udev-late.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z60_usbmount.rules' as rules file
unable to open device '/class/block/sdc1'

> Another good diagnostic tool would be the following:
> 
> udevinfo -a -p $(udevinfo -q path -n /dev/sda1) (idem)

root@sbg-ajuntament:~# udevinfo -a -p $(udevinfo -q path -n /dev/sdc1)

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/sdc/sdc1':
    KERNEL=="sdc1"
    SUBSYSTEM=="block"
    DRIVER==""
    ATTR{dev}=="8:33"
    ATTR{start}=="63"
    ATTR{size}=="976768002"
    ATTR{stat}=="18090600 403056096 91848243 734783800"

looking at parent device '/block/sdc':
    KERNELS=="sdc"
    SUBSYSTEMS=="block"
    DRIVERS==""
    ATTRS{dev}=="8:32"
    ATTRS{range}=="16"
    ATTRS{removable}=="0"
    ATTRS{size}=="976773168"
    ATTRS{stat}=="16512534  1578225 403057816 155993970 30539872
61307870 734786456 847550580        0 128924260 1003549200"
    ATTRS{capability}=="12"

looking at parent device
'/devices/pci0000:00/0000:00:1d.7/usb5/5-4/5-4:1.0/host4/target4:0:0/4:0:0:0':
    KERNELS=="4:0:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS=="sd"
    ATTRS{device_blocked}=="0"
    ATTRS{type}=="0"
    ATTRS{scsi_level}=="3"
    ATTRS{vendor}=="ST350083"
    ATTRS{model}=="0AS             "
    ATTRS{rev}=="    "
    ATTRS{state}=="running"
    ATTRS{timeout}=="30"
    ATTRS{iocounterbits}=="32"
    ATTRS{iorequest_cnt}=="0x2cdf67d"
    ATTRS{iodone_cnt}=="0x2cdf67d"
    ATTRS{ioerr_cnt}=="0x0"
    ATTRS{modalias}=="scsi:t-0x00"
    ATTRS{evt_media_change}=="0"
    ATTRS{queue_depth}=="1"
    ATTRS{queue_type}=="none"
    ATTRS{max_sectors}=="240"

looking at parent device
'/devices/pci0000:00/0000:00:1d.7/usb5/5-4/5-4:1.0/host4/target4:0:0':
    KERNELS=="target4:0:0"
    SUBSYSTEMS==""
    DRIVERS==""

looking at parent device
'/devices/pci0000:00/0000:00:1d.7/usb5/5-4/5-4:1.0/host4':
    KERNELS=="host4"
    SUBSYSTEMS==""
    DRIVERS==""

looking at parent device
'/devices/pci0000:00/0000:00:1d.7/usb5/5-4/5-4:1.0':
    KERNELS=="5-4:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb-storage"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{bNumEndpoints}=="02"
    ATTRS{bInterfaceClass}=="08"
    ATTRS{bInterfaceSubClass}=="06"
    ATTRS{bInterfaceProtocol}=="50"
    ATTRS{modalias}=="usb:v059Fp1010dC683dc00dsc00dp00ic08isc06ip50"
    ATTRS{interface}=="Bulk Only Interface"

looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb5/5-4':
    KERNELS=="5-4"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{dev}=="189:514"
    ATTRS{configuration}=="Bulk Only Configuration"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bmAttributes}=="c0"
    ATTRS{bMaxPower}=="  2mA"
    ATTRS{urbnum}=="227760827"
    ATTRS{idVendor}=="059f"
    ATTRS{idProduct}=="1010"
    ATTRS{bcdDevice}=="c683"
    ATTRS{bDeviceClass}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{speed}=="480"
    ATTRS{busnum}=="5"
    ATTRS{devnum}=="3"
    ATTRS{version}==" 2.00"
    ATTRS{maxchild}=="0"
    ATTRS{quirks}=="0x0"
    ATTRS{authorized}=="1"
    ATTRS{manufacturer}=="LaCie"
    ATTRS{product}=="LaCie Desktop Hard Drive"
    ATTRS{serial}=="ST3500830A            9QG617ZE"

looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb5':
    KERNELS=="usb5"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{dev}=="189:512"
    ATTRS{configuration}==""
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bmAttributes}=="e0"
    ATTRS{bMaxPower}=="  0mA"
    ATTRS{urbnum}=="53"
    ATTRS{idVendor}=="0000"
    ATTRS{idProduct}=="0000"
    ATTRS{bcdDevice}=="0206"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="01"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{speed}=="480"
    ATTRS{busnum}=="5"
    ATTRS{devnum}=="1"
    ATTRS{version}==" 2.00"
    ATTRS{maxchild}=="8"
    ATTRS{quirks}=="0x0"
    ATTRS{authorized}=="1"
    ATTRS{manufacturer}=="Linux 2.6.24-21-server ehci_hcd"
    ATTRS{product}=="EHCI Host Controller"
    ATTRS{serial}=="0000:00:1d.7"
    ATTRS{authorized_default}=="1"

looking at parent device '/devices/pci0000:00/0000:00:1d.7':
    KERNELS=="0000:00:1d.7"
    SUBSYSTEMS=="pci"
    DRIVERS=="ehci_hcd"
    ATTRS{vendor}=="0x8086"
    ATTRS{device}=="0x268c"
    ATTRS{subsystem_vendor}=="0x1025"
    ATTRS{subsystem_device}=="0x268c"
    ATTRS{class}=="0x0c0320"
    ATTRS{irq}=="17"
    ATTRS{local_cpus}=="00000000,00000000"

ATTRS{modalias}=="pci:v00008086d0000268Csv00001025sd0000268Cbc0Csc03i20"
    ATTRS{numa_node}=="-1"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""

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

It seems all data is ok, no ?

BTW mount command don't show the device:

root@sbg-ajuntament:~# mount
/dev/md0 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/md1 on /home type xfs (rw)
securityfs on /sys/kernel/security type securityfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)

But it is mounted on:

/var/run/usbmount/ST350083_0AS_1/

Thaks.

-- 
"Si has construido un castillo en el aire, no has perdido el tiempo, es
allí donde debería estar. Ahora debes construir los cimientos debajo de
él." - George Bernard Shaw, escritor irlandés

Marc Montañés   *   mail: marc@teclliure.net   *   telf: 622216489

Revision history for this message

Daniel T Chen (crimsun) wrote on 2008-11-28:

#3

Is this symptom still reproducible in 9.04?

Changed in usbmount:
status:	New → Incomplete

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2009-01-14:

#4

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in usbmount:
status:	Incomplete → Invalid

Ubuntu
usbmount package

Usbmount not showing mounted partitions to mount

Bug Description

Other bug subscribers

Remote bug watches

Ubuntuusbmount package

Usbmount not showing mounted partitions to mount

Bug Description

Other bug subscribers

Remote bug watches

Ubuntu
usbmount package