On 20.05.2014, Alan Stern wrote: > I have no idea if this will help, but you can try posting a usbmon > trace showing what happens when the device is plugged in and the errors > occur. Connected the drive and did some "dd if=/dev/zero..." to it. It failed within seconds. This is what "dmesg" shows right after that. [a whole bunch of the next two lines deleted here] [ 294.528690] xhci_hcd 0000:02:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880222ed2000 [ 294.528702] xhci_hcd 0000:02:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880222ed2040 [ 294.530087] sd 17:0:0:0: [sdb] Unhandled error code [ 294.530097] sd 17:0:0:0: [sdb] [ 294.530102] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 294.530107] sd 17:0:0:0: [sdb] CDB: [ 294.530110] Write(10): 2a 00 00 00 14 a0 00 00 f0 00 [ 294.530128] end_request: I/O error, dev sdb, sector 5280 Right after that, the drive has been assigned to /dev/sdc. /dev/sdb does no longer exist. [htd@keera ~]$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 238.5G 0 disk ├─sda1 8:1 0 500M 0 part /boot ├─sda2 8:2 0 50G 0 part / ├─sda3 8:3 0 8G 0 part [SWAP] └─sda4 8:4 0 180G 0 part /home sdc 8:32 0 149.1G 0 disk └─sdc1 8:33 0 149.1G 0 part sr0 11:0 1 1024M 0 rom The usbmon dump of the whole process is here: http://www.fritha.org/usblog.zip While writing this mail, the USB disk is popping in and out on the other machine which it is connected to... What I know for sure (because I verified it): 1. The harddrive itself is fine, and so is the fs on it (before it is mounted) 2. The faulty behaviour described here only occurs using USB 3.0. UBS 2 and 1.1 are fine. 3. The faulty behaviour is the same on two other machines with different hardware. Thanks, Heinz. -- 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
