From: Mark Lord <liml@rtr.ca>
To: Tomas Lund <tlund@nxs.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: Need help understanding SATA error message.
Date: Fri, 28 Mar 2008 23:50:31 -0400 [thread overview]
Message-ID: <47EDBC87.8090109@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.61.0803282315330.5510@envy.nxs.se>
Tomas Lund wrote:
> On Fri, 28 Mar 2008, Mark Lord wrote:
>
>> Mark Lord wrote:
>>
>> Duh.. actually, we were just discussing this very error in another
>> thread. The drive is really telling us that it hit an unrecoverable
>> WRITE error at sector 0a:24:f9 on the drive. Bad sector.
>
> Aha, ok :(
>
>> There are patches queued up for 2.6.26 to automatically resume the
>> cache flush after the failed sector, but you'll still lose data at
>> that sector.
>
> Lucky for me, there is no data yet on the system yet!
>
>> Time for a low-level reformat, if the manufacturer has a utility for
>> that. Otherwise, RMA it.
>
> The drive is brand spanking new, less than 3 weeks, its going back!
>
> I do however wonder, what is an "unrecoverable write error", does it
> mean it even failed to re-allocate it? Reallocated_Sector_Ct is still 0
> according to smartcl...
..
Mmm.. it does seem rather unlikely there, doesn't it ?
One thing to try, if you have 12000 seconds to spare, :)
is to simply try this:
cat /dev/zero > /dev/sdX
sync
hdparm -F /dev/sdX
And see if that completes without error.
If it does, then the drive may be fine.
Software bugs are always possible, but do seem unlikely in this case.
But then, so does a hardware failure seem unlikely on a new drive.
Cheers
next prev parent reply other threads:[~2008-03-29 3:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 7:04 Need help understanding SATA error message Tomas Lund
2008-03-28 13:40 ` Jeff Garzik
2008-03-28 14:28 ` Tomas Lund
2008-03-28 15:49 ` Mark Lord
2008-03-28 15:59 ` Mark Lord
2008-03-28 22:21 ` Tomas Lund
2008-03-29 3:50 ` Mark Lord [this message]
2008-03-30 15:01 ` Tomas Lund
2008-03-31 0:59 ` Tejun Heo
2008-03-31 14:53 ` Mark Lord
2008-04-01 0:26 ` Tejun Heo
2008-04-01 2:01 ` Mark Lord
2008-04-01 7:11 ` Tomas Lund
2008-04-01 12:05 ` Mark Lord
2008-04-01 16:15 ` Tejun Heo
2008-04-02 5:17 ` Tomas Lund
2008-04-03 10:39 ` Tomas Lund
2008-04-11 6:16 ` Tejun Heo
2008-03-29 3:54 ` Mark Lord
2008-03-29 10:39 ` Tomas Lund
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=47EDBC87.8090109@rtr.ca \
--to=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=tlund@nxs.se \
/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;
as well as URLs for NNTP newsgroup(s).