Framework Desktop Keeps Disconnecting Framework USB-C Storage Device

[Tim_Soderstrom]

I’m having an issue with the 1TB Framework Storage device when using either of the front USB-C bays. I’m trying to rsync some data over to it and keep getting stuff like this:

[1262129.817003] usb 4-2.1: new SuperSpeed Plus Gen 2x1 USB device number 5 using xhci_hcd
[1262129.828654] usb 4-2.1: New USB device found, idVendor=32ac, idProduct=0005, bcdDevice= 1.10
[1262129.828673] usb 4-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1262129.828677] usb 4-2.1: Product: 1TB Expansion Card
[1262129.828680] usb 4-2.1: Manufacturer: Framework
[1262129.828681] usb 4-2.1: SerialNumber: 071C48FA31201277
[1262129.831351] scsi host0: uas
[1262131.094452] scsi 0:0:0:0: Direct-Access     FRMW     1TB Card         PMAP PQ: 0 ANSI: 6
[1262131.146396] sd 0:0:0:0: Attached scsi generic sg0 type 0
[1262131.149783] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[1262131.152296] sd 0:0:0:0: [sda] Write Protect is off
[1262131.152302] sd 0:0:0:0: [sda] Mode Sense: 5f 00 00 08
[1262131.158059] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[1262131.185231] sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
[1262131.185243] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
[1262131.234943] sd 0:0:0:0: [sda] Attached SCSI disk
[1262196.308522] XFS (sda): Mounting V5 Filesystem 7b1ad154-7a27-434b-8213-4cdcff7fb5dd
[1262196.379597] XFS (sda): Starting recovery (logdev: internal)
[1262196.421469] XFS (sda): Ending recovery (logdev: internal)
[1262216.597053] sd 0:0:0:0: [sda] tag#22 data cmplt err -71 uas-tag 12 inflight: CMD 
[1262216.597068] sd 0:0:0:0: [sda] tag#22 CDB: Write(10) 2a 00 3b 88 dc e8 00 03 00 00
[1262221.871657] scsi host0: uas_pre_reset: timed out
[1262221.973487] sd 0:0:0:0: [sda] tag#16 uas_zap_pending 0 uas-tag 1 inflight: CMD 
[1262221.973492] sd 0:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 3b 88 e2 e8 00 04 00 00
[1262221.973495] sd 0:0:0:0: [sda] tag#25 uas_zap_pending 0 uas-tag 2 inflight: CMD 
[1262221.973496] sd 0:0:0:0: [sda] tag#25 CDB: Write(10) 2a 00 3b 88 e6 e8 00 04 00 00
[1262221.973497] sd 0:0:0:0: [sda] tag#26 uas_zap_pending 0 uas-tag 3 inflight: CMD 
[1262221.973498] sd 0:0:0:0: [sda] tag#26 CDB: Write(10) 2a 00 3b 88 ea e8 00 04 00 00
[1262221.973499] sd 0:0:0:0: [sda] tag#27 uas_zap_pending 0 uas-tag 4 inflight: CMD 
[1262221.973500] sd 0:0:0:0: [sda] tag#27 CDB: Write(10) 2a 00 3b 88 ee e8 00 04 00 00
[1262221.973501] sd 0:0:0:0: [sda] tag#28 uas_zap_pending 0 uas-tag 5 inflight: CMD 
[1262221.973501] sd 0:0:0:0: [sda] tag#28 CDB: Write(10) 2a 00 3b 88 f2 e8 00 04 00 00
[1262221.973503] sd 0:0:0:0: [sda] tag#29 uas_zap_pending 0 uas-tag 6 inflight: CMD 
[1262221.973503] sd 0:0:0:0: [sda] tag#29 CDB: Write(10) 2a 00 3b 88 f6 e8 00 04 00 00
[1262221.973504] sd 0:0:0:0: [sda] tag#22 uas_zap_pending 0 uas-tag 12 inflight: CMD 
[1262221.973505] sd 0:0:0:0: [sda] tag#22 CDB: Write(10) 2a 00 3b 88 dc e8 00 03 00 00
[1262221.973506] sd 0:0:0:0: [sda] tag#23 uas_zap_pending 0 uas-tag 13 inflight: CMD 
[1262221.973507] sd 0:0:0:0: [sda] tag#23 CDB: Write(10) 2a 00 3b 88 df e8 00 03 00 00
[1262221.973508] sd 0:0:0:0: [sda] tag#24 uas_zap_pending 0 uas-tag 14 inflight: CMD 
[1262221.973509] sd 0:0:0:0: [sda] tag#24 CDB: Write(10) 2a 00 38 c1 e1 70 00 00 08 00
[1262221.973510] sd 0:0:0:0: [sda] tag#0 uas_zap_pending 0 uas-tag 15 inflight: CMD 
[1262221.973511] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 3b 88 fa e8 00 04 00 00
[1262221.973512] sd 0:0:0:0: [sda] tag#1 uas_zap_pending 0 uas-tag 16 inflight: CMD 
[1262221.973513] sd 0:0:0:0: [sda] tag#1 CDB: Write(10) 2a 00 3b 88 fe e8 00 04 00 00
[1262221.973514] sd 0:0:0:0: [sda] tag#2 uas_zap_pending 0 uas-tag 17 inflight: CMD 
[1262221.973514] sd 0:0:0:0: [sda] tag#2 CDB: Write(10) 2a 00 3b 89 02 e8 00 04 00 00
[1262221.973515] sd 0:0:0:0: [sda] tag#3 uas_zap_pending 0 uas-tag 18 inflight: CMD 
[1262221.973516] sd 0:0:0:0: [sda] tag#3 CDB: Write(10) 2a 00 3b 89 06 e8 00 04 00 00
[1262221.973517] sd 0:0:0:0: [sda] tag#4 uas_zap_pending 0 uas-tag 19 inflight: CMD 
[1262221.973517] sd 0:0:0:0: [sda] tag#4 CDB: Write(10) 2a 00 3b 89 0a e8 00 04 00 00
[1262221.973518] sd 0:0:0:0: [sda] tag#5 uas_zap_pending 0 uas-tag 20 inflight: CMD 
[1262221.973519] sd 0:0:0:0: [sda] tag#5 CDB: Write(10) 2a 00 3b 89 0e e8 00 04 00 00
[1262221.973520] sd 0:0:0:0: [sda] tag#6 uas_zap_pending 0 uas-tag 21 inflight: CMD 
[1262221.973520] sd 0:0:0:0: [sda] tag#6 CDB: Write(10) 2a 00 3b 89 12 e8 00 04 00 00
[1262221.973521] sd 0:0:0:0: [sda] tag#7 uas_zap_pending 0 uas-tag 22 inflight: CMD 
[1262221.973522] sd 0:0:0:0: [sda] tag#7 CDB: Write(10) 2a 00 3b 89 16 e8 00 04 00 00
[1262221.973775] scsi_io_completion_action: 11 callbacks suppressed
[1262221.973821] sd 0:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[1262221.973830] sd 0:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 3b 88 e2 e8 00 04 00 00
[1262221.973833] blk_print_req_error: 44008 callbacks suppressed
[1262221.973836] I/O error, dev sda, sector 998826728 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
[1262221.974181] sd 0:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[1262221.974186] sd 0:0:0:0: [sda] tag#25 CDB: Write(10) 2a 00 3b 88 e6 e8 00 04 00 00
[1262221.974190] I/O error, dev sda, sector 998827752 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
[1262221.974481] sd 0:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[1262221.974484] sd 0:0:0:0: [sda] tag#26 CDB: Write(10) 2a 00 3b 88 ea e8 00 04 00 00
[1262221.974486] I/O error, dev sda, sector 998828776 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
[1262221.974676] sd 0:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[1262221.974678] sd 0:0:0:0: [sda] tag#27 CDB: Write(10) 2a 00 3b 88 ee e8 00 04 00 00
[1262221.974679] I/O error, dev sda, sector 998829800 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
[1262221.974829] sd 0:0:0:0: [sda] tag#28 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[1262221.974831] sd 0:0:0:0: [sda] tag#28 CDB: Write(10) 2a 00 3b 88 f2 e8 00 04 00 00
[1262221.974832] I/O error, dev sda, sector 998830824 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
[1262221.974977] sd 0:0:0:0: [sda] tag#29 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[1262221.974980] sd 0:0:0:0: [sda] tag#29 CDB: Write(10) 2a 00 3b 88 f6 e8 00 04 00 00
[1262221.974981] I/O error, dev sda, sector 998831848 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
[1262221.975127] sd 0:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[1262221.975129] sd 0:0:0:0: [sda] tag#22 CDB: Write(10) 2a 00 3b 88 dc e8 00 03 00 00
[1262221.975130] I/O error, dev sda, sector 998825192 op 0x1:(WRITE) flags 0x104000 phys_seg 96 prio class 2
[1262221.975276] sd 0:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[1262221.975278] sd 0:0:0:0: [sda] tag#23 CDB: Write(10) 2a 00 3b 88 df e8 00 03 00 00
[1262221.975280] I/O error, dev sda, sector 998825960 op 0x1:(WRITE) flags 0x100000 phys_seg 96 prio class 2
[1262221.975433] sd 0:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[1262221.975436] sd 0:0:0:0: [sda] tag#24 CDB: Write(10) 2a 00 38 c1 e1 70 00 00 08 00
[1262221.975438] I/O error, dev sda, sector 952230256 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2
[1262221.975584] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[1262221.975586] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 3b 88 fa e8 00 04 00 00
[1262221.975587] I/O error, dev sda, sector 998832872 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2
[1262221.976186] iomap_finish_ioend_buffered: 2116 callbacks suppressed
[1262221.976187] sda: writeback error on inode 1043148479, offset 0, sector 998818024
[1262221.976205] sda: writeback error on inode 1046172544, offset 0, sector 998825960
[1262221.976433] sda: writeback error on inode 1043148478, offset 0, sector 952230256
[1262221.976808] sda: writeback error on inode 1046172545, offset 0, sector 998826728
[1262221.977134] sda: writeback error on inode 1046172545, offset 61079552, sector 998946024
[1262221.977201] sda: writeback error on inode 1046172550, offset 0, sector 999267152
[1262221.977328] sda: writeback error on inode 1046172546, offset 0, sector 998958608
[1262221.977412] sda: writeback error on inode 722589506, offset 0, sector 999284048
[1262221.977422] sda: writeback error on inode 1046172551, offset 0, sector 999292408
[1262221.977474] sda: writeback error on inode 1046172552, offset 0, sector 999298128
[1262222.552677] XFS (sda): log I/O error -19
[1262222.553095] XFS (sda): Filesystem has been shut down due to log error (0x2).
[1262222.553241] XFS (sda): Please unmount the filesystem and rectify the problem(s).
[1262222.553399] XFS (sda): log I/O error -19
[1262222.553537] XFS (sda): log I/O error -19
[1262222.553678] XFS (sda): log I/O error -19
[1262222.553811] XFS (sda): log I/O error -19
[1262222.553946] XFS (sda): log I/O error -19
[1262222.554078] XFS (sda): log I/O error -19
[1262222.554206] XFS (sda): log I/O error -19
[1262223.015100] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[1262223.175874] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[1262223.476950] usb 4-2.1: reset SuperSpeed Plus Gen 2x1 USB device number 5 using xhci_hcd
[1262223.491009] scsi host1: uas
[1262223.503217] scsi 1:0:0:0: Direct-Access     FRMW     1TB Card         PMAP PQ: 0 ANSI: 6
[1262223.537844] sd 1:0:0:0: Attached scsi generic sg0 type 0
[1262223.540428] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[1262223.542571] sd 1:0:0:0: [sdb] Write Protect is off
[1262223.542577] sd 1:0:0:0: [sdb] Mode Sense: 5f 00 00 08
[1262223.546673] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[1262223.571989] sd 1:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
[1262223.572001] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
[1262223.613256] sd 1:0:0:0: [sdb] Attached SCSI disk

Both bays seem to be doing it. I’m running Ubuntu 24.04 (server) and am trying to rsync ~400GB of data. This seems to happen whether or not I create a partition table or simply use the whole disk for the filesystem (XFS).

I was previously trying to use it with my Framework 13" (with full disk encryption) but I found it flaky. I was hoping that wouldn’t be the case for the Desktop. I find it’s good to ~250GB and then it starts to have issues much more rapidly.

Anyone have any idears?

[Tim_Soderstrom]

I was able to finish the rsync by adding --bwlimit 250M. Trying to find a way to limit performance via mount options or some such. Looks like I have to use cgroups for that.

[sun]

@Tim_Soderstrom You have most likely hit on the USB-C port underpower issue.

Edit: was the problem with the front USB-C ports or the back USB4.0 ones? If it’s the USB4.0 ones, then yes I think it’s the USB-C 15W power profile issue. If the front ports, still possible a power issue but not exactly what I mentioned below.

See details here

Desktop Issue - New 3 amp power profile does not work. [3.03 BETA Bios]

And the discussions in this thread around these parts:

[TRACKING] Framework Desktop Ryzen AI MAX 300 BIOS 3.04 Release STABLE

I had unplugged it to plug my power meter into it. In doing so, and from further testing, I have determined that if the drive is plugged in on boot, it grabs the 15W PD profile. If plugged in while running, it only grabs 7.5W. The PD firmware does not seem to handle hot-plug at 15W. On boot: [PD15] on hotplug (showing zero draw because the drive powered down due to power constraints): [PD7]

[TRACKING] Framework Desktop Ryzen AI MAX 300 BIOS 3.04 Release STABLE

Recap: I used a USB3 (10 Gbps) hub to connect my gamepad and headset dongle to the motherboard, and I’ve been experiencing random flickering. I spent a significant amount of time testing and trying to reproduce the issue, and I’m increasingly convinced it’s power related. I’ve also noticed a couple of new scenarios, so I think it’s appropriate to post in this thread. Test setup Motherboard: Framework Desktop (motherboard only, 128 GB) PSU 1: SilverStone SFX 450W PSU 2: Seasonic Prime TX-1000 …

I would suggest adding your case in the Github issue and contact support.

[Tim_Soderstrom]

I read up on the rear power USB ports yep. I tried it in both the front ports, but not the rears. I’ll read those links over though thanks! Does seem plausible that it could be a power issue though yep.