Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Debian User (http://www.linux-archive.org/debian-user/)
-   -   sid: USB-stick - /dev/disk/by-id/ not populated (http://www.linux-archive.org/debian-user/93550-sid-usb-stick-dev-disk-id-not-populated.html)

Bruno Voigt 05-22-2008 07:16 PM

sid: USB-stick - /dev/disk/by-id/ not populated
 
Hi all,

I have one daily updated sid system running,
which doesn't populate the /dev/disk/by-id/ path
for an connecting USB-stick (w32 FAT)
as it is done by my other sid systems.
(it only shows up as eg /dev/uba1)

I compared the /etc/udev/rules.d/ contents
and they look very similar,
e.g. persistent.rules is identical.

Which rule/file is responsible
for populating the /dev/disk/by-id/ path.

How can I debug what's going on?
I suspect it might be some left over cfg
from older udev-releases or so,
because the system is very old / always being upgraded from sarge/or older.

TIA for any hints,
Bruno



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Florian Kulzer 05-25-2008 11:09 AM

sid: USB-stick - /dev/disk/by-id/ not populated
 
On Thu, May 22, 2008 at 21:16:00 +0200, Bruno Voigt wrote:
> Hi all,
>
> I have one daily updated sid system running,
> which doesn't populate the /dev/disk/by-id/ path
> for an connecting USB-stick (w32 FAT)
> as it is done by my other sid systems.
> (it only shows up as eg /dev/uba1)
>
> I compared the /etc/udev/rules.d/ contents
> and they look very similar,
> e.g. persistent.rules is identical.
>
> Which rule/file is responsible
> for populating the /dev/disk/by-id/ path.

That should be persistent.rules, which you have compared already. Is
this file symlinked in rules.d the same way on the two systems?

> How can I debug what's going on?
> I suspect it might be some left over cfg
> from older udev-releases or so,
> because the system is very old / always being upgraded from sarge/or older.

Has the "hotplug" package been purged (not just removed) on the old
system?

In any case, you can use "udevtest" to see which rules are applied. Here
is an example for a usb stick at /dev/sdc:

$ udevtest /block/sdc | egrep 'persistent.rules|by-id'
parse_file: reading '/etc/udev/rules.d/z20_persistent.rules' as rules file
udev_rules_get_name: add symlink 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device'
udev_node_update_symlinks: update symlink 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device' of '/block/sdc'
udev_db_get_devices_by_name: found index directory '/dev/.udev/names/diskx2fby-idx2fusb-Prolific_Technology_Inc._USB_Mass_Storage_Device'
update_link: found 1 devices with name 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device'
update_link: found '/block/sdc' for 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device'
update_link: 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device' with target 'sdc' has the highest priority 0, create it

And here is what should happen for the first partition (/dev/sdc1/):

$ udevtest /block/sdc/sdc1 | egrep 'persistent.rules|by-id'
parse_file: reading '/etc/udev/rules.d/z20_persistent.rules' as rules file
udev_rules_get_name: add symlink 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1'
udev_node_update_symlinks: update symlink 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1' of '/block/sdc/sdc1'
udev_db_get_devices_by_name: found index directory '/dev/.udev/names/diskx2fby-idx2fusb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1'
update_link: found 1 devices with name 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1'
update_link: found '/block/sdc/sdc1' for 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1'
update_link: 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1' with target 'sdc1' has the highest priority 0, create it

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Bruno Voigt 05-27-2008 10:21 PM

sid: USB-stick - /dev/disk/by-id/ not populated
 
Florian Kulzer wrote:

Thanks for your reply!
> Has the "hotplug" package been purged (not just removed) on the old
> system?
>
Yes, I purged it as advised by the NEWS.
> In any case, you can use "udevtest" to see which rules are applied. Here
> is an example for a usb stick at /dev/sdc:
>
> $ udevtest /block/sdc/sdc1 | egrep 'persistent.rules|by-id'
> parse_file: reading '/etc/udev/rules.d/z20_persistent.rules' as rules file
> udev_rules_get_name: add symlink 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1'
> udev_node_update_symlinks: update symlink 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1' of '/block/sdc/sdc1'
> udev_db_get_devices_by_name: found index directory '/dev/.udev/names/diskx2fby-idx2fusb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1'
> update_link: found 1 devices with name 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1'
> update_link: found '/block/sdc/sdc1' for 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1'
> update_link: 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1' with target 'sdc1' has the highest priority 0, create it
>
>
Only the first line is shown:

root@host:~# udevtest /block/uba/uba1 | egrep 'persistent.rules|by-id'
parse_file: reading '/etc/udev/rules.d/z20_persistent.rules' as rules file

I'm using a selfcompiled kernel 2.6.25.4 (previosuly 2.6.24.4),
are there any special config options needed ?

Here is a excerpt from the syslog after plugging the stick:

May 27 23:47:38 host kernel: usb 1-1: new high speed USB device using
ehci_hcd and address 4
May 27 23:47:38 host kernel: usb 1-1: configuration #1 chosen from 1 choice
May 27 23:47:38 host kernel: uba: uba1
May 27 23:47:38 host kernel: usb 1-1: New USB device found,
idVendor=0781, idProduct=5151
May 27 23:47:38 host kernel: usb 1-1: New USB device strings: Mfr=1,
Product=2, SerialNumber=3
May 27 23:47:38 host kernel: usb 1-1: Product: Cruzer Micro
May 27 23:47:38 host kernel: usb 1-1: Manufacturer: SanDisk Corporation
May 27 23:47:38 host kernel: usb 1-1: SerialNumber: SNDKB749E40AD9708702


WR,
Bruno


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Florian Kulzer 05-28-2008 04:36 PM

sid: USB-stick - /dev/disk/by-id/ not populated
 
On Wed, May 28, 2008 at 00:21:21 +0200, Bruno Voigt wrote:
> Florian Kulzer wrote:

[...]

> > In any case, you can use "udevtest" to see which rules are applied. Here
> > is an example for a usb stick at /dev/sdc:
> >
> > $ udevtest /block/sdc/sdc1 | egrep 'persistent.rules|by-id'
> > parse_file: reading '/etc/udev/rules.d/z20_persistent.rules' as rules file
> > udev_rules_get_name: add symlink 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1'
> > udev_node_update_symlinks: update symlink 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1' of '/block/sdc/sdc1'
> > udev_db_get_devices_by_name: found index directory '/dev/.udev/names/diskx2fby-idx2fusb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1'
> > update_link: found 1 devices with name 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1'
> > update_link: found '/block/sdc/sdc1' for 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1'
> > update_link: 'disk/by-id/usb-Prolific_Technology_Inc._USB_Mass_Storage_Device-part1' with target 'sdc1' has the highest priority 0, create it
> >
> >
> Only the first line is shown:
>
> root@host:~# udevtest /block/uba/uba1 | egrep 'persistent.rules|by-id'
> parse_file: reading '/etc/udev/rules.d/z20_persistent.rules' as rules file

The problem seems to be that the USB stick is recognized as a USB block
device (/dev/ub*) instead of an SCSI disk device (/dev/sd*). The udev
rules do not contain any by-id symlink creation rules for ub* devices.

> I'm using a selfcompiled kernel 2.6.25.4 (previosuly 2.6.24.4),
> are there any special config options needed ?

I would check if the stock Debian 2.6.25 kernel shows the same behavior
for this particular USB stick. If the Debian kernel works normally then
you can diff the result of "grep USB" for the two kernel configuration
files to find out where the problem with your kenel is.

> Here is a excerpt from the syslog after plugging the stick:
>
> May 27 23:47:38 host kernel: usb 1-1: new high speed USB device using
> ehci_hcd and address 4
> May 27 23:47:38 host kernel: usb 1-1: configuration #1 chosen from 1 choice
> May 27 23:47:38 host kernel: uba: uba1
> May 27 23:47:38 host kernel: usb 1-1: New USB device found,
> idVendor=0781, idProduct=5151
> May 27 23:47:38 host kernel: usb 1-1: New USB device strings: Mfr=1,
> Product=2, SerialNumber=3
> May 27 23:47:38 host kernel: usb 1-1: Product: Cruzer Micro
> May 27 23:47:38 host kernel: usb 1-1: Manufacturer: SanDisk Corporation
> May 27 23:47:38 host kernel: usb 1-1: SerialNumber: SNDKB749E40AD9708702

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


All times are GMT. The time now is 12:06 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.