ext3 formatted memory stick not automounting

Bug #229883 reported by JP Viljoen
4
Affects Status Importance Assigned to Milestone
usbmount (Ubuntu)
Invalid
Undecided
Rogério Theodoro de Brito

Bug Description

Description: I have a memory stick formatted to ext3 (partition label also marked as ext3), but automounting of it is not taking place.

Expected behaviour: device gets detected and then mounted with write-permissions for the current user

What actually happens: device gets detected, but no action is taken.

Further details:

from syslog:
[ 8004.128283] usb 2-1: new high speed USB device using ehci_hcd and address 11
[ 8004.199427] usb 2-1: configuration #1 chosen from 1 choice
[ 8004.197852] scsi10 : SCSI emulation for USB Mass Storage devices
[ 8004.198564] usb-storage: device found at 11
[ 8004.198568] usb-storage: waiting for device to settle before scanning
[ 8006.704283] usb-storage: device scan complete
[ 8006.698521] scsi 10:0:0:0: Direct-Access KINGMAX USB2.0 Flashdisk 2.00 PQ: 0 ANSI: 2
[ 8006.702007] sd 10:0:0:0: [sdb] 2015231 512-byte hardware sectors (1032 MB)
[ 8006.703438] sd 10:0:0:0: [sdb] Write Protect is off
[ 8006.703442] sd 10:0:0:0: [sdb] Mode Sense: 00 00 00 00
[ 8006.703445] sd 10:0:0:0: [sdb] Assuming drive cache: write through
[ 8006.707999] sd 10:0:0:0: [sdb] 2015231 512-byte hardware sectors (1032 MB)
[ 8006.709435] sd 10:0:0:0: [sdb] Write Protect is off
[ 8006.709438] sd 10:0:0:0: [sdb] Mode Sense: 00 00 00 00
[ 8006.709441] sd 10:0:0:0: [sdb] Assuming drive cache: write through
[ 8006.709447] sdb: sdb1
[ 8006.764430] sd 10:0:0:0: [sdb] Attached SCSI removable disk
[ 8006.764478] sd 10:0:0:0: Attached scsi generic sg2 type 0

root@froztymobile:~# fdisk -l
Disk /dev/sdb: 1031 MB, 1031798272 bytes
255 heads, 63 sectors/track, 125 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x91f72d24

   Device Boot Start End Blocks Id System
/dev/sdb1 * 1 126 1007584 83 Linux

root@froztymobile:~# mount
/dev/sda1 on / type ext3 (rw,relatime,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)
lrm on /lib/modules/2.6.24-16-generic/volatile type tmpfs (rw)
securityfs on /sys/kernel/security type securityfs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)

Revision history for this message
Rogério Theodoro de Brito (rbrito) wrote :

Hi, I am upstream for usbmount.

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 sdb1 in your case)

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) (again, sdb1 in your case, if it has not changed).

Regards, Rogério Brito.

Changed in usbmount (Ubuntu):
assignee: nobody → Rogério Theodoro de Brito (rbrito)
status: New → Incomplete
Changed in usbmount (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.