AMD Framework and NVMe SSD Enclosure Compatibility Investigation

Community Support
,
69

Me and some other testing volunteers have ruled this possibility out on their enclosure.

For my enclosure+SSD+cable combination specifically, it works perfectly fine on 12th Gen Intel Framework, MacBooks (running Windows and macOS), and multiple other non-Framework computers including an 8840U-based one. It only exhibits issue on AMD FW13, which is consistent with reports from a few other users (alongside issues like Type-C display compatibility, USB-C iPhone compatibility).

Therefore a faulty enclosure doesn’t appear to be the cause, at least for me and a few other users in this post :slight_smile:

4 Likes
70

I got another SSD and it also has the same problem when connect to FW13 (AMD version).

SSD: Kingston KC2500
SSD enclosure chip: Realtek RTL9210
OS: NixOS 24.05

I use this to rsync data. After transmit about 100GB then it failed. Here is the dmesg log

[  957.904982] sd 0:0:0:0: [sda] tag#29 uas_eh_abort_handler 0 uas-tag 17 inflight: CMD OUT 
[  957.904997] sd 0:0:0:0: [sda] tag#29 CDB: Write(10) 2a 00 83 50 62 00 00 00 10 00
[  957.905139] sd 0:0:0:0: [sda] tag#28 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD 
[  957.905151] sd 0:0:0:0: [sda] tag#28 CDB: Write(10) 2a 00 83 50 60 20 00 00 08 00
[  957.905161] sd 0:0:0:0: [sda] tag#20 uas_eh_abort_handler 0 uas-tag 23 inflight: CMD OUT 
[  957.905167] sd 0:0:0:0: [sda] tag#20 CDB: Write(10) 2a 00 83 50 63 e0 00 00 10 00
[  957.905302] sd 0:0:0:0: [sda] tag#19 uas_eh_abort_handler 0 uas-tag 21 inflight: CMD OUT 
[  957.905311] sd 0:0:0:0: [sda] tag#19 CDB: Write(10) 2a 00 83 50 63 a0 00 00 10 00
[  957.905422] sd 0:0:0:0: [sda] tag#18 uas_eh_abort_handler 0 uas-tag 20 inflight: CMD OUT 
[  957.905433] sd 0:0:0:0: [sda] tag#18 CDB: Write(10) 2a 00 83 50 63 38 00 00 08 00
[  957.905540] sd 0:0:0:0: [sda] tag#17 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD 
[  957.905547] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 13 0e 8f e0 00 00 70 00
[  957.905554] sd 0:0:0:0: [sda] tag#16 uas_eh_abort_handler 0 uas-tag 22 inflight: CMD OUT 
[  957.905558] sd 0:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 83 50 63 d0 00 00 08 00
[  957.905681] sd 0:0:0:0: [sda] tag#15 uas_eh_abort_handler 0 uas-tag 19 inflight: CMD OUT 
[  957.905692] sd 0:0:0:0: [sda] tag#15 CDB: Write(10) 2a 00 83 50 62 a0 00 00 08 00
[  957.905794] sd 0:0:0:0: [sda] tag#14 uas_eh_abort_handler 0 uas-tag 18 inflight: CMD OUT 
[  957.905799] sd 0:0:0:0: [sda] tag#14 CDB: Write(10) 2a 00 83 50 62 78 00 00 10 00
[  957.905888] sd 0:0:0:0: [sda] tag#13 uas_eh_abort_handler 0 uas-tag 16 inflight: CMD OUT 
[  957.905892] sd 0:0:0:0: [sda] tag#13 CDB: Write(10) 2a 00 83 50 61 f0 00 00 08 00
[  957.905988] sd 0:0:0:0: [sda] tag#12 uas_eh_abort_handler 0 uas-tag 15 inflight: CMD OUT 
[  957.905993] sd 0:0:0:0: [sda] tag#12 CDB: Write(10) 2a 00 83 50 61 a0 00 00 08 00
[  957.906078] sd 0:0:0:0: [sda] tag#11 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD OUT 
[  957.906083] sd 0:0:0:0: [sda] tag#11 CDB: Write(10) 2a 00 83 50 61 80 00 00 18 00
[  957.906167] sd 0:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD OUT 
[  957.906171] sd 0:0:0:0: [sda] tag#10 CDB: Write(10) 2a 00 83 50 61 70 00 00 08 00
[  957.906252] sd 0:0:0:0: [sda] tag#9 uas_eh_abort_handler 0 uas-tag 12 inflight: CMD OUT 
[  957.906257] sd 0:0:0:0: [sda] tag#9 CDB: Write(10) 2a 00 83 50 61 48 00 00 08 00
[  957.906342] sd 0:0:0:0: [sda] tag#8 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT 
[  957.906345] sd 0:0:0:0: [sda] tag#8 CDB: Write(10) 2a 00 83 50 61 20 00 00 18 00
[  957.906418] sd 0:0:0:0: [sda] tag#7 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD OUT 
[  957.906420] sd 0:0:0:0: [sda] tag#7 CDB: Write(10) 2a 00 83 50 60 f0 00 00 08 00
[  957.906491] sd 0:0:0:0: [sda] tag#6 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT 
[  957.906494] sd 0:0:0:0: [sda] tag#6 CDB: Write(10) 2a 00 83 50 60 d8 00 00 10 00
[  957.906564] sd 0:0:0:0: [sda] tag#5 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT 
[  957.906566] sd 0:0:0:0: [sda] tag#5 CDB: Write(10) 2a 00 83 50 60 c8 00 00 08 00
[  957.906636] sd 0:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD OUT 
[  957.906638] sd 0:0:0:0: [sda] tag#4 CDB: Write(10) 2a 00 83 50 60 b8 00 00 08 00
[  957.906708] sd 0:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT 
[  957.906710] sd 0:0:0:0: [sda] tag#3 CDB: Write(10) 2a 00 83 50 60 a0 00 00 08 00
[  957.906779] sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT 
[  957.906781] sd 0:0:0:0: [sda] tag#2 CDB: Write(10) 2a 00 83 50 60 88 00 00 10 00
[  957.906846] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT 
[  957.906848] sd 0:0:0:0: [sda] tag#1 CDB: Write(10) 2a 00 83 50 60 50 00 00 10 00
[  957.906913] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT 
[  957.906915] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 83 50 60 30 00 00 08 00
[  959.761004] sd 0:0:0:0: [sda] tag#27 uas_eh_abort_handler 0 uas-tag 30 inflight: CMD OUT 
[  959.761026] sd 0:0:0:0: [sda] tag#27 CDB: Write(10) 2a 00 74 58 32 88 00 04 00 00
[  959.761233] sd 0:0:0:0: [sda] tag#26 uas_eh_abort_handler 0 uas-tag 29 inflight: CMD OUT 
[  959.761243] sd 0:0:0:0: [sda] tag#26 CDB: Write(10) 2a 00 74 58 2e 88 00 04 00 00
[  959.761406] sd 0:0:0:0: [sda] tag#25 uas_eh_abort_handler 0 uas-tag 28 inflight: CMD OUT 
[  959.761415] sd 0:0:0:0: [sda] tag#25 CDB: Write(10) 2a 00 74 58 2a 88 00 04 00 00
[  959.761610] sd 0:0:0:0: [sda] tag#24 uas_eh_abort_handler 0 uas-tag 27 inflight: CMD OUT 
[  959.761619] sd 0:0:0:0: [sda] tag#24 CDB: Write(10) 2a 00 74 58 26 88 00 04 00 00
[  959.761777] sd 0:0:0:0: [sda] tag#23 uas_eh_abort_handler 0 uas-tag 26 inflight: CMD OUT 
[  959.761789] sd 0:0:0:0: [sda] tag#23 CDB: Write(10) 2a 00 74 58 22 88 00 04 00 00
[  959.761904] sd 0:0:0:0: [sda] tag#22 uas_eh_abort_handler 0 uas-tag 25 inflight: CMD OUT 
[  959.761910] sd 0:0:0:0: [sda] tag#22 CDB: Write(10) 2a 00 74 58 1e 88 00 04 00 00
[  959.762064] sd 0:0:0:0: [sda] tag#21 uas_eh_abort_handler 0 uas-tag 24 inflight: CMD OUT 
[  959.762073] sd 0:0:0:0: [sda] tag#21 CDB: Write(10) 2a 00 74 58 1a 88 00 04 00 00
[  959.770071] scsi host0: uas_eh_device_reset_handler start
[  959.889345] usb 8-1: reset SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd
[  962.942519] scsi host0: uas_eh_device_reset_handler success
[  973.247196] sd 0:0:0:0: [sda] tag#29 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD 
[  973.247209] sd 0:0:0:0: [sda] tag#29 CDB: Test Unit Ready 00 00 00 00 00 00
[  973.247214] scsi host0: uas_eh_device_reset_handler start
[  973.362021] usb 8-1: reset SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd
[  973.441038] scsi host0: uas_eh_device_reset_handler success
[  973.441057] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441063] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441066] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441069] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441072] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441075] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441078] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441082] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441085] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441088] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441091] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441094] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441097] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441100] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441103] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441106] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441109] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441112] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441115] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441118] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441121] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441124] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441127] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441130] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441133] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441136] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441139] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441142] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441146] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441149] sd 0:0:0:0: Device offlined - not ready after error recovery
[  973.441231] sd 0:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=43s
[  973.441241] sd 0:0:0:0: [sda] tag#21 CDB: Write(10) 2a 00 74 58 1a 88 00 04 00 00
[  973.441245] I/O error, dev sda, sector 1951931016 op 0x1:(WRITE) flags 0xd800 phys_seg 128 prio class 2
[  973.441434] sd 0:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=43s
[  973.441439] sd 0:0:0:0: [sda] tag#22 CDB: Write(10) 2a 00 74 58 1e 88 00 04 00 00
[  973.441442] I/O error, dev sda, sector 1951932040 op 0x1:(WRITE) flags 0xd800 phys_seg 128 prio class 2
[  973.441590] sd 0:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=43s
[  973.441595] sd 0:0:0:0: [sda] tag#23 CDB: Write(10) 2a 00 74 58 22 88 00 04 00 00
[  973.441597] I/O error, dev sda, sector 1951933064 op 0x1:(WRITE) flags 0xd800 phys_seg 128 prio class 2
[  973.441794] sd 0:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=43s
[  973.441805] sd 0:0:0:0: [sda] tag#24 CDB: Write(10) 2a 00 74 58 26 88 00 04 00 00
[  973.441808] I/O error, dev sda, sector 1951934088 op 0x1:(WRITE) flags 0xd800 phys_seg 128 prio class 2
[  973.441973] sd 0:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=43s
[  973.441978] sd 0:0:0:0: [sda] tag#25 CDB: Write(10) 2a 00 74 58 2a 88 00 04 00 00
[  973.441980] I/O error, dev sda, sector 1951935112 op 0x1:(WRITE) flags 0xd800 phys_seg 128 prio class 2
[  973.442147] sd 0:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=43s
[  973.442151] sd 0:0:0:0: [sda] tag#26 CDB: Write(10) 2a 00 74 58 2e 88 00 04 00 00
[  973.442154] I/O error, dev sda, sector 1951936136 op 0x1:(WRITE) flags 0xd800 phys_seg 128 prio class 2
[  973.442364] sd 0:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=43s
[  973.442368] sd 0:0:0:0: [sda] tag#27 CDB: Write(10) 2a 00 74 58 32 88 00 04 00 00
[  973.442371] I/O error, dev sda, sector 1951937160 op 0x1:(WRITE) flags 0xd800 phys_seg 128 prio class 2
[  973.442543] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=45s
[  973.442548] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 83 50 60 30 00 00 08 00
[  973.442551] I/O error, dev sda, sector 2203082800 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
[  973.442559] Buffer I/O error on dev dm-0, logical block 275253510, lost async page write
[  973.442589] sd 0:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=45s
[  973.442593] sd 0:0:0:0: [sda] tag#1 CDB: Write(10) 2a 00 83 50 60 50 00 00 10 00
[  973.442596] I/O error, dev sda, sector 2203082832 op 0x1:(WRITE) flags 0x103000 phys_seg 2 prio class 0
[  973.442602] Buffer I/O error on dev dm-0, logical block 275253514, lost async page write
[  973.442609] Buffer I/O error on dev dm-0, logical block 275253515, lost async page write
[  973.442624] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=45s
[  973.442629] sd 0:0:0:0: [sda] tag#2 CDB: Write(10) 2a 00 83 50 60 88 00 00 10 00
[  973.442631] I/O error, dev sda, sector 2203082888 op 0x1:(WRITE) flags 0x103000 phys_seg 2 prio class 0
[  973.442638] Buffer I/O error on dev dm-0, logical block 275253521, lost async page write
[  973.442646] Buffer I/O error on dev dm-0, logical block 275253522, lost async page write
[  973.442680] Buffer I/O error on dev dm-0, logical block 275253524, lost async page write
[  973.442692] Buffer I/O error on dev dm-0, logical block 275253527, lost async page write
[  973.442704] Buffer I/O error on dev dm-0, logical block 275253529, lost async page write
[  973.442716] Buffer I/O error on dev dm-0, logical block 275253531, lost async page write
[  973.442722] Buffer I/O error on dev dm-0, logical block 275253532, lost async page write
[  973.442935] sd 0:0:0:0: rejecting I/O to offline device
[  973.443030] Aborting journal on device dm-0-8.
[  973.443078] JBD2: I/O error when updating journal superblock for dm-0-8.
[  973.443087] EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5735: IO failure
[  973.443106] EXT4-fs error (device dm-0): ext4_dirty_inode:5939: inode #68856363: comm rsync: mark_inode_dirty error
[  973.443116] EXT4-fs error (device dm-0) in ext4_dirty_inode:5940: IO failure
[  973.443552] EXT4-fs error (device dm-0): ext4_journal_check_start:84: comm rsync: Detected aborted journal
[  973.443613] EXT4-fs (dm-0): I/O error while writing superblock
[  973.443801] EXT4-fs (dm-0): I/O error while writing superblock
[  973.443813] EXT4-fs (dm-0): Remounting filesystem read-only
[  973.454892] EXT4-fs warning (device dm-0): dx_probe:822: inode #68829534: lblock 0: comm rsync: error -5 reading directory block
[  973.515420] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #68830768: lblock 0: comm rsync: error -5 reading directory block
[  973.759360] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #68832314: lblock 0: comm rsync: error -5 reading directory block
[  973.804461] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #68832750: lblock 0: comm rsync: error -5 reading directory block
[  973.810746] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #68832885: lblock 0: comm rsync: error -5 reading directory block
[  973.830473] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #68833159: lblock 0: comm rsync: error -5 reading directory block
[  974.028463] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #68835909: lblock 0: comm rsync: error -5 reading directory block
[  974.051661] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #68836587: lblock 0: comm rsync: error -5 reading directory block
[  974.051739] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #68836610: lblock 0: comm rsync: error -5 reading directory block
[  974.228818] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #68838694: lblock 0: comm rsync: error -5 reading directory block
[  978.463600] blk_print_req_error: 1422 callbacks suppressed
[  978.463608] I/O error, dev sda, sector 2157027688 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  978.463633] EXT4-fs warning: 1212 callbacks suppressed
[  978.463636] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67389580: lblock 0: comm rsync: error -5 reading directory block
[  978.484645] I/O error, dev sda, sector 2157027792 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  978.484683] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67390054: lblock 0: comm rsync: error -5 reading directory block
[  978.485389] I/O error, dev sda, sector 2157027816 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  978.485405] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67390074: lblock 0: comm rsync: error -5 reading directory block
[  978.490835] I/O error, dev sda, sector 2157027864 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  978.490858] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67390227: lblock 0: comm rsync: error -5 reading directory block
[  978.497017] I/O error, dev sda, sector 2157028096 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  978.497034] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67390631: lblock 0: comm rsync: error -5 reading directory block
[  978.497274] I/O error, dev sda, sector 2156996752 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  978.497288] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67381735: lblock 0: comm rsync: error -5 reading directory block
[  978.497644] I/O error, dev sda, sector 2156996696 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  978.497658] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67381713: lblock 0: comm rsync: error -5 reading directory block
[  978.497705] I/O error, dev sda, sector 2156996672 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  978.497717] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67381710: lblock 0: comm rsync: error -5 reading directory block
[  978.497869] I/O error, dev sda, sector 2156996712 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  978.497882] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67381720: lblock 0: comm rsync: error -5 reading directory block
[  978.498213] I/O error, dev sda, sector 2156996480 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  978.498226] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67381088: lblock 0: comm rsync: error -5 reading directory block
[  983.468799] blk_print_req_error: 2152 callbacks suppressed
[  983.468803] I/O error, dev sda, sector 2157004504 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  983.468813] EXT4-fs warning: 2018 callbacks suppressed
[  983.468814] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67392622: lblock 0: comm rsync: error -5 reading directory block
[  983.468912] I/O error, dev sda, sector 2157004520 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  983.468917] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67392629: lblock 0: comm rsync: error -5 reading directory block
[  983.469420] I/O error, dev sda, sector 2157004600 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  983.469426] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67392679: lblock 0: comm rsync: error -5 reading directory block
[  983.469768] I/O error, dev sda, sector 2157004696 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  983.469772] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67392728: lblock 0: comm rsync: error -5 reading directory block
[  983.469787] I/O error, dev sda, sector 2157004704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  983.469791] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67392731: lblock 0: comm rsync: error -5 reading directory block
[  983.470117] I/O error, dev sda, sector 2157004728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  983.470121] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67392736: lblock 0: comm rsync: error -5 reading directory block
[  983.470135] I/O error, dev sda, sector 2157004736 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  983.470139] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67392739: lblock 0: comm rsync: error -5 reading directory block
[  983.470204] I/O error, dev sda, sector 2157004752 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  983.470207] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67392747: lblock 0: comm rsync: error -5 reading directory block
[  983.470842] I/O error, dev sda, sector 2157004840 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  983.470846] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67392823: lblock 0: comm rsync: error -5 reading directory block
[  983.470983] I/O error, dev sda, sector 2157004864 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  983.470987] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:1082: inode #67392835: lblock 0: comm rsync: error -5 reading directory block
71

I think it would help to know which expansion card slot the NVME enclosure was plugged into at the time. I think some slots are better than others.

72

I think he is using a USB M2 adapter. He mentions an “enclosure” that uses a Realtek chip.

73

As the drive appears to be in an adapter I suspect that with that much data it is getting hot and shutting down.

74

IMO it’s pretty amazing it lasted 100GB before giving out.

In my own case, all four ports are subject to this issue.

As I previously documented (but I totally understand this post is getting long and hard to track), I can hit the enclosure and NVMe drive with a sustained load to long enough the point of it becoming too hot to safely touch, but the most that could happen is thermal throttling and never ‘crapped out’, it just keeps going on and on, when tested with Intel FW13 and few other devices. (And even the thermal throttling can be well mitigated or eliminated by providing cooling to the enclosure)

When tested with AMD13, the disconnect could occur way before the enclosure and drive heat up to any appreciable level. Therefore, IMO the thermal of external devices probably isn’t relevant. (Especially since compatibility issue with USB-C iPhones, certain Samsung phones, and certain Power Banks that has since been discovered on AMD13/FW16)

75

I’m not sure it’s fully over 100GB or it just rsync calculate. When the SSD disconnect, I saw a lot of IO error message. The total data which I want to rsync about 130GB. I forget to calculate the actual size that rsync did.

All 4 ports I tested having the same issue. I did this test before using RTK9210 with Transcend SSD. This also happened with framework USB-A adapter. I had reply earlier.

1 Like
76

My System: Framework 16, BIOS 3.03, Kubuntu 24.04

SSD-Enclosure: Icy Box (Raidsonic) IB-1922MF-C32, USB 3.2 Gen 2x2, 20 GBits, ASMedia ASM2364 Chip, M.2 PCIe 3.0 M-Key

SSD: ADATA LEGEND 960 MAX, PCIe 4, 1 TByte

Test: Copy Videofiles (150 GBytes) from internal to external SSD

Port 1: Ok, 500-600 MBytes/sec
Poet 2: not tested
Port 3: not enough Power (5 V, 0,9 A)
Port 4: Ok, 500-600 MBytes/sec
Port 5: only ~30 MBytes/sec Write-Speed
Port 6: not enough Power (5 V, 0,9 A)

Got an error message in 'dmesg’ everytime i disconnect the Enclosure:
sd 0:0:0:0: [sda] Synchronizing SCSI cache
sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK

1 Like
77

I think I may be running into this problem also with a Samsung PSSD T7, though I am not sure; the inconsistencies with USB on FW16 are slowly driving me mad.

The reason why I suspect I am having the same problem and that it is a FW16 issue rather than a device or kernel issue is because it also seems to be port-specific. I had no trouble so far with USB-A on Port 3 nor USB-C on Port 4, but USB-A on Port 5 had big trouble (and this is my primary backup disk, so I don’t want to keep testing it until I end up with a corrupt backup). (Ports 1, 2, and 6 are populated by FW power adaptor, USB-C hub, and audio expansion card, respectively.)

At first, the laptop didn’t notice the device being connected at all until I unplugged and replugged the USB-A expansion card. Problems with the USB-A and Ethernet expansion cards not working right after a cold boot until they are unplugged/replugged has been a problem since day 1 for me. However, usually they work correctly after a replug, but in this case, after mounting the device, its activity indicator light was blinking constantly and uas driver errors started appearing in kernel log:

Aug 16 01:22:56 kernel: sd 0:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
Aug 16 01:22:56 kernel: sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 2d 4a 8b a0 00 00 20 00
Aug 16 01:22:56 kernel: scsi host0: uas_eh_device_reset_handler start
Aug 16 01:22:56 kernel: usb 2-2.1: reset SuperSpeed Plus Gen 2x1 USB device number 9 using xhci_hcd
Aug 16 01:22:56 kernel: scsi host0: uas_eh_device_reset_handler success
Aug 16 01:23:29 kernel: sd 0:0:0:0: [sda] tag#8 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
Aug 16 01:23:29 kernel: sd 0:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 2d 4f 17 20 00 00 20 00
Aug 16 01:23:29 kernel: scsi host0: uas_eh_device_reset_handler start
Aug 16 01:23:29 kernel: usb 2-2.1: reset SuperSpeed Plus Gen 2x1 USB device number 9 using xhci_hcd
Aug 16 01:23:29 kernel: scsi host0: uas_eh_device_reset_handler success

Eventually I ended up just pulling the USB cable because something was clearly very wrong. When I did that, here is the information the kernel provided about the transaction that was in flight at the time:

Aug 16 01:23:42 kernel: usb 2-2.1: USB disconnect, device number 9
Aug 16 01:23:42 kernel: sd 0:0:0:0: [sda] tag#10 uas_zap_pending 0 uas-tag 1 inflight: CMD 
Aug 16 01:23:42 kernel: sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 3f 9a ad 20 00 00 20 00
Aug 16 01:23:42 kernel: sd 0:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=12s
Aug 16 01:23:42 kernel: sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 3f 9a ad 20 00 00 20 00
Aug 16 01:23:42 kernel: I/O error, dev sda, sector 1067101472 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0

Reviews suggest that Samsung are using ASM2362 for this device.

2 Likes
78

What you are describing sounds like my issue I’m having with PSSD T7 when running the drive through a Thunderbolt 4 dock (on my Framework 13 AMD 7840U). Though I suspect your case might be slightly different.

79

Yeah, I saw your post when I searched the forum and had about the same reaction as you. I think it is more likely than not that the root cause is the same. Did you ever get any update on that internal engineering ticket? I get the sense USB-IF compliance testing was skipped, or the USB-IF compliance tests are deficient, given the number of USB issues I have had with this laptop (USB-PD through a hub not working, SSD failing in some ports, USB cable sense errors, USB thumb drive spontaneously dropping off the bus in USB3 mode, internal keyboard can’t survive USB powersave, lag in BIOS until USB devics are replugged, ethernet expansion card not working until replugged on cold boot, USB-A expansion card not working until replugged on cold boot, DP expansion card causing monitor wakeups every 60s when in DPMS standby that doesn’t happen when using a non-Framework DP hub).

80

Unfortunately not. But I was not too persistent.

81

Thank you Jason for showing me this thread, I had my own thread going before noticing this one USB Storage issue. I have very similar issues all of you are having on my FW 16. I have an SSK NVME enclosure that when I use windows to go I get I/O lockup at random or under high load, regardless of connection port or cable type. 100% disk utilization, 0 throughput, disk queue climbing into the hundreds while windows waits for the drive to reconnect. The drive won’t work on port 6 or port 3, although my SanDisk 10gbps external SSD works fine on those ports. Latest NVME firmware.

20241016_181800
20241016_1818001920×2560 308 KB

Works fine on my desktop Ryzen 5 3600 system at 10gbps.

20241022_083603
20241022_0836031920×1440 253 KB

And it worked fine on my 11th gen Intel XPS 9710. So clearly it’s a framework AMD USB implementation issue at work here sadly.

A workaround I have used (and hopefully is helpful to some) is I use a USB 3.1 5gbps capable USB hub as a “speed limiter” for my SSK NVME enclosure and that resolves my issue but of course cuts my speed in half and I have to use an additional device to make it possible. For me it seems to be that the FW16 can’t handle full load from 10 gbps while booted from it, however I did verify I have no issues using this drive when not using it as a boot device. I was able to get 950MBps copies from my SSK NVME to my SanDisk 10gbps SSD. SSK NVME was in port 5 USB-A and SanDisk was in Port 6 USB-A.

1 Like
82

Yeah. At this point it does seems to be an compatibility issue that could be similarly observed on both the AMD13 and FW16. I just don’t have the expertise nor equipment to determine if the issue is happening on the data level, or power-level.

83

Hi,
My guess is that the problem is usb power related.
A way to test this would be to put a 10Gbps separately powered hub between the laptop and external ssd and see if it is any more reliable.

84

Sadly. After upgrade BIOS 3.06 beta, this problem still exists.

85

Yeah, and ‘Known Issues’ section only addressed connectivity issue with USB-C equipped Apple devices, but not this problem we have here. I’m gradually becoming less and less inclined to believe Framework is still at the investigation stage of this issue with no more details to offer, after nearly a year of initial reporting to them.

I know FW16, which uses similar architecture as AMD13 and also affected by this issue per community reports, got a new board revision, Rev: 1A on 2024-05-07 vs the original Rev: 1.0 on 2023-10-19. I’m unsure if this revision is due to other unrelated reasons, or included mid-cycle fixes for issues like this post. Hopefully someone that recently purchased or RMAed AMD13 boards can check the revision on the new boards they are receiving.

86

My AMD13 just got shipped, where would i find the revision?

87

On the back of the mainboard is where you would find the REV and date.

You do need to take out the mainboard to check, but taking it out shouldn’t damage anything or affect your warranty as long as performed carefully.

1 Like
88

So my Board says Rev. 1A with Date 2023-08-04 but i have not yet installed an OS, but it boots after teardown and reassembly :sweat_smile: