this post was submitted on 29 Sep 2025
7 points (100.0% liked)
Do-It-Yourself, Repairs and Fixes
3167 readers
1 users here now
Share tips and tricks to keep people from throwing out that broken item. Repair before replace!
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The physical connector? Like this thing:
If it’s an issue with that you’d likely be able to straight up see it, bent or missing pin. Or check with a meter for shorts. And clean the pins I guess just in case they’re oxidized.
But this is wayyyyy down the list. Is the same LBA bad every scrub? Then it’s the drive, probably. If not did you check the cable (most likely culprit), the sata controller would be next most likely, then port, then solder joints (which you’d have to redo to replace that port anyway so moot point I guess). Udma crc errors?
If you do replace it you’d need to solder. I don’t know how to source that sata connector, that would be the hardest part. There is likely a part number on the actual sata port somewhere though it may not be visible until it’s removed (and even then it may not be available, may have been a custom part or it may be legacy at this point).
The soldering is actually not that tough though if you can find one. Add flux, add leaded solder, hot air, remove, wick to clean pads, fresh solder to pads, more flux, hot air new one on (second tricky part - patience with temp low enough to not melt plastic but enough to melt solder, can be a pain for connectors like that)
Not sure. I'll keep it in mind and keep a record.
No UDMA CRC errors. Here's the whole smart output in case anything pops out.
I don't think there's a cable, it seems to be attached directly. And I'm no good with soldering. So I guess I'm out of options.
That log is fine and I bet your sata connector is too. And duh of course no sata cable (my build is a rack mount so I jump to that because it’s always the first thing to check).
I would guess you have data corruption from lack of redundancy and i/o error. zpool status -v to show impacted files, restore from backup, then scrub again
Shouldn't that show up as checksum errors though, instead of read/write errors? I never see checksum errors.
Ahhh right right
R/w would suggest media (especially if it’s the same sectors), but not necessarily that the drive is toast
zpool status -v | grep "errors" may output files associated with bad blocks
zpool status -v might just give you filenames though, worth it to try that first. It might just give object IDs tho and I forget what to do at that point. You have to map them to file paths but I don’t remember how to do this.
If the errors are in different spots though totally different story. Back to sata I/o issues. Controller issues, kernel/driver issue, etc. technically could be the sata port but I seriously doubt it