From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Drive breakdown or bug?
Date: Sun, 16 Nov 2008 18:33:58 +0000 [thread overview]
Message-ID: <20081116183358.4d7f61eb@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <200811161325.57557.gene.heskett@gmail.com>
> 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
prev parent reply other threads:[~2008-11-16 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 18:25 Drive breakdown or bug? Gene Heskett
2008-11-16 18:33 ` Alan Cox [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081116183358.4d7f61eb@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=gene.heskett@gmail.com \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox