▲ 6 r/linuxhardware+1 crossposts

Cloning a failing M.2 nvme ssd to a new one

So guys I have thinkpad t14 gen3 and the drive on it is failing (the maxwell controller is degrading) so I got a new drive and wanna clone it because all that’s on that drive is important (about 150GB out of 512GB).

I used ddrescue but it just runs for like 2mins before the drive drops off the bus and my os freeze which I have to restart the pc again to try to continue the process. And it’s tiring and frustrating and I don’t wanna corrupt or mess the pc up with that process.

Is there any solutions to cloning a failed drive to the new one. I have a live usb running fedora, a ssd enclosure housing the new drive which I plug in the pc. What can I do to make sure this is a successful clone. Both drives are 512GB too btw

reddit.com
u/RelevantTear6092 — 13 days ago
▲ 6 r/linuxhardware+4 crossposts

WD SN720 NVMe SSD drops off PCIe bus under sustained reads on Fedora (ThinkPad T14 Gen 3)

I'm dealing with a really frustrating issue: my NVMe SSD completely disappears from the PCIe bus during any sustained read workload (BTRFS scrub, copying large files, `find` over the filesystem, etc.). The drive vanishes, the filesystem goes read-only, and I get `Input/output error` until I hard power-off the laptop.

Hardware & OS
- Laptop: Lenovo ThinkPad T14 Gen 3 (Intel i5-1245U)
- OS: Fedora Workstation 44 (kernel 7.0.10)
- SSD: WD PC SN720 512GB (Marvell 88SS1093 controller, firmware 10112006)
- Storage stack: BTRFS on LUKS2

Symptoms
- Normal light usage (browsing, coding, small writes) is completely stable.
- Any heavy sustained read load causes the system to freeze after ~60–90 seconds.
- Journal logs cut off abruptly. RAM-buffered services continue for a short time but any disk access hangs.
- After hard reboot, the drive remounts fine and BTRFS recovers with **zero data loss**.

Diagnostics
- SMART: PASSED
- Media/Data Integrity Errors: 0
- Available Spare: 100%
- Percentage Used: 14% (good health)
- Unsafe Shutdowns: 328 (almost all caused by this issue)
- Power-On Hours: ~18,081 (~2 years)

BTRFS device stats also show zero read/write/corruption errors.

What I've already tried (no improvement)

  1. Disabled APST (`nvme_core.default_ps_max_latency_us=0`)
  2. Disabled ASPM (`pcie_aspm=off`)
  3. Increased NVMe timeout (`nvme_core.io_timeout=255`)
  4. LUKS flags: `no-read-workqueue,no-write-workqueue`
  5. BTRFS tweaks: lowered `thread_pool` and compression overhead

Despite all the usual power-management and timeout workarounds, sustained reads still kill the drive.

Questions

  1. Is this almost certainly a hardware issue with the Marvell 88SS1093 controller (thermal/voltage degradation), or is there some PCIe/BIOS setting on ThinkPads I'm missing?
  2. Has anyone fixed this on a ThinkPad with better thermal pads or an aftermarket heatsink?
  3. If I need to replace it, what Gen4 NVMe drives have proven to run cool and work reliably with Linux/ThinkPad power management?

Any help or similar experiences would be greatly appreciated!

reddit.com
u/RelevantTear6092 — 2 months ago