On Sun, Sep 2, 2012 at 6:47 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > > On Sun, 2 Sep 2012, Alon Bar-Lev wrote: > > > Attached usbmon, I hope I've done this OK. > > The errors start here: > > > ffff880112a12d80 3034504955 S Bo:2:009:2 -115 31 = 55534243 0a000000 > > 00100000 80000a28 00000000 00000008 00000000 000000 > > ffff880112a12d80 3034505013 C Bo:2:009:2 0 31 > > > ffff880132074d80 3034505019 S Bi:2:009:1 -115 4096 < > > ffff880132074d80 3034505155 C Bi:2:009:1 -32 0 > > ffff880112a12d80 3034505161 S Co:2:009:0 s 02 01 0000 0081 0000 0 > > ffff880112a12d80 3034505298 C Co:2:009:0 0 0 > > ffff880112a12d80 3034505308 S Bi:2:009:1 -115 13 < > > ffff880112a12d80 3034505441 C Bi:2:009:1 0 13 = 55534253 0a000000 > > 00000000 02 > > This shows the computer asking the drive to read 8 blocks starting at > block 0. The drive (actually the JMicron USB interface, not the drive > itself) returns an error code indicating that it thinks the command > was not sent properly -- even though it was. > > I don't understand why the JMicron unit doesn't accept this command. > It simply appears to be broken. Does it work if you plug it into a > computer running Windows or Mac OS X? > > Alan Stern > Hi, I don't know... I don't use these... and the disk is ext4... I have XP in qemu, I mapped the device and took usbmon (attached), so you probably see plugin within Linux, the plugout, then windows takes charge. I see the disk in device manager, but not in disk manager... don't know why. Maybe this will help... Thanks, Alon.
Attachment:
disk2
Description: Binary data
