<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:12pt"><div><span>Hi,</span></div><div><span><br></span></div><div><span>I'm having a bit of a problem with some SATA drives in docking stations connected to USB ports.</span></div><div><span><br></span></div><div><span>The problem seems to be unrelated to heavy I/O and occurs randomly. Once, without the drive even being mounted.<br></span></div><div><span><br></span></div><div><span>Here's a sample of output from /var/log/messages:<br></span></div><div><span><br></span></div><div><span>Mar 12 20:54:07 joker kernel: [396376.705286] usb 2-1.3.1: reset high-speed USB device number 8 using ehci_hcd<br>Mar 12 20:54:15 joker kernel: [396384.983920] sd 6:0:0:0: Device offlined - not ready after error recovery<br>Mar 12 20:54:15 joker kernel: [396384.983972] sd 6:0:0:0: [sdb] Unhandled error code<br>Mar 12 20:54:15 joker kernel: [396384.983978] sd
6:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK<br>Mar 12 20:54:15 joker kernel: [396384.983988] sd 6:0:0:0: [sdb] CDB: Read(10): 28 00 2a 8d e8 58 00 00 08 00<br>Mar 12 20:54:15 joker kernel: [396384.984016] end_request: I/O error, dev sdb, sector 713943128<br>Mar 12 20:54:15 joker kernel: [396384.984268] sd 6:0:0:0: rejecting I/O to offline device<br>Mar 12 20:54:15 joker kernel: [396384.984497] usb 2-1.3.1: USB disconnect, device number 8<br>Mar 12 20:54:15 joker kernel: [396385.052205] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27041406: block 108005895: comm differ: unable to read itable block<br>Mar 12 20:54:15 joker kernel: [396385.053693] EXT4-fs (sdb1): previous I/O error to superblock detected<br>Mar 12 20:54:15 joker kernel: [396385.053745] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27041406: block 108005895: comm differ: unable to read itable block<br>Mar 12 20:54:15 joker kernel:
[396385.058106] EXT4-fs (sdb1): previous I/O error to superblock detected<br>Mar 12 20:54:15 joker kernel: [396385.058144] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27041406: block 108005895: comm ls: unable to read itable block<br>Mar 12 20:54:15 joker kernel: [396385.257785] EXT4-fs (sdb1): previous I/O error to superblock detected<br>Mar 12 20:54:15 joker kernel: [396385.257841] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27039895: block 108005801: comm differ: unable to read itable block<br>Mar 12 20:54:15 joker kernel: [396385.260088] EXT4-fs (sdb1): previous I/O error to superblock detected<br>Mar 12 20:54:15 joker kernel: [396385.260144] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27039895: block 108005801: comm differ: unable to read itable block<br>Mar 12 20:54:15 joker kernel: [396385.266710] EXT4-fs (sdb1): previous I/O error to superblock detected<br>Mar 12 20:54:15 joker kernel:
[396385.266766] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27039895: block 108005801: comm ls: unable to read itable block<br>Mar 12 20:54:15 joker kernel: [396385.319579] EXT4-fs (sdb1): previous I/O error to superblock detected<br>Mar 12 20:54:15 joker kernel: [396385.319636] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27039963: block 108005805: comm differ: unable to read itable block<br>Mar 12 20:54:15 joker kernel: [396385.321703] EXT4-fs (sdb1): previous I/O error to superblock detected<br>Mar 12 20:54:15 joker kernel: [396385.321758] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27039963: block 108005805: comm differ: unable to read itable block<br>Mar 12 20:54:15 joker kernel: [396385.330217] EXT4-fs (sdb1): previous I/O error to superblock detected<br>Mar 12 20:54:15 joker kernel: [396385.330299] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27039963: block 108005805: comm
ls: unable to read itable block<br>Mar 12 20:54:17 joker kernel: [396386.455141] usb 2-1.3.1: new high-speed USB device number 9 using ehci_hcd<br>Mar 12 20:54:17 joker kernel: [396386.542050] usb 2-1.3.1: New USB device found, idVendor=152d, idProduct=2336<br>Mar 12 20:54:17 joker kernel: [396386.542054] usb 2-1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5<br>Mar 12 20:54:17 joker kernel: [396386.542056] usb 2-1.3.1: Product: JM20336 SATA, USB Combo<br>Mar 12 20:54:17 joker kernel: [396386.542058] usb 2-1.3.1: Manufacturer: JMicron<br>Mar 12 20:54:17 joker kernel: [396386.542059] usb 2-1.3.1: SerialNumber: 61B888888888<br>Mar 12 20:54:17 joker kernel: [396386.544168] scsi7 : usb-storage 2-1.3.1:1.0<br>Mar 12 20:54:17 joker mtp-probe: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3.1"<br>Mar 12 20:54:17 joker mtp-probe: bus: 2, device: 9 was not an MTP device<br>Mar 12 20:54:18 joker kernel:
[396387.546454] scsi 7:0:0:0: Direct-Access ST975042 0AS PQ: 0 ANSI: 2 CCS<br>Mar 12 20:54:18 joker kernel: [396387.551247] sd 7:0:0:0: Attached scsi generic sg2 type 0<br>Mar 12 20:54:18 joker kernel: [396387.551433] sd 7:0:0:0: [sdc] 1465149168 512-byte logical blocks: (750 GB/698 GiB)<br>Mar 12 20:54:18 joker kernel: [396387.552554] sd 7:0:0:0: [sdc] Write Protect is off<br>Mar 12 20:54:18 joker kernel: [396387.553693] sd 7:0:0:0: [sdc] Asking for cache data failed<br>Mar 12 20:54:18 joker kernel: [396387.553697] sd 7:0:0:0: [sdc] Assuming drive cache: write through<br>Mar 12 20:54:18 joker kernel: [396387.557552] sd 7:0:0:0: [sdc] Asking for cache data failed<br>Mar 12 20:54:18 joker kernel: [396387.557556] sd 7:0:0:0: [sdc] Assuming drive cache: write through<br>Mar 12 20:54:18 joker kernel: [396387.605119] sdc: sdc1<br>Mar 12 20:54:18 joker kernel: [396387.609143] sd 7:0:0:0: [sdc] Asking for cache data failed<br>Mar 12
20:54:18 joker kernel: [396387.609146] sd 7:0:0:0: [sdc] Assuming drive cache: write through<br>Mar 12 20:54:18 joker kernel: [396387.609153] sd 7:0:0:0: [sdc] Attached SCSI disk<br>Mar 12 20:54:18 joker ata_id[7747]: HDIO_GET_IDENTITY failed for '/dev/sdc': Invalid argument<br>Mar 12 20:54:20 joker kernel: [396389.683950] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #2: comm differ: reading directory lblock 0<br>Mar 12 21:01:52 joker kernel: [396841.458607] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #24248321: block 96993312: comm ls: unable to read itable block<br>Mar 12 21:01:52 joker kernel: [396841.458614] EXT4-fs error (device sdb1) in ext4_reserve_inode_write:4467: IO failure<br>Mar 12 21:01:58 joker kernel: [396847.074007] Aborting journal on device sdb1-8.<br>Mar 12 21:01:58 joker kernel: [396847.074020] Buffer I/O error on device sdb1, logical block 91258880<br>Mar 12 21:01:58 joker kernel: [396847.074021] lost
page write due to I/O error on sdb1<br>Mar 12 21:01:58 joker kernel: [396847.074027] JBD2: I/O error detected when updating journal superblock for sdb1-8.<br>Mar 12 21:02:01 joker kernel: [396850.173099] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #2: comm bash: reading directory lblock 0<br>Mar 12 21:05:09 joker kernel: [397037.916573] EXT4-fs error (device sdb1): ext4_put_super:818: Couldn't clean up the journal<br>Mar 12 21:05:09 joker kernel: [397037.916578] EXT4-fs (sdb1): Remounting filesystem read-only<br><br></span></div><div><span><br></span></div><div><span><br></span></div><div><span>I also have made a couple of bug reports which appear to be getting no attention.<br></span></div><div><span><br></span></div><div><span>[Bug 802607] New: reset high-speed USB device (sata drive and USB connection)<br></span></div><div><br></div><div>I've started loosing data now.</div><div><br></div><div>Does anyone have any
clues?</div><div><br></div><div>The system is running FC 16 x86_64 fully up to date. The problem has persisted across several kernels including the current kernel.</div><div><br></div><div>Any help would be greatly appreciated.</div><div><br></div><div>Thanks,</div><div><br></div><div>George...</div><div><br></div><div> </div><div>"It's not what you know that hurts you, It's what you know that ain't so." Will Rogers... Will would say, "STIFF THE FED"!!!</div></div></body></html>