@delroth Isn't this "just" a sector that failed and wasn't reallocated yet, because it wasn't written to?
@delroth Or even s/failed/is unreadable due to crc mismatch/
@robryk No clue. The disk is telling me it's broken, I'm not particularly interested in trying out how much it's broken before it eats my data. I'm guessing that an extended offline test would take care of reallocating if it could too.
@delroth No, it won't.
The sector won't be reallocated until it's written to. The reasoning behind that is that maybe the next read will actually succeed, and we should never trash that possibility without explicit instructions to do so.
@delroth Take a look at Reallocated_Sector_Ct (and Offline_Uncorrectable and Current_Pending_Sector) counters. If there are few remaining spare sectors, then the disk is really close to failure. This is indicated by Reallocated_Sector_Ct being marked as dangerously high.
Other than that, sectors that cannot be corrected with the error correction code happen at some rate. This rate can be increased by various issues that make the drive arguably broken, but it's nonzero even with totally operational drive.
@robryk [nix-shell:~]# dd if=/dev/zero of=/dev/sdh bs=512 seek=8896601104
dd: error writing '/dev/sdh': Input/output error
1+0 records in
0+0 records out
0 bytes copied, 3.38237 s, 0.0 kB/s
Can't be written to at all, from what I can tell.
@delroth Huh. That's really surprising (the read error was not immediate, so it's not _totally_ borked, but then why it seems totally borked for writes? is that the read-errored sector that you're trying to write to?). Would you mind pasting `smartctl -a /dev/sdh` and the presentation of this error in dmesg for my curiosity?