[hardy] input/output error with usb storage phone

[cansei]

I'm using Kubuntu 8.04 since Alpha 4 but since last update I can't use my cell phone (Motorola V360 - USB Storage mode) anymore, dmesg show a lot of input/output errors when I plug it. Under Windows XP I have no problem. Last week was all working perfectly.

This problem occurs in both my machines (Desktop Athlon XP 2000+ and notebook Dell Vostro 1500 Intel Celeron M540)

Other devices such a Nikon Coolpix and the SD Card slot (notebook) still working OK

dmesg on 8.04 fully updated:

[ 306.689012] usb 3-1: new full speed USB device using uhci_hcd and address 6
[ 306.885886] usb 3-1: configuration #1 chosen from 2 choices
[ 306.908930] scsi6 : SCSI emulation for USB Mass Storage devices
[ 306.909573] usb-storage: device found at 6
[ 306.909576] usb-storage: waiting for device to settle before scanning
[ 311.910026] usb-storage: device scan complete
[ 315.757453] scsi 6:0:0:0: Direct-Access Motorola Motorola Phone 2.31 PQ: 0 ANSI: 2
[ 315.781414] sd 6:0:0:0: [sdb] 990976 512-byte hardware sectors (507 MB)
[ 315.793394] sd 6:0:0:0: [sdb] Write Protect is off
[ 315.793398] sd 6:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[ 315.793400] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 315.848408] sd 6:0:0:0: [sdb] 990976 512-byte hardware sectors (507 MB)
[ 315.860400] sd 6:0:0:0: [sdb] Write Protect is off
[ 315.860403] sd 6:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[ 315.860405] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 315.860411] sdb: sdb1
[ 315.888431] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[ 315.888471] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 316.328309] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 316.328317] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 316.328320] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 316.328325] end_request: I/O error, dev sdb, sector 990912
[ 316.328327] printk: 108 messages suppressed.
[ 316.328330] Buffer I/O error on device sdb, logical block 123864
[ 316.486300] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 316.486307] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 316.486311] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 316.486315] end_request: I/O error, dev sdb, sector 990912
[ 316.486319] Buffer I/O error on device sdb, logical block 123864
[ 316.640281] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 316.640288] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 316.640291] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 316.640295] end_request: I/O error, dev sdb, sector 96
[ 316.640299] Buffer I/O error on device sdb, logical block 12
[ 316.640305] Buffer I/O error on device sdb, logical block 13
[ 316.640307] Buffer I/O error on device sdb, logical block 14
[ 316.640310] Buffer I/O error on device sdb, logical block 15
[ 316.640312] Buffer I/O error on device sdb, logical block 16
[ 316.640314] Buffer I/O error on device sdb, logical block 17
[ 316.640316] Buffer I/O error on device sdb, logical block 18
[ 316.640318] Buffer I/O error on device sdb, logical block 19
[ 316.789251] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 316.789258] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 316.789262] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 316.789266] end_request: I/O error, dev sdb, sector 96
[ 316.936228] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 316.936234] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 316.936237] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 316.936242] end_request: I/O error, dev sdb, sector 96
[ 317.177196] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 317.177203] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 317.177207] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 317.177211] end_request: I/O error, dev sdb, sector 0
[ 317.343152] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 317.343160] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 317.343163] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 317.343168] end_request: I/O error, dev sdb, sector 0
[ 317.497146] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 317.497153] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 317.497157] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 317.497161] end_request: I/O error, dev sdb, sector 237
[ 317.641125] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 317.641132] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 317.641136] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 317.641140] end_request: I/O error, dev sdb, sector 237
[ 317.795094] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 317.795102] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 317.795106] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 317.795110] end_request: I/O error, dev sdb, sector 238
[ 317.942080] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 317.942087] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 317.942091] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 317.942095] end_request: I/O error, dev sdb, sector 0
[ 318.156043] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 318.156051] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 318.156054] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 318.156059] end_request: I/O error, dev sdb, sector 237
[ 318.308009] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 318.308017] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 318.308021] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 318.308025] end_request: I/O error, dev sdb, sector 237
[ 318.459998] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 318.460005] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 318.460009] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 318.460013] end_request: I/O error, dev sdb, sector 238
[ 318.626971] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 318.626978] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 318.626982] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 318.626986] end_request: I/O error, dev sdb, sector 0
[ 318.784954] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 318.784962] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 318.784966] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 318.784970] end_request: I/O error, dev sdb, sector 0
[ 318.928923] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 318.928931] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 318.928934] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 318.928939] end_request: I/O error, dev sdb, sector 0
[ 320.236717] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 320.236725] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 320.236728] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 320.236732] end_request: I/O error, dev sdb, sector 0
[ 320.380695] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 320.380703] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 320.380706] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 320.380710] end_request: I/O error, dev sdb, sector 0
[ 320.524667] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 320.524674] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 320.524678] sd 6:0:0:0: [sdb] Add. Sense: No additional sense information
[ 320.524682] end_request: I/O error, dev sdb, sector 0

Using Kubuntu 8.04 Beta LiveCD I can access it without problems:

[ 242.564478] usb 3-1: new full speed USB device using uhci_hcd and address 5
[ 242.567695] usb 3-1: configuration #1 chosen from 2 choices
[ 242.852981] usbcore: registered new interface driver libusual
[ 242.870248] Initializing USB Mass Storage driver...
[ 242.889248] scsi5 : SCSI emulation for USB Mass Storage devices
[ 242.889865] usbcore: registered new interface driver usb-storage
[ 242.889870] USB Mass Storage support registered.
[ 242.890653] usb-storage: device found at 5
[ 242.890657] usb-storage: waiting for device to settle before scanning
[ 242.989655] usb-storage: device scan complete
[ 243.164642] scsi 5:0:0:0: Direct-Access Motorola Motorola Phone 2.31 PQ: 0 ANSI: 2
[ 243.194606] sd 5:0:0:0: [sdb] 990976 512-byte hardware sectors (507 MB)
[ 243.206590] sd 5:0:0:0: [sdb] Write Protect is off
[ 243.206594] sd 5:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[ 243.206596] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[ 243.259601] sd 5:0:0:0: [sdb] 990976 512-byte hardware sectors (507 MB)
[ 243.271596] sd 5:0:0:0: [sdb] Write Protect is off
[ 243.271600] sd 5:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[ 243.271601] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[ 243.271607] sdb: sdb1
[ 243.300630] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[ 243.300670] sd 5:0:0:0: Attached scsi generic sg2 type 0

[Mariano Faraco (mfaraco)]

I can confirm this since Gutsy. My Motorola v360 worked fine in Feisty.
Your will be able to make it work first removing the microSD card, attaching the phone, and later inserting the microsd card. It's not a practical method, but it works.
It also get the phone detected as an Motorola V3 Series.

I post the output from syslog using this last method, otherwise i get the exact same output/problem as in the original but report :

Apr 26 18:39:27 mgg-laptop kernel: [17645.156429] usb 3-1: new full speed USB device using uhci_hcd and address 4
Apr 26 18:39:27 mgg-laptop kernel: [17645.188963] usb 3-1: configuration #1 chosen from 2 choices
Apr 26 18:39:27 mgg-laptop NetworkManager: <debug> [1209245967.500891] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_22b8_4810_noserial').
Apr 26 18:39:27 mgg-laptop kernel: [ 8822.607374] scsi8 : SCSI emulation for USB Mass Storage devices
Apr 26 18:39:27 mgg-laptop kernel: [ 8822.615242] usb-storage: device found at 4
Apr 26 18:39:27 mgg-laptop kernel: [ 8822.615246] usb-storage: waiting for device to settle before scanning
Apr 26 18:39:27 mgg-laptop NetworkManager: <debug> [1209245967.654282] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_22b8_4810_noserial_if0').
Apr 26 18:39:32 mgg-laptop kernel: [17646.998728] usb-storage: device scan complete
Apr 26 18:39:32 mgg-laptop kernel: [17647.003664] scsi 8:0:0:0: Direct-Access Motorola Motorola Phone 2.31 PQ: 0 ANSI: 2
Apr 26 18:39:32 mgg-laptop kernel: [ 8823.517759] sd 8:0:0:0: [sdc] Attached SCSI removable disk
Apr 26 18:39:32 mgg-laptop kernel: [ 8823.517806] sd 8:0:0:0: Attached scsi generic sg3 type 0
Apr 26 18:39:32 mgg-laptop NetworkManager: <debug> [1209245972.698927] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_22b8_4810_noserial_if0_scsi_host').
Apr 26 18:39:32 mgg-laptop NetworkManager: <debug> [1209245972.701403] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_22b8_4810_noserial_if0_scsi_host_scsi_device_lun0').
Apr 26 18:39:32 mgg-laptop NetworkManager: <debug> [1209245972.724134] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_22b8_4810_noserial_if0_scsi_host_scsi_device_lun0_scsi_generic').
Apr 26 18:39:33 mgg-laptop NetworkManager: <debug> [1209245973.077216] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/storage_serial_Motorola_Motorola_Phone_0_0').
Apr 26 18:39:39 mgg-laptop kernel: [ 8824.913774] sd 8:0:0:0: [sdc] 1984000 512-byte hardware sectors (1016 MB)
Apr 26 18:39:39 mgg-laptop kernel: [ 8824.918017] sd 8:0:0:0: [sdc] Write Protect is off
Apr 26 18:39:39 mgg-laptop kernel: [ 8824.918022] sd 8:0:0:0: [sdc] Mode Sense: 0b 00 00 08
Apr 26 18:39:39 mgg-laptop kernel: [ 8824.918025] sd 8:0:0:0: [sdc] Assuming drive cache: write through
Apr 26 18:39:39 mgg-laptop kernel: [17649.854357] sd 8:0:0:0: [sdc] 1984000 512-byte hardware sectors (1016 MB)
Apr 26 18:39:39 mgg-laptop kernel: [17649.860172] sd 8:0:0:0: [sdc] Write Protect is off
Apr 26 18:39:39 mgg-laptop kernel: [...

[Leann Ogasawara (leannogasawara)]

Hi Cansei,

Can you comment the specific Hardy kernel versions you are using when this does and doesn't work (cat /proc/version_signature) ? I could most likely take a guess, but I'd like to have the exact version info for sure to help narrow down what may have caused this regression. Thanks.

[cansei (filbot)]

Hi

Like Mariano said, Gusty has the same problem and Feisty not

About your question:

Kubuntu 8.04 fully updated (doesn't work):
Ubuntu 2.6.24-16.30-generic

Kubuntu 8.04 Beta (works fine):
Ubuntu 2.6.24-12.22-generic

[cansei (filbot)]

Hi

Kubuntu 8.04 fully updated (doesn't work):
Ubuntu 2.6.24-16.30-generic

Kubuntu 8.04 Beta (works fine):
Ubuntu 2.6.24-12.22-generic

[Mariano Faraco (mfaraco)]

Same here, i'm running a fully updated:

Ubuntu 2.6.24-16.30-generic

[cansei (filbot)]

After a lot of tests I think I found some packages that could cause these errors

I cleaned the Linux partition on my desktop and installed Kubuntu Beta again, but this time I selected only a small number of packages to be updated at a time to see which package is causing this problem, and the errors mentioned before occurs after these changes:

volumeid will be removed
grub (versão 0.97-29ubuntu18) will be updated to 0.97-29ubuntu21
initramfs-tools (versão 0.85eubuntu33) will be updated to 0.85eubuntu36
udev (versão 117-4) will be updated to 117-8

Tested with both kernels avaliable: 2.6.24-16.30-generic and 2.6.24-12.22-generic

[cansei (filbot)]

Hi again

I finally found where the problem is:

/etc/udev/rules.d/60-persistent-storage.rules

Removing this file and placing the old version in the folder made my V360 works again! Unfortunately kio_umountwrapper isn't working well, it only unmount the disk

If someone want to test, here is the old version:

http://www.esnips.com/doc/2ca0b833-cae6-4522-81ff-d6d0439ddf70/65-persistent-storage.rules.tar

About kio_umountwrapper I noticed that replacing rules.d folder with the old one it works as expected, here is the old version:

http://www.esnips.com/doc/3aeee9e6-cbfe-4afc-b098-82038288bc2b/udevrulesfolderold.tar

[Mariano Faraco (mfaraco)]

I confirm the fix provided by cansei

the line that makes de v360 work again is:
ENV{DEVTYPE}=="partition", IMPORT{program}="vol_id --export $tempnode"

while the line in the current stable package misses the ENV{DEVTYPE} part and is:
IMPORT{program}="vol_id --export $tempnode"

I cuoldn't test de kio_umountwrapper part

Thanks Cansei

--
Mariano

[cansei (filbot)]

Hi again

I found that the problem with kio_umountwrapper is with 40-permission.rules

Placing the old version of the file in the rules folder I can unmount without problems

Here is the old version:

http://www.esnips.com/doc/79f10bc4-bb62-439c-995d-398a7b9ac210/40-permissions.rules.tar

[cansei (filbot)]

I found that this problem happens because of some udev rules:

40-permission.rules and 60-persistent-storage.rules

[Aníbal Deboni Neto (adneto)]

Hi guys

I'm using Hardy 8.04.1 with kernel 2.6.24-19-generic, and I'm getting the same error.
Do you know how to fix it? I have never changed something in udev, if you could explain how to fix, I'll be thankful.

thx

[]'s

[cansei (filbot)]

Hi, as root remove (or move to an other folder) these files:

40-permissions.rules
60-persistent-storage.rules

They are here: /etc/udev/rules.d/

After doing this, download both files above and put them into the rules.d folder

http://www.esnips.com/doc/2ca0b833-cae6-4522-81ff-d6d0439ddf70/65-persistent-storage.rules.tar

http://www.esnips.com/doc/79f10bc4-bb62-439c-995d-398a7b9ac210/40-permissions.rules.tar

Rename the 65-persistent-storage.rules to 60-persistent-storage.rules

that is it

[Aníbal Deboni Neto (adneto)]

Hi cansei,

I did exactly what you say, but nothing happened, the problem keeps the same...
I updated my kernel to 2.6.24-20-generic,
Here's my dmesg output

[ 442.194586] usb 4-2: new full speed USB device using uhci_hcd and address 3
[ 442.392183] usb 4-2: configuration #1 chosen from 2 choices
[ 442.426206] scsi3 : SCSI emulation for USB Mass Storage devices
[ 442.426579] usb-storage: device found at 3
[ 442.426582] usb-storage: waiting for device to settle before scanning
[ 447.416033] usb-storage: device scan complete
[ 447.607559] scsi 3:0:0:0: Direct-Access Motorola Motorola Phone 2.31 PQ: 0 ANSI: 2
[ 447.631480] sd 3:0:0:0: [sdb] 246016 512-byte hardware sectors (126 MB)
[ 447.643452] sd 3:0:0:0: [sdb] Write Protect is off
[ 447.643460] sd 3:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[ 447.643464] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 447.700336] sd 3:0:0:0: [sdb] 246016 512-byte hardware sectors (126 MB)
[ 447.713328] sd 3:0:0:0: [sdb] Write Protect is off
[ 447.713336] sd 3:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[ 447.713340] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 447.713348] sdb: sdb1
[ 447.758170] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[ 447.758226] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 448.758517] sd 3:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 448.758527] sd 3:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 448.758532] sd 3:0:0:0: [sdb] Add. Sense: No additional sense information
[ 448.758538] end_request: I/O error, dev sdb, sector 245953
[ 448.758541] printk: 86 messages suppressed.
[ 448.758545] Buffer I/O error on device sdb1, logical block 245856
[ 448.758550] Buffer I/O error on device sdb1, logical block 245857
[ 448.758553] Buffer I/O error on device sdb1, logical block 245858
[ 448.758556] Buffer I/O error on device sdb1, logical block 245859
[ 448.758559] Buffer I/O error on device sdb1, logical block 245860
[ 448.758562] Buffer I/O error on device sdb1, logical block 245861
[ 448.758565] Buffer I/O error on device sdb1, logical block 245862
[ 448.758568] Buffer I/O error on device sdb1, logical block 245863
[ 448.906135] sd 3:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 448.906145] sd 3:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 448.906150] sd 3:0:0:0: [sdb] Add. Sense: No additional sense information
[ 448.906156] end_request: I/O error, dev sdb, sector 245953
[ 448.906161] Buffer I/O error on device sdb1, logical block 245856
[ 449.135540] sd 3:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 449.135550] sd 3:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 449.135555] sd 3:0:0:0: [sdb] Add. Sense: No additional sense information
[ 449.135561] end_request: I/O error, dev sdb, sector 245954
[ 449.135567] Buffer I/O error on device sdb1, logical block 245857
[ 449.282162] sd 3:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 449.282172] sd 3:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 449.282178] sd 3:0:0:0: [sdb] Add. Sense: No additional sense information
[ 449.282183] end_request: I/O error, ...

[cansei (filbot)]

oh sorry, I said "above" but I meant 'below"

my english is poor so I will try again, download both files:

http://www.esnips.com/doc/2ca0b833-cae6-4522-81ff-d6d0439ddf70/65-persistent-storage.rules.tar

http://www.esnips.com/doc/79f10bc4-bb62-439c-995d-398a7b9ac210/40-permissions.rules.tar

1- open both files and extract them to your home folder (did you extracted last time?). You will have two text files named: 65-persistent-storage.rules and 40-permissions.rules

2- rename 65-persistent-storage.rules to 60-persistent-storage.rules

3- copy 60-persistent-storage.rules and 40-permissions.rules and paste in rules.d folder

4- plug your V360 and check

if this doesn't work I will have no more idea since with both files my (and Mariano) V360 is working again

[Aníbal Deboni Neto (adneto)]

I did exactly what you said, despite of the "below" error hehehehehe,
I'm not too newbie with linux. What language do you speak? Portuguese?
I'll try to change the file permissions to see what happens.

thx again =)

[]'s

On 7/27/08, cansei <email address hidden> wrote:
> oh sorry, I said "above" but I meant 'below"
>
> my english is poor so I will try again, download both files:
>
> http://www.esnips.com/doc/2ca0b833-cae6-4522-81ff-d6d0439ddf70/65
> -persistent-storage.rules.tar
>
> http://www.esnips.com/doc/79f10bc4-bb62-439c-995d-
> 398a7b9ac210/40-permissions.rules.tar
>
> 1- open both files and extract them to your home folder (did you
> extracted last time?). You will have two text files named: 65
> -persistent-storage.rules and 40-permissions.rules
>
> 2- rename 65-persistent-storage.rules to 60-persistent-storage.rules
>
> 3- copy 60-persistent-storage.rules and 40-permissions.rules and paste
> in rules.d folder
>
> 4- plug your V360 and check
>
> if this doesn't work I will have no more idea since with both files my
> (and Mariano) V360 is working again
>
> --
> [hardy] input/output error with usb storage phone
> https://bugs.launchpad.net/bugs/221983
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Aníbal Deboni Neto¹

--
¹. É Bacharel em Turismo pela UNESP e graduando em Engenharia
Florestal - ESALQ/USP.
   Membro do Grupo de Adequação Ambiental - GADE

   + 55 (19) 8172-7858
   Email/GTalk: <email address hidden>
   MSN: <email address hidden>
   ICQ: 83576976
   Skype: anibaldeboni

[none (ubuntu-bugs-nullinfinity-deactivatedaccount)]

I see exactly the same error when I connect my Motorola A1200 phone. Changing the udev rules files does not seem to help. If I remove the microSD card from the phone, put it into an SD adapter and plug that into the card reader on my laptop, I can read and write files just fine.

Connecting the phone via USB used to work with the early Hardy kernels, just as reported above.

[none (ubuntu-bugs-nullinfinity-deactivatedaccount)]

Apparently this problem also affects suse: http://forums.opensuse.org/hardware/389136-motorola-a1200-connect-error-usbstorage-after-os11-upgrade.html

And fedora: http://<email address hidden>/msg06877.html

[Scott James Remnant (Canonical) (canonical-scott)]

Sorry, didn't read the entire bug.

This is being caused by vol_id being run on the storage device?

[none (ubuntu-bugs-nullinfinity-deactivatedaccount)]

This was a kernel bug in the SCSI subsystem, fixed by git commit ID 44ea91c597ae4641d9ac21b8bbba0795d2f4261e.

[Scott James Remnant (Canonical) (canonical-scott)]

Thought it probably was ;-)

[Magnus Hedemark (viridari)]

Is this going to be committed to Ubuntu? I have the same problem in Intrepid.

uname -a output:
Linux mudskipper 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux

[none (ubuntu-bugs-nullinfinity-deactivatedaccount)]

This fix is in the Intrepid kernel:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=commit;h=44ea91c597ae4641d9ac21b8bbba07

Your problem is most likely caused by something else.

[Scott James Remnant (Canonical) (canonical-scott)]

Was a kernel bug, not udev