The H/D disables the USB 3 port once it was plugged in (via Amazon USB-3 hub or direct connectoin).
The same connection works for WD 4TB H/D. It makes me think that the problem is specific to Seagate H/D (5TB model: SRD0NF1, file type: NTFS).
When plugged the H/D to USB, the light on the H/D blinked a few seconds and turned stable. But the entire USB hub went down the same time. Unplug the hub and plug in any USB device would have no response on the port.
I had to reflash the TX2, and made sure to have a Bluetooth mouse and keyboard connected before trying to duplicate the case on my second Seagate H/D (same model). BTW, the good news is that recovery mode works; while “reset” or reboot maks no difference one the USB port is disabled.
Plug in the second Seagate 5TB H/D, and soon the USB port goes down like the other H/D. Same failure!
If I run “lsusb” command, only two buses are shown after the USB port went down:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The other buses are not shown, which should otherwise be seen normally such as
Bus 002 Device 002: ID 2109:8110 VIA Labs, Inc. Hub
I then plugged the Seagate H/D to a Windows 10 PC. The drive works.
It seems to me the issue is related to compatibility. Ideally, it’d be better to reject a unwanted external device, instead being killed by the device.
I can do another round of debug/rebuild before return the Seagate H/Ds. Please let me know if any idea to bring the USB port back to life.