On 10 Aug 2024 18:20 +1000, from c...@goproject.info (George at Clug): > I have changed the port it is connected to, and the SATA cable, but > still the errors follow the disk drive.
So that potentially leaves things like the SATA controller (unlikely), the power supply (possible) and the drive itself (highly likely), including the drive's onboard controller hardware and firmware. > I suspect that the error message "Medium Error", means just that, an > area of the disk has failed, hence "Unrecovered read error". That would be the typical conclusion, yes. > Sadly "Unrecovered read error" also implies "auto reallocate failed", No, it does not necessarily imply that. > so what ever data was on the failed area, it is gone forever. Likely, yes. Especially if they recur in the same physical location, which with LBA mapping can be moderately difficult to tell. Specifically, unrecoverable read error does not imply _that_ automatic remapping failed _if_ the error developed after the data was written. In that case, the firmware can't know what _should_ be stored (if it could, then the error wouldn't be unrecoverable/uncorrectable), so remapping _can't_ be done. If the firmware is doing the right thing, then the problematic sectors will be remapped on the next write if they fail to hold the newly-written data; but that doesn't help with the data that _was_ there. Check SMART data for the drive. If offline uncorrectable or pending sectors is climbing as you try a read test, that's a strong signal that the drive is somehow physically damaged. Each drive has a limited pool of spare sectors and once that pool is used up for remapping, it cannot handle any further sectors going bad. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
