USB 3.0 Disk Drive Not Recognized.

[tomdean]

WD My Passport 2T USB 3.0 Disk Drive.
External Plugable 7 port USB 3.0 hub.

When I connect the WD drive to the external USB 3.0 hub it is not recognized.
The drive led blinks one time and it is not in dmesg or in the output of lsusb.

> sudo lsusb -v causes the drive led to blink several times and it is recognized.

With Autosuspend good for this device, long access applications like dump fail.
After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes and then dump asks for operator intervention. Looking at dmesg the drive (initially sdf) was disconnected and reconnected as sdg.

  Bad Autosuspend for USB device xHCI Host Controller [usb6]

seems to correct this behavior but not the initial connection problem.

Some discussion and testing in bug 1242321.

If I connect the drive to a USB 3.0 port on the motherboard, it is recognized.

There is no problem with an Plugable 7-port USB 2.0 hub.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-78-generic 4.4.0-78.99
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: tomdean 3698 F.... pulseaudio
 /dev/snd/controlC0: tomdean 3698 F.... pulseaudio
Date: Fri May 26 09:05:20 2017
HibernationDevice: RESUME=UUID=8c377624-f972-4b2b-9364-832f70b2a67a
InstallationDate: Installed on 2016-05-15 (375 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 lo no wireless extensions.

 eno1 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=47d8903b-afb2-4432-bc92-b1f4e30209ef ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-78-generic N/A
 linux-backports-modules-4.4.0-78-generic N/A
 linux-firmware 1.157.8
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P9X79 PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd07/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3

[tomdean (tomdean)]

On 05/30/2017 08:14 AM, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?

This did not start happening after an upgrade.
I do not know of a previous version where this did work.

>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.12 kernel[0].

The v4.12.0-041200rc3-generic kernel would not boot. In grub, I
selected the kernel to boot. The system hung with a black screen and a
blinking cursor at the top left. This happened with generic, upstart,
and recovery.

I installed the 4.22.3 kernel,
 > uname -a
Linux P9X79 4.11.3-041103-generic #201705251233 SMP Thu May 25 16:34:52
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

This boots but has the same USB 3.0 problem as 4.4.0-75-generic.

Tom Dean

[tomdean (tomdean)]

I installed the '4.22.3' kernel, should be 4.11.3

I marked the bug as confirmed as requested by Joseph Salisbury.

I also tagged the bug as 'kernel-bug-exists-upstream' as requested by Joseph Salisbury.

[tomdean (tomdean)]

As suggested by kai.heng.feng, I installed the 4.12.0-041200rc2 kernel.

If I connect my WD My Passport drive into an Plugable 7-port, external
USB 3.0 hub, it is not recognized. 'sudo lsusb -v' causes the drive to
be recognized and I can mount it. If I disconnect the drive, wait a few
seconds, and connect it back to the same port in the external USB 3.0
hub, it is not recognized.

If I connect the WD My Passport drive to a MOTHERBOARD USB 3.0 port, it
is recognized and I can mount it. Disconnecting and reconnecting the
drive to a MOTHERBOARD USB 3.0 port, it is again recognized.

The difference is using the external USB 3.0 hub port or the motherboard
USB 3.0 port.

[Kai-Heng Feng (kaihengfeng)]

You mentioned
"3. Mount the drive and start a dump level 0.
     After a 1/2 hour, or so, dump required operator intervention.
     In dmesg, the drive disconnected and reconnected as sdg."

Does this happen to the motherboard port?

[Kai-Heng Feng (kaihengfeng)]

Sounds like there are two problems here,
1. The external drive does not work well in UAS mode (see previous comment)
2. The VIA hub has a remote wakeup bug.

[tomdean (tomdean)]

On 06/02/2017 12:27 AM, Kai-Heng Feng wrote:
> Sounds like there are two problems here,
> 1. The external drive does not work well in UAS mode (see previous comment)
> 2. The VIA hub has a remote wakeup bug.
>

 > uname -a
Linux P9X79 4.12.0-041200rc2-generic #201705212331 SMP Mon May 22
03:32:26 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I connected the WD My Passport to a motherboard USB 3.0 port. It was
recognized. A level 0 dump completed:
   DUMP: 160901600 blocks (157130.47MB) on 1 volume(s)
   DUMP: finished in 1970 seconds, throughput 81675 kBytes/sec
Note: the tunables are at the kernel default settings.

Remote wakeup: tested with a Broadcom Bluetooth device.

 > lsusb
Bus 002 Device 003: ID 0cf3:3005 Qualcomm Atheros Communications AR3011
      Bluetooth
Bus 002 Device 002: ID 8087:0024 Intel Corp.Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 009: ID 1058:25e2 Western Digital Technologies, Inc.
Bus 006 Device 004: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 006 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 006 Device 002: ID 2109:0810 VIA Labs, Inc. VL81x Hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 004: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 005 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 005 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 045e:00cb MicrosoftCorp. Basic Optical Mouse v2.0
Bus 001 Device 003: ID 045e:0768 Microsoft Corp. Sidewinder X4
Bus 001 Device 002: ID 8087:0024 Intel Corp.Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Connect a bluetooth device to the external USB 3.0 hub.

 > lsusb | grep Bluetooth
Bus 002 Device 003: ID 0cf3:3005 Qualcomm Atheros Communications AR3011
Bluetooth
Bus 005 Device 007: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0

A device other than the WD My Passport is recognized upon connection to
the external USB 3.0 hub.

[Kai-Heng Feng (kaihengfeng)]

If you plugged a USB mouse or keyboard to the same port, will it be recognized?

[tomdean (tomdean)]

On 06/05/2017 08:57 PM, Kai-Heng Feng wrote:
> If you plugged a USB mouse or keyboard to the same port, will it be
> recognized?
>

I plugged a Microsoft USB 2.0 mouse into the externa Plugable USB 3.0
hub and it was recognized.

[Kai-Heng Feng (kaihengfeng)]

Okay, I just found a hub with the same VIA chip inside.
Remote wakeup works when autosuspend is enabled.

Hub like this generally can connect to auxiliary power cord. Does power cord connection make any difference?

[tomdean (tomdean)]

On 08/03/2017 10:54 PM, Kai-Heng Feng wrote:
> Okay, I just found a hub with the same VIA chip inside.
> Remote wakeup works when autosuspend is enabled.
>
> Hub like this generally can connect to auxiliary power cord. Does power
> cord connection make any difference?
>

I normally run the hub with a power cord connected, providing power to
the unit.

Tom Dean

[tomdean (tomdean)]

On 08/03/2017 10:54 PM, Kai-Heng Feng wrote:
> Okay, I just found a hub with the same VIA chip inside.
> Remote wakeup works when autosuspend is enabled.
>
> Hub like this generally can connect to auxiliary power cord. Does power
> cord connection make any difference?
>

I upgraded the system by apt-get dist-upgrade and rebooted.

Now, the WD drive is recognized when plugged into the USB 3.0 powered Hub.

Dump completed without error.

Unmount and disconnect the drive. Wait a few seconds. Reconnect the drive.

In dmesg, the drive is seen, but, it takes several seconds before it is
fully recognized.

Repeated the umount and disconnect several times. Each time, it took a
few seconds, but, the drive was recognized and I was able to mount it.

 > dmesg -T | tail
[Mon Aug 7 20:35:26 2017] usb 6-1.2.4: USB disconnect, device number 8
[Mon Aug 7 20:35:29 2017] usb 6-1.2.4: new SuperSpeed USB device number
9 using xhci_hcd
[Mon Aug 7 20:35:29 2017] usb 6-1.2.4: New USB device found,
idVendor=1058, idProduct=25e2
[Mon Aug 7 20:35:29 2017] usb 6-1.2.4: New USB device strings: Mfr=2,
Product=3, SerialNumber=1
[Mon Aug 7 20:35:29 2017] usb 6-1.2.4: Product: My Passport 25E2
[Mon Aug 7 20:35:29 2017] usb 6-1.2.4: Manufacturer: Western Digital
[Mon Aug 7 20:35:29 2017] usb 6-1.2.4: SerialNumber:
575853314131374E50323158
[Mon Aug 7 20:35:29 2017] usb-storage 6-1.2.4:1.0: USB Mass Storage
device detected
[Mon Aug 7 20:35:29 2017] usb-storage 6-1.2.4:1.0: Quirks match for vid
1058 pid 25e2: 800000
[Mon Aug 7 20:35:29 2017] scsi host16: usb-storage 6-1.2.4:1.0
[Mon Aug 7 20:35:30 2017] scsi 16:0:0:0: Direct-Access WD My
Passport 25E2 4004 PQ: 0 ANSI: 6
[Mon Aug 7 20:35:30 2017] scsi 16:0:0:1: Enclosure WD SES
Device 4004 PQ: 0 ANSI: 6
[Mon Aug 7 20:35:30 2017] sd 16:0:0:0: Attached scsi generic sg7 type 0
[Mon Aug 7 20:35:30 2017] ses 16:0:0:1: Attached Enclosure device
[Mon Aug 7 20:35:30 2017] ses 16:0:0:1: Attached scsi generic sg8 type 13
[Mon Aug 7 20:35:30 2017] sd 16:0:0:0: [sdf] Spinning up disk...
[Mon Aug 7 20:35:31 2017] .
[Mon Aug 7 20:35:32 2017] .
[Mon Aug 7 20:35:33 2017] .
[Mon Aug 7 20:35:34 2017] .
[Mon Aug 7 20:35:34 2017] ready
[Mon Aug 7 20:35:34 2017] sd 16:0:0:0: [sdf] 3906963456 512-byte
logical blocks: (2.00 TB/1.82 TiB)
[Mon Aug 7 20:35:34 2017] sd 16:0:0:0: [sdf] Write Protect is off
[Mon Aug 7 20:35:34 2017] sd 16:0:0:0: [sdf] Mode Sense: 47 00 10 08
[Mon Aug 7 20:35:34 2017] sd 16:0:0:0: [sdf] No Caching mode page found
[Mon Aug 7 20:35:34 2017] sd 16:0:0:0: [sdf] Assuming drive cache:
write through
[Mon Aug 7 20:35:34 2017] sdf: sdf1
[Mon Aug 7 20:35:34 2017] sd 16:0:0:0: [sdf] Attached SCSI disk

Maybe it safe to close this report????

Tom Dean

[Kai-Heng Feng (kaihengfeng)]

Probably. Although a quick look at the USB stack difference from 4.4.0-78.99 to 4.4.0-89.112, I can't find commits related to this issue.

But feel free to reopen the bug if this happens again.

[tomdean (tomdean)]

On 08/07/2017 11:39 PM, Kai-Heng Feng wrote:
> Probably. Although a quick look at the USB stack difference from
> 4.4.0-78.99 to 4.4.0-89.112, I can't find commits related to this issue.
>
> But feel free to reopen the bug if this happens again.
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Fix Released
>

I don't understand why this is now working.

I am still running 4.12.0-041200rc2.

> uname -a
Linux P9X79 4.12.0-041200rc2-generic #201705212331 SMP Mon May 22
03:32:26 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

> cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

> dmesg -T | tail
[Tue Aug 8 11:40:47 2017] usb 6-1.2.4: USB disconnect, device number 9
[Tue Aug 8 11:40:51 2017] usb 6-1.2.2: new SuperSpeed USB device number
10 using xhci_hcd
[Tue Aug 8 11:40:51 2017] usb 6-1.2.2: New USB device found,
idVendor=1058, idProduct=25e2
[Tue Aug 8 11:40:51 2017] usb 6-1.2.2: New USB device strings: Mfr=2,
Product=3, SerialNumber=1
[Tue Aug 8 11:40:51 2017] usb 6-1.2.2: Product: My Passport 25E2
[Tue Aug 8 11:40:51 2017] usb 6-1.2.2: Manufacturer: Western Digital
[Tue Aug 8 11:40:51 2017] usb 6-1.2.2: SerialNumber:
575853314131374E50323158
[Tue Aug 8 11:40:51 2017] usb-storage 6-1.2.2:1.0: USB Mass Storage
device detected
[Tue Aug 8 11:40:51 2017] usb-storage 6-1.2.2:1.0: Quirks match for vid
1058 pid 25e2: 800000
[Tue Aug 8 11:40:51 2017] scsi host16: usb-storage 6-1.2.2:1.0
[Tue Aug 8 11:40:52 2017] scsi 16:0:0:0: Direct-Access WD My
Passport 25E2 4004 PQ: 0 ANSI: 6
[Tue Aug 8 11:40:52 2017] scsi 16:0:0:1: Enclosure WD SES
Device 4004 PQ: 0 ANSI: 6
[Tue Aug 8 11:40:52 2017] sd 16:0:0:0: Attached scsi generic sg7 type 0
[Tue Aug 8 11:40:52 2017] ses 16:0:0:1: Attached Enclosure device
[Tue Aug 8 11:40:52 2017] ses 16:0:0:1: Attached scsi generic sg8 type 13
[Tue Aug 8 11:40:52 2017] sd 16:0:0:0: [sdf] Spinning up disk...
[Tue Aug 8 11:40:53 2017] .
[Tue Aug 8 11:40:54 2017] .
[Tue Aug 8 11:40:55 2017] .
[Tue Aug 8 11:40:56 2017] .
[Tue Aug 8 11:40:57 2017] .
[Tue Aug 8 11:40:58 2017] .
[Tue Aug 8 11:40:58 2017] ready
[Tue Aug 8 11:40:58 2017] sd 16:0:0:0: [sdf] 3906963456 512-byte
logical blocks: (2.00 TB/1.82 TiB)
[Tue Aug 8 11:40:58 2017] sd 16:0:0:0: [sdf] Write Protect is off
[Tue Aug 8 11:40:58 2017] sd 16:0:0:0: [sdf] Mode Sense: 47 00 10 08
[Tue Aug 8 11:40:58 2017] sd 16:0:0:0: [sdf] No Caching mode page found
[Tue Aug 8 11:40:58 2017] sd 16:0:0:0: [sdf] Assuming drive cache:
write through
[Tue Aug 8 11:40:58 2017] sdf: sdf1
[Tue Aug 8 11:40:58 2017] sd 16:0:0:0: [sdf] Attached SCSI disk

Tom Dean

[Pablo (ppmmcc01)]

Hi,

I have a USB 3.0 Disk 2TB (WD Elements).

When I plug in a 2.0 USB Port the disk is recognized, but when I plug in a 3.0 USB Port the disk is not recognized and the dmesg not show anything.

This is the exit of command "sudo lsusb":

Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 062a:4101 Creative Labs Wireless Keyboard/Mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

This is the exit of command "lsusb -v -d 1d6b:0003":

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 3.00
  bDeviceClass 9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 3
  bMaxPacketSize0 9
  idVendor 0x1d6b Linux Foundation
  idProduct 0x0003 3.0 root hub
  bcdDevice 4.04
  iManufacturer 3 Linux 4.4.0-103-generic xhci-hcd
  iProduct 2 xHCI Host Controller
  iSerial 1 0000:00:14.0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 31
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 0mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 9 Hub
      bInterfaceSubClass 0 Unused
      bInterfaceProtocol 0 Full speed (or root) hub
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0004 1x 4 bytes
        bInterval 12
        bMaxBurst 0
Hub Descriptor:
  bLength 12
  bDescriptorType 42
  nNbrPorts 2
  wHubCharacteristic 0x000a
    No power switching (usb 1.0)
    Per-port overcurrent protection
  bPwrOn2PwrGood 10 * 2 milli seconds
  bHubContrCurrent 0 milli Ampere
  bHubDecLat 0.0 micro seconds
  wHubDelay 0 nano seconds
  DeviceRemovable 0x00
 Hub Port Status:
   Port 1: 0000.02a0 5Gbps power Rx.Detect
   Port 2: 0000.02a0 5Gbps power Rx.Detect
Binary Object Store Descriptor:
  bLength 5
  bDescriptorType 15
  wTotalLength 15
  bNumDeviceCaps 1
  SuperSpeed USB Device Capability:
    bLength 10
    bDescriptorType 16
    bDevCapabilityType 3
    bmAttributes 0x02
      Latency Tolerance Messages (LTM) Supported
    ...

[Pablo (ppmmcc01)]

Hi again,

I forgot to comment that this issue also appear in Debian 9 (my other PC)...

[tomdean (tomdean)]

On 01/04/18 09:29, Pablo wrote:
> Hi again,
>
> I forgot to comment that this issue also appear in Debian 9 (my other
> PC)...
>

As I posted earlier, this seems to be related to the version of Linux.

I do not have this problem with

Meerkat> uname -a
Linux Meerkat 4.13.9-041309-generic #201710211231 SMP Sat Oct 21
16:32:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

P9X79> uname -a
Linux P9X79 4.12.0-041200rc2-generic #201705212331 SMP Mon May 22
03:32:26 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Tom Dean