second usb hard drive destroys connection [Solved]

[bernd_b]

I am out of ideas.

I have two of the same usb hard drives (CN Memory Airy USB 2.0 2TB) which worked liked charm. I could use the first one and mount the second one and made backup from disk one to disk two.

Yesterday I tried to mount the second hard drive and the result was that I was unable to mount it and the first one lost its connection - which means it wasn't mounted anymore.

What makes it even worth: I am now unable to mount both devices. I tried different ports and other cable - no effect. Both drives work without problems on a windows laptop.

Now I downgraded from 3.6 to kernel 3.5 and wow: I could mount the drive again. I transferred 20 GB on it without a problem. So I plugged in the second drive and bang - no connection to both drives again.

Here is my actual output of dmesg when i plug in one of the drives. Any idea welcome. Was there an update of udev or something similar which breaks compability?

Code: Select all

[  199.106043] usb 1-1: new high-speed USB device number 3 using ehci_hcd
[  199.320374] usb 1-1: New USB device found, idVendor=152d, idProduct=2329
[  199.320380] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[  199.320383] usb 1-1: Product: USB to ATA/ATAPI bridge
[  199.320385] usb 1-1: Manufacturer: JMicron
[  199.320388] usb 1-1: SerialNumber: 59D82464
[  199.368130] usb-storage 1-1:1.0: Quirks match for vid 152d pid 2329: 8020
[  199.368166] scsi4 : usb-storage 1-1:1.0
[  200.618534] scsi 4:0:0:0: Direct-Access     ST2000DL 003-9VT166       CC45 PQ: 0 ANSI: 2 CCS
[  200.679258] sd 4:0:0:0: Attached scsi generic sg4 type 0
[  200.680757] sd 4:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[  200.683403] sd 4:0:0:0: [sdb] Write Protect is off
[  200.683410] sd 4:0:0:0: [sdb] Mode Sense: 28 00 00 00
[  200.685384] sd 4:0:0:0: [sdb] No Caching mode page present
[  200.685387] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  205.089403] sd 4:0:0:0: [sdb] No Caching mode page present
[  205.089410] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  206.496043] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  207.674798]  sdb: sdb1
[  209.584048] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  210.759033] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  212.013044] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  213.058045] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  214.131037] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  215.178039] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  215.973049] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  216.716048] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  216.902434] sd 4:0:0:0: [sdb] Asking for cache data failed
[  216.902440] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  216.902444] sd 4:0:0:0: [sdb] Attached SCSI disk
[  217.637035] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  218.756031] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  219.570037] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  220.911039] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  221.134381] usb 1-1: device descriptor read/all, error -71
[  221.237037] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  222.066050] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  222.864038] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  223.488063] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  224.217051] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  225.028045] usb 1-1: reset high-speed USB device number 3 using ehci_hcd
[  225.217264] sd 4:0:0:0: [sdb] Unhandled error code
[  225.217268] sd 4:0:0:0: [sdb] 
[  225.217269] Result: hostbyte=0x07 driverbyte=0x00
[  225.217272] sd 4:0:0:0: [sdb] CDB:
[  225.217273] cdb[0]=0x28: 28 00 e8 e0 88 00 00 00 08 00
[  225.217281] end_request: I/O error, dev sdb, sector 3907028992
[  225.217284] Buffer I/O error on device sdb, logical block 488378624


[Fitzcarraldo]

Please post the output of the command lsmod issued as root user in a Konsole/Terminal window.

[bernd_b]

Here it is:

Code: Select all

localhost / # lsmod
Module                  Size  Used by
w83627ehf              25728  0
hwmon_vid               1956  1 w83627ehf
lm90                   11360  0
ipv6                  244158  30
8021q                  13691  0
garp                    4350  1 8021q
stp                     1372  1 garp
llc                     3232  2 stp,garp
vboxnetadp             17254  0
vboxnetflt             13181  0
vboxdrv              1785700  2 vboxnetadp,vboxnetflt
snd_hda_codec_hdmi     19437  4
snd_hda_codec_realtek    44032  1
snd_hda_intel          20888  3
snd_hda_codec          67503  3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep               4542  1 snd_hda_codec
snd_pcm                56407  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
k8temp                  2896  0
forcedeth              45008  0
ppdev                   5960  0
nv_tco                  3928  0
i2c_nforce2             5000  0
parport_pc             25585  0
pcspkr                  1520  0
floppy                 47169  0
edac_core              26721  0
nvidia               9327673  44
snd_page_alloc          5925  2 snd_pcm,snd_hda_intel
snd_timer              14262  1 snd_pcm
kvm_amd                37144  0
snd                    46367  13 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
kvm                   192374  1 kvm_amd
sha512_generic          4545  0
sha1_generic            1787  0
virtio_pci              6011  0
virtio_blk              5497  0
virtio_net             13035  0
virtio_console         13486  0
virtio_balloon          4011  0
virtio_ring             4658  5 virtio_blk,virtio_net,virtio_pci,virtio_balloon,virtio_console
virtio                  3309  5 virtio_blk,virtio_net,virtio_pci,virtio_balloon,virtio_console
xts                     2773  0
gf128mul                5338  1 xts
cryptd                  6863  0
aes_x86_64              7340  0
sha256_generic          9549  0
iscsi_tcp               7676  0
tg3                   117410  0
e1000                 108578  0
fuse                   56588  2
zfs                   816172  0
zcommon                28284  1 zfs
znvpair                24477  2 zfs,zcommon
zavl                    4187  1 zfs
zunicode              316738  1 zfs
spl                   103567  5 zfs,zavl,zunicode,zcommon,znvpair
xfs                   412647  1
nfs                   221014  0
lockd                  51657  1 nfs
auth_rpcgss            26280  1 nfs
nfs_acl                 1983  1 nfs
sunrpc                145223  4 nfs,auth_rpcgss,lockd,nfs_acl
jfs                   139905  2
reiserfs              206125  2
ext4                  246369  0
jbd2                   48809  1 ext4
ext3                  107397  0
jbd                    37438  1 ext3
ext2                   53462  0
mbcache                 4529  3 ext2,ext3,ext4
scsi_wait_scan           695  0
sl811_hcd               8919  0
hid_generic             1025  0
xhci_hcd              100882  0
ohci_hcd               24190  0
uhci_hcd               20386  0
ehci_hcd               44303  0
sx8                    10965  0
imm                     8661  0
parport                26727  3 imm,ppdev,parport_pc
pata_pcmcia             9621  0
pcmcia                 38968  1 pata_pcmcia


[Fitzcarraldo]

A couple of things to try:

1. Force the use of USB 1.1 instead of USB 2.0:

Code: Select all

# rmmod -f ehci_hcd

or:

2. Disable CONFIG_USB_SUSPEND:

Code: Select all

# cat /sys/module/usbcore/parameters/autosuspend
# echo -1 > /sys/module/usbcore/parameters/autosuspend

[bernd_b]

I tried the second one.
Before I tried the second one, I had both of the devices running on my windows box copying 9 GB of Data from one to another.

O.K., back to the Sabayon Station:
First one: Mounting.
Second one: Mount fails. Drive one: not accessible anymore. Every attempt ls "ls" hangs endlessly.

Will try disabling USB 2.0 - but it ran in the past with it. Was there really no usb related update of a software package recently which could cause the problem?

dmesg of the described operations again:

Code: Select all

[ 1648.545034] usb 1-2: new high-speed USB device number 12 using ehci_hcd
[ 1648.664148] usb 1-2: New USB device found, idVendor=152d, idProduct=2329
[ 1648.664153] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 1648.664156] usb 1-2: Product: USB to ATA/ATAPI bridge
[ 1648.664158] usb 1-2: Manufacturer: JMicron
[ 1648.664160] usb 1-2: SerialNumber: 59D82464
[ 1648.664724] usb-storage 1-2:1.0: Quirks match for vid 152d pid 2329: 8020
[ 1648.665541] scsi4 : usb-storage 1-2:1.0
[ 1649.674568] scsi 4:0:0:0: Direct-Access     ST2000DL 003-9VT166       CC45 PQ: 0 ANSI: 2 CCS
[ 1649.713251] sd 4:0:0:0: Attached scsi generic sg4 type 0
[ 1649.715678] sd 4:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 1649.718422] sd 4:0:0:0: [sdb] Write Protect is off
[ 1649.718428] sd 4:0:0:0: [sdb] Mode Sense: 28 00 00 00
[ 1649.720403] sd 4:0:0:0: [sdb] No Caching mode page present
[ 1649.720407] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 1649.725413] sd 4:0:0:0: [sdb] No Caching mode page present
[ 1649.725418] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 1649.739685]  sdb: sdb1
[ 1649.776416] sd 4:0:0:0: [sdb] No Caching mode page present
[ 1649.776422] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 1649.776426] sd 4:0:0:0: [sdb] Attached SCSI disk
[ 1714.492038] usb 1-1: new high-speed USB device number 13 using ehci_hcd
[ 1714.615299] usb 1-1: New USB device found, idVendor=152d, idProduct=2329
[ 1714.615303] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 1714.615306] usb 1-1: Product: USB to ATA/ATAPI bridge
[ 1714.615308] usb 1-1: Manufacturer: JMicron
[ 1714.615310] usb 1-1: SerialNumber: 59D88C3A
[ 1714.616649] usb-storage 1-1:1.0: Quirks match for vid 152d pid 2329: 8020
[ 1714.616720] scsi5 : usb-storage 1-1:1.0
[ 1715.631095] scsi 5:0:0:0: Direct-Access     ST2000DL 003-9VT166       CC45 PQ: 0 ANSI: 2 CCS
[ 1715.671347] sd 5:0:0:0: Attached scsi generic sg5 type 0
[ 1715.727696] sd 5:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 1715.774448] sd 5:0:0:0: [sdc] Write Protect is off
[ 1715.774452] sd 5:0:0:0: [sdc] Mode Sense: 28 00 00 00
[ 1715.777441] sd 5:0:0:0: [sdc] No Caching mode page present
[ 1715.777445] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[ 1715.782440] sd 5:0:0:0: [sdc] No Caching mode page present
[ 1715.782444] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[ 1715.811216]  sdc: sdc1
[ 1715.895451] sd 5:0:0:0: [sdc] No Caching mode page present
[ 1715.895458] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[ 1715.895462] sd 5:0:0:0: [sdc] Attached SCSI disk
[ 1755.438036] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1756.179043] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1757.028038] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1758.014034] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1759.031035] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1759.713036] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1759.905595] sd 5:0:0:0: [sdc] Unhandled error code
[ 1759.905600] sd 5:0:0:0: [sdc] 
[ 1759.905602] Result: hostbyte=0x07 driverbyte=0x00
[ 1759.905604] sd 5:0:0:0: [sdc] CDB:
[ 1759.905606] cdb[0]=0x28: 28 00 00 00 08 00 00 00 20 00
[ 1759.905613] end_request: I/O error, dev sdc, sector 2048
[ 1759.905616] Buffer I/O error on device sdc1, logical block 0
[ 1759.905623] Buffer I/O error on device sdc1, logical block 1
[ 1759.905625] Buffer I/O error on device sdc1, logical block 2
[ 1759.905628] Buffer I/O error on device sdc1, logical block 3
[ 1760.307039] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1760.923043] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1761.678044] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1762.380032] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1762.965036] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1763.547029] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1764.171036] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1764.905047] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1765.515035] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1766.457061] usb 1-1: reset high-speed USB device number 13 using ehci_hcd
[ 1853.461038] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1854.300036] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1855.128029] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1855.672041] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1856.192031] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1856.792066] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1856.984881] sd 4:0:0:0: [sdb] Unhandled error code
[ 1856.984887] sd 4:0:0:0: [sdb] 
[ 1856.984889] Result: hostbyte=0x07 driverbyte=0x00
[ 1856.984891] sd 4:0:0:0: [sdb] CDB:
[ 1856.984893] cdb[0]=0x28: 28 00 38 e8 f5 00 00 00 08 00
[ 1856.984900] end_request: I/O error, dev sdb, sector 954791168
[ 1856.984903] Buffer I/O error on device sdb1, logical block 119348640
[ 1857.394043] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1857.948034] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1858.601035] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1859.146034] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1859.693046] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1860.283038] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1860.475902] sd 4:0:0:0: [sdb] Unhandled error code
[ 1860.475907] sd 4:0:0:0: [sdb] 
[ 1860.475909] Result: hostbyte=0x07 driverbyte=0x00
[ 1860.475912] sd 4:0:0:0: [sdb] CDB:
[ 1860.475913] cdb[0]=0x28: 28 00 38 e8 f5 00 00 00 08 00
[ 1860.475920] end_request: I/O error, dev sdb, sector 954791168
[ 1860.475923] Buffer I/O error on device sdb1, logical block 119348640
[ 1860.838043] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1861.518044] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1862.196036] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1862.844035] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1863.513035] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1864.125035] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1864.317898] sd 4:0:0:0: [sdb] Unhandled error code
[ 1864.317904] sd 4:0:0:0: [sdb] 
[ 1864.317906] Result: hostbyte=0x07 driverbyte=0x00
[ 1864.317908] sd 4:0:0:0: [sdb] CDB:
[ 1864.317909] cdb[0]=0x28: 28 00 38 e8 f5 00 00 00 08 00
[ 1864.317917] end_request: I/O error, dev sdb, sector 954791168
[ 1864.317920] Buffer I/O error on device sdb1, logical block 119348640
[ 1864.651039] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1865.303037] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1865.888043] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1866.446033] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1867.081038] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1867.651037] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
[ 1867.843896] sd 4:0:0:0: [sdb] Unhandled error code
[ 1867.843902] sd 4:0:0:0: [sdb] 
[ 1867.843904] Result: hostbyte=0x07 driverbyte=0x00
[ 1867.843906] sd 4:0:0:0: [sdb] CDB:
[ 1867.843908] cdb[0]=0x28: 28 00 38 e8 f5 00 00 00 08 00
[ 1867.843915] end_request: I/O error, dev sdb, sector 954791168
[ 1867.843918] Buffer I/O error on device sdb1, logical block 119348640
[ 1868.225034] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
.
.
.


[Fitzcarraldo]

No idea, but if it worked with a previous kernel but not the latest then my guess would be that it's a kernel regression. I've seen a bug report on the ehci_hcd module regarding your problem with USB 2.0 devices, and one guy suggested trying a different kernel I/O scheduler, so you could try that to see if it helps. SL uses the BFQ scheduler:

Code: Select all

# cat /sys/block/sda/queue/scheduler
noop deadline cfq [bfq]

so you could add the following parameter to the end of the kernel boot line in /boot/grub/grub.cfg to make the kernel use, for example, the deadline scheduler instead:

Code: Select all

elevator=deadline

Try that (you'll need to reboot, of course).

[bernd_b]

Unfortunately all these things didn't help.

Atfter fooling around I thing a can narrow down the problem as follows:
Both of the drive work perfectly if plugged and mounted alone. Even when drives of another manufacturer are plugged in, there are no problems.

When I plug in the second drive of the same model, mounting succeded when tried the first time an the hard drives are freshly powerd on, but writing dies after some hundred of MB.

Dmesg introduces these drives (Cemory Airy 2TB USB2.0) as

Code: Select all

usb 1-5: new high-speed USB device number 17 using ehci_hcd
Dec 31 13:03:13 localhost kernel: [ 1611.489694] usb 1-5: New USB device found, idVendor=152d, idProduct=2329
Dec 31 13:03:13 localhost kernel: [ 1611.489700] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Dec 31 13:03:13 localhost kernel: [ 1611.489703] usb 1-5: Product: USB to ATA/ATAPI bridge
Dec 31 13:03:13 localhost kernel: [ 1611.489705] usb 1-5: Manufacturer: JMicron
Dec 31 13:03:13 localhost kernel: [ 1611.489707] usb 1-5: SerialNumber: 59D82464
Dec 31 13:03:13 localhost kernel: [ 1611.490878] usb-storage 1-5:1.0: Quirks match for vid 152d pid 2329: 8020
Dec 31 13:03:13 localhost kernel: [ 1611.490897] scsi19 : usb-storage 1-5:1.0
Dec 31 13:03:14 localhost kernel: [ 1612.494106] scsi 19:0:0:0: Direct-Access     ST2000DL 003-9VT166       CC45 PQ: 0 ANSI: 2 CCS
Dec 31 13:03:14 localhost kernel: [ 1612.537263] sd 19:0:0:0: Attached scsi generic sg4 type 0
Dec 31 13:03:14 localhost kernel: [ 1612.538369] sd 19:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Dec 31 13:03:14 localhost kernel: [ 1612.541970] sd 19:0:0:0: [sdb] Write Protect is off
Dec 31 13:03:14 localhost kernel: [ 1612.541976] sd 19:0:0:0: [sdb] Mode Sense: 28 00 00 00
Dec 31 13:03:14 localhost kernel: [ 1612.543954] sd 19:0:0:0: [sdb] No Caching mode page present
Dec 31 13:03:14 localhost kernel: [ 1612.543958] sd 19:0:0:0: [sdb] Assuming drive cache: write through
Dec 31 13:03:14 localhost kernel: [ 1612.548955] sd 19:0:0:0: [sdb] No Caching mode page present
Dec 31 13:03:14 localhost kernel: [ 1612.548959] sd 19:0:0:0: [sdb] Assuming drive cache: write through
Dec 31 13:03:14 localhost kernel: [ 1612.570023]  sdb: sdb1
sd 19:0:0:0: [sdb] No Caching mode page present
Dec 31 13:03:14 localhost kernel: [ 1612.575958] sd 19:0:0:0: [sdb] Assuming drive cache: write through
Dec 31 13:03:14 localhost kernel: [ 1612.575961] sd 19:0:0:0: [sdb] Attached SCSI disk


or

Code: Select all

Dec 31 13:03:22 localhost kernel: [ 1620.799038] usb 1-2: new high-speed USB device number 18 using ehci_hcd
Dec 31 13:03:22 localhost kernel: [ 1620.922696] usb 1-2: New USB device found, idVendor=152d, idProduct=2329
Dec 31 13:03:22 localhost kernel: [ 1620.922701] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Dec 31 13:03:22 localhost kernel: [ 1620.922704] usb 1-2: Product: USB to ATA/ATAPI bridge
Dec 31 13:03:22 localhost kernel: [ 1620.922706] usb 1-2: Manufacturer: JMicron
Dec 31 13:03:22 localhost kernel: [ 1620.922708] usb 1-2: SerialNumber: 59D88C3A
Dec 31 13:03:22 localhost kernel: [ 1620.924067] usb-storage 1-2:1.0: Quirks match for vid 152d pid 2329: 8020
Dec 31 13:03:22 localhost kernel: [ 1620.924129] scsi20 : usb-storage 1-2:1.0
Dec 31 13:03:23 localhost kernel: [ 1621.928116] scsi 20:0:0:0: Direct-Access     ST2000DL 003-9VT166       CC45 PQ: 0 ANSI: 2 CCS
Dec 31 13:03:23 localhost kernel: [ 1621.971247] sd 20:0:0:0: Attached scsi generic sg5 type 0
Dec 31 13:03:23 localhost kernel: [ 1621.972480] sd 20:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Dec 31 13:03:23 localhost kernel: [ 1621.975971] sd 20:0:0:0: [sdc] Write Protect is off
Dec 31 13:03:23 localhost kernel: [ 1621.975977] sd 20:0:0:0: [sdc] Mode Sense: 28 00 00 00
Dec 31 13:03:23 localhost kernel: [ 1621.977952] sd 20:0:0:0: [sdc] No Caching mode page present
Dec 31 13:03:23 localhost kernel: [ 1621.977955] sd 20:0:0:0: [sdc] Assuming drive cache: write through
Dec 31 13:03:23 localhost kernel: [ 1621.982953] sd 20:0:0:0: [sdc] No Caching mode page present
Dec 31 13:03:23 localhost kernel: [ 1621.982958] sd 20:0:0:0: [sdc] Assuming drive cache: write through
Dec 31 13:03:23 localhost kernel: [ 1621.983733]  sdc: sdc1
Dec 31 13:03:23 localhost kernel: [ 1621.988951] sd 20:0:0:0: [sdc] No Caching mode page present
Dec 31 13:03:23 localhost kernel: [ 1621.988955] sd 20:0:0:0: [sdc] Assuming drive cache: write through
Dec 31 13:03:23 localhost kernel: [ 1621.988958] sd 20:0:0:0: [sdc] Attached SCSI disk


where I can only see a different Serial number.

Is this a hardware failure of my board? Does the line

Code: Select all

usb-storage 1-2:1.0: Quirks match for vid 152d pid 2329: 8020

leads to anything further?

[Fitzcarraldo]

No, your motherboard is not failing. I don't think that message signifies anything untoward: it is just telling you that the same driver quirk is being used by the usb-storage driver for two different USB devices, which is to be expected if the model of the two USB drives is the same. Anyway, have a look in the directory /etc/modprobe.d/ to see if any of the files in there specify an option for usb-storage as a module, and have a look in the /boot/grub/grub.cfg file to see if there is a "usb-storage.quirks=" parameter in the kernel boot line for usb-storage as a built-in.

However, messages you posted such as "[sdb] Asking for cache data failed", "usb 1-1: device descriptor read/all, error -71", "sd 4:0:0:0: [sdb] Unhandled error code", "end_request: I/O error, dev sdb, sector 3907028992" and "Buffer I/O error on device sdb, logical block 488378624" clearly show a major problem. As the SL kernel configuration file contains CONFIG_USB_STORAGE=y (i.e. usb-storage is a built-in rather than a module), you could try adding the "usb-storage.quirks=" parameter to the kernel boot line in the grub.cfg file with the applicable vendor ID, model ID and a quirk specified. You posted the vendor ID and model ID, so the kernel boot parameter would be "usb-storage.quirks=0x152d:0x2329:<quirk>" (without the quotes), where <quirk> would be one or more letters from the list shown on the following page under "usb-storage.quirks=": Linux/Documentation/kernel-parameters.txt. The question is: which quirk or quirks might be of use. Given some of the error messages you posted, my first try would be "c" (without the quotes).

Also, according to the kernel source code Linux/drivers/usb/storage/unusual_devs.h there is something about your JMicron drives that is unusual:

1889 /* Reported by Alexandre Oliva <oliva@lsd.ic.unicamp.br>
1890 * JMicron responds to USN and several other SCSI ioctls with a
1891 * residue that causes subsequent I/O requests to fail. */
1892 UNUSUAL_DEV( 0x152d, 0x2329, 0x0100, 0x0100,
1893 "JMicron",
1894 "USB to ATA/ATAPI Bridge",
1895 USB_SC_DEVICE, USB_PR_DEVICE, NULL,
1896 US_FL_IGNORE_RESIDUE | US_FL_SANE_SENSE ),

so another quirk you could try would be "r":

r = IGNORE_RESIDUE (the device reports bogus residue values);

although that is probably the quirk that the message "usb-storage 1-2:1.0: Quirks match for vid 152d pid 2329: 8020" refers to, i.e. the "r" quirk is probably already applied. Wouldn't do any harm to try it, though.

You wrote that, if you only have one of the drives plugged in, it works OK. This leads me to suspect that somehow the version of the kernel you're using cannot handle properly more than one drive simultaneously with the IGNORE_RESIDUE quirk applied. Just my guess, though, but you may find there isn't a solution with the current kernel and it will be fixed in a future version of the kernel.

Given the source code snippet quoted above, I'd be inclined to try a kernel boot parameter such as:

Code: Select all

usb-storage.quirks=0x152d:0x2329:ra

and also "ral", "rac", "racl" etc.

//Note to self: Don't buy CnMemory Airy USB 2.0 2TB drives (or any other drives that use JMicron chips). //

[bernd_b]

I am glad to be able to tell that it is working again.

Since this happens with the newly installed kernel 3.7 and one of the formerly used 3.6 (both sabayon-ones), I guess that the suggested boot option finally did the magic.

I can now mount again both devices on any port without problems and copying files is back to the speed I used to have (which is at least 30 MiB/s copying files from the built-in-sata-port to one of the usb drives or about 20 MiB/s when copying from one of the CN Memory devices with JMicron chips to the same model.

I hope the situation keeps stable - not sure if I buy one of those drives again anyway since the prices seems to normalize again.