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.
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.
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.
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.
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.
hardware - I have seem some enclosures have loose or faulty connectors.
Fixed by returning the faulty unit.
power supply from the usb port not enough.
Fixed by putting a powered hub between the FW and the enclosure.
Note: not all powered hubs work. I have a power hub that has 4 usb ports. Only one of the usb ports work with my enclosure.
Over heating
Some SSDs have temp sensors on them, that can be reported by smartmon tools.
Monitor the temps over time and see if they are getting too hot. Once you loose the usb connection, you loose the temp sensing also.
faulty cables. Some usb cables are just better than others. I have some that work OK a low speed and then are intermittently faulty at higher speeds.
If you can try the above suggestion and maybe narrow down the problem to which one it is, you might make some progress towards a solution.
This is a huge one. I have bought over 8 external enclosures and it happens more often than not that the actual usb cable that comes with the enclosure is faulty. Either it can’t provide enough power to the enclosure, or it causes it to connect at slower speeds. Always try a new cable when you have problems. It’s the easiest thing to try.
