Arch Linux

InFerYes

Member

Registered: 2012-11-13

Posts: 67

USB disk keeps disconnecting

Hi, I have a USB disk I use to create backups. I've been using this device in this configuration for a few years, today it started acting up. It has disconnected 4 times today.  What's different is that I have a new PC and this is the first time I'm using this PC to create the backup. The disk is a 20TB TOSHIBA MG10ACA20TE (0102). It is always disconnected and in a powered off state, unless I want to create a backup or restore a file.

This backup is a 20TB LUKS encrypted volume with a 20TB Ext4 FS.

My old PC had 1 blue USB3 connector on the back panel of the mainboard that I used to connect this disk to. This PC has several, as well as on the front-panel of the case. I used the red USB3 port that is labeled USB 10G. The hard drive enclosure is a StarTech.com USB3.1 Gen2 (https://www.amazon.co.uk/StarTech-com-S … AZEFC?th=1)

The command I use is rsync -av --delete --exclude 'Security' . /run/media/user/Backup/server2 --progress

lsusb (erroneous state):

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0489:e10a Foxconn / Hon Hai 
Bus 001 Device 003: ID 0db0:0076 Micro Star International MYSTIC LIGHT
Bus 002 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 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 007 Device 003: ID 046d:c07e Logitech, Inc. G402 Gaming Mouse
Bus 007 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 007 Device 005: ID 3434:0251 Keychron Keychron K5 Pro
Bus 007 Device 006: ID 534d:2109 MacroSilicon USB Video

lsblk (sdc, correct state, disk is not listed in lsblk when in erroneous state)

NAME                                        MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda                                           8:0    0 931,5G  0 disk  
└─sda1                                        8:1    0 931,5G  0 part  
sdb                                           8:16   0 232,9G  0 disk  
└─sdb1                                        8:17   0 232,9G  0 part  
sdc                                           8:32   0  18,2T  0 disk  
└─luks-1526e5b2-ba12-4d3a-9e61-ae443891454f 253:0    0  18,2T  0 crypt /run/media/user/Backup
nvme1n1                                     259:0    0 931,5G  0 disk  
├─nvme1n1p1                                 259:1    0   512M  0 part  /boot
├─nvme1n1p2                                 259:2    0 638,7G  0 part  /
├─nvme1n1p3                                 259:3    0    16M  0 part  
├─nvme1n1p4                                 259:4    0 291,8G  0 part  
└─nvme1n1p5                                 259:5    0   515M  0 part  
nvme0n1                                     259:6    0 931,5G  0 disk  
├─nvme0n1p1                                 259:7    0    16M  0 part  
├─nvme0n1p2                                 259:8    0 698,1G  0 part  
└─nvme0n1p3                                 259:9    0 233,4G  0 part  

(partial) dmesg:

[36728.775728] sd 6:0:0:0: [sdc] tag#29 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT 
[36728.775738] sd 6:0:0:0: [sdc] tag#29 CDB: Write(16) 8a 00 00 00 00 04 ce 12 44 00 00 00 04 00 00 00
[36728.775826] sd 6:0:0:0: [sdc] tag#28 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT 
[36728.775829] sd 6:0:0:0: [sdc] tag#28 CDB: Write(16) 8a 00 00 00 00 04 ce 12 40 00 00 00 04 00 00 00
[36728.775891] sd 6:0:0:0: [sdc] tag#27 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT 
[36728.775893] sd 6:0:0:0: [sdc] tag#27 CDB: Write(16) 8a 00 00 00 00 04 ce 12 30 00 00 00 04 00 00 00
[36728.775955] sd 6:0:0:0: [sdc] tag#26 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT 
[36728.775957] sd 6:0:0:0: [sdc] tag#26 CDB: Write(16) 8a 00 00 00 00 04 ce 12 3c 00 00 00 04 00 00 00
[36728.776023] sd 6:0:0:0: [sdc] tag#25 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT 
[36728.776025] sd 6:0:0:0: [sdc] tag#25 CDB: Write(16) 8a 00 00 00 00 04 ce 12 38 00 00 00 04 00 00 00
[36728.776087] sd 6:0:0:0: [sdc] tag#24 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT 
[36728.776088] sd 6:0:0:0: [sdc] tag#24 CDB: Write(16) 8a 00 00 00 00 04 ce 12 34 00 00 00 04 00 00 00
[36728.776153] sd 6:0:0:0: [sdc] tag#4 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD OUT 
[36728.776155] sd 6:0:0:0: [sdc] tag#4 CDB: Write(16) 8a 00 00 00 00 04 ce 12 58 00 00 00 04 00 00 00
[36728.776220] sd 6:0:0:0: [sdc] tag#3 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT 
[36728.776221] sd 6:0:0:0: [sdc] tag#3 CDB: Write(16) 8a 00 00 00 00 04 ce 12 54 00 00 00 04 00 00 00
[36728.776287] sd 6:0:0:0: [sdc] tag#2 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT 
[36728.776288] sd 6:0:0:0: [sdc] tag#2 CDB: Write(16) 8a 00 00 00 00 04 ce 12 50 00 00 00 04 00 00 00
[36728.776353] sd 6:0:0:0: [sdc] tag#1 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD OUT 
[36728.776354] sd 6:0:0:0: [sdc] tag#1 CDB: Write(16) 8a 00 00 00 00 04 ce 12 4c 00 00 00 04 00 00 00
[36728.776417] sd 6:0:0:0: [sdc] tag#0 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT 
[36728.776418] sd 6:0:0:0: [sdc] tag#0 CDB: Write(16) 8a 00 00 00 00 04 ce 12 48 00 00 00 04 00 00 00
[36728.787718] scsi host6: uas_eh_device_reset_handler start
[36728.787783] usb 4-1: cmd cmplt err -2
[36734.383738] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36740.015732] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36740.223705] usb 4-1: device not accepting address 12, error -62
[36745.647721] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36751.279712] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36751.487676] usb 4-1: device not accepting address 12, error -62
[36756.911705] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36762.543708] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36762.752668] usb 4-1: device not accepting address 12, error -62
[36768.175695] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36773.807666] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36774.016651] usb 4-1: device not accepting address 12, error -62
[36774.032782] usb 4-1: USB disconnect, device number 12
[36774.032787] scsi host6: uas_eh_device_reset_handler FAILED err -19
[36774.032794] sd 6:0:0:0: Device offlined - not ready after error recovery
[36774.032796] sd 6:0:0:0: Device offlined - not ready after error recovery
[36774.032798] sd 6:0:0:0: Device offlined - not ready after error recovery
[36774.032799] sd 6:0:0:0: Device offlined - not ready after error recovery
[36774.032800] sd 6:0:0:0: Device offlined - not ready after error recovery
[36774.032800] sd 6:0:0:0: Device offlined - not ready after error recovery
[36774.032801] sd 6:0:0:0: Device offlined - not ready after error recovery
[36774.032802] sd 6:0:0:0: Device offlined - not ready after error recovery
[36774.032803] sd 6:0:0:0: Device offlined - not ready after error recovery
[36774.032804] sd 6:0:0:0: Device offlined - not ready after error recovery
[36774.032805] sd 6:0:0:0: Device offlined - not ready after error recovery
[36774.032816] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=75s
[36774.032819] sd 6:0:0:0: [sdc] tag#0 CDB: Write(16) 8a 00 00 00 00 04 ce 12 48 00 00 00 04 00 00 00
[36774.032820] I/O error, dev sdc, sector 20637173760 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2
[36774.036684] EXT4-fs warning (device dm-0): ext4_end_bio:369: I/O error 16 writing to inode 153456664 starting block 2579642336)
[36774.036693] EXT4-fs (dm-0): failed to convert unwritten extents to written extents -- potential data loss!  (inode 153456664, error -5)
[36774.036698] buffer_io_error: 92150 callbacks suppressed
[36774.036699] Buffer I/O error on device dm-0, logical block 2579640320
[36774.036701] Buffer I/O error on device dm-0, logical block 2579640321
[36774.036701] Buffer I/O error on device dm-0, logical block 2579640322
[36774.036702] Buffer I/O error on device dm-0, logical block 2579640323
[36774.036702] Buffer I/O error on device dm-0, logical block 2579640324
[36774.036703] Buffer I/O error on device dm-0, logical block 2579640325
[36774.036703] Buffer I/O error on device dm-0, logical block 2579640326
[36774.036704] Buffer I/O error on device dm-0, logical block 2579640327
[36774.036704] Buffer I/O error on device dm-0, logical block 2579640328
[36774.036704] Buffer I/O error on device dm-0, logical block 2579640329
[36774.036811] EXT4-fs warning (device dm-0): ext4_end_bio:369: I/O error 10 writing to inode 153456664 starting block 2579646432)
[36774.036875] EXT4-fs warning (device dm-0): ext4_end_bio:369: I/O error 10 writing to inode 153456664 starting block 2579648480)
[36774.036897] EXT4-fs (dm-0): failed to convert unwritten extents to written extents -- potential data loss!  (inode 153456664, error -5)
[36774.036934] EXT4-fs warning (device dm-0): ext4_end_bio:369: I/O error 10 writing to inode 153456664 starting block 2579650528)
[36774.036999] EXT4-fs warning (device dm-0): ext4_end_bio:369: I/O error 10 writing to inode 153456664 starting block 2579652576)
[36774.037059] EXT4-fs warning (device dm-0): ext4_end_bio:369: I/O error 10 writing to inode 153456664 starting block 2579654624)
[36774.037088] EXT4-fs (dm-0): failed to convert unwritten extents to written extents -- potential data loss!  (inode 153456664, error -5)
[36774.037126] EXT4-fs warning (device dm-0): ext4_end_bio:369: I/O error 10 writing to inode 153456664 starting block 2579656672)
[36774.037195] EXT4-fs warning (device dm-0): ext4_end_bio:369: I/O error 10 writing to inode 153456664 starting block 2579658720)
[36774.037264] EXT4-fs warning (device dm-0): ext4_end_bio:369: I/O error 10 writing to inode 153456664 starting block 2579660768)
[36774.037271] EXT4-fs (dm-0): failed to convert unwritten extents to written extents -- potential data loss!  (inode 153456664, error -5)
[36774.037323] EXT4-fs warning (device dm-0): ext4_end_bio:369: I/O error 10 writing to inode 153456664 starting block 2579662816)
[36774.037453] EXT4-fs (dm-0): failed to convert unwritten extents to written extents -- potential data loss!  (inode 153456664, error -5)
[36774.037630] EXT4-fs (dm-0): failed to convert unwritten extents to written extents -- potential data loss!  (inode 153456664, error -5)
[36774.037680] Buffer I/O error on dev dm-0, logical block 1230, lost async page write
[36774.037685] Buffer I/O error on dev dm-0, logical block 2441375175, lost sync page write
[36774.037695] Aborting journal on device dm-0-8.
[36774.037700] Buffer I/O error on dev dm-0, logical block 2578972685, lost async page write
[36774.037702] Buffer I/O error on dev dm-0, logical block 2578972686, lost async page write
[36774.037704] Buffer I/O error on dev dm-0, logical block 2578972687, lost async page write
[36774.037705] EXT4-fs error (device dm-0) in ext4_reserve_inode_write:6291: Journal has aborted
[36774.037722] Buffer I/O error on dev dm-0, logical block 2441117696, lost sync page write
[36774.037726] JBD2: I/O error when updating journal superblock for dm-0-8.
[36774.037734] EXT4-fs (dm-0): Delayed block allocation failed for inode 153456665 at logical offset 0 with max blocks 2048 with error 5
[36774.037737] EXT4-fs (dm-0): This should not happen!! Data will be lost

[36774.037739] EXT4-fs error (device dm-0) in ext4_do_writepages:2948: IO failure
[36774.037743] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
[36774.037748] EXT4-fs (dm-0): previous I/O error to superblock detected
[36774.037756] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
[36774.037759] EXT4-fs (dm-0): I/O error while writing superblock
[36774.060784] sd 6:0:0:0: [sdc] Synchronizing SCSI cache
[36774.221656] sd 6:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[36779.439645] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36785.071655] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36785.279636] usb 4-1: device not accepting address 13, error -62
[36790.703636] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36796.335632] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36796.543601] usb 4-1: device not accepting address 14, error -62
[36796.551647] usb usb4-port1: attempt power cycle
[36802.479646] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36808.111624] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36808.319587] usb 4-1: device not accepting address 15, error -62
[36813.743613] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36819.375602] xhci_hcd 0000:11:00.3: Timeout while waiting for setup device command
[36819.583565] usb 4-1: device not accepting address 16, error -62
[36819.591659] usb usb4-port1: unable to enumerate USB device
[39632.582163] usb 2-3: new SuperSpeed USB device number 2 using xhci_hcd
[39632.595911] usb 2-3: New USB device found, idVendor=174c, idProduct=1053, bcdDevice= 1.00
[39632.595918] usb 2-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[39632.595919] usb 2-3: Product: USB3.0 Device
[39632.595920] usb 2-3: Manufacturer: Generic
[39632.595921] usb 2-3: SerialNumber: AC0000000001
[39632.634958] scsi host7: uas
[39632.635301] scsi 7:0:0:0: Direct-Access     ASMT     2105             0    PQ: 0 ANSI: 6
[39632.636511] sd 7:0:0:0: Attached scsi generic sg2 type 0
[39658.889709] sd 7:0:0:0: [sdd] 39063650304 512-byte logical blocks: (20.0 TB/18.2 TiB)
[39658.889714] sd 7:0:0:0: [sdd] 4096-byte physical blocks
[39658.889825] sd 7:0:0:0: [sdd] Write Protect is off
[39658.889826] sd 7:0:0:0: [sdd] Mode Sense: 43 00 00 00
[39658.889986] sd 7:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[39658.914102] sd 7:0:0:0: [sdd] Preferred minimum I/O size 512 bytes not a multiple of physical block size (4096 bytes)
[39658.914106] sd 7:0:0:0: [sdd] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[39658.939914] sd 7:0:0:0: [sdd] Attached SCSI disk
[39694.619661] EXT4-fs: 1 callbacks suppressed
[39694.619665] EXT4-fs (dm-0): unmounting filesystem a31f7d3e-e323-43e1-89b4-e4ea73f9fd0f.
[39718.100999] usb 2-3: USB disconnect, device number 2
[39718.114832] sd 7:0:0:0: [sdd] Synchronizing SCSI cache
[39718.279034] sd 7:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[39891.149515] usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd
[39891.162267] usb 2-3: New USB device found, idVendor=174c, idProduct=1053, bcdDevice= 1.00
[39891.162269] usb 2-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[39891.162270] usb 2-3: Product: USB3.0 Device
[39891.162271] usb 2-3: Manufacturer: Generic
[39891.162272] usb 2-3: SerialNumber: AC0000000001
[39891.201128] scsi host6: uas
[39891.201514] scsi 6:0:0:0: Direct-Access     ASMT     2105             0    PQ: 0 ANSI: 6
[39891.202726] sd 6:0:0:0: Attached scsi generic sg2 type 0
[39911.716894] sd 6:0:0:0: [sdc] 39063650304 512-byte logical blocks: (20.0 TB/18.2 TiB)
[39911.716901] sd 6:0:0:0: [sdc] 4096-byte physical blocks
[39911.717054] sd 6:0:0:0: [sdc] Write Protect is off
[39911.717059] sd 6:0:0:0: [sdc] Mode Sense: 43 00 00 00
[39911.717235] sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[39911.741248] sd 6:0:0:0: [sdc] Preferred minimum I/O size 512 bytes not a multiple of physical block size (4096 bytes)
[39911.741253] sd 6:0:0:0: [sdc] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[39911.764002] sd 6:0:0:0: [sdc] Attached SCSI disk
[39927.905681] EXT4-fs (dm-0): recovery complete
[39927.908314] EXT4-fs (dm-0): mounted filesystem a31f7d3e-e323-43e1-89b4-e4ea73f9fd0f r/w with ordered data mode. Quota mode: none.
[40181.356764] handle_bus_lock: 13009 callbacks suppressed

/dev/mapper/luks-1526e5b2-ba12-4d3a-9e61-ae443891454f is active and is in use.
  type:    LUKS2
  cipher:  aes-xts-plain64
  keysize: 512 [bits]
  key location: keyring
  device:  /dev/sdc
  sector size:  4096 [bytes]
  offset:  32768 [512-byte units] (16777216 [bytes])
  size:    39063617536 [512-byte units] (20000572178432 [bytes])
  mode:    read/write

I had FS/disk issues earlier, but on a different PC, different disk, so unrelated. It does strike me as odd that I'm having mounting issues across different devices. This disk is mountable again after I toggle the enclosure's power button.

I have now changed to a different USB port (front panel of PC) to see if it will fail again after a while.

cryptearth

Member

Registered: 2024-02-03

Posts: 2,090

Re: USB disk keeps disconnecting

for bulk transfer avoid sockets with long internal leads - stick to whatever the board offers at rear - which should at least one fairly high speed usb-c these days

mmy8x

Member

Registered: 2025-03-02

Posts: 97

Re: USB disk keeps disconnecting

Hi, I have a USB disk I use to create backups. I've been using this device in this configuration for a few years, today it started acting up. It has disconnected 4 times today.  What's different is that I have a new PC and this is the first time I'm using this PC to create the backup.

Do you still have the old PC?
Does the disk work properly there?
Does it work for a time longer than typical time to failure on the new machine?
Are both machines running the same linux package version?

lsusb (erroneous state):

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0489:e10a Foxconn / Hon Hai 
Bus 001 Device 003: ID 0db0:0076 Micro Star International MYSTIC LIGHT
Bus 002 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 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 007 Device 003: ID 046d:c07e Logitech, Inc. G402 Gaming Mouse
Bus 007 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 007 Device 005: ID 3434:0251 Keychron Keychron K5 Pro
Bus 007 Device 006: ID 534d:2109 MacroSilicon USB Video

Which of these devices is the disk?
Or none of them?

(partial) dmesg

Could you post full dmesg from the moment of connection (or boot) up to things going weird?

Last edited by mmy8x (Yesterday 08:26:32)

InFerYes

Member

Registered: 2012-11-13

Posts: 67

Re: USB disk keeps disconnecting

for bulk transfer avoid sockets with long internal leads - stick to whatever the board offers at rear - which should at least one fairly high speed usb-c these days

As I mentioned, I used the port on the board directly. I crawled under the desk because I wanted to use those ports. Unfortunately, in this case, the ports on the front of the case proved to work better. I managed to run the full backup without further issues.

Hi, I have a USB disk I use to create backups. I've been using this device in this configuration for a few years, today it started acting up. It has disconnected 4 times today.  What's different is that I have a new PC and this is the first time I'm using this PC to create the backup.

Do you still have the old PC? No
Does the disk work properly there? It did, can't test anymore.
Does it work for a time longer than typical time to failure on the new machine? It used to run overnight. I'm not staying at the PC while it backs up 6TB over USB. The disk remained connected in the morning, when I would unmount.
Are both machines running the same linux package version? I have moved the internal disks, so it is the same configuration, just a different PC (mainboard, RAM, CPU, and GPU). I didn't want to start a fresh install. Of course, the packages are frequently updated.

lsusb (erroneous state):

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0489:e10a Foxconn / Hon Hai 
Bus 001 Device 003: ID 0db0:0076 Micro Star International MYSTIC LIGHT
Bus 002 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 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 007 Device 003: ID 046d:c07e Logitech, Inc. G402 Gaming Mouse
Bus 007 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 007 Device 005: ID 3434:0251 Keychron Keychron K5 Pro
Bus 007 Device 006: ID 534d:2109 MacroSilicon USB Video

Which of these devices is the disk? Bus 004 Device 001, which you can deduct from the dmesg output.
Or none of them?

(partial) dmesg

Could you post full dmesg from the moment of connection (or boot) up to things going weird?

Have replied in-quote next to your questions. I will check next time.

Mainly created the post because I can't shake the feeling something regressed. I'd rather go through the trouble to report it, if others experience the same issue it might be a larger thing, if not then I'm just in a stroke of bad luck with our disks

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,024

Re: USB disk keeps disconnecting

Mainly created the post because I can't shake the feeling something regressed.

Is this on the 7.0x kernel? Do you  get this w/ the LTS kernel?

Does this only happen under high pressure or also when just trying to cp few MB to the drive?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

InFerYes

Member

Registered: 2012-11-13

Posts: 67

Re: USB disk keeps disconnecting

Linux ranger 7.0.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 27 Apr 2026 18:22:44 +0000 x86_64 GNU/Linux

I haven't tried just letting it "sit" on that port without any actions, but I had it occur during the large copy job. I generally don't keep this disk attached longer than necessary. Unlike that other disk, this one does contain valuable data and I haven't needed it much, but it has happened that I needed to fish out a file that got corrupted, so I can't try any destructive test methods.

If it's OK, I'd like to let this sit until next backup, then I will try the front panel first (check if that indeed does keep working without unmounting), then try a larger copy on the mainboard port ("USB 10G").

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,024

Re: USB disk keeps disconnecting

This runs entirely at your pace - none of us is struggling with petulant drives

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

mmy8x

Member

Registered: 2025-03-02

Posts: 97

Re: USB disk keeps disconnecting

lsusb (erroneous state):

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0489:e10a Foxconn / Hon Hai 
Bus 001 Device 003: ID 0db0:0076 Micro Star International MYSTIC LIGHT
Bus 002 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 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 007 Device 003: ID 046d:c07e Logitech, Inc. G402 Gaming Mouse
Bus 007 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 007 Device 005: ID 3434:0251 Keychron Keychron K5 Pro
Bus 007 Device 006: ID 534d:2109 MacroSilicon USB Video

Which of these devices is the disk? Bus 004 Device 001, which you can deduct from the dmesg output.

OK, I looked at dmesg. It shows "usb 4-1" which is device on the 1st port of the root hub of bus 4. Device 004:001 is the root hub itself. There are no other devices on bus 4, so the disk is gone from this lsusb output.

This is consistent with dmesg in the sense that dmesg shows:
- UAS commands timing out and being aborted (the UAS device got stuck apparently)
- attempted reset of the USB device failing
- the device being disconnected => it seems that you ran lsusb later

As for the cause and why it got fixed by moving to another port, I'm not sure. A few possibilities:
1. Something unique to 10G speed. Is the front port limited to 5G?
2. Something unique to a particular USB controller. Is the front port different bus number than 4?
3. Better link quality for random reasons, combined with poor error handling in the device, the USB host or the kernel, or all of them.