USB volumes not mounting... what's missing?

Andrey Borzenkov arvidjaar at mail.ru
Sat Nov 11 20:49:12 PST 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 10 November 2006 12:46, Simon Geard wrote:
> I'm trying to make a USB stick automount on a new LFS system, but HAL
> doesn't seem to be acquiring all the info it should have. Udev creates
> the device node which can be mounted by hand.
>
> Running udevmonitor produces the following when the device is plugged
> in:
[...]
> hotplug.c:168:
> /sys/devices/pci0000:00/0000:00:02.2/usb3/3-5/3-5:1.0/host6/target6:0:0/6:0
>:0:0 is a bus device (subsystem) 21:16:27.625 [I] physdev.c:1583: phys_add:
> subsys=scsi
> sysfs_path=/sys/devices/pci0000:00/0000:00:02.2/usb3/3-5/3-5:1.0/host6/targ
>et6:0:0/6:0:0:0, parent=0x08160ce0 21:16:27.625 [E] util.c:362: Cannot open
> '/sys/devices/pci0000:00/0000:00:02.2/usb3/3-5/3-5:1.0/host6/target6:0:0/6:
>0:0:0/model' 21:16:27.625 [E] util.c:362: Cannot open
> '/sys/devices/pci0000:00/0000:00:02.2/usb3/3-5/3-5:1.0/host6/target6:0:0/6:
>0:0:0/vendor' 21:16:27.625 [E] util.c:170: Cannot open
> '/sys/devices/pci0000:00/0000:00:02.2/usb3/3-5/3-5:1.0/host6/target6:0:0/6:
>0:0:0/type' 21:16:27.625 [I]
> physdev.c:675:
> /sys/devices/pci0000:00/0000:00:02.2/usb3/3-5/3-5:1.0/host6/target6:0:0/6:0
>:0:0/type -> -1082059736 (-> scsi.type)
[...]
> 21:16:27.720 [I] blockdev.c:637: block_add: sysfs_path=/sys/block/sdb
> dev=/dev/sdb is_part=0, parent=0x08160ba0
> 21:16:27.720 [I] blockdev.c:951: parent_bus is scsi
> 21:16:27.720 [W] blockdev.c:990: scsi.type is unknown
> 21:16:27.720 [W] blockdev.c:1151: Not adding device object
[...]
>
> Some experimenting suggests hald-probe-storage isn't getting called when
> HAL sees the memory stick... not sure how important this is?
>


It is but HAL can't read type and other attributes of your memory stick. Wat 
is the content 
of /sys/devices/pci0000:00/0000:00:02.2/usb3/3-5/3-5:1.0/host6/target6:0:0/6:0:0:0? 
It is possible that device needs more time to initialize, so adding 
WAIT_FOR_SYSFS somewhere may help; current udev should have something like

{pts/1}% cat /etc/udev/rules.d/05-udev-early.rules
# sysfs is populated after the event is sent
ACTION=="add", SUBSYSTEM=="scsi", WAIT_FOR_SYSFS="ioerr_cnt"

do you have similar?

- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFVqfJR6LMutpd94wRAnuVAKClccY1cYKpK/z8k2QPmPYpOxnyRACfZ5gA
ylX4BxVChR8H6hEqyomYzoY=
=tG61
-----END PGP SIGNATURE-----


More information about the hal mailing list