Wrong port? bad expansion card? other ideas? previous SSD keeps unmounting when I'm transferring `$HOME` from old 2TB (`SN850` via USB-c enclosure) to new internal 4TB SSD

[jon]

@Jason_Username_Taken

The disconnection also happened with your replacement board, did I understand correctly? Do you still have the replacement board’s packaging? Do you still have the bad board or you have already shipped it back? What BIOS version did the replacement board arrive with?

Yes you understood right. That original board had BIOS InsydeH2O Version: KFM30.03.01.

The warranty replacement board, of which I’d already applied firmware updates (fwupdmgr update && fwupdmgr upgrade) shows KFM30.03.04.

@Jason_Username_Taken

There should be a production date on the packaging of the replacement board. On the reverse side of the board itself, its PCB revision version and revision date should also be printed there.

• original (faulty boot) mainboard upgrade:
  • Manufacture date: 09/2024
• second (warrantied, but still faulty data-transfers) mainboard upgrade:
  • Manufacture date: 10/2024

both boards have this on the back of their PCB:

• KFM30 LA-N611P
• Rev: 1.0
• 2025-05-28

I took detailed pictures of everything, but just in case: let me know if I can share any other details before I send this back.

base-line: confirming SSD transfer OK elsewhere

@Jason_Username_Taken

Also, have you confirmed that your specific combination of SSD+enclosure+cable can perform a sustained transfer on other known-good system? Preferably something non-Framework.

Oh my goodness, thanks so much for asking this. I can’t believe I didn’t do this baseline check right away…

thinkpad x1 nano

I indeed was able to move a whole TB on first try with my old Thinkpad X1 Nano, using the same enclosure and same old framework SSD I’ve been struggling to copy data from. I copied the whole TB and only a few dmesg errors, but never a disconnect and never and issue with the transfer. Used the exact same rsync commandline as I’ve been using all along (only changed the destination to a random new dir inside home: ~/test-content-DELETE-ME).

1st gen framework13 motherboard

@Jason_Username_Taken

I’m pretty surprised you are having this issue, hopefully we can pin point it.

interesting: I’m now trying this base-line a second time, but now with my original first-gen motherboard (the one I’m trying to upgrade away from). So far: it’s looking like it’ll succeed, which I think is pretty telling since the only thing changing would be: ram sticks and motherboard (SSDs involved are identical). I’ll report back though when the test is done.

edit 1: running 1hr now, and already 500GB through, with zero retries required from me. It’s certainly looking damning for this new mainboard model. (Or I coincidentally got two lemons in a row).

edit 2: done! 100% success, rsync exited 0, all of my 1 TB moved over in 84 min, without issues! dmesg was very quiet!

---

This was the push I needed to just go back to my original/old mainboard, and return both of these new ones. I’ve been unable to use my machine for almost a month as I debug this, all because I’m simply trying to upgrade. I’ll just wait until these issues are figured out by framework. Hopefully framework team just takes back the order and refunds me.