From: Mark Lord <kernel@start.ca>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Ondrej Zary <linux@rainbow-software.org>,
Pavel Machek <pavel@ucw.cz>, Mark Lord <mlord@pobox.com>,
Marcus Overhagen <marcus.overhagen@gmail.com>,
kernel list <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, tj@kernel.org
Subject: Re: SATA hdd refuses to reallocate a sector?
Date: Sat, 29 Jun 2013 19:02:14 -0400 [thread overview]
Message-ID: <51CF6776.7090206@start.ca> (raw)
In-Reply-To: <20130629184716.GA9330@khazad-dum.debian.net>
On 13-06-29 02:47 PM, Henrique de Moraes Holschuh wrote:
> You know, either the "long" or the "offline" SMART test routines do exactly
> that on any spinning rust device with a firmware that is not utterly broken.
>
> The HDD's firmware will rewrite, and even reallocate any "weak" sectors
> found by the surface scan.
>
The drives I have tried this on (smartctl -t long),
abort at the first bad sector. Not useful.
next prev parent reply other threads:[~2013-06-29 23:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-23 10:19 SATA hdd refuses to reallocate a sector? Pavel Machek
2013-06-23 11:21 ` Pavel Machek
2013-06-23 13:16 ` Marcus Overhagen
2013-06-23 19:00 ` Pavel Machek
2013-06-23 21:27 ` Mark Lord
2013-06-23 21:51 ` Pavel Machek
2013-06-23 22:35 ` Mark Lord
2013-06-24 6:19 ` Marcus Overhagen
2013-06-24 12:28 ` Pavel Machek
2013-06-24 7:14 ` Ondrej Zary
2013-06-24 11:06 ` Pavel Machek
2013-06-24 12:18 ` Mark Lord
2013-06-26 3:04 ` James Bottomley
2013-06-26 6:11 ` Ondrej Zary
2013-06-29 18:47 ` Henrique de Moraes Holschuh
2013-06-29 23:02 ` Mark Lord [this message]
2013-06-30 14:34 ` Henrique de Moraes Holschuh
2013-06-30 16:49 ` Pavel Machek
2013-07-01 13:28 ` Henrique de Moraes Holschuh
2015-04-30 19:01 ` Pavel Machek
2013-06-24 12:48 ` Zdenek Kaspar
2013-06-24 13:08 ` Ondrej Zary
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=51CF6776.7090206@start.ca \
--to=kernel@start.ca \
--cc=hmh@hmh.eng.br \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=marcus.overhagen@gmail.com \
--cc=mlord@pobox.com \
--cc=pavel@ucw.cz \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).