From: Chris Purves <chris@northfolk.ca>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Cc: "Alexander Kühn" <alexander.kuehn@nagilum.de>, jeromepoulin@gmail.com
Subject: Re: unable to recover RAID 5 due to bad block
Date: Thu, 10 Nov 2011 12:50:46 -0400 [thread overview]
Message-ID: <4EBC00E6.3030404@northfolk.ca> (raw)
In-Reply-To: <20111110172003.Horde.byVZeZk8pphOu-mzTQXxKL8@cakebox.homeunix.net>
On 2011-11-10 12:20, Alexander Kühn wrote:
> ddrescue to the rescue!
> Get a another new disk, then ddrescue the one with the read error to the new disk.
> Assemble the array using the new disk instead of the one with the read error.
> You will loose the blocks that can't be read of course.
> And in the future do run raid check/scrubbing at regular intervals. ;)
I have tried this already. After cloning the disk with errors, I replaced it with the clone and tried to re-start the array using
mdadm --assemble --force /dev/md1
mdadm assigned the new disk as a spare and said there were only three disks to start the array and so couldn't start it.
After I clone the disk with the error, how precisely should I re-start the array?
--
Chris Purves
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-10 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 16:04 unable to recover RAID 5 due to bad block Chris Purves
2011-11-10 16:20 ` Alexander Kühn
2011-11-10 16:50 ` Robin Hill
2011-11-10 17:04 ` Chris Purves
2011-11-10 16:50 ` Chris Purves [this message]
2011-11-10 17:02 ` Alexander Kühn
2011-11-10 17:07 ` Chris Purves
2011-11-10 20:09 ` NeilBrown
2011-11-10 20:11 ` NeilBrown
2011-11-11 0:15 ` unable to recover RAID 5 due to bad block [solved] Chris Purves
[not found] ` <CALJXSJrdBX8xqkwamauRsz27LUQYg-gV-G4K+RrNkdhB5ki31w@mail.gmail.com>
2011-11-10 16:42 ` unable to recover RAID 5 due to bad block Jérôme Poulin
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=4EBC00E6.3030404@northfolk.ca \
--to=chris@northfolk.ca \
--cc=alexander.kuehn@nagilum.de \
--cc=jeromepoulin@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).