2026-09-17 12:50 UTC
One of my NVMe SSDs dropped out of several arrays, again.
👉 a Transcend MTE220S 256er
As an IT guy myself, i've just rebooted the box.
That made matters worse, because the dodgy SSD didn't enumerate (/dev/nvme*), and i was left with 3/4 SSDs, incorrectly enumerated. My #ZFS pools re-imported fine, albeit in a DEGRADED state.
zpool replace is bullshit! 🤬 ..it NEVER wörks!
I had to power-cycle the box, and zpool detach/remove, then add & resilver shit!
SMART reports look fine!
🧵1/n..
Replies (1)
-
@platymew@layer8.space 2026-09-17 13:01
🧵 2/n using /dev/disk/by-id/ links might be useful in such a scenario, but those long "friendly names" require too much width in "zpool iostat" - i'm using the short kernel names - nvme0-3. In my case, it's merely an inconvenience, because everything that needs to be redundant, IS. I'm just not font of the tools recommending zpool replace, and then getting noped out of it by errors like "nvme1n1p2 is a member of tank" - NOT IT'S NOT, it WAS, but it dropped out and got reenumerated differently!