how to mount scsi device - android phone

[ssb]

Hello


How can i do to mount a scsi device ? it is a lg android phone ...

My dmesg shows :

sb 2-2: New USB device found, idVendor=1004, idProduct=618e
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-2: Product: LG Android USB Device
usb 2-2: Manufacturer: LG Electronics Inc.
usb 2-2: SerialNumber: 80A356544042770053
usb 2-2: usb_probe_device
usb 2-2: configuration #1 chosen from 1 choice
usb 2-2: adding 2-2:1.0 (config #1, interface 0)
usb 2-2: adding 2-2:1.1 (config #1, interface 1)
usb 2-2: adding 2-2:1.2 (config #1, interface 2)
usb 2-2: adding 2-2:1.3 (config #1, interface 3)
usb 2-2: adding 2-2:1.4 (config #1, interface 4)
usb-storage 2-2:1.4: usb_probe_interface
usb-storage 2-2:1.4: usb_probe_interface - got id
scsi9 : usb-storage 2-2:1.4
usb 2-2: adding 2-2:1.5 (config #1, interface 5)
drivers/usb/core/inode.c: creating file '003'
scsi 9:0:0:0: Direct-Access GOOGLE Mass Storage ffff PQ: 0 ANSI: 2
sd 9:0:0:0: Attached scsi generic sg6 type 0
sd 9:0:0:0: [sdf] Attached SCSI removable disk

Thank you

[scott32746]

Hello,

With my droid phone it shows up the same way.

You should be able to
# mount /dev/sdf1 /mnt


What I have in my /etc/fstab is :
UUID=6164-6165 /mnt/droid auto noauto,user,exec 0 0

this lets me type "mount /mnt/droid" after hooking up my droid.
To get UUID :
cd /dev/disk/by-uuid
look for sdf1

[KBerger]

Right, you usually need to know which name the system gives to the USB device. In your case pay attention to the [sdf] part in the string I quoted from your log. It is usually "sd(something)" and once configured it can be mounted as /dev/sd(something)1 into to mount point of your choice.

Originally Posted by ssb

sd 9:0:0:0: [sdf] Attached SCSI removable disk

[ssb]

Hello

Thank you for your response

I got a question ... by uuid doesn't show my lg ...

$ cd /dev/disk/by-uuid/
$ ls -lrt
total 0
lrwxrwxrwx 1 root root 10 Jul 16 11:17 72d947e4-91a9-42c8-a11a-d92b72f4efad -> ../../sda1
lrwxrwxrwx 1 root root 10 Jul 16 11:17 23a81245-ae1f-4e33-a554-adbc84443b1a -> ../../sda2

$lsusb
Bus 002 Device 003: ID 1004:618e LG Electronics, Inc.

where can i find uuid ?

thank you

[bruno.taglienti]

try

 blkid

[ssb]

Hello,

Done.

]$ blkid
/dev/sda1: UUID="72d947e4-91a9-42c8-a11a-d92b72f4efad" TYPE="ext4"
/dev/sda2: UUID="23a81245-ae1f-4e33-a554-adbc84443b1a" TYPE="swap"

no info about phone

sorry

[bruno.taglienti]

A simple workaround to assign a unique name to your device is to use udev.
Create a file /etc/udev/rules.d/00-local.rules containing the following line:

KERNEL=="sd[a-z]*",ATTRS{serial}=="80A356544042770053",SYMLINK="droid%n"

(notice that I used the serial number you provided in your post)
When you plug your phone to USB, a symlink /dev/droid1 is created for the physical
device name (in your example /dev/sdf1). This is useful because you can use
the following line in /etc/fstab:

/dev/droid1              /mnt/droid auto noauto,user,exec 0 0

/dev/droid1 points to the physical device name of your phone, whatever it is.

If you want, udev can be used to automatically mount the device.

[scott32746]

Hello,

I try your udev way.
Had to make a little change. In order to get it to see /dev/sdg1 and not /dev/sdg I changed
changed KERNEL=="sd[a-z]*" --to-- KERNEL=="sd[a-z]1"
Then worked great.
thanks for info, I am not up on udev rules.

Here is what I was getting before my change:
[dev]# ll droid
lrwxrwxrwx. 1 root root 3 Jul 16 15:22 droid -> sdg

After change :
ll /dev/droid1
lrwxrwxrwx. 1 root root 4 Jul 16 15:25 /dev/droid1 -> sdg1

[ssb]

Hello,

I have some problem, but something is running ok ...

I've changed:

$cat /etc/udev/rules.d/00-android.rules
SUBSYSTEM=="usb",ATTRS{serial}=="80A35654404277005 3",SYMLINK="droid1"

$cat /etc/fstab
/dev/droid1 /mnt/droid auto noauto,user,exec 0 0

$ ll /dev/droid1
lrwxrwxrwx 1 root root 15 Jul 22 21:28 /dev/droid1 -> bus/usb/002/009

$lsusb
Bus 002 Device 009: ID 1004:618e LG Electronics, Inc.

And then, it seems that rules check ok my phone, but it is not mounted ... why ?

Where can i find "logs" about this process?

Thank you

[scott32746]

Hello,
try this line in your undev

KERNEL=="sd[a-z]1",ATTRS{serial}=="80A35654404277005 3",SYMLINK="droid%n"


Here is the error I am getting when I try it with the SUBSYSTEM line
# mount /mnt/droid
mount: /dev/bus/usb/001/004 is not a block device

Not a block device is why it can not be mounted
Double check your serial number in dmesg
There is no space in my serial number

EAMPLE:
[29985.356563] usb 1-3.4: Manufacturer: Motorola
[29985.356565] usb 1-3.4: SerialNumber:

[ssb]

Hello,

Change,

KERNEL=="sd[a-z]1",ATTRS{serial}=="80A356544042770053",SYMLINK="dr oid%n"

now

there is no /dev/droid

??

---------- Post added at 12:08 PM ---------- Previous post was at 12:06 PM ----------

and

if i change

SUBSYSTEM=="usb",ATTR{idVendor}=="1004",SYMLINK+=" android_adb",MODE="0666"

then

$ll /dev/android_adb
lrwxrwxrwx 1 root root 15 Jul 22 22:06 /dev/android_adb -> bus/usb

$ mount /dev/android_adb /mnt/droid/
mount: /dev/bus/usb/002/019 is not a block device

what am i doing wrong ?

[bruno.taglienti]

Read this:

http://www.reactivated.net/writing_udev_rules.html

[scott32746]

With KERNEL=="sd[a-z]1",ATTRS{serial}=="YOUR_SERIAL_#_FROM_DMESG",SYMLI NK="dr oid%n"
you should see /dev/droid1