Laptop specs
EndeavourOS, updated to latest as of 2025-02-07
Kernel 6.12.12-1-lts (64-bit)
BIOS 3.05
Framework 13 i5-1340P w/ 16GB RAM, 1TB SSD
Logs
log-sda-only - Pastebin.com
log-sdb-only - Pastebin.com
log-excerpt - Pastebin.com
I am having problems transferring data with an M.2 SSD that is connected via USBC3.2 through an NVME case/holder. I am unable to add ext4 and FAT32 partitions through KDE Partition Manager and GParted, however adding through the command line seems to work fine. I am also unable to transfer large amounts of data, as KDE’s Dolphin errors out with “Unknown error 5” (and journald seems to have a superblock error?). This also happens if I boot off of a live USB (I have tried EndeavourOS and Fedora KDE) or if I use USBA instead of USBC. However, this does not happen if I use a slower USB speed (USB2) or if I connect the SSD directly via the M.2 slot on the mainboard. This also doesn’t happen on other computers, even when using the same cable, speed, and OS.
What could be going wrong? Some journald logs are linked at the top.
(this was posted on Reddit a day ago, but I feel like this forum is more active)
Interestingly, if I plug in the drive to a USBC hub, I can finally create an ext4 partition. However, the hub and drive are still USB3.2, but now show 5000Mbit/s instead of the 10,000Mbit/s that shows when I plug in the drive directly.
I have also noticed that KDE’s Info Center shows the USB controller on the mainboard (“xHCI Host Controller (2)”) as USB 3.1, but the drive connects as USB 3.2. Could this be the reason for inconsistent behaviour?
UPDATE: smartctl logs are at drive-smartctl - Pastebin.com
I am thinking that something is wrong with the 10,000Mbit/s mode, as 5000Mbit/s works fine and was the one used on other computers. I have bought another drive case to test this, hopefully I can solve this in a couple of days.
journalctl logs if needed: journalctl logs - Pastebin.com
These show up when the drive is directly connected (not through a hub), using USB3.2 10Gbit/s, and making an ext4 partition to cover the whole SSD through KDE Partition Manager.
SOLVED: Something is going wrong with my original SSD case, so I’m just using a different one. I still don’t think that the original case is fully at fault.
The framework does seem to be a little pickier with ssd and enclosure combinations which is a bit weird but there have been a lot of reports.
Personally the only combo I had issues with was a 970 evo in an asm usb4 enclosure in usb 4 mode on linux, everything else worked.