I can 100% confirm/reproduce the issue (with only a Samsung PM951), on all ports of my AMD 7840U mainboard, while it’s okay on my 11th gen Intel i7-1165G7 mainboard (and other devices).
TLDR
A Samsung 1TB P951 SSD in 3 different enclosures with 3 different chipsets work perfectly in my other devices including my previous Framework Intel i71165-G7 mainboard but do not in my Framework AMD 7840U mainboard. It exhibits the same issue @Jason_Username_Taken described, with USB3 5Gbps and 10Gbps where copying a large file (e.g. 10GB) will reset/disconnect the SSD/enclosure). It does work when connected to the (I think powerered) USB3.1 Gen 1 5Gbps hub of my monitor which is then connected to the USB-C port of the mainboard, as well as forcing USB2 with a cable/adapter. I think it might be a USB3 specific power overdraw issue that’s causing it since it works with the USB3 hub in the middle or forced into USB2. This same behavior happens on both Windows and Linux, on different kernel versions, so I’m fairly confident it’s not because of an operating system/driver/kernel error. I’ve also tested various enclosure chipset firmware including the respective latest versions — no dice.
System:
- AMD 7840U mainboard swapped into 11th gen Intel body.
- BIOS 3.03 since day one when I received in early November. I experienced the issue within the first week and did not test BIOS 3.02, but @Jason_Username_Taken has issues on 3.02 as well.
My AMD 7840U mainboard test results
The transfer tests were run by copying 10GB to the SSD (e.g. fallocate -l 10G / rsync -ah --progress [src] [dest]).
| Enclosure | Chipset | Samsung PM951: 10GB File transfer | SK hynix Gold 2TB P31: 10GB File transfer | LITEON C A3-8D512512GB: 10GB File transfer | Notes |
|---|---|---|---|---|---|
| Plugable USB 3.1 Gen 2 (10Gbps) NVME Enclosure | JMicron JMS583 | Fails | Succeeds | Succeeds | I’ve had this since 2019, and it’s worked in all my devices including my previous Intel i7-1165G7 mainboard. The internet says it’s not a stable chipset, but it runs perfectly fine (very well, high speeds) on that Framework Intel mainboard. |
| Plugable USB 3.1 Gen 2 (10Gbps) NVME Enclosure | Realtek RTL9120 (non B) | Fails | Succeeds | Succeeds | Plugable sent me the updated version (super appreciated). It’s slightly more “stable” on the AMD 7840 mainbord, as the JMicron JMS583 version can hang processes and it seems both the RTL9120B and non-B reset cleanly, although still unfortunately reset. |
| Sabrent USB 3.2 (also 10Gbps) NVME Enlosure (EC-SNVE) | Realtek RTL9120B | Fails | Succeeds | Succeeds | Same enclosure as @Jason_Username_Taken’s. Got this as I thought my old Plugable JMicron JMS583 enclosure was broken (it wasn’t). |
Basically, after a few gigabytes are transferred, the SSD/enclosure will reset/disconnect. Here is a sample of journalctl logs when it resets/disconnects:
kernel: usb 6-1: USB disconnect, device number 3
kernel: usb 6-1: cmd cmplt err -108
kernel: usb 6-1: cmd cmplt err -108
kernel: usb 6-1: cmd cmplt err -108
kernel: usb 6-1: cmd cmplt err -108
kernel: usb 6-1: cmd cmplt err -108
kernel: usb 6-1: cmd cmplt err -108
kernel: usb 6-1: cmd cmplt err -108
kernel: usb 6-1: cmd cmplt err -108
kernel: usb 6-1: cmd cmplt err -108
kernel: usb 6-1: cmd cmplt err -108
kernel: usb 6-1: cmd cmplt err -108
kernel: usb 6-1: cmd cmplt err -108
kernel: usb 6-1: cmd cmplt err -108
kernel: sd 0:0:0:0: [sda] tag#14 uas_zap_pending 0 uas-tag 1 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#14 CDB: Write(10) 2a 00 28 67 3d 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#15 uas_zap_pending 0 uas-tag 2 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#15 CDB: Write(10) 2a 00 28 67 41 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#9 uas_zap_pending 0 uas-tag 3 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#9 CDB: Write(10) 2a 00 28 67 45 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#18 uas_zap_pending 0 uas-tag 4 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#18 CDB: Write(10) 2a 00 28 67 49 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#19 uas_zap_pending 0 uas-tag 5 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#19 CDB: Write(10) 2a 00 28 67 4d 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#16 uas_zap_pending 0 uas-tag 6 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 28 67 51 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#10 uas_zap_pending 0 uas-tag 7 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#10 CDB: Write(10) 2a 00 28 67 55 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#17 uas_zap_pending 0 uas-tag 8 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#17 CDB: Write(10) 2a 00 28 67 59 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#11 uas_zap_pending 0 uas-tag 9 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#11 CDB: Write(10) 2a 00 28 67 65 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#8 uas_zap_pending 0 uas-tag 10 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#8 CDB: Write(10) 2a 00 28 67 75 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#12 uas_zap_pending 0 uas-tag 11 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#12 CDB: Write(10) 2a 00 28 67 35 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#13 uas_zap_pending 0 uas-tag 12 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#13 CDB: Write(10) 2a 00 28 67 39 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#23 uas_zap_pending 0 uas-tag 13 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#23 CDB: Write(10) 2a 00 28 67 5d 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#20 uas_zap_pending 0 uas-tag 14 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#20 CDB: Write(10) 2a 00 28 67 61 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#21 uas_zap_pending 0 uas-tag 15 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#21 CDB: Write(10) 2a 00 28 67 69 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#22 uas_zap_pending 0 uas-tag 16 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#22 CDB: Write(10) 2a 00 28 67 6d 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#24 uas_zap_pending 0 uas-tag 17 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#24 CDB: Write(10) 2a 00 28 67 71 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#25 uas_zap_pending 0 uas-tag 18 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#25 CDB: Write(10) 2a 00 28 67 79 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#26 uas_zap_pending 0 uas-tag 19 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#26 CDB: Write(10) 2a 00 28 67 7d 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#27 uas_zap_pending 0 uas-tag 20 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#27 CDB: Write(10) 2a 00 28 67 81 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#29 uas_zap_pending 0 uas-tag 21 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#29 CDB: Write(10) 2a 00 28 67 85 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#28 uas_zap_pending 0 uas-tag 22 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#28 CDB: Write(10) 2a 00 28 67 89 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#0 uas_zap_pending 0 uas-tag 23 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 28 67 8d 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#1 uas_zap_pending 0 uas-tag 24 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#1 CDB: Write(10) 2a 00 28 67 91 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#2 uas_zap_pending 0 uas-tag 25 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#2 CDB: Write(10) 2a 00 28 67 95 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#3 uas_zap_pending 0 uas-tag 26 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#3 CDB: Write(10) 2a 00 28 67 99 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#4 uas_zap_pending 0 uas-tag 27 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#4 CDB: Write(10) 2a 00 28 67 9d 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#5 uas_zap_pending 0 uas-tag 28 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#5 CDB: Write(10) 2a 00 28 67 a1 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#6 uas_zap_pending 0 uas-tag 29 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#6 CDB: Write(10) 2a 00 28 67 a5 00 00 04 00 00
kernel: sd 0:0:0:0: [sda] tag#7 uas_zap_pending 0 uas-tag 30 inflight: CMD
kernel: sd 0:0:0:0: [sda] tag#7 CDB: Write(10) 2a 00 28 67 a9 00 00 04 00 00
kernel: scsi_io_completion_action: 24 callbacks suppressed
kernel: sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 0:0:0:0: [sda] tag#14 CDB: Write(10) 2a 00 28 67 3d 00 00 04 00 00
kernel: blk_print_req_error: 19398 callbacks suppressed
kernel: I/O error, dev sda, sector 677854464 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
kernel: buffer_io_error: 964878 callbacks suppressed
kernel: Buffer I/O error on dev sda1, logical block 84731552, lost async page write
kernel: Buffer I/O error on dev sda1, logical block 84731553, lost async page write
kernel: Buffer I/O error on dev sda1, logical block 84731554, lost async page write
kernel: Buffer I/O error on dev sda1, logical block 84731555, lost async page write
kernel: Buffer I/O error on dev sda1, logical block 84731556, lost async page write
kernel: Buffer I/O error on dev sda1, logical block 84731557, lost async page write
kernel: Buffer I/O error on dev sda1, logical block 84731558, lost async page write
kernel: Buffer I/O error on dev sda1, logical block 84731559, lost async page write
kernel: Buffer I/O error on dev sda1, logical block 84731560, lost async page write
kernel: Buffer I/O error on dev sda1, logical block 84731561, lost async page write
kernel: sd 0:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 0:0:0:0: [sda] tag#15 CDB: Write(10) 2a 00 28 67 41 00 00 04 00 00
kernel: I/O error, dev sda, sector 677855488 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
kernel: sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 0:0:0:0: [sda] tag#9 CDB: Write(10) 2a 00 28 67 45 00 00 04 00 00
kernel: I/O error, dev sda, sector 677856512 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
kernel: sd 0:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 0:0:0:0: [sda] tag#18 CDB: Write(10) 2a 00 28 67 49 00 00 04 00 00
kernel: I/O error, dev sda, sector 677857536 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
kernel: sd 0:0:0:0: [sda] tag#19 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 0:0:0:0: [sda] tag#19 CDB: Write(10) 2a 00 28 67 4d 00 00 04 00 00
kernel: I/O error, dev sda, sector 677858560 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
kernel: sd 0:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 0:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 28 67 51 00 00 04 00 00
kernel: I/O error, dev sda, sector 677859584 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
kernel: sd 0:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 0:0:0:0: [sda] tag#10 CDB: Write(10) 2a 00 28 67 55 00 00 04 00 00
kernel: I/O error, dev sda, sector 677860608 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
kernel: sd 0:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 0:0:0:0: [sda] tag#17 CDB: Write(10) 2a 00 28 67 59 00 00 04 00 00
kernel: I/O error, dev sda, sector 677861632 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
kernel: sd 0:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 0:0:0:0: [sda] tag#11 CDB: Write(10) 2a 00 28 67 65 00 00 04 00 00
kernel: I/O error, dev sda, sector 677864704 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
kernel: sd 0:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 0:0:0:0: [sda] tag#8 CDB: Write(10) 2a 00 28 67 75 00 00 04 00 00
kernel: I/O error, dev sda, sector 677868800 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
systemd-homed[1418]: block device /sys/devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb6/6-1/6-1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1 has been removed.
systemd-homed[1418]: block device /sys/devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb6/6-1/6-1:1.0/host0/target0:0:0/0:0:0:0/block/sda has been removed.
udisksd[1425]: Cleaning up mount point /run/media/mwu/PM951 (device 8:1 no longer exists)
systemd[1]: run-media-mwu-PM951.mount: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit run-media-mwu-PM951.mount has successfully entered the 'dead' state.
kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
nautilus[6427]: (../src/nautilus-list-base.c:1252):real_set_selection: runtime check failed: (files_to_find == NULL)
kernel: sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
ntfs-3g[8142]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
ntfs-3g[8142]: Reading $BITMAP failed: Input/output error
ntfs-3g[8142]: Failed to allocate clusters: Input/output error
ntfs-3g[8142]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
ntfs-3g[8142]: Reading $BITMAP failed: Input/output error
ntfs-3g[8142]: Failed to allocate clusters: Input/output error
ntfs-3g[8142]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
ntfs-3g[8142]: Reading $BITMAP failed: Input/output error
ntfs-3g[8142]: Failed to allocate clusters: Input/output error
ntfs-3g[8142]: Failed to write buffer to bitmap (-1 != 8192). Leaving inconsistent metadata: Input/output error
ntfs-3g[8142]: Cluster deallocation failed (84730400, 407834): Input/output error
ntfs-3g[8142]: Failed to free clusters. Leaving inconsistent metadata.
ntfs-3g[8142]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
ntfs-3g[8142]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
ntfs-3g[8142]: Failed to free base MFT record. Leaving inconsistent metadata.
ntfs-3g[8142]: ntfs_attr_mst_pwrite: written=-1: Input/output error
ntfs-3g[8142]: Error writing $Mft record(s): Input/output error
ntfs-3g[8142]: MFT record sync failed, inode 5: Input/output error
ntfs-3g[8142]: ntfs_attr_mst_pwrite: written=-1: Input/output error
ntfs-3g[8142]: Error writing $Mft record(s): Input/output error
ntfs-3g[8142]: MFT record sync failed, inode 5: Input/output error
ntfs-3g[8142]: Unmounting /dev/sda1 (PM951)
ntfs-3g[8142]: Failed to sync device /dev/sda1: Input/output error
ntfs-3g[8142]: Failed to fsync device /dev/sda1: Input/output error
ntfs-3g[8142]: Failed to close volume /dev/sda1: Device or resource busy
kernel: usb 6-1: new SuperSpeed Plus Gen 2x1 USB device number 4 using xhci_hcd
kernel: usb 6-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
kernel: usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 6-1: Product: RTL9210
kernel: usb 6-1: Manufacturer: Realtek
kernel: usb 6-1: SerialNumber: 012345678924
kernel: probe of 6-1:1.0 returned 6 after 33 usecs
kernel: scsi host0: uas
kernel: probe of 6-1:1.0 returned 0 after 44402 usecs
kernel: probe of 6-1 returned 0 after 73125 usecs
kernel: scsi 0:0:0:0: Direct-Access PM951 NV Me SAMSUNG 1024G 1.00 PQ: 0 ANSI: 6
mtp-probe[9185]: checking bus 6, device 4: "/sys/devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb6/6-1"
mtp-probe[9185]: bus: 6, device: 4 was not an MTP device
kernel: probe of 0:0:0:0 returned 19 after 5 usecs
kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
kernel: sd 0:0:0:0: [sda] 2000409264 512-byte logical blocks: (1.02 TB/954 GiB)
kernel: sd 0:0:0:0: [sda] Write Protect is off
kernel: sd 0:0:0:0: [sda] Mode Sense: 37 00 00 08
kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes
kernel: sda: sda1
kernel: sd 0:0:0:0: [sda] Attached SCSI disk
kernel: probe of 0:0:0:0 returned 0 after 19476 usecs
boltd[1532]: probing: started [1000]
mtp-probe[9211]: checking bus 6, device 4: "/sys/devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb6/6-1"
mtp-probe[9211]: bus: 6, device: 4 was not an MTP device
udisksd[1425]: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
(g-io-error-quark, 0)
- The issue remains when forcing the direct USB connection from USB3 10Gbps to USB3 5Gbps with a cable.
- When the enclosures are connected to the USB-C port (pretty sure it’s a powered USB3 hub) of my Dell U3421WE monitor (at USB 3.1 Gen 1 5Gbps speeds) which is then connected to the mainboard via USB-C, they succeed and do not reset/disconnect.
- When the enclosures are forced into USB2 (480Mbps) with a cable or Pixel USB-A to USB-C adapter, they succeed and do not reset/disconnect.
- Reading from the enclosure/SSD works fine.
These work without issue:
- Sandisk 2TB Portable USB 3.2 Gen 2 10Gbps SSD (USB-C)
- Toshiba Portable 2TB USB 3.0 2.5 SATA HDD (USB-A)
- SanDisk Extreme Pro 512GB SSD connected via Sabrent USB 3.0 SATA to USB-A adapter
So in summary, my 1TB Samsung PM951 SSD in all those enclosures reset/disconnect when transferring a 10GB file to it over directly connected USB3+ but are fine over USB2. It was never and is still not an issue on my 11th gen Intel i7-1165G7 mainboard. For some reason, other SSDs in those enclosures do work in the AMD 7840U mainboard. I can get the PM951 to work by connecting it to the USB3.1 Gen 1 5Gbps hub on my monitor, and from what I’ve seen/researched, my intuition is that at USB3 speeds, for some reason the SSD pulls too much power and causes the mainboard’s USB3 port to reset and/or reset the enclosure/SSD. Connecting to my monitor’s USB3 hub might be routing around that issue since I’m pretty sure it’s powered. Again, it was totally fine on my previous 11th gen Intel mainboard, (like how it was fine on @Jason_Username_Taken’s 12th gen mainboard), and I’ve been using it in an enclosure successfully since 2019. So there’s likely something broken with the AMD mainboard implementation (or our’s).
I also came across this AMD USB issue in 500 series motherboards from 2021, but it’s a completely different, older series.
I found these that detail Samsung PM951 instability: 1, 2, 3, 4, 5. However, they’re for direct M.2 motherboard connections for that specific SSD and not USB-NVME enclosures, so they might some mixture of misleading and enlightening. I have not read through the lengthy 5. yet, but leaving these here in case they help.
Sidenote, this thread was incredibly hard to find (I searched for “AMD USB” which for some reason didn’t pop up many results, which I’ve been keeping an eye on since I first encountered this issue in early November when I received my board. It wasn’t until I searched just for “USB” and went through each thread title that I found this…I’m glad I found this though, as it confirms that I’m not alone in this. I didn’t see this thread until I performed my own troubleshooting that went quite deep, so this is reassurance that this is a real issue affecting more than 1 person, with different devices. Maybe if I add “AMD 7840U USB-C USB NVME SSD copy transfer disconnect/reconnect failure issue” it’ll pop up in search for others:
Ahem, AMD 7840U USB-C USB NVME SSD copy transfer disconnect/reconnect failure issue 
Happy new year! Please let me know if I should send a ticket to support as well. Let’s try to get to the bottom of this and I’d of course be happy to test.