Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: Onyarian on October 19, 2011, 12:08:43 PM
-
The android smartphone's memory card is recognized as SEMC when I connect the phone with USB:
dmesg:
usb 1-1: new high speed USB device using ehci_hcd and address 4
scsi3 : usb-storage 1-1:1.0
scsi 3:0:0:0: Direct-Access SEMC Mass Storage 0100 PQ: 0 ANSI: 2
sd 3:0:0:0: Attached scsi generic sg5 type 0
sd 3:0:0:0: [sdf] Attached SCSI removable disk
but it is not reflected in the mounttool, so I can't mount it
then when I next mount an usb-pendrive, both are recognized in dmesg and are ready to mount in the mounttool, the phone card as sdf1 and the pendrive as sdg1
dmesg:
usb 1-1: new high speed USB device using ehci_hcd and address 4
scsi3 : usb-storage 1-1:1.0
scsi 3:0:0:0: Direct-Access SEMC Mass Storage 0100 PQ: 0 ANSI: 2
sd 3:0:0:0: Attached scsi generic sg5 type 0
sd 3:0:0:0: [sdf] Attached SCSI removable disk
usb 1-5: new high speed USB device using ehci_hcd and address 5
scsi4 : usb-storage 1-5:1.0
scsi 4:0:0:0: Direct-Access Sony MSAC-UAM2 1.00 PQ: 0 ANSI: 0 CCS
sd 4:0:0:0: Attached scsi generic sg6 type 0
sd 4:0:0:0: [sdg] 249856 512-byte logical blocks: (127 MB/122 MiB)
sd 4:0:0:0: [sdg] Write Protect is off
sd 4:0:0:0: [sdg] Mode Sense: 03 00 00 00
sd 4:0:0:0: [sdg] Assuming drive cache: write through
sd 4:0:0:0: [sdg] Assuming drive cache: write through
sdg: sdg1
sd 4:0:0:0: [sdg] Assuming drive cache: write through
sd 4:0:0:0: [sdg] Attached SCSI removable disk
sd 3:0:0:0: [sdf] 15523840 512-byte logical blocks: (7.94 GB/7.40 GiB)
sd 3:0:0:0: [sdf] Assuming drive cache: write through
sd 3:0:0:0: [sdf] Assuming drive cache: write through
sdf: sdf1
I mount it and I can browse in the phone card.
My question is: How can it be recognized automatically by the mounttool when I make the USB connection?
-
Hi Onyarian
Maybe rebuildfstab needs to be called when the card is detected but isn't. I think it might get
called if you click the refresh button in MountTool. Try it and see if it shows up. If not, try running
rebuildfstab from a terminal after plugging the card in, then run MountTool and see if it shows up.
-
Hi Rich,
Thank you, you are right. After the card is detected, the refresh button in MountTool makes nothing, but running rebuildfstab in a terminal then shows up in MountTool.
Do you know if I can put some code somewhere to be showing up in the Mountool without the need to run rebuildfstab?
-
rebuildfstab is normally controlled by udev rules.
Although I could add a call to rebuildfstab to the refresh button in mnttool.
-
Hi Roberts,
it could be a good solution for this kind of cards
I have googled and other people talk about access the SEMC cards across virtualbox, but why if it is detected by dmesg?
-
Hi Onyarian
For a short term solution, two things come to mind.
1. Add or modify an existing udev file and add that to your backup. Since my knowledge of udev
is somewhere between zero and nil, someone else would have to help you with that.
2. Open the file /home/tc/.wmx/SystemTools/MountTool and add a rebuildfstab line right above
the exec mnttool line. Then add that file to your backup.
For method 2 to work, you have to plug your device in and give the system 5 to 10 seconds to
recognize it before calling up MountTool. Messing with .wmx directory might be considered to
be bad form, I don't know.
The dmesg entries are just messages telling you what happened, udev actually controls the actions
to take.
-
Messing with .wmx directory might be considered to be bad form, I don't know.
Hacking dynamic system files to be static will cause much grief.
-
After several attempts I have not gotten it to work with a udev rules (unfortunately I'm not an expert in udev too).
Based on data from the command:
udevadm info -a -p $(udevadm info -q path -n /dev/sdf1)
looking at device '/devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdf/sdf1':
KERNEL=="sdf1"
SUBSYSTEM=="block"
DRIVER==""
ATTR{partition}=="1"
ATTR{start}=="8192"
ATTR{size}=="15515648"
ATTR{ro}=="0"
ATTR{alignment_offset}=="0"
ATTR{discard_alignment}=="0"
ATTR{stat}==" 97 6 824 176 0 0 0 0 0 176 176"
ATTR{inflight}==" 0 0"
looking at parent device '/devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdf':
KERNELS=="sdf"
SUBSYSTEMS=="block"
DRIVERS==""
ATTRS{range}=="16"
ATTRS{ext_range}=="256"
ATTRS{removable}=="1"
ATTRS{ro}=="0"
ATTRS{size}=="15523840"
ATTRS{alignment_offset}=="0"
ATTRS{discard_alignment}=="0"
ATTRS{capability}=="51"
ATTRS{stat}==" 252 9 2088 296 0 0 0 0 0 296 296"
ATTRS{inflight}==" 0 0"
ATTRS{events}=="media_change"
ATTRS{events_async}==""
ATTRS{events_poll_msecs}=="-1"
looking at parent device '/devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0':
KERNELS=="5:0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{device_blocked}=="0"
ATTRS{type}=="0"
ATTRS{scsi_level}=="3"
ATTRS{vendor}=="SEMC "
ATTRS{model}=="Mass Storage "
ATTRS{rev}=="0100"
ATTRS{state}=="running"
ATTRS{timeout}=="30"
ATTRS{iocounterbits}=="32"
ATTRS{iorequest_cnt}=="0x137"
ATTRS{iodone_cnt}=="0x137"
ATTRS{ioerr_cnt}=="0x8"
ATTRS{evt_media_change}=="0"
ATTRS{dh_state}=="detached"
ATTRS{queue_depth}=="1"
ATTRS{queue_type}=="none"
ATTRS{max_sectors}=="240"
looking at parent device '/devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0':
KERNELS=="target5:0:0"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5':
KERNELS=="host5"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0':
KERNELS=="1-1: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{supports_autosuspend}=="1"
looking at parent device '/devices/pci0000:00/0000:00:10.4/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bMaxPower}=="500mA"
ATTRS{urbnum}=="937"
ATTRS{idVendor}=="0fce"
ATTRS{idProduct}=="e156"
ATTRS{bcdDevice}=="0226"
ATTRS{bDeviceClass}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="480"
ATTRS{busnum}=="1"
ATTRS{devnum}=="4"
ATTRS{devpath}=="1"
ATTRS{version}==" 2.00"
ATTRS{maxchild}=="0"
ATTRS{quirks}=="0x0"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="SEMC"
ATTRS{product}=="SEMC HSUSB Device"
ATTRS{serial}=="4258393032454B524145"
looking at parent device '/devices/pci0000:00/0000:00:10.4/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bMaxPower}==" 0mA"
ATTRS{urbnum}=="64"
ATTRS{idVendor}=="1d6b"
ATTRS{idProduct}=="0002"
ATTRS{bcdDevice}=="0300"
ATTRS{bDeviceClass}=="09"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="480"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{devpath}=="0"
ATTRS{version}==" 2.00"
ATTRS{maxchild}=="8"
ATTRS{quirks}=="0x0"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="Linux 3.0.3-tinycore ehci_hcd"
ATTRS{product}=="EHCI Host Controller"
ATTRS{serial}=="0000:00:10.4"
ATTRS{authorized_default}=="1"
looking at parent device '/devices/pci0000:00/0000:00:10.4':
KERNELS=="0000:00:10.4"
SUBSYSTEMS=="pci"
DRIVERS=="ehci_hcd"
ATTRS{vendor}=="0x1106"
ATTRS{device}=="0x3104"
ATTRS{subsystem_vendor}=="0x1106"
ATTRS{subsystem_device}=="0x3104"
ATTRS{class}=="0x0c0320"
ATTRS{irq}=="21"
ATTRS{local_cpus}=="ff"
ATTRS{local_cpulist}=="0-7"
ATTRS{dma_mask_bits}=="32"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{broken_parity_status}=="0"
ATTRS{msi_bus}==""
ATTRS{companion}==""
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
I create the rule:
/etc/udev/rules.d/11-android-semc.rules
KERNELS=="1-1", SUBSYSTEM=="usb", ATTR{product}=="SEMC HSUSB Device", ACTION=="add", RUN+="/usr/sbin/rebuildfstab"
this and similar (with the idVendor and idProduct for example) have failed to recognize it and run rebuildfstab
Any help is welcome.
-
It doesn't seem like udev or rebuildfstab is the issue, from your first post it looks like the phone is slow to recognize.
-
Hi curaga,
I don't think so, because after connect it and wait a lot it is still in the same situation. Only when I run rebuildfstab shows up and I can mount it.
before running rebulidfstab here is the result of lsusb
tc@box:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 047d:1047 Kensington
Bus 004 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 001 Device 004: ID 0fce:e156 Sony Ericsson Mobile Communications AB
and ls -l dev/sd*
tc@box:~$ ls -l /dev/sd*
brw-rw---- 1 root staff 8, 0 Oct 20 20:11 /dev/sda
brw-rw---- 1 root staff 8, 1 Oct 20 20:11 /dev/sda1
brw-rw---- 1 root staff 8, 2 Oct 20 20:11 /dev/sda2
brw-rw---- 1 root staff 8, 3 Oct 20 20:11 /dev/sda3
brw-rw---- 1 root staff 8, 4 Oct 20 20:11 /dev/sda4
brw-r--r-- 1 root root 8, 5 Mar 4 2010 /dev/sda5
brw-r--r-- 1 root root 8, 6 Mar 4 2010 /dev/sda6
brw-r--r-- 1 root root 8, 7 Mar 4 2010 /dev/sda7
brw-r--r-- 1 root root 8, 8 Mar 4 2010 /dev/sda8
brw-r--r-- 1 root root 8, 9 Mar 4 2010 /dev/sda9
brw-rw---- 1 root staff 8, 16 Oct 20 20:11 /dev/sdb
brw-r--r-- 1 root root 8, 17 Mar 4 2010 /dev/sdb1
brw-r--r-- 1 root root 8, 18 Mar 4 2010 /dev/sdb2
brw-r--r-- 1 root root 8, 19 Mar 4 2010 /dev/sdb3
brw-r--r-- 1 root root 8, 20 Mar 4 2010 /dev/sdb4
brw-r--r-- 1 root root 8, 21 Mar 4 2010 /dev/sdb5
brw-r--r-- 1 root root 8, 22 Mar 4 2010 /dev/sdb6
brw-r--r-- 1 root root 8, 23 Mar 4 2010 /dev/sdb7
brw-r--r-- 1 root root 8, 24 Mar 4 2010 /dev/sdb8
brw-r--r-- 1 root root 8, 25 Jul 2 2010 /dev/sdb9
brw-rw---- 1 root staff 8, 32 Oct 20 20:11 /dev/sdc
brw-rw---- 1 root staff 8, 48 Oct 20 20:11 /dev/sdd
brw-rw---- 1 root staff 8, 64 Oct 20 20:11 /dev/sde
brw-rw---- 1 root staff 8, 80 Oct 20 20:11 /dev/sdf
and after running rebuildfstab
tc@box:~$ sudo /usr/sbin/rebuildfstab
tc@box:~$ ls -l /dev/sd*
brw-rw---- 1 root staff 8, 0 Oct 20 20:11 /dev/sda
brw-rw---- 1 root staff 8, 1 Oct 20 20:11 /dev/sda1
brw-rw---- 1 root staff 8, 2 Oct 20 20:11 /dev/sda2
brw-rw---- 1 root staff 8, 3 Oct 20 20:11 /dev/sda3
brw-rw---- 1 root staff 8, 4 Oct 20 20:11 /dev/sda4
brw-r--r-- 1 root root 8, 5 Mar 4 2010 /dev/sda5
brw-r--r-- 1 root root 8, 6 Mar 4 2010 /dev/sda6
brw-r--r-- 1 root root 8, 7 Mar 4 2010 /dev/sda7
brw-r--r-- 1 root root 8, 8 Mar 4 2010 /dev/sda8
brw-r--r-- 1 root root 8, 9 Mar 4 2010 /dev/sda9
brw-rw---- 1 root staff 8, 16 Oct 20 20:11 /dev/sdb
brw-r--r-- 1 root root 8, 17 Mar 4 2010 /dev/sdb1
brw-r--r-- 1 root root 8, 18 Mar 4 2010 /dev/sdb2
brw-r--r-- 1 root root 8, 19 Mar 4 2010 /dev/sdb3
brw-r--r-- 1 root root 8, 20 Mar 4 2010 /dev/sdb4
brw-r--r-- 1 root root 8, 21 Mar 4 2010 /dev/sdb5
brw-r--r-- 1 root root 8, 22 Mar 4 2010 /dev/sdb6
brw-r--r-- 1 root root 8, 23 Mar 4 2010 /dev/sdb7
brw-r--r-- 1 root root 8, 24 Mar 4 2010 /dev/sdb8
brw-r--r-- 1 root root 8, 25 Jul 2 2010 /dev/sdb9
brw-rw---- 1 root staff 8, 32 Oct 20 20:11 /dev/sdc
brw-rw---- 1 root staff 8, 48 Oct 20 20:11 /dev/sdd
brw-rw---- 1 root staff 8, 64 Oct 20 20:11 /dev/sde
brw-rw---- 1 root staff 8, 80 Oct 20 20:48 /dev/sdf
brw-rw---- 1 root staff 8, 81 Oct 20 20:48 /dev/sdf1
-
Yeah, that is definitely weird. Rebuildfstab can't force devices to appear, that's the job of the kernel and udev.
Perhaps your phone doesn't activate until someone tries to scan it - try "sudo blkid /dev/sdf" to see if that makes sdf1 appear too.
-
Yes, you're right.
"sudo blkid /dev/sdf" makes the same as rebuildfstab
tc@box:~$ sudo blkid /dev/sdf
tc@box:~$ ls -l /dev/sd*
brw-rw---- 1 root staff 8, 0 Oct 20 23:52 /dev/sda
brw-rw---- 1 root staff 8, 1 Oct 20 23:52 /dev/sda1
brw-rw---- 1 root staff 8, 2 Oct 20 23:52 /dev/sda2
brw-rw---- 1 root staff 8, 3 Oct 20 23:52 /dev/sda3
brw-rw---- 1 root staff 8, 4 Oct 20 23:52 /dev/sda4
brw-r--r-- 1 root root 8, 5 Mar 4 2010 /dev/sda5
brw-r--r-- 1 root root 8, 6 Mar 4 2010 /dev/sda6
brw-r--r-- 1 root root 8, 7 Mar 4 2010 /dev/sda7
brw-r--r-- 1 root root 8, 8 Mar 4 2010 /dev/sda8
brw-r--r-- 1 root root 8, 9 Mar 4 2010 /dev/sda9
brw-rw---- 1 root staff 8, 16 Oct 20 23:52 /dev/sdb
brw-r--r-- 1 root root 8, 17 Mar 4 2010 /dev/sdb1
brw-r--r-- 1 root root 8, 18 Mar 4 2010 /dev/sdb2
brw-r--r-- 1 root root 8, 19 Mar 4 2010 /dev/sdb3
brw-r--r-- 1 root root 8, 20 Mar 4 2010 /dev/sdb4
brw-r--r-- 1 root root 8, 21 Mar 4 2010 /dev/sdb5
brw-r--r-- 1 root root 8, 22 Mar 4 2010 /dev/sdb6
brw-r--r-- 1 root root 8, 23 Mar 4 2010 /dev/sdb7
brw-r--r-- 1 root root 8, 24 Mar 4 2010 /dev/sdb8
brw-r--r-- 1 root root 8, 25 Jul 2 2010 /dev/sdb9
brw-rw---- 1 root staff 8, 32 Oct 20 23:52 /dev/sdc
brw-rw---- 1 root staff 8, 48 Oct 20 23:52 /dev/sdd
brw-rw---- 1 root staff 8, 64 Oct 20 23:52 /dev/sde
brw-rw---- 1 root staff 8, 80 Oct 20 23:54 /dev/sdf
brw-rw---- 1 root staff 8, 81 Oct 20 23:54 /dev/sdf1
and shows up in the MountTool to be mounted
Do you know if there is any way to automate it?
-
udev rules, I'm afraid.
-
I finally got it.
Thank you all, I learned something about the udev system.
Connecting the android phone via USB, the udev system recognize the first part of the existence of a phone card, then giving the order to phone to connect the card to PC, it previously umount the card from phone, this is the second part which is not recognized by udev until rebuildfstab runs.
Thus the command "RUN+="sudo /usr/sbin/rebuildfstab"" in the rule made no sense until the card is first umounted from the phone.
The solution is to create a command to run rebuildfstab after waiting a few seconds for time to umount the card from the phone.
This command I have called rebuildsemc and whose code is this:
#!/bin/sh
sleep 10
sudo /usr/sbin/rebuildfstab
and the /etc/udev/rules.d/99-android-semc.rules
SUBSYSTEMS=="usb", ATTRS{product}=="SEMC HSUSB Device", ACTION=="add", RUN+="/bin/sh -c '/usr/sbin/rebuildsemc"
Previously, running the command "sudo udevadm monitor" and then connecting the phone the result was the next black code, then running rebuildfstab it completes with the red code. Now, with rebuildsemc, the result is all the code in a few seconds :)
tc@box:~$ sudo udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[74.804532] add /devices/pci0000:00/0000:00:10.4/usb1/1-1 (usb)
KERNEL[74.804596] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0 (usb)
KERNEL[74.805651] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5 (scsi)
KERNEL[74.805700] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/scsi_host/host5 (scsi_host)
KERNEL[75.804633] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0 (scsi)
KERNEL[75.804686] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0 (scsi)
KERNEL[75.804748] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0 (scsi_disk)
KERNEL[75.804870] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0 (scsi_device)
KERNEL[75.805068] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg7 (scsi_generic)
KERNEL[75.805113] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0 (bsg)
KERNEL[75.806720] add /devices/virtual/bdi/8:80 (bdi)
KERNEL[75.806776] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdf (block)
UDEV [75.806805] add /devices/virtual/bdi/8:80 (bdi)
KERNEL[75.808120] change /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdf (block)
UDEV [85.797215] add /devices/pci0000:00/0000:00:10.4/usb1/1-1 (usb)
UDEV [96.334210] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0 (usb)
UDEV [106.868703] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5 (scsi)
UDEV [116.884889] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/scsi_host/host5 (scsi_host)
UDEV [117.936283] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0 (scsi)
UDEV [128.469618] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0 (scsi)
UDEV [138.495277] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0 (scsi_device)
UDEV [138.498279] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0 (bsg)
UDEV [138.499511] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0 (scsi_disk)
UDEV [138.499730] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg7 (scsi_generic)
KERNEL[139.026003] change /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdf (block)
KERNEL[139.026314] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdf/sdf1 (block)
UDEV [140.330358] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdf (block)
UDEV [140.331452] change /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdf (block)
UDEV [140.332367] change /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdf (block)
UDEV [151.650945] add /devices/pci0000:00/0000:00:10.4/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdf/sdf1 (block)
Perhaps it could be a little more polished, but it works!