cannot copy from nokia 5200 mass storage device

Bug #129502 reported by Soos Gergely
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
usbmount (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I recently bought a Nokia 5200 phone with a microSD card.
If I plug it into USB I can copy files on it and the phone can read those files correctly but I cannot copy them back to my hard disk.
If I connect the phone in "Printing & media" mode I can download the files using KDE's camera:// protocol (which automatically pops up).
Here is what dmesg lists when the error occures:

[ 2263.183529] usb 3-2: new full speed USB device using uhci_hcd and address 8
[ 2263.360484] usb 3-2: configuration #1 chosen from 1 choice
[ 2263.362525] scsi1 : SCSI emulation for USB Mass Storage devices
[ 2263.362674] usb-storage: device found at 8
[ 2263.362676] usb-storage: waiting for device to settle before scanning
[ 2268.358672] usb-storage: device scan complete
[ 2268.361691] scsi 1:0:0:0: Direct-Access Nokia Nokia 5200 0000 PQ: 0 ANSI: 4
[ 2268.366631] SCSI device sda: 2012161 512-byte hdwr sectors (1030 MB)
[ 2268.369641] sda: Write Protect is off
[ 2268.369647] sda: Mode Sense: 03 00 00 00
[ 2268.369649] sda: assuming drive cache: write through
[ 2268.381885] SCSI device sda: 2012161 512-byte hdwr sectors (1030 MB)
[ 2268.384640] sda: Write Protect is off
[ 2268.384647] sda: Mode Sense: 03 00 00 00
[ 2268.384649] sda: assuming drive cache: write through
[ 2268.384656] sda: sda1
[ 2268.811452] sd 1:0:0:0: Attached scsi removable disk sda
[ 2268.811501] sd 1:0:0:0: Attached scsi generic sg0 type 0
[ 2283.756874] usb 3-2: reset full speed USB device using uhci_hcd and address 8
[ 2283.876811] usb 3-2: device descriptor read/64, error -71
[ 2284.100703] usb 3-2: device descriptor read/64, error -71
[ 2284.316591] usb 3-2: reset full speed USB device using uhci_hcd and address 8
[ 2284.436524] usb 3-2: device descriptor read/64, error -71
[ 2284.660413] usb 3-2: device descriptor read/64, error -71
[ 2284.876308] usb 3-2: reset full speed USB device using uhci_hcd and address 8
[ 2285.284073] usb 3-2: device not accepting address 8, error -71
[ 2285.340095] usb 3-2: USB disconnect, address 8
[ 2285.340547] sd 1:0:0:0: SCSI error: return code = 0x00010000
[ 2285.340551] end_request: I/O error, dev sda, sector 2000864
[ 2285.340579] Buffer I/O error on device sda1, logical block 569
[ 2285.340582] lost page write due to I/O error on sda1
[ 2285.340599] sd 1:0:0:0: SCSI error: return code = 0x00010000
[ 2285.340602] end_request: I/O error, dev sda, sector 2001104
[ 2285.354554] scsi 1:0:0:0: rejecting I/O to dead device
[ 2285.356307] scsi 1:0:0:0: rejecting I/O to dead device
[ 2285.356403] scsi 1:0:0:0: rejecting I/O to dead device
[ 2285.356468] scsi 1:0:0:0: rejecting I/O to dead device
[ 2285.356473] scsi 1:0:0:0: rejecting I/O to dead device
[ 2285.356478] sda : READ CAPACITY failed.
[ 2285.356479] sda : status=0, message=00, host=1, driver=00
[ 2285.356481] sda : sense not available.
[ 2285.356486] scsi 1:0:0:0: rejecting I/O to dead device
[ 2285.356490] sda: Write Protect is off
[ 2285.356492] sda: Mode Sense: 00 00 00 00
[ 2285.356494] sda: assuming drive cache: write through
[ 2291.728753] usb 3-2: new full speed USB device using uhci_hcd and address 9
[ 2291.907672] usb 3-2: configuration #1 chosen from 1 choice
[ 2291.988647] drivers/usb/class/cdc-acm.c: Ignoring extra header, type -3, length 4
[ 2291.988664] cdc_acm 3-2:1.1: ttyACM0: USB ACM device
[ 2304.510144] scsi 1:0:0:0: rejecting I/O to dead device
[ 2304.510550] FAT: unable to read inode block for updating (i_pos 9108)
[ 2310.886852] usb 3-2: USB disconnect, address 9

As you can see, when I start copying the kernel keeps resetting the USB device up to the point where the phone disconnects itself (at 2285.340095) and goes into the third usb mode, which is the USB ACM device. I can copy only the first 64kb.
The last disconnect at 2310.886852 appeared because I unplugged the USB cable.

I use Ubuntu Feisty, every package is up to date.

Revision history for this message
Soos Gergely (sogerc1) wrote :

I would like to add that today I tried to download from the phone a large file (344Mb) in "Printing & media" mode and it did not work. For a long time the KDE's copy window said that the copying is Stalled then the window just disappeared without copying anything. Only small files can be downloaded.

I checked the phone with an M$ vindoze and the phone works perfectly with that as a mass storage device.

Revision history for this message
wolfger (wolfger) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested at https://help.ubuntu.com/community/DebuggingUSBStorage as separate attachments.

Revision history for this message
Soos Gergely (sogerc1) wrote :

The following command solves the problem:
sudo sh -c "echo 64 > /sys/block/sda/queue/max_sectors_kb"
Thank you for the tip.

Revision history for this message
wolfger (wolfger) wrote :

Would it be possible for you to test this bug with the Hardy (8.04) kernel, and report back whether the bug exists there as well?

Revision history for this message
Soos Gergely (sogerc1) wrote :

Actually since I reported the bug I upgraded to Gutsy but I'm stuck with the Feisty kernel because of the lirc problem.
But I can do it. As soon as I will have some time to play, I will test it and report back the results.

Revision history for this message
wolfger (wolfger) wrote :

Just a reminder: have you had time to test with Hardy, or with Gutsy using a Gutsy kernel?

Revision history for this message
Soos Gergely (sogerc1) wrote :

Thank you for the reminder and my apologies for the long delay.
I tested the problem with the latest downloadable Gutsy kernel (2.6.22-14-386) and the same thing happens, the read hangs but "echo 64 > /sys/block/sda/queue/max_sectors_kb" solves the problem.
Actually if you read the file max_sectors_kb right after you plug in the device it says 120.

wolfger (wolfger)
Changed in usbmount:
status: Incomplete → New
Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 beta or later?

Changed in usbmount:
status: New → Incomplete
Revision history for this message
Javier Jardón (jjardon) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
Changed in usbmount:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.