I second this. SATA cables are cheaply made and can present issues that seem to indicate drive failure.
Comment on 🏳️(TrueNAS) Is my drive dying and should be replaced?🏳️
frongt@lemmy.zip 1 week ago
Not necessarily. I would shut the system down completely and check the drive connectors. If it’s on a backplane, try swapping slots, or if it’s breakout connector, swap it with another drive (and clear the zpool errors). If the errors start happening on the other drive, it’s a cable problem. If they continue on the same drive, it’s a drive problem. If they stop happening, it was a bad connection and it ought to be fine now.
That’s kind of a short output from smartctl -a, though. Shouldn’t it include the attribute data? I’d run a smart test (after doing the swap above) and see what it says.
On a raidz2, I wouldn’t be too concerned about losing a drive, but you should always be prepared to order a replacement if you value your data.
s38b35M5@lemmy.world 1 week ago
BigDaddySlim@lemmy.world 1 week ago
Had this issue once, 2 drives kept not initializing during boot, rebooting a few times got them to register but showed drive errors. I thought either the drives or my SAS card was dying. Fully reseating the connectors fixed it and haven’t had an issue since.
frongt@lemmy.zip 1 week ago
OP is using SAS, but it’s not too far from SATA.
s38b35M5@lemmy.world 1 week ago
Good catch. I don’t usually see SAS as /dev/sd* so I assumed. Same basic cables, though *usually better made.
ragebutt@lemmy.dbzer0.com 1 week ago
I would bet money that drive is done. Cable would be udma crc errors, not media failure. Drive made it 11 years (even if power on time is only about half of that)