Need a GURU! Trouble mounting Mass Storage from phone

mrglimm · 01-29-2008, 04:19 PM

Ok can't mount Mass Storage device. Using latest Ubuntu 7.10 Computer shows device but reports "Unable to Mount Media"

cat /proc/scsi/scsi =

Attached devices:
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: HL-DT-ST Model: CD-RW GCE-8483B Rev: 1.04
Type: CD-ROM ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: ATA Model: ST34311A Rev: 6.01
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi11 Channel: 00 Id: 00 Lun: 00
Vendor: Samsung Model: Mass Storage Rev: 2.31
Type: Direct-Access ANSI SCSI revision: 02

DMESG=

Code:

[42937.454173] usb 3-2: USB disconnect, address 20
[42937.458288] scsi 10:0:0:0: rejecting I/O to dead device
[42937.458439] scsi 10:0:0:0: [sdb] READ CAPACITY failed
[42937.458443] scsi 10:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
[42937.458449] scsi 10:0:0:0: [sdb] Sense not available.
[42937.458898] scsi 10:0:0:0: rejecting I/O to dead device
[42937.459036] scsi 10:0:0:0: [sdb] Write Protect is off
[42937.459041] scsi 10:0:0:0: [sdb] Mode Sense: 00 00 00 00
[42937.459044] scsi 10:0:0:0: [sdb] Assuming drive cache: write through
[42937.459444] scsi 10:0:0:0: rejecting I/O to dead device
[42937.463002] scsi 10:0:0:0: rejecting I/O to dead device
[42937.463187] scsi 10:0:0:0: rejecting I/O to dead device
[42937.463728] scsi 10:0:0:0: rejecting I/O to dead device
[42937.463914] scsi 10:0:0:0: rejecting I/O to dead device
[42937.464078] scsi 10:0:0:0: [sdb] READ CAPACITY failed
[42937.464082] scsi 10:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
[42937.464090] scsi 10:0:0:0: [sdb] Sense not available.
[42937.465046] scsi 10:0:0:0: rejecting I/O to dead device
[42937.465210] scsi 10:0:0:0: [sdb] Write Protect is off
[42937.465215] scsi 10:0:0:0: [sdb] Mode Sense: 00 00 00 00
[42937.465218] scsi 10:0:0:0: [sdb] Assuming drive cache: write through
[42937.468319] scsi 10:0:0:0: rejecting I/O to dead device
[42938.738870] usb 3-2: new full speed USB device using uhci_hcd and address 21
[42938.901732] usb 3-2: configuration #1 chosen from 1 choice
[42938.904706] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
[42939.756321] usb 3-2: USB disconnect, address 21
[43200.387557] usb 3-2: new full speed USB device using uhci_hcd and address 22
[43200.551229] usb 3-2: configuration #1 chosen from 1 choice
[43200.554180] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
[43204.409384] usb 3-2: USB disconnect, address 22
[43205.905564] usb 3-2: new full speed USB device using uhci_hcd and address 23
[43206.072441] usb 3-2: configuration #1 chosen from 1 choice
[43206.075483] scsi11 : SCSI emulation for USB Mass Storage devices
[43206.075727] usb-storage: device found at 23
[43206.075731] usb-storage: waiting for device to settle before scanning
[43211.062021] usb-storage: device scan complete
[43211.065003] scsi 11:0:0:0: Direct-Access     Samsung  Mass Storage     2.31 PQ: 0 ANSI: 2
[43211.180191] usb 3-2: reset full speed USB device using uhci_hcd and address 23
[43211.447525] usb 3-2: reset full speed USB device using uhci_hcd and address 23

Manually mounting the device reports "is not a block device" and actually, fdisk does not even show a disk...

Code:

Disk /dev/sda: 4327 MB, 4327464960 bytes
255 heads, 63 sectors/track, 526 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8bc58bc5

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         496     3984088+  83  Linux
/dev/sda2             497         526      240975    5  Extended
/dev/sda5             497         526      240943+  82  Linux swap / Solaris

I'm a little dizzy chasing all the leads around, I thought maybe someone can troubleshoot this with me and explain these outputs to a nooB.
Sorry if I left anything out...

Thanks in advance

anupamsr · 01-29-2008, 06:46 PM

I got the error "is not a block device" once, when I was trying to mount my camera (I wanted to download all the images)

The reason I learned was this: the camera does not provide a frontend to USB. It can be accessed as USB with special commands, but it lacks the hardware to fully support USB (that is why you cannot write on the SD card using Camera).

I don't know if my camera analogy works with your phone. Does it?

maroonbaboon · 01-29-2008, 06:57 PM

Quote:

Originally Posted by anupamsr

It can be accessed as USB with special commands, but it lacks the hardware to fully support USB

I'll believe that. Manufacturer makes buggy hardware and instead of fixing the hardware they put a workaround in the windows driver

I wonder if the manufacturer is allowed to use the official USB logo in such cases?

mrglimm · 01-29-2008, 07:07 PM

Well I know in Windows it mounts regularly through Mass Media driver and accessed like a regular removable usb drive. I've read in prior Ubuntu rev. it worked. I'm wondering if it has something to do with udev...
Also no special driver was required in Windows to acces it, it was a default USB Mass Media driver

maroonbaboon · 01-29-2008, 08:45 PM

OK it sounds like it should work. To check out udev you can get debugging information by setting

udev_log="debug"

in /etc/udev/udev.conf. Maybe compare with what happens with a working Mass Storage device if you have one.

You say there is no /dev/sdb created when you plug the device in?

mrglimm · 01-29-2008, 10:20 PM

Actually yes /dev/sdb is created, but does not show up in fdisk -l The device shows up when I go to Computer, but "Unable to mount media"

Manual mounting just hangs in terminal or "mount: No medium found"

Here's what I don't get, the system acts like it's seeing the device, and gives me an icon with Samsung info, but lsusb says this

Code:

Bus 005 Device 003: ID 148f:2573 Ralink Technology, Corp. 
Bus 005 Device 001: ID 0000:0000  
Bus 002 Device 003: ID 045e:008c Microsoft Corp. Wireless Intellimouse Explorer 2.0
Bus 002 Device 001: ID 0000:0000  
Bus 004 Device 001: ID 0000:0000  
Bus 001 Device 021: ID 05c6:1000 Qualcomm, Inc. 
Bus 001 Device 001: ID 0000:0000  
Bus 003 Device 001: ID 0000:0000

Qualcomm is obviously my phone, but where is the rest maybe? Samsung...Qualcomm....

I also read a bug report (sorry bug number not at hand)
but it said to change the 65.persistent.rules in udev,

Code:

ENV{DEVTYPE}!="disk", ENV{ID_VENDOR}!="Samsung", ENV{DEVNAME}!="/dev/sdb", IMPORT{program}="vol_id --export $tempnode"

How exactly do I debug udev?

maroonbaboon · 01-29-2008, 11:01 PM

If you google the USB ID 05c6:1000 it looks like this ID is for some sort of wireless modem. There are also refs to some 'switch' command (to change how the device is recognised?). All new to me

To see what udev is doing you can edit the config file as suggested and restart the computer (or maybe '/etc/init.d/udev restart' is good enough). I'm not sure where the debug messages show up - maybe in dmesg output, or /var/log/messages.

mrglimm · 01-30-2008, 03:10 AM

Brings up a great point, been messing with Bitpim realizing the NOT connected lsusb output

Bus 005 Device 004: ID 148f:2573 Ralink Technology, Corp.
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 003: ID 045e:008c Microsoft Corp. Wireless Intellimouse Explorer 2.0
Bus 002 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 009: ID 04e8:6640 Samsung Electronics Co., Ltd
Bus 001 Device 001: ID 0000:0000

and when I switch the phone to pc connect like usual...
it changes

Bus 005 Device 004: ID 148f:2573 Ralink Technology, Corp.
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 003: ID 045e:008c Microsoft Corp. Wireless Intellimouse Explorer 2.0
Bus 002 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 010: ID 05c6:1000 Qualcomm, Inc.
Bus 001 Device 001: ID 0000:0000

bitpim finds and detects the first way, with phone un-enabled but plugged in, when hardware says Samsung

gettings discouraged, but it's all interesting anyway, just wish i could figure how to make the left hand talk to the right.