On Sun, 12 Feb 2012, Glynn Clements wrote: > > I have an external USB drive which is working fine on a Windows-7 > system (using the stock USB storage driver); attempting to access it > from my Linux system is ... unreliable to say the least. > > Opening the TrueCrypt container normally works, but attempting to > mount the underlying filesystem (with ntfs-3g) either fails, or > succeeds only after a long delay and many error messages in syslog, > which doesn't make me feel particularly comfortable about writing to > the mounted filesystem. > > Typical error messages are: > > Feb 12 01:28:57 cerise klogd: [117028.672742] Buffer I/O error on device dm-1, logical block 6174632 > Feb 12 01:28:57 cerise klogd: [117028.672752] Buffer I/O error on device dm-1, logical block 6174633 > Feb 12 01:28:57 cerise klogd: [117028.672761] Buffer I/O error on device dm-1, logical block 6174634 > Feb 12 01:28:57 cerise klogd: [117028.672771] Buffer I/O error on device dm-1, logical block 6174635 > > and: > > Feb 12 01:28:57 cerise klogd: [117028.922636] sd 14:0:0:0: [sdc] Unhandled sense code > Feb 12 01:28:57 cerise klogd: [117028.922646] sd 14:0:0:0: [sdc] Result: hostbyte=invalid driverbyte=DRIVER_SENSE > Feb 12 01:28:57 cerise klogd: [117028.922657] sd 14:0:0:0: [sdc] Sense Key : Medium Error [current] > Feb 12 01:28:57 cerise klogd: [117028.922669] sd 14:0:0:0: [sdc] Add. Sense: Unrecovered read error > Feb 12 01:28:57 cerise klogd: [117028.922681] sd 14:0:0:0: [sdc] CDB: Read(10): 28 00 00 5e 39 10 00 00 08 00 > Feb 12 01:28:57 cerise klogd: [117028.922707] end_request: critical target error, dev sdc, sector 6174992 > > Any suggestions as to what to try to improve matters? The drive is > connected to the back-panel connector via a short (~1m) cable. > > "uname -a" says: > > Linux cerise 3.2.2-hardened-r1 #2 SMP Fri Feb 10 00:03:45 GMT 2012 x86_64 Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz GenuineIntel GNU/Linux > > The system has a nondescript VIA P4M900 motherboard. > > "lsusb -v" output is attached (the device in question is the last one; > JMicron USB-ATA bridge). > > The complete syslog (85kb) for the connect, mount, unmount, disconnect > cycle is attached. > > I have a usbmon trace, but it's 4.4Mb, which I'm assuming is too large > to post to the list. Can you place the usbmon trace on a Web server somewhere? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
