Cannot mount Samsung E2370 phone as USB Storage device

[PCXT]

Hello
I'm using Debian since version 5 and I got a problem with mounting phone as USB mass storage.
Computer is Dell D430 notebook, Intel Core2 1.3GHz, 2GB RAM, running Jessie with the latest updates.
So if I plug any USB mass storage device in, the system detects it, and it pops in my /dev/... as some filesystem device like sd?? or mmc*. Then I can mount it or make my desktop environment mount it. Everything works fine.
Any mass storage device... except my cell phone. It's Samsung Solid E2370 configured to work as "Mass Storage". In my older machine with WinXP, it just shows a drive using generic USB mass storage driver. In Linux, I can't mount the device which becomes available in /dev/ as /dev/sdf with partition /dev/sdf1. After

Code: Select all

sudo mount /dev/sdf1 /media/tel

the console freezes (permissions to directory are OK, directory exists, I can mount any flash drive there).

In lsusb the phone shows as:

Code: Select all

Bus 004 Device 015: ID 04e8:681e Samsung Electronics Co., Ltd

And here's the /var/log/kern.log after plugging it in. About 19:11:20 mount command has been announced:

Code: Select all

Feb 10 19:10:56 user kernel: [ 8898.500141] usb 4-8.1: new full-speed USB device number 14 using ehci-pci
Feb 10 19:10:56 user kernel: [ 8898.504615] usb 4-8: clear tt 1 (8000) error -32
Feb 10 19:10:56 user kernel: [ 8898.508726] usb 4-8: clear tt 1 (8000) error -32
Feb 10 19:10:56 user kernel: [ 8898.512967] usb 4-8: clear tt 1 (8000) error -32
Feb 10 19:10:58 user kernel: [ 8899.780084] usb 4-8.1: new full-speed USB device number 15 using ehci-pci
Feb 10 19:10:58 user kernel: [ 8899.884226] usb 4-8.1: New USB device found, idVendor=04e8, idProduct=681e
Feb 10 19:10:58 user kernel: [ 8899.884239] usb 4-8.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 10 19:10:58 user kernel: [ 8899.884246] usb 4-8.1: Product: USB MMC Storag
Feb 10 19:10:58 user kernel: [ 8899.884253] usb 4-8.1: Manufacturer: SAMSUNG Electronics Co.,Ltd
Feb 10 19:10:58 user kernel: [ 8899.884971] usb-storage 4-8.1:1.0: USB Mass Storage device detected
Feb 10 19:10:58 user kernel: [ 8899.885812] scsi5 : usb-storage 4-8.1:1.0
Feb 10 19:10:59 user kernel: [ 8900.886533] scsi 5:0:0:0: Direct-Access     Samsung  E2370   0        USB  PQ: 0 ANSI: 0 CCS
Feb 10 19:10:59 user kernel: [ 8900.887451] sd 5:0:0:0: Attached scsi generic sg6 type 0
Feb 10 19:10:59 user kernel: [ 8900.924859] sd 5:0:0:0: [sdf] 3862528 512-byte logical blocks: (1.97 GB/1.84 GiB)
Feb 10 19:10:59 user kernel: [ 8900.927732] sd 5:0:0:0: [sdf] Write Protect is off
Feb 10 19:10:59 user kernel: [ 8900.927737] sd 5:0:0:0: [sdf] Mode Sense: 43 00 00 00
Feb 10 19:10:59 user kernel: [ 8900.930614] sd 5:0:0:0: [sdf] No Caching mode page found
Feb 10 19:10:59 user kernel: [ 8900.930622] sd 5:0:0:0: [sdf] Assuming drive cache: write through
Feb 10 19:10:59 user kernel: [ 8900.947245]  sdf: sdf1
Feb 10 19:10:59 user kernel: [ 8900.958131] sd 5:0:0:0: [sdf] Attached SCSI removable disk
Feb 10 19:11:30 user kernel: [ 8931.888086] usb 4-8.1: reset full-speed USB device number 15 using ehci-pci
Feb 10 19:12:01 user kernel: [ 8962.984096] usb 4-8.1: reset full-speed USB device number 15 using ehci-pci
Feb 10 19:12:32 user kernel: [ 8993.968079] usb 4-8.1: reset full-speed USB device number 15 using ehci-pci
Feb 10 19:13:03 user kernel: [ 9024.936069] usb 4-8.1: reset full-speed USB device number 15 using ehci-pci
Feb 10 19:13:34 user kernel: [ 9055.920097] usb 4-8.1: reset full-speed USB device number 15 using ehci-pci
Feb 10 19:14:05 user kernel: [ 9086.888059] usb 4-8.1: reset full-speed USB device number 15 using ehci-pci
Feb 10 19:14:05 user kernel: [ 9086.983501] sd 5:0:0:0: [sdf] Unhandled error code
Feb 10 19:14:05 user kernel: [ 9086.983511] sd 5:0:0:0: [sdf]
Feb 10 19:14:05 user kernel: [ 9086.983514] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
Feb 10 19:14:05 user kernel: [ 9086.983518] sd 5:0:0:0: [sdf] CDB:
Feb 10 19:14:05 user kernel: [ 9086.983521] Read(10): 28 00 00 00 00 80 00 00 f0 00
Feb 10 19:14:05 user kernel: [ 9086.983534] end_request: I/O error, dev sdf, sector 128
Feb 10 19:14:05 user kernel: [ 9086.983541] quiet_error: 8 callbacks suppressed
Feb 10 19:14:05 user kernel: [ 9086.983545] Buffer I/O error on device sdf, logical block 16
Feb 10 19:14:05 user kernel: [ 9086.983552] Buffer I/O error on device sdf, logical block 17
Feb 10 19:14:05 user kernel: [ 9086.983556] Buffer I/O error on device sdf, logical block 18
Feb 10 19:14:05 user kernel: [ 9086.983559] Buffer I/O error on device sdf, logical block 19
Feb 10 19:14:05 user kernel: [ 9086.983563] Buffer I/O error on device sdf, logical block 20
Feb 10 19:14:05 user kernel: [ 9086.983566] Buffer I/O error on device sdf, logical block 21
Feb 10 19:14:05 user kernel: [ 9086.983570] Buffer I/O error on device sdf, logical block 22
Feb 10 19:14:05 user kernel: [ 9086.983573] Buffer I/O error on device sdf, logical block 23
Feb 10 19:14:05 user kernel: [ 9086.983576] Buffer I/O error on device sdf, logical block 24
Feb 10 19:14:05 user kernel: [ 9086.983580] Buffer I/O error on device sdf, logical block 25
Feb 10 19:14:36 user kernel: [ 9117.936091] usb 4-8.1: reset full-speed USB device number 15 using ehci-pci
Feb 10 19:15:07 user kernel: [ 9148.968087] usb 4-8.1: reset full-speed USB device number 15 using ehci-pci
Feb 10 19:15:21 user kernel: [ 9162.979267] usb 4-8: clear tt 1 (90f1) error -32
Feb 10 19:15:21 user kernel: [ 9162.993138] usb 4-8.1: USB disconnect, device number 15
Feb 10 19:15:21 user kernel: [ 9162.996058] scsi 5:0:0:0: rejecting I/O to offline device
Feb 10 19:15:21 user kernel: [ 9162.996071] scsi 5:0:0:0: [sdf] killing request
Feb 10 19:15:21 user kernel: [ 9162.996096] scsi 5:0:0:0: [sdf] Unhandled error code
Feb 10 19:15:21 user kernel: [ 9162.996100] scsi 5:0:0:0: [sdf]
Feb 10 19:15:21 user kernel: [ 9162.996104] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Feb 10 19:15:21 user kernel: [ 9162.996107] scsi 5:0:0:0: [sdf] CDB:
Feb 10 19:15:21 user kernel: [ 9162.996110] Read(10): 28 00 00 00 01 70 00 00 90 00
Feb 10 19:15:21 user kernel: [ 9162.996123] end_request: I/O error, dev sdf, sector 368
Feb 10 19:15:21 user kernel: [ 9162.996129] quiet_error: 20 callbacks suppressed
Feb 10 19:15:21 user kernel: [ 9162.996132] Buffer I/O error on device sdf, logical block 46
Feb 10 19:15:21 user kernel: [ 9162.996142] Buffer I/O error on device sdf, logical block 47
Feb 10 19:15:21 user kernel: [ 9162.996145] Buffer I/O error on device sdf, logical block 48
Feb 10 19:15:21 user kernel: [ 9162.996148] Buffer I/O error on device sdf, logical block 49
Feb 10 19:15:21 user kernel: [ 9162.996152] Buffer I/O error on device sdf, logical block 50
Feb 10 19:15:21 user kernel: [ 9162.996155] Buffer I/O error on device sdf, logical block 51
Feb 10 19:15:21 user kernel: [ 9162.996158] Buffer I/O error on device sdf, logical block 52
Feb 10 19:15:21 user kernel: [ 9162.996162] Buffer I/O error on device sdf, logical block 53
Feb 10 19:15:21 user kernel: [ 9162.996165] Buffer I/O error on device sdf, logical block 54
Feb 10 19:15:21 user kernel: [ 9162.996168] Buffer I/O error on device sdf, logical block 55

In Windows, quick check with chkdsk does not reveal any FAT errors on phone's SD card. All files are readable so card seems to be OK.

How to mount this device?

[bw123]

Don't know, what filesystem is it? fdisk -l or so should tell, is it an older mmc or sd card? is it some sdxc format?

[PCXT]

fdisk -l doesn't return information, but hangs when it is about to detect sdf.
It's a microSD 2GB card formatted to FAT, mountable when put into adapter and connected through SD card reader.

[arzgi]

Maybe jmptfs would help?

[pylkko]

There are many threads on this forum in which the different ways and protocols (mtp adb etc) used to connect phones are discussed. Maybe look at those. Also make sure that android is allowing access to storage


Also consider connecting over WiFi instead

[PCXT]

This is not Android phone, it is running its own relatively simple system. There is no MTP/PTP or wi-fi in this phone. For USB connection, it can operate as "Mass Storage" or "PC Studio".
The "PC Studio" option opens a virtual COM port for e.g. syncing contacts, but it's probably not documented. I always used mass storage.

I think that it some way reads damaged data from the phone and fails to get all information about filesystem from it.