Hide Forgot
Description of problem: I have a La Cie USB3/FireWire external hard drive. It behaves normally when plugged into the USB 2 ports of my Lenovo Thinkpad W540. When plugged into a USB 3 port, it fails to show up in the file system for around 15 minutes, then mounts as normal. hdparm suggests that, when it monuts with USB3, it runs at appropriate USB3 speeds. When the same drive is plugged into the same computer running Windows 10, it behaves as expected. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Plug in external La Cie drive 2. 3. Actual results: Disk mounts after 15 minutes Expected results: Disk mounts immediately Additional info: When I run lspci -k, there are 2 USB controllers listed. I'm not sure which one is for USB£. They are: 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) Subsystem: Lenovo Device 2211 Kernel driver in use: xhci_hcd 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04) Subsystem: Lenovo Device 2211 Kernel driver in use: ehci-pci If I run journalctl -f and plug the drive in, I get this output: Sep 28 22:04:40 localhost.localdomain kernel: usb 4-2: new SuperSpeed USB device number 2 using xhci_hcd Sep 28 22:04:40 localhost.localdomain kernel: usb 4-2: New USB device found, idVendor=059f, idProduct=1061 Sep 28 22:04:40 localhost.localdomain kernel: usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 Sep 28 22:04:40 localhost.localdomain kernel: usb 4-2: Product: Rugged USB3-FW Sep 28 22:04:40 localhost.localdomain kernel: usb 4-2: Manufacturer: LaCie Sep 28 22:04:40 localhost.localdomain kernel: usb 4-2: SerialNumber: 000000003563fa70104e Sep 28 22:04:40 localhost.localdomain kernel: scsi host6: uas Sep 28 22:04:40 localhost.localdomain kernel: scsi 6:0:0:0: Direct-Access LaCie Rugged FW USB3 051E PQ: 0 ANSI: 6 Sep 28 22:04:40 localhost.localdomain mtp-probe[2917]: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb4/4-2" Sep 28 22:04:40 localhost.localdomain mtp-probe[2917]: bus: 4, device: 2 was not an MTP device Sep 28 22:04:40 localhost.localdomain kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0 Sep 28 22:04:41 localhost.localdomain kernel: sd 6:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/466 GiB) Sep 28 22:04:41 localhost.localdomain kernel: sd 6:0:0:0: [sdb] Write Protect is off Sep 28 22:04:41 localhost.localdomain kernel: sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00 Sep 28 22:04:41 localhost.localdomain kernel: sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 28 22:04:45 localhost.localdomain PackageKit[1386]: get-updates transaction /4112_dcaeccbb from uid 1000 finished with success after 43ms Sep 28 22:05:11 localhost.localdomain kernel: sd 6:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: IN Sep 28 22:05:11 localhost.localdomain kernel: sd 6:0:0:0: tag#0 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00 Sep 28 22:05:11 localhost.localdomain kernel: scsi host6: uas_eh_bus_reset_handler start Sep 28 22:05:11 localhost.localdomain kernel: usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd Sep 28 22:05:11 localhost.localdomain kernel: scsi host6: uas_eh_bus_reset_handler success It then seems to loop round: Sep 28 22:06:44 localhost.localdomain kernel: sd 6:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: IN Sep 28 22:06:44 localhost.localdomain kernel: sd 6:0:0:0: tag#0 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00 Sep 28 22:06:44 localhost.localdomain kernel: scsi host6: uas_eh_bus_reset_handler start Sep 28 22:06:44 localhost.localdomain kernel: usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd Sep 28 22:06:44 localhost.localdomain kernel: scsi host6: uas_eh_bus_reset_handler success
The filesystem package has nothing to do with the file system implementation in the kernel. Moreover, the bug you are trying to report does not seem to be file system-related anyway. I am switching the component to kernel...
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.