USB troubles

So I am having some what I would consider weird issues regarding to usb. It half or part works but why It does or doesn’t is beyond me. Some usb devices work other just don’t. They don’t appear in lsusb there is no record of them being plugged in dsmeg or journalctl. During my trouble shooting I discovered other internal devices on the usb bus that should be connected but are not showing up. What I know is all of the hardware worked on an older distro, everything was showing up like it should have. For reference this is on a laptop and a fresh install. I need some help troubleshooting where do I go next?

I am open to suggestions for a better topic title but I can’t really think of anything better to describe the issues at the moment.

For us to assist we need additional information.
Please post (in </> Preformatted text tags) the output of inxi -Fzxx and lsusb so we can see what the system actually sees at the time those commands are run.

Also, whenever you plug in a usb device the system should log an entry in dmesg so you can look at the last few lines of that output each time you plug in a device. If it successfully configures it the info will be there. If it fails the info should also be there. For failed devices you can post the last few lines of the ‘dmesg’ output so we can see what the system actually does with that device.

We also could use some info about what device is not being seen at the same time as you provide the related ‘dmesg’ output.

Here is the output from the commands

[user1@fedora ~]$ inxi -Fzxx
System:
  Kernel: 5.16.16-200.fc35.x86_64 x86_64 bits: 64 compiler: gcc
    v: 2.37-10.fc35 Desktop: GNOME 41.4 tk: GTK 3.24.31 wm: gnome-shell dm: GDM
    Distro: Fedora release 35 (Thirty Five)
Machine:
  Type: Laptop System: Apple product: MacBookPro14,3 v: 1.0
    serial: <superuser required> Chassis: type: 9 v: Mac-551B86E5744E2388
    serial: <superuser required>
  Mobo: Apple model: Mac-551B86E5744E2388 v: MacBookPro14,3
    serial: <superuser required> UEFI: Apple v: 205.0.0.0.0 date: 01/31/2020
Battery:
  ID-1: BAT0 charge: 65.1 Wh (96.4%) condition: 67.5/76.7 Wh (88.0%)
    volts: 12.7 min: 11.5 model: SMP bq20z451 serial: N/A status: Full
  Device-1: apple_mfi_fastcharge model: N/A serial: N/A charge: N/A
    status: N/A
CPU:
  Info: quad core model: Intel Core i7-7820HQ bits: 64 type: MT MCP
    arch: Kaby Lake rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 1209 high: 1278 min/max: 800/3900 cores: 1: 1200
    2: 1200 3: 1200 4: 1200 5: 1200 6: 1200 7: 1200 8: 1278 bogomips: 46398
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: AMD Baffin [Radeon RX 460/560D / Pro
  450/455/460/555/555X/560/560X]
    vendor: Apple driver: amdgpu v: kernel pcie: speed: 8 GT/s lanes: 8 ports:
    active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4 bus-ID: 01:00.0
    chip-ID: 1002:67ef
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 21.1.4
    compositor: gnome-shell driver: gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: Apple Color LCD res: 2880x1800 dpi: 221
    diag: 390mm (15.4")
  OpenGL: renderer: AMD Radeon RX Graphics (POLARIS11 DRM 3.44.0
    5.16.16-200.fc35.x86_64 LLVM 13.0.0)
    v: 4.6 Mesa 21.3.8 direct render: Yes
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170
  Device-2: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / 560/560X]
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 1002:aae0
  Sound Server-1: ALSA v: k5.16.16-200.fc35.x86_64 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Broadcom BCM43602 802.11ac Wireless LAN SoC vendor: Apple
    driver: brcmfmac v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0
    chip-ID: 14e4:43ba
  IF: wlp3s0 state: up mac: <filter>
Drives:
  Local Storage: total: 523.22 GiB used: 4.67 GiB (0.9%)
  ID-1: /dev/nvme0n1 vendor: Apple model: SSD SM0512L size: 465.92 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 37.9 C
  ID-2: /dev/sda type: USB vendor: SanDisk model: USB 3.2Gen1
    size: 57.3 GiB serial: <filter>
Partition:
  ID-1: / size: 385.45 GiB used: 4.38 GiB (1.1%) fs: btrfs dev: /dev/dm-0
    mapped: luks-49b8d11c-266c-4a35-98be-c885cb916a99
  ID-2: /boot size: 973.4 MiB used: 224.9 MiB (23.1%) fs: ext4
    dev: /dev/nvme0n1p3
  ID-3: /boot/efi size: 299 MiB used: 23.4 MiB (7.8%) fs: hfsplus
    dev: /dev/nvme0n1p1
  ID-4: /home size: 385.45 GiB used: 4.38 GiB (1.1%) fs: btrfs
    dev: /dev/dm-0 mapped: luks-49b8d11c-266c-4a35-98be-c885cb916a99
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 60.0 C mobo: N/A gpu: amdgpu temp: 52.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 376 Uptime: 5h 16m Memory: 15.52 GiB used: 5.19 GiB (33.5%)
  Init: systemd v: 249 runlevel: 5 target: graphical.target Compilers:
  gcc: 11.2.1 Packages: N/A note: see --pkg Shell: Bash v: 5.1.8
  running-in: gnome-terminal inxi: 3.3.13

lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 050: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 052: ID 05e3:0751 Genesys Logic, Inc. microSD Card Reader
Bus 001 Device 051: ID 05e3:0751 Genesys Logic, Inc. microSD Card Reader
Bus 001 Device 049: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 048: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 0781:55ab SanDisk Corp.  SanDisk 3.2Gen1
Bus 001 Device 002: ID 05ac:1281 Apple, Inc. Apple Mobile Device [Recovery Mode]
Bus 001 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 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

An update here running inxi for what ever reason makes one of the devices show up. I am checking more logs and I see an error

ar 26 19:08:34 fedora kernel: usb usb4-port1: Cannot enable. Maybe the USB cab>

running the inxi command causes it to show up in lsusb.
Here is some of the relevant output from journalctl

Mar 26 19:08:33 fedora kernel: scsi 2:0:0:0: Direct-Access     Generic  STORAGE DEVICE   1404 PQ: 0 ANSI: 6
Mar 26 19:08:33 fedora kernel: sd 2:0:0:0: Attached scsi generic sg3 type 0
Mar 26 19:08:33 fedora kernel: scsi 3:0:0:0: Direct-Access     Generic  STORAGE DEVICE   1404 PQ: 0 ANSI: 6
Mar 26 19:08:33 fedora kernel: sd 3:0:0:0: Attached scsi generic sg4 type 0
Mar 26 19:08:33 fedora kernel: sd 2:0:0:0: [sdc] Media removed, stopped polling
Mar 26 19:08:33 fedora kernel: sd 2:0:0:0: [sdc] Attached SCSI removable disk
Mar 26 19:08:33 fedora kernel: sd 3:0:0:0: [sdd] Media removed, stopped polling
Mar 26 19:08:33 fedora kernel: sd 3:0:0:0: [sdd] Attached SCSI removable disk
Mar 26 19:08:34 fedora kernel: usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
Mar 26 19:08:34 fedora kernel: usb 4-1: USB disconnect, device number 4
Mar 26 19:08:34 fedora systemd-homed[1331]: block device /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:02.0/0000:07:00.0/usb4/4-1/4-1:1.0/host1/target1:0:0/1:0:0:0/block/sdb has been removed.
Mar 26 19:08:34 fedora kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Mar 26 19:08:35 fedora kernel: sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Mar 26 19:08:47 fedora systemd[2163]: Started VTE child process 28853 launched by gnome-terminal-server process 8866.
Mar 26 19:09:29 fedora systemd[2163]: Started VTE child process 28893 launched by gnome-terminal-server process 8866.
Mar 26 19:09:34 fedora kernel: usb 4-1: new SuperSpeed Plus Gen 2x1 USB device number 5 using xhci_hcd
Mar 26 19:09:34 fedora kernel: usb 4-1: New USB device found, idVendor=0781, idProduct=55ae, bcdDevice=30.00
Mar 26 19:09:34 fedora kernel: usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Mar 26 19:09:34 fedora kernel: usb 4-1: Product: Extreme 55AE
Mar 26 19:09:34 fedora kernel: usb 4-1: Manufacturer: SanDisk
Mar 26 19:09:34 fedora kernel: usb 4-1: SerialNumber: 323134303143343031333035
Mar 26 19:09:34 fedora kernel: scsi host1: uas
Mar 26 19:09:34 fedora mtp-probe[28954]: checking bus 4, device 5: "/sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:02.0/0000:07:00.0/usb4/4-1"
Mar 26 19:09:34 fedora mtp-probe[28954]: bus: 4, device: 5 was not an MTP device
Mar 26 19:09:34 fedora boltd[1418]: probing: started [1000]
Mar 26 19:09:34 fedora mtp-probe[28955]: checking bus 4, device 5: "/sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:02.0/0000:07:00.0/usb4/4-1"
Mar 26 19:09:34 fedora mtp-probe[28955]: bus: 4, device: 5 was not an MTP device
Mar 26 19:09:34 fedora audit[28993]: USER_CMD pid=28993 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/home/user1" cmd=2F7362696E2F68646474656D70202D6E71202D752043202F6465762F736461 exe="/u>
Mar 26 19:09:34 fedora sudo[28993]:    user1 : a password is required ; TTY=pts/0 ; PWD=/home/user1 ; USER=root ; COMMAND=/sbin/hddtemp -nq -u C /dev/sda
Mar 26 19:09:35 fedora polkitd[1321]: Registered Authentication Agent for unix-process:29004:1940188 (system bus name :1.585 [/bin/flatpak list], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C)
Mar 26 19:09:35 fedora polkitd[1321]: Unregistered Authentication Agent for unix-process:29004:1940188 (system bus name :1.585, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C)
Mar 26 19:09:35 fedora kernel: scsi 1:0:0:0: Direct-Access     SanDisk  Extreme 55AE     3000 PQ: 0 ANSI: 6
Mar 26 19:09:35 fedora kernel: scsi 1:0:0:1: Enclosure         SanDisk  SES Device       3000 PQ: 0 ANSI: 6
Mar 26 19:09:35 fedora kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Mar 26 19:09:35 fedora kernel: sd 1:0:0:0: [sdb] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB)
Mar 26 19:09:35 fedora kernel: ses 1:0:0:1: Attached Enclosure device
Mar 26 19:09:35 fedora kernel: sd 1:0:0:0: [sdb] Write Protect is off
Mar 26 19:09:35 fedora kernel: sd 1:0:0:0: [sdb] Mode Sense: 37 00 10 00
Mar 26 19:09:35 fedora kernel: ses 1:0:0:1: Attached scsi generic sg2 type 13
Mar 26 19:09:35 fedora kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Mar 26 19:09:35 fedora kernel: ses 1:0:0:1: Failed to get diagnostic page 0x1
Mar 26 19:09:35 fedora kernel: ses 1:0:0:1: Failed to bind enclosure -19
Mar 26 19:09:35 fedora kernel: sd 1:0:0:0: [sdb] Optimal transfer size 1048576 bytes
Mar 26 19:09:35 fedora kernel:  sdb:
Mar 26 19:09:35 fedora kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Mar 26 19:09:38 fedora boltd[1418]: probing: timeout, done: [2885193] (2000000)

It seems it can not enable then disconnects then something that inxi causes it to be re recognized.

That seems like it may be related to either a bad port (unlikely) or a bad cable. We often see issues with cables going bad and or using a cable that is not high enough quality for USB 3 connections.

Have you tried replacing the cable with one that is for certain USB 3 capable and good?

You did not include enough of the dmesg output to see what was happening before 19:08:33 but I see a disconnect of sdc and sdd. Are they the same device that was connecting and then disconnecting? Or was that different devices and you unplugging them?

Yes I would assume that sdc and sdd sdb could all be the same device The only other storage is a flash drive that is showing up correctly and the internal nvme. I will re run my experiment a couple times changing out the cable and capture more of the logs.

As for the cables I am testing with they are relatively thick and only about 6in or 15 cm long. They are rated for usb 3.2 Gen 2 (10Gb/s). They are also the oem cables that come with this model of device. They’re relatively new and the drive is backwards compatible with previous specs of usb.

At 12:13 I plugged in the device. At 12:15 I ran inxi -Fzxx and just after I did the drive showed up though it still looks like there may be some errors.

[Mar27 12:13] usb 1-7: new full-speed USB device number 6 using xhci_hcd
[  +0.114050] usb 1-7: device descriptor read/64, error -71
[  +0.220072] usb 1-7: device descriptor read/64, error -71
[  +0.215960] usb 1-7: new full-speed USB device number 7 using xhci_hcd
[  +0.113968] usb 1-7: device descriptor read/64, error -71
[  +0.223054] usb 1-7: device descriptor read/64, error -71
[  +0.109047] usb usb1-port7: attempt power cycle
[  +0.379857] usb 1-7: new full-speed USB device number 8 using xhci_hcd
[  +0.000204] usb 1-7: Device not responding to setup address.
[  +0.204030] usb 1-7: Device not responding to setup address.
[  +0.207854] usb 1-7: device not accepting address 8, error -71
[  +0.114007] usb 1-7: new full-speed USB device number 9 using xhci_hcd
[  +0.000202] usb 1-7: Device not responding to setup address.
[  +0.205997] usb 1-7: Device not responding to setup address.
[  +0.207778] usb 1-7: device not accepting address 9, error -71
[  +0.000143] usb usb1-port7: unable to enumerate USB device
[Mar27 12:15] usb 4-1: new SuperSpeed Plus Gen 2x1 USB device number 6 using xhci_hcd
[  +0.013159] usb 4-1: New USB device found, idVendor=0781, idProduct=55ae, bcdDevice=30.00
[  +0.000010] usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  +0.000004] usb 4-1: Product: Extreme 55AE
[  +0.000003] usb 4-1: Manufacturer: SanDisk
[  +0.000003] usb 4-1: SerialNumber: 323134303143343031333035
[  +0.004994] scsi host1: uas
[  +1.133590] scsi 1:0:0:0: Direct-Access     SanDisk  Extreme 55AE     3000 PQ: 0 ANSI: 6
[  +0.000858] scsi 1:0:0:1: Enclosure         SanDisk  SES Device       3000 PQ: 0 ANSI: 6
[  +0.000967] sd 1:0:0:0: Attached scsi generic sg1 type 0
[  +0.000452] ses 1:0:0:1: Attached Enclosure device
[  +0.000106] sd 1:0:0:0: [sdb] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB)
[  +0.000096] ses 1:0:0:1: Attached scsi generic sg2 type 13
[  +0.000026] sd 1:0:0:0: [sdb] Write Protect is off
[  +0.000007] sd 1:0:0:0: [sdb] Mode Sense: 37 00 10 00
[  +0.000127] ses 1:0:0:1: Failed to get diagnostic page 0x1
[  +0.000006] ses 1:0:0:1: Failed to bind enclosure -19
[  +0.000067] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[  +0.000267] sd 1:0:0:0: [sdb] Optimal transfer size 1048576 bytes
[  +0.013379]  sdb: sdb1
[  +0.024367] sd 1:0:0:0: [sdb] Attached SCSI disk
[  +0.184376] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none.
[  +2.777047] usb usb6-port2: Cannot enable. Maybe the USB cable is bad?
[  +4.071920] usb usb6-port2: Cannot enable. Maybe the USB cable is bad?
[  +0.000112] usb usb6-port2: attempt power cycle

Round 2 with a different cable
At 12:31 I plugged in device with a new cable and there was no output on dmesg logs? I waited a few minutes.

At 12:34 I ran the inxi -Fzxx command and the drive was recognized and this is the output from the logs.

[Mar27 12:34] usb 4-1: new SuperSpeed Plus Gen 2x1 USB device number 7 using xhci_hcd
[  +0.013141] usb 4-1: New USB device found, idVendor=0781, idProduct=55ae, bcdDevice=30.00
[  +0.000010] usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  +0.000003] usb 4-1: Product: Extreme 55AE
[  +0.000003] usb 4-1: Manufacturer: SanDisk
[  +0.000003] usb 4-1: SerialNumber: 323134303143343031333035
[  +0.009338] scsi host1: uas
[  +1.122538] scsi 1:0:0:0: Direct-Access     SanDisk  Extreme 55AE     3000 PQ: 0 ANSI: 6
[  +0.000796] scsi 1:0:0:1: Enclosure         SanDisk  SES Device       3000 PQ: 0 ANSI: 6
[  +0.001047] sd 1:0:0:0: Attached scsi generic sg1 type 0
[  +0.000361] ses 1:0:0:1: Attached Enclosure device
[  +0.000178] ses 1:0:0:1: Attached scsi generic sg2 type 13
[  +0.000001] sd 1:0:0:0: [sdb] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB)
[  +0.000130] sd 1:0:0:0: [sdb] Write Protect is off
[  +0.000003] ses 1:0:0:1: Failed to get diagnostic page 0x1
[  +0.000002] sd 1:0:0:0: [sdb] Mode Sense: 37 00 10 00
[  +0.000002] ses 1:0:0:1: Failed to bind enclosure -19
[  +0.000157] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[  +0.000242] sd 1:0:0:0: [sdb] Optimal transfer size 1048576 bytes
[  +0.015070]  sdb: sdb1
[  +0.025333] sd 1:0:0:0: [sdb] Attached SCSI disk
[  +0.180129] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none.

What really baffles me is that it was plugged in and it was just not recognized like it didn’t exist nothing on the logs at all?

Update
Just ran some benchmarks on it and when It does decide to show up it runs as advertised.

It seems that for some reason udev is not properly identifying the device.

In the first part of your log it is reporting

[Mar27 12:13] usb 1-7: new full-speed USB device number 6 using xhci_hcd
[  +0.114050] usb 1-7: device descriptor read/64, error -71
[  +0.220072] usb 1-7: device descriptor read/64, error -71
[  +0.215960] usb 1-7: new full-speed USB device number 7 using xhci_hcd
[  +0.113968] usb 1-7: device descriptor read/64, error -71
[  +0.223054] usb 1-7: device descriptor read/64, error -71

which indicates to me that there may be something that is confusing the system with that error. I don’t know the device details, but it could be a case of the device firmware not properly communicating with the OS so it does not get enough info to properly configure it. Then when you scan it with inxi it seems to get different info and finishes the config.

I would like to see a continuous output of
dmesg
and
journalctl --=since=-10minutes
from the time you plug in the device until after it is configured properly.

This should let us see everything the system does and logs for that time period and hopefully related to why it is not getting configured at first.

With the trials using different cables it seems to rule out potential bad cables. Inxi should be doing nothing that would trigger configuring the device. Thus at present it is difficult to see why it is not being properly recognized quickly, though it does eventually get configured. My next step would be to suggest you look for possible firmware updates for that device (both the enclosure and the sandisk).

The issue may be related to the usb 3.2 device specs while the PC is likely only 3.0 or 3.1. Even though those specs are supposed to be compatible it is also related to how the software handles the differences.

I will see about getting updated logs.

The drive is sold as sealed unit. Maybe San disk has updated firmware?

So this laptop was sold before usb decided to make everything confusing with the naming. The ports on the laptop are 10Gbps which at the time was usb 3.1 Gen 2 but usb renamed part of the spec meaning they are now considered 3.2 Gen 2 (10gbps) I’ll attach a chart because It can get confusing. The port and drive should be using the same spec of usb.

16:54 Logs start (journalctl 16:44) then usb device is plugged in
17:00 ran inxi -Fzxx and drive shows up
17:01 ran umount
17:02 unplugged usb device
17:03 Logs end

I left it plugged in and nothing for ~6 mins until after I run inxi and it promptly shows up. When the drive is working bencmark data confirms that the usb device is transfering at ~8Gbps wich is inline with usb 3.2 gen 2 anything less than that would be limited by the usb bandwidth.

dmesg nothing for the 10mins before testing

[Mar27 17:00] usb 4-1: new SuperSpeed Plus Gen 2x1 USB device number 9 using xhci_hcd
[  +0.012778] usb 4-1: New USB device found, idVendor=0781, idProduct=55ae, bcdDevice=30.00
[  +0.000009] usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  +0.000004] usb 4-1: Product: Extreme 55AE
[  +0.000003] usb 4-1: Manufacturer: SanDisk
[  +0.000002] usb 4-1: SerialNumber: 323134303143343031333035
[  +0.004772] scsi host1: uas
[  +1.176621] scsi 1:0:0:0: Direct-Access     SanDisk  Extreme 55AE     3000 PQ: 0 ANSI: 6
[  +0.001028] scsi 1:0:0:1: Enclosure         SanDisk  SES Device       3000 PQ: 0 ANSI: 6
[  +0.001094] sd 1:0:0:0: Attached scsi generic sg1 type 0
[  +0.000292] ses 1:0:0:1: Attached Enclosure device
[  +0.000194] ses 1:0:0:1: Attached scsi generic sg2 type 13
[  +0.000004] sd 1:0:0:0: [sdb] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB)
[  +0.000094] sd 1:0:0:0: [sdb] Write Protect is off
[  +0.000004] sd 1:0:0:0: [sdb] Mode Sense: 37 00 10 00
[  +0.000111] ses 1:0:0:1: Failed to get diagnostic page 0x1
[  +0.000004] ses 1:0:0:1: Failed to bind enclosure -19
[  +0.000117] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[  +0.000240] sd 1:0:0:0: [sdb] Optimal transfer size 1048576 bytes
[  +0.012594]  sdb: sdb1
[  +0.021469] sd 1:0:0:0: [sdb] Attached SCSI disk
[  +0.176053] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none.
[Mar27 17:02] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[  +0.000026] usb 4-1: USB disconnect, device number 9
[  +0.010966] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[  +0.121917] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK

journalctl with lines containg gnome removed to make it more legible unedited logs below

[user1@fedora ~]$  journalctl -f --since=-10minutes
Mar 27 16:50:59 fedora systemd[1]: Starting dnf makecache...
Mar 27 16:50:59 fedora dnf[65464]: Metadata cache refreshed recently.
Mar 27 16:50:59 fedora systemd[1]: dnf-makecache.service: Deactivated successfully.
Mar 27 16:50:59 fedora systemd[1]: Finished dnf makecache.
Mar 27 16:50:59 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 27 16:50:59 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 27 17:00:01 fedora kernel: usb 4-1: new SuperSpeed Plus Gen 2x1 USB device number 9 using xhci_hcd
Mar 27 17:00:01 fedora kernel: usb 4-1: New USB device found, idVendor=0781, idProduct=55ae, bcdDevice=30.00
Mar 27 17:00:01 fedora kernel: usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Mar 27 17:00:01 fedora kernel: usb 4-1: Product: Extreme 55AE
Mar 27 17:00:01 fedora kernel: usb 4-1: Manufacturer: SanDisk
Mar 27 17:00:01 fedora kernel: usb 4-1: SerialNumber: 323134303143343031333035
Mar 27 17:00:01 fedora kernel: scsi host1: uas
Mar 27 17:00:01 fedora mtp-probe[65646]: checking bus 4, device 9: "/sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:02.0/0000:07:00.0/usb4/4-1"
Mar 27 17:00:01 fedora mtp-probe[65646]: bus: 4, device: 9 was not an MTP device
Mar 27 17:00:01 fedora boltd[1418]: probing: started [1000]
Mar 27 17:00:01 fedora mtp-probe[65647]: checking bus 4, device 9: "/sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:02.0/0000:07:00.0/usb4/4-1"
Mar 27 17:00:01 fedora mtp-probe[65647]: bus: 4, device: 9 was not an MTP device
Mar 27 17:00:02 fedora audit[65685]: USER_CMD pid=65685 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/home/user1" cmd=2F7362696E2F68646474656D70202D6E71202D752043202F6465762F736461 exe="/usr/bin/sudo" terminal=pts/0 res=failed'
Mar 27 17:00:02 fedora sudo[65685]:    user1 : a password is required ; TTY=pts/0 ; PWD=/home/user1 ; USER=root ; COMMAND=/sbin/hddtemp -nq -u C /dev/sda
Mar 27 17:00:02 fedora polkitd[1321]: Registered Authentication Agent for unix-process:65696:9802922 (system bus name :1.1116 [/bin/flatpak list], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C)
Mar 27 17:00:02 fedora polkitd[1321]: Unregistered Authentication Agent for unix-process:65696:9802922 (system bus name :1.1116, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C)
Mar 27 17:00:02 fedora kernel: scsi 1:0:0:0: Direct-Access     SanDisk  Extreme 55AE     3000 PQ: 0 ANSI: 6
Mar 27 17:00:02 fedora kernel: scsi 1:0:0:1: Enclosure         SanDisk  SES Device       3000 PQ: 0 ANSI: 6
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Mar 27 17:00:02 fedora kernel: ses 1:0:0:1: Attached Enclosure device
Mar 27 17:00:02 fedora kernel: ses 1:0:0:1: Attached scsi generic sg2 type 13
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: [sdb] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB)
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: [sdb] Write Protect is off
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: [sdb] Mode Sense: 37 00 10 00
Mar 27 17:00:02 fedora kernel: ses 1:0:0:1: Failed to get diagnostic page 0x1
Mar 27 17:00:02 fedora kernel: ses 1:0:0:1: Failed to bind enclosure -19
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: [sdb] Optimal transfer size 1048576 bytes
Mar 27 17:00:02 fedora kernel:  sdb: sdb1
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Mar 27 17:00:03 fedora kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none.
Mar 27 17:00:03 fedora udisksd[1340]: Mounted /dev/sdb1 at /run/media/user1/External on behalf of uid 1000
Mar 27 17:00:05 fedora boltd[1418]: probing: timeout, done: [2782968] (2000000)
Mar 27 17:00:16 fedora audit: BPF prog-id=196 op=LOAD
Mar 27 17:00:16 fedora systemd[1]: Starting Fingerprint Authentication Daemon...
Mar 27 17:00:17 fedora systemd[1]: Started Fingerprint Authentication Daemon.
Mar 27 17:00:17 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 27 17:00:20 fedora cupsd[1511]: REQUEST localhost - - "POST / HTTP/1.1" 200 184 Renew-Subscription successful-ok
Mar 27 17:00:47 fedora systemd[1]: fprintd.service: Deactivated successfully.
Mar 27 17:00:47 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 27 17:00:47 fedora audit: BPF prog-id=0 op=UNLOAD
Mar 27 17:01:00 fedora audit[65761]: USER_AUTH pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_usertype,pam_localuser,pam_unix acct="user1" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
Mar 27 17:01:00 fedora audit[65761]: USER_ACCT pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="user1" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
Mar 27 17:01:00 fedora audit[65761]: USER_CMD pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/home/user1" cmd=756D6F756E74202F72756E2F6D656469612F75736572312F45787465726E616C exe="/usr/bin/sudo" terminal=pts/4 res=success'
Mar 27 17:01:00 fedora sudo[65761]:    user1 : TTY=pts/4 ; PWD=/home/user1 ; USER=root ; COMMAND=/usr/bin/umount /run/media/user1/External
Mar 27 17:01:00 fedora audit[65761]: CRED_REFR pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
Mar 27 17:01:00 fedora audit[65761]: USER_START pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
Mar 27 17:01:00 fedora sudo[65761]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Mar 27 17:01:00 fedora systemd[1]: run-media-user1-External.mount: Deactivated successfully.
Mar 27 17:01:00 fedora udisksd[1340]: Cleaning up mount point /run/media/user1/External (device 8:17 is not mounted)
Mar 27 17:01:00 fedora sudo[65761]: pam_unix(sudo:session): session closed for user root
Mar 27 17:01:00 fedora audit[65761]: USER_END pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
Mar 27 17:01:00 fedora audit[65761]: CRED_DISP pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
Mar 27 17:02:04 fedora kernel: usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
Mar 27 17:02:04 fedora kernel: usb 4-1: USB disconnect, device number 9
Mar 27 17:02:04 fedora kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Mar 27 17:02:04 fedora systemd-homed[1331]: block device /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:02.0/0000:07:00.0/usb4/4-1/4-1:1.0/host1/target1:0:0/1:0:0:0/block/sdb/sdb1 has been removed.
Mar 27 17:02:04 fedora systemd-homed[1331]: block device /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:02.0/0000:07:00.0/usb4/4-1/4-1:1.0/host1/target1:0:0/1:0:0:0/block/sdb has been removed.
Mar 27 17:02:04 fedora kernel: sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK

Her are the journalctl logs completely unedited starting 10mins before testing started and concluding 1 min after the usb device has been unplugged. There is a lot of stuff pertaining to gnome and it kind of overwhelms the logs that’s why I originally removed any line containing “gnome”.

Journalctl

Unedited journalctl logs exceed the character post limit.

If you really need to see the lines containing gnome-system-monitor I’ll have to figure out a different way to share them.

journalctl without lines containg “gnome-system-monitor”

[user1@fedora ~]$  journalctl -f --since=-10minutes
Mar 27 16:44:15 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:44:19 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:44:20 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:44:32 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:44:33 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:45:06 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:45:07 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:46:44 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:47:11 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:47:38 fedora gnome-shell[2291]: libinput error: event7  - Apple SPI Keyboard: client bug: event processing lagging behind by 30ms, your system is too slow
Mar 27 16:49:24 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:49:25 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:50:15 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:50:19 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:50:24 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:50:37 fedora gnome-shell[2291]: libinput error: event7  - Apple SPI Keyboard: client bug: event processing lagging behind by 22ms, your system is too slow
Mar 27 16:50:52 fedora gnome-shell[2291]: libinput error: event7  - Apple SPI Keyboard: client bug: event processing lagging behind by 11ms, your system is too slow
Mar 27 16:50:52 fedora gnome-shell[2291]: libinput error: event7  - Apple SPI Keyboard: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.
Mar 27 16:50:55 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:50:59 fedora systemd[1]: Starting dnf makecache...
Mar 27 16:50:59 fedora dnf[65464]: Metadata cache refreshed recently.
Mar 27 16:50:59 fedora systemd[1]: dnf-makecache.service: Deactivated successfully.
Mar 27 16:50:59 fedora systemd[1]: Finished dnf makecache.
Mar 27 16:50:59 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 27 16:50:59 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 27 16:51:30 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:51:44 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:51:45 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:51:58 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:51:59 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:52:09 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:52:14 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:53:52 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:54:08 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:54:34 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:54:37 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:55:48 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:55:49 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:55:50 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:56:02 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:57:44 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:57:47 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:59:03 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:59:09 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:59:15 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 16:59:16 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 17:00:01 fedora kernel: usb 4-1: new SuperSpeed Plus Gen 2x1 USB device number 9 using xhci_hcd
Mar 27 17:00:01 fedora kernel: usb 4-1: New USB device found, idVendor=0781, idProduct=55ae, bcdDevice=30.00
Mar 27 17:00:01 fedora kernel: usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Mar 27 17:00:01 fedora kernel: usb 4-1: Product: Extreme 55AE
Mar 27 17:00:01 fedora kernel: usb 4-1: Manufacturer: SanDisk
Mar 27 17:00:01 fedora kernel: usb 4-1: SerialNumber: 323134303143343031333035
Mar 27 17:00:01 fedora kernel: scsi host1: uas
Mar 27 17:00:01 fedora mtp-probe[65646]: checking bus 4, device 9: "/sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:02.0/0000:07:00.0/usb4/4-1"
Mar 27 17:00:01 fedora mtp-probe[65646]: bus: 4, device: 9 was not an MTP device
Mar 27 17:00:01 fedora boltd[1418]: probing: started [1000]
Mar 27 17:00:01 fedora mtp-probe[65647]: checking bus 4, device 9: "/sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:02.0/0000:07:00.0/usb4/4-1"
Mar 27 17:00:01 fedora mtp-probe[65647]: bus: 4, device: 9 was not an MTP device
Mar 27 17:00:02 fedora audit[65685]: USER_CMD pid=65685 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/home/user1" cmd=2F7362696E2F68646474656D70202D6E71202D752043202F6465762F736461 exe="/usr/bin/sudo" terminal=pts/0 res=failed'
Mar 27 17:00:02 fedora sudo[65685]:    user1 : a password is required ; TTY=pts/0 ; PWD=/home/user1 ; USER=root ; COMMAND=/sbin/hddtemp -nq -u C /dev/sda
Mar 27 17:00:02 fedora polkitd[1321]: Registered Authentication Agent for unix-process:65696:9802922 (system bus name :1.1116 [/bin/flatpak list], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C)
Mar 27 17:00:02 fedora polkitd[1321]: Unregistered Authentication Agent for unix-process:65696:9802922 (system bus name :1.1116, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C)
Mar 27 17:00:02 fedora kernel: scsi 1:0:0:0: Direct-Access     SanDisk  Extreme 55AE     3000 PQ: 0 ANSI: 6
Mar 27 17:00:02 fedora kernel: scsi 1:0:0:1: Enclosure         SanDisk  SES Device       3000 PQ: 0 ANSI: 6
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Mar 27 17:00:02 fedora kernel: ses 1:0:0:1: Attached Enclosure device
Mar 27 17:00:02 fedora kernel: ses 1:0:0:1: Attached scsi generic sg2 type 13
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: [sdb] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB)
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: [sdb] Write Protect is off
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: [sdb] Mode Sense: 37 00 10 00
Mar 27 17:00:02 fedora kernel: ses 1:0:0:1: Failed to get diagnostic page 0x1
Mar 27 17:00:02 fedora kernel: ses 1:0:0:1: Failed to bind enclosure -19
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: [sdb] Optimal transfer size 1048576 bytes
Mar 27 17:00:02 fedora kernel:  sdb: sdb1
Mar 27 17:00:02 fedora kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Mar 27 17:00:03 fedora kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none.
Mar 27 17:00:03 fedora udisksd[1340]: Mounted /dev/sdb1 at /run/media/user1/External on behalf of uid 1000
Mar 27 17:00:03 fedora systemd[2163]: Started dbus-:1.2-org.gnome.Shell.HotplugSniffer@5.service.
Mar 27 17:00:05 fedora boltd[1418]: probing: timeout, done: [2782968] (2000000)
Mar 27 17:00:16 fedora audit: BPF prog-id=196 op=LOAD
Mar 27 17:00:16 fedora systemd[1]: Starting Fingerprint Authentication Daemon...
Mar 27 17:00:17 fedora systemd[1]: Started Fingerprint Authentication Daemon.
Mar 27 17:00:17 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 27 17:00:20 fedora cupsd[1511]: REQUEST localhost - - "POST / HTTP/1.1" 200 184 Renew-Subscription successful-ok
Mar 27 17:00:47 fedora systemd[1]: fprintd.service: Deactivated successfully.
Mar 27 17:00:47 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 27 17:00:47 fedora audit: BPF prog-id=0 op=UNLOAD
Mar 27 17:01:00 fedora audit[65761]: USER_AUTH pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_usertype,pam_localuser,pam_unix acct="user1" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
Mar 27 17:01:00 fedora audit[65761]: USER_ACCT pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="user1" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
Mar 27 17:01:00 fedora audit[65761]: USER_CMD pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/home/user1" cmd=756D6F756E74202F72756E2F6D656469612F75736572312F45787465726E616C exe="/usr/bin/sudo" terminal=pts/4 res=success'
Mar 27 17:01:00 fedora sudo[65761]:    user1 : TTY=pts/4 ; PWD=/home/user1 ; USER=root ; COMMAND=/usr/bin/umount /run/media/user1/External
Mar 27 17:01:00 fedora audit[65761]: CRED_REFR pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
Mar 27 17:01:00 fedora audit[65761]: USER_START pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
Mar 27 17:01:00 fedora sudo[65761]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Mar 27 17:01:00 fedora systemd[1]: run-media-user1-External.mount: Deactivated successfully.
Mar 27 17:01:00 fedora udisksd[1340]: Cleaning up mount point /run/media/user1/External (device 8:17 is not mounted)
Mar 27 17:01:00 fedora sudo[65761]: pam_unix(sudo:session): session closed for user root
Mar 27 17:01:00 fedora audit[65761]: USER_END pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
Mar 27 17:01:00 fedora audit[65761]: CRED_DISP pid=65761 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
Mar 27 17:01:27 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 17:01:36 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 17:01:40 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Mar 27 17:02:04 fedora kernel: usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
Mar 27 17:02:04 fedora kernel: usb 4-1: USB disconnect, device number 9
Mar 27 17:02:04 fedora kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Mar 27 17:02:04 fedora systemd-homed[1331]: block device /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:02.0/0000:07:00.0/usb4/4-1/4-1:1.0/host1/target1:0:0/1:0:0:0/block/sdb/sdb1 has been removed.
Mar 27 17:02:04 fedora systemd-homed[1331]: block device /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:02.0/0000:07:00.0/usb4/4-1/4-1:1.0/host1/target1:0:0/1:0:0:0/block/sdb has been removed.
Mar 27 17:02:04 fedora kernel: sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Mar 27 17:02:30 fedora gnome-shell[2291]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
^C
[user1@fedora ~]$ 


The device is being seen and identified when it is plugged in. It is, however, not being defined as a drive (sdb) nor mounted as sdb1 until something triggers that action. The inxi scan apparently triggers that config though it has nothing to do with the actual process.

What happens if you have the file manager open before the device is attached? Does it get identified and mounted immediately? or does it wait until you click on the device in the left column of the file manager? Does it even show up in the left column when first attached?

This definitely seems like it is not a device issue, per se, but rather something to do with udev and the way it handles that very new usb 3.2 device. Possibly also related to the mismatch between the usb port specs and the device specs.

There are 3 different specs for USB 3.2 in what you posted. Where does that device fall in that range? Where does the PC USB port fall in that range? lsusb -v will give something like this for each usb device and port, and as you can see here my port is designated as usb 3.10.

$  lsusb -v

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.10
  bDeviceClass            9 Hub
  bDeviceSubClass         0 
  bDeviceProtocol         3 
  bMaxPacketSize0         9
  idVendor           0x1d6b Linux Foundation
  idProduct          0x0003 3.0 root hub
  bcdDevice            5.16
  iManufacturer           3 Linux 5.16.15-201.fc35.x86_64 xhci-hcd
  iProduct                2 xHCI Host Controller
  iSerial                 1 0000:01:00.2
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x001f
    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 
      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

Similar info will be seen for each device as well as each hub/port.

I see the device is seen by the kernel as

[Mar27 17:00] usb 4-1: new SuperSpeed Plus Gen 2x1 USB device number 9 using xhci_hcd
[  +0.012778] usb 4-1: New USB device found, idVendor=0781, idProduct=55ae, bcdDevice=30.00
[  +0.000009] usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  +0.000004] usb 4-1: Product: Extreme 55AE
[  +0.000003] usb 4-1: Manufacturer: SanDisk
[  +0.000002] usb 4-1: SerialNumber: 323134303143343031333035

If I am reading the above and the specs correctly the device would seem to be in the USB 3.2 Gen 2 column with 10gbps transfer speed.

So I did a test I plugged the usb device in and left it for many hours. The logs did not recognize or identify that it was plugged in. It did not show up in lsusb. Having the file manager open or not doesn’t have an effect if it shows up or not. Nothing is there to be clicked on. inxi must cause something to happen that causes the system to recognize / identify that a device is plugged in. Once it does it works like it is meant to. Which makes some level of sense because this is the first time I have had this issue.

I included the chart because it is my understanding that usb 3.0 is no longer a thing. It would be called usb 3.2 Gen1 (5 gbps) currently. Its kind of like if there was a king everyone has been calling a certain color pink for instance then one day he decides no we are now going to call it brown then a little later on he says no its not brown we are going to call it black. This all leads to confusion when talking about the colors pink brown or black. It makes my head hurt. If you have a few minutes this video breaks down the confusion as best as any I have heard.

You are correct yes both the drive and the port are in marketing terms SuperSpeed + 10gbps (aka 3.2 Gen 2 capable of 10gbps). Usb 3.2 isn’t really that new at this point its 2 generations old. Though the device it self is a year old at this point. The port on the laptop can’t be anything less than 3.2 Gen 2 because I ran benchmarks on the device after connecting it with inxi and it was transferring at 8gbps.

8+ hours plugged in and the system did not recognize or identify the drive. inxi triggers something that causes it to be recognized or identified. You can see where I ran inxi at 12:38.

[user1@fedora ~]$ journalctl -fk --since=-10minutes
Mar 28 03:43:05 fedora kernel: ieee80211 phy0: brcmf_inetaddr_changed: fail to get arp ip table err:-52
Mar 28 03:43:09 fedora kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Mar 28 03:43:11 fedora kernel: ieee80211 phy0: brcmf_inetaddr_changed: fail to get arp ip table err:-52
Mar 28 03:44:28 fedora kernel: ieee80211 phy0: brcmf_inetaddr_changed: fail to get arp ip table err:-52
Mar 28 04:00:51 fedora kernel: show_signal_msg: 115 callbacks suppressed
Mar 28 04:00:51 fedora kernel: Thread (pooled)[11016]: segfault at 0 ip 000055c7ef3ec4e8 sp 00007ff013ffe8b0 error 4 in keepassxc[55c7ef355000+24c000]
Mar 28 04:00:51 fedora kernel: Code: f8 ff 74 69 f0 83 2f 01 48 8b 7c 24 08 75 5e ba 08 00 00 00 be 01 00 00 00 e8 c4 24 f7 ff eb 4d 66 90 48 8b 53 28 49 89 14 24 <8b> 02 83 c0 01 83 f8 01 77 4e 48 89 ef e8 46 23 f7 ff 48 8b 44 24
Mar 28 12:38:44 fedora kernel: usb 6-2: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd
Mar 28 12:38:44 fedora kernel: usb 6-2: New USB device found, idVendor=0781, idProduct=55ae, bcdDevice=30.00
Mar 28 12:38:44 fedora kernel: usb 6-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Mar 28 12:38:44 fedora kernel: usb 6-2: Product: Extreme 55AE
Mar 28 12:38:44 fedora kernel: usb 6-2: Manufacturer: SanDisk
Mar 28 12:38:44 fedora kernel: usb 6-2: SerialNumber: 323134303143343031333035
Mar 28 12:38:44 fedora kernel: scsi host1: uas
Mar 28 12:38:45 fedora kernel: scsi 1:0:0:0: Direct-Access     SanDisk  Extreme 55AE     3000 PQ: 0 ANSI: 6
Mar 28 12:38:45 fedora kernel: scsi 1:0:0:1: Enclosure         SanDisk  SES Device       3000 PQ: 0 ANSI: 6
Mar 28 12:38:45 fedora kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Mar 28 12:38:45 fedora kernel: scsi 1:0:0:1: Attached scsi generic sg2 type 13
Mar 28 12:38:45 fedora kernel: sd 1:0:0:0: [sdb] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB)
Mar 28 12:38:45 fedora kernel: sd 1:0:0:0: [sdb] Write Protect is off
Mar 28 12:38:45 fedora kernel: sd 1:0:0:0: [sdb] Mode Sense: 37 00 10 00
Mar 28 12:38:45 fedora kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Mar 28 12:38:45 fedora kernel: sd 1:0:0:0: [sdb] Optimal transfer size 1048576 bytes
Mar 28 12:38:45 fedora kernel:  sdb: sdb1
Mar 28 12:38:45 fedora kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Mar 28 12:38:45 fedora kernel: scsi 1:0:0:1: Failed to get diagnostic page 0x1
Mar 28 12:38:45 fedora kernel: scsi 1:0:0:1: Failed to bind enclosure -19
Mar 28 12:38:45 fedora kernel: ses 1:0:0:1: Attached Enclosure device
Mar 28 12:38:46 fedora kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none.

I am as lost as you are here. It should be reported as a bug since the USB device does not automatically get seen & configured. I think it is udev that is responsible for that so the bug should be reported against that component.
https://bugzilla.redhat.com/post_bug.cgi
You should reference this thread in the bug report so the developers have access to all you have done to this point.

I’ll have to read up on on udev. Yea that was why I was originally so confused I would plug it in and according to the kernel and system logs nothing had happened. The fact that the usb forum has made a complete mess of the naming of anything usb 3.x. Even to the point of needing short class to know what is compatible with what or event to know what to call what doesn’t help.

I might boot up a different drive and get some known good output. Ironically it is also a decedent of rhel (I think) but has a reputation of having very slim hardware support. It was a border line miracle that I even got it to work on this laptop.