From: Roger Heflin <rogerheflin@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: "linux-raid@vger.kernel.org List" <linux-raid@vger.kernel.org>,
Roman Mamedov <rm@romanrm.net>
Subject: Re: writing zeros to bad sector results in persistent read error
Date: Sat, 7 Jun 2014 20:50:43 -0500 [thread overview]
Message-ID: <CAAMCDeddsKzi71KDBPik5i+wBp+On3gochDs_PqKoP9bN2szCQ@mail.gmail.com> (raw)
In-Reply-To: <0E76B97E-96DF-43A3-B8EC-4867964BF8E9@colorremedies.com>
Check messages file and see if it has in the last few weeks reporting
sectors bad.
Or do a dd if=/dev/sda of=/dev/null read test until it hits something,
then correct it, then continue on.
Or do repeated long/selective tests to see if you can find them.
Though, I had a seagate disk that I was able to get all of the pending
to be fixed, I had to remove the disk from the raid as it still would
randomly pause for 7 seconds while reading sectors that were not yet
classified as pending. I tried a number of things to try to get the
disk to behave and/or replace those bad sectors, but finally gave up
on that disk and just replaced it (out of warranty) as I could not
ever get it to behave right.
On Sat, Jun 7, 2014 at 7:52 PM, Chris Murphy <lists@colorremedies.com> wrote:
> I wrote:
>> How can there still be pending bad sectors, and yet no error and LBA reported?
>
> So I started another -t long test. And it comes up with an LBA not previously reported.
>
> # 1 Extended offline Completed: read failure 60% 1214 430234064
>
> # dd if=/dev/zero of=/dev/sda seek=430234064 count=8
> dd: writing to '/dev/sda': Input/output error
> 1+0 records in
> 0+0 records out
> 0 bytes (0 B) copied, 3.63342 s, 0.0 kB/s
>
> On this sector the technique fails.
>
> # dd if=/dev/zero of=/dev/sda seek=430234064 count=8 oflag=direct
> 8+0 records in
> 8+0 records out
> 4096 bytes (4.1 kB) copied, 3.73824 s, 1.1 kB/s
>
> This technique works.
>
> However, this seems like a contradiction. A complete -t long results in:
>
> # 1 Extended offline Completed without error 00% 1219 -
>
> and yet
>
> 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 16
>
> How are there 16 pending sectors, with no errors found during the extended offline test? In order to fix this without SMART reporting the affected LBAs, I'd have to write to every sector on the drive. This seems like bad design or implementation.
>
> Chris Murphy
next prev parent reply other threads:[~2014-06-08 1:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 0:11 writing zeros to bad sector results in persistent read error Chris Murphy
2014-06-07 1:26 ` Roger Heflin
2014-06-07 1:51 ` Roman Mamedov
2014-06-07 16:42 ` Chris Murphy
2014-06-07 18:26 ` Chris Murphy
2014-06-08 0:52 ` Chris Murphy
2014-06-08 1:50 ` Roger Heflin [this message]
2014-06-08 21:50 ` Chris Murphy
2014-06-08 8:10 ` Wilson Jonathan
2014-06-10 0:09 ` Chris Murphy
2014-06-10 6:52 ` Wilson Jonathan
2014-10-08 17:56 ` Phillip Susi
2014-06-09 19:37 ` Wolfgang Denk
2014-06-10 2:48 ` Chris Murphy
2014-06-10 13:40 ` Phil Turmel
2014-06-29 0:05 ` Chris Murphy
2014-06-29 23:50 ` Martin K. Petersen
2014-06-30 0:51 ` Roger Heflin
2014-10-08 17:51 ` Phillip Susi
2014-06-10 22:18 ` Eyal Lebedinsky
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=CAAMCDeddsKzi71KDBPik5i+wBp+On3gochDs_PqKoP9bN2szCQ@mail.gmail.com \
--to=rogerheflin@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=rm@romanrm.net \
/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).