Issues with USB 3.0 hard drives

I’m having some issues with external USB 3.0 HDDs. I’m using the AGX DevKit with JetPack 4.5.1 and two brand new Seagate drives are having issues, while working perfectly with a desktop Linux computer. A USB power portable drive shows very slow performance and it doesn’t eject properly. And a powered external drive is not recognized as a valid drive: it’s listed by lsusb, it shows up in Disks but the partition is not recognized. Is there any particular issue with Seagate drives? Any other troubleshooting ideas?

Can you check if the dmesg gives out any error when you write file to the usb disk and when the partition is gone?

Also, can you use some tool like iozone to test the write speed to the Segate drive?

Does same issue happen to other non-Segate brand HDD?

1 Like

If a drive is able to connect to the bus, then you might also consider using the drive’s own diagnostics to see what it thinks. If you don’t have it installed already, you can add the “smartctl” command via “sudo apt-get install smartmontools”.

To see and create a log of what the smartdrive output is for “/dev/sda”, you could run this command (assuming it is “/dev/sda”):
sudo smartctl -a /dev/sda 2>&1 | tee log_smartctl_sda.txt

Also, if the drive works, you might post the output from (assuming sda):
sudo gdisk -l /dev/sda
(or logged: “sudo gdisk -l /dev/sda 2>&1 | tee log_sda_partitions.txt”)

1 Like

Here’s the output of dmesg:

[591986.115951] usb 2-3: new SuperSpeed USB device number 4 using tegra-xusb
[591986.136508] usb 2-3: New USB device found, idVendor=0bc2, idProduct=331a
[591986.136518] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[591986.136524] usb 2-3: Product: Expansion Desk
[591986.136529] usb 2-3: Manufacturer: Seagate
[591986.136534] usb 2-3: SerialNumber: NAABSB52
[591986.147118] scsi host3: uas
[591986.149248] scsi 3:0:0:0: Direct-Access     Seagate  Expansion Desk   0915 PQ: 0 ANSI: 6
[591986.188567] sd 3:0:0:0: [sdb] Spinning up disk...
[591987.215145] .
[591988.239063] .
[591989.263011] .
[591990.286959] .
[591991.310949] .
[591991.712559] ucsi_ccg 1-0008: port0 evt: Source Disabled State Entered
[591992.163450] hub 2-1:1.0: hub_ext_port_status failed (err = -110)
[591992.334851] .
[591993.358847] .
[591994.382739] .
[591995.406679] .
[591996.430635] .
[591997.454588] .
[591997.454863] ready
[591997.455180] sd 3:0:0:0: [sdb] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB)
[591997.455409] sd 3:0:0:0: [sdb] 4096-byte physical blocks
[591997.456546] sd 3:0:0:0: [sdb] Write Protect is off
[591997.456674] sd 3:0:0:0: [sdb] Mode Sense: 53 00 00 08
[591997.457137] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[591998.211651] sd 3:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[591998.273742]  sdb: sdb1 sdb2
[591998.276583] sd 3:0:0:0: [sdb] Attached SCSI disk
[592002.242908] hub 2-1:1.0: hub_ext_port_status failed (err = -110)
[592012.322436] hub 2-1:1.0: hub_ext_port_status failed (err = -110)
[592022.401871] hub 2-1:1.0: hub_ext_port_status failed (err = -110)
[592032.481414] hub 2-1:1.0: hub_ext_port_status failed (err = -110)
[592042.560814] hub 2-1:1.0: hub_ext_port_status failed (err = -110)
[592052.640218] hub 2-1:1.0: hub_ext_port_status failed (err = -110)
[592062.719713] hub 2-1:1.0: hub_ext_port_status failed (err = -110)
[592072.799164] hub 2-1:1.0: hub_ext_port_status failed (err = -110)
[592082.878646] hub 2-1:1.0: hub_ext_port_status failed (err = -110)
[592092.958163] hub 2-1:1.0: hub_ext_port_status failed (err = -110)
[592103.037549] hub 2-1:1.0: hub_ext_port_status failed (err = -110)

smartctl didn’t work right away, but after some research I was able to get something out of it with sudo smartctl -d sat -T permissive -a /dev/sdb

smartctl 6.6 2016-05-31 r4324 [aarch64-linux-4.9.201-tegra] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke,

Read Device Identity failed: scsi error unsupported field in scsi command

Device Model:     [No Information Found]
Serial Number:    [No Information Found]
Firmware Version: [No Information Found]
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   [No Information Found]
Local Time is:    Thu Aug  5 12:02:04 2021 EDT
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

And this is gdisk:

GPT fdisk (gdisk) version 1.0.3

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 15628053167 sectors, 7.3 TiB
Model: Expansion Desk  
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): A6193E12-97C9-4FD4-8ACD-F5859361776B
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 15628053133
Partitions will be aligned on 8-sector boundaries
Total free space is 2668 sectors (1.3 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              34          262177   128.0 MiB   0C01  Microsoft reserved ...
   2          264192     15628052479   7.3 TiB     0700  Basic data partition

Hard to say, but is this going through a USB HUB? Or is the disk directly connected to the Jetson? There seem to be a lot of similar issues in web searches which mostly point to the HUB itself. If this goes through a HUB, can you remove that HUB and try either a different HUB (or better yet) a direct USB connection without a HUB?

Also, is the drive self-powered? I am hoping so. If not, then when testing with another USB HUB I suggest one which is externally powered and not powered via the USB cable.

It is possible that the smartctl command doesn’t work over USB, but it is also possible that USB issues cause the command to fail. I don’t think much can be said about the disk itself until the USB side talking to the disk is working.

1 Like

@linuxdev the drive is self-powered and directly connected to the DevKit. I tested a couple of other external HDDs, both self-powered and USB-powered, and they worked properly. I’m starting to suspect that there’s something funky with Seagate enclosures.

I couldn’t say for sure on this, and I’m not sure how to otherwise test. As you suspect I also suspect that there might be something different about that enclosure since it is USB which first shows an error, and you can’t really make a conclusion about the hard drive side of things until USB works correctly.

About the only test I can think of to narrow it further is to swap some known “standard” hard drive into the enclosure (if you can), and see if the USB issues remain.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.