From: Kay Diederichs <kay.diederichs@uni-konstanz.de>
To: linux-raid@vger.kernel.org
Subject: Re: force remapping a pending sector in sw raid5 array
Date: Wed, 7 Feb 2018 10:42:39 +0100 [thread overview]
Message-ID: <aedfc1ac-a95f-b20f-2713-87cf412afdf4@uni-konstanz.de> (raw)
In-Reply-To: <20180206181416.amo6geclrvc6ylrf@merlins.org>
On 02/06/2018 07:14 PM, Marc MERLIN wrote:
> So, I have 2 drives on a 5x6TB array that have respectively 1 and 8
> pending sectors in smart.
>
...
> # 3 Extended offline Completed: read failure 90% 289
1287409520
I have successfully used "badblocks" to overwrite bad sectors.
The variety of badblocks that comes with RHEL (there may be others!)
could be used with e.g.
badblocks -svnb512 /dev/sdh 1287409599 1287409400
where
-n Use non-destructive read-write mode. By default only a
non-destructive read-only test is done. This option must not be
combined with the -w option, as they are mutually exclusive.
I've adjusted the last-block and first-block numbers in the command
above so that they
a) encompass the known bad blocks
b) start and end on 4k-boundaries
This command leaves those blocks intact that still can be read.
After that, use a destructive-write badblocks e.g.
badblocks -sfvwb512 /dev/sdh <x> <y>
You'll have to adjust x and y to match just those blocks that cannot be
read, based on the output of the first badblocks run.
Afterwards, "smartctl -t short /dev/sdh" may clean up the SMART statistics.
HTH,
Kay
next prev parent reply other threads:[~2018-02-07 9:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 18:14 force remapping a pending sector in sw raid5 array Marc MERLIN
2018-02-06 18:59 ` Reindl Harald
2018-02-06 19:36 ` Marc MERLIN
2018-02-06 20:03 ` Andreas Klauer
2018-02-06 21:51 ` Adam Goryachev
2018-02-06 22:02 ` Marc MERLIN
2018-02-06 22:31 ` Roger Heflin
2018-02-06 22:46 ` Marc MERLIN
2018-02-07 4:29 ` Marc MERLIN
2018-02-07 9:42 ` Kay Diederichs [this message]
2018-02-09 19:29 ` Marc MERLIN
2018-02-09 19:57 ` Kay Diederichs
2018-02-09 20:02 ` Roger Heflin
2018-02-09 20:13 ` Phil Turmel
2018-02-09 20:29 ` Marc MERLIN
2018-02-09 20:44 ` Phil Turmel
2018-02-09 21:22 ` Marc MERLIN
2018-02-09 22:07 ` Wol's lists
2018-02-09 22:36 ` Marc MERLIN
2018-02-09 20:52 ` Kay Diederichs
2018-02-11 20:52 ` Roger Heflin
2018-02-09 21:17 ` Kay Diederichs
2018-02-10 21:43 ` Mateusz Korniak
2018-02-11 15:41 ` Marc MERLIN
2018-02-11 16:41 ` Marc MERLIN
2018-02-11 17:13 ` Phil Turmel
2018-02-11 18:02 ` Wols Lists
2018-02-12 10:43 ` Mateusz Korniak
2018-02-12 15:29 ` Phil Turmel
2018-02-12 16:49 ` Marc MERLIN
2018-02-12 17:16 ` Phil Turmel
2018-02-12 17:30 ` Marc MERLIN
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=aedfc1ac-a95f-b20f-2713-87cf412afdf4@uni-konstanz.de \
--to=kay.diederichs@uni-konstanz.de \
--cc=linux-raid@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