> Nov 16 12:55:11 coyote kernel: [57888.336419] res 51/40:08:18:c6:ba/40:00:2a:00:00/e0 Emask 0x9 (media error)
> Nov 16 12:55:11 coyote kernel: [57888.336473] ata1.00: status: { DRDY ERR }
> Nov 16 12:55:11 coyote kernel: [57888.336498] ata1.00: error: { UNC }
Unrecoverable read error on the disk is what is being reported
> So I am running badblocks, and have collected a lengthy list. But the drive
> is not re-allocating them, and has not re-allocated any bad blocks according
> to smartctl.
It cannot reallocate a block which it cannot read as the data on it would
be lost silently at that point. It should reallocate such blocks on a
write to them (which is why fsck.ext3 knows how to rewrite bad inode
blocks when recovering stuff)
> but the last 5 all occurred while amdump was running earlier today, and
> the last 5 is all the drive apparently keeps.
Yes
> The question then is:
>
> Bad drive, (un-)known bug, or configuration?
Probably bad drive but could also be bad drive as a symptom of something
else (eg heat)
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
