From: Roman Mamedov <rm@romanrm.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: "linux-raid@vger.kernel.org List" <linux-raid@vger.kernel.org>
Subject: Re: writing zeros to bad sector results in persistent read error
Date: Sat, 7 Jun 2014 07:51:40 +0600 [thread overview]
Message-ID: <20140607075140.277c0880@natsu> (raw)
In-Reply-To: <B7EA34DA-1064-45B1-B0C0-B7C423C7EB47@colorremedies.com>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
On Fri, 6 Jun 2014 18:11:03 -0600
Chris Murphy <lists@colorremedies.com> wrote:
> # dd if=/dev/zero of=/dev/sda seek=430196560 count=2048
> dd: writing to ‘/dev/sda’: Input/output error
> 1025+0 records in
> 1024+0 records out
>
> It stops right at LBA 430197584, again with a read error. So even though the drive SMART health assessment is "pass" and there are no other SMART values below threshold indicating "works as designed" this drive has effectively failed because any write operation to this LBA results in unrecoverable failure.
Hello,
Try again with "oflag=direct";
If that doesn't help, remember this is a 4K-sector drive, maybe you should
retry with bs=4096 (recalculating the offset so it still writes to the proper
place).
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-06-07 1:51 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 [this message]
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
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=20140607075140.277c0880@natsu \
--to=rm@romanrm.net \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).