linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Hill <robin@robinhill.me.uk>
To: linux-raid@vger.kernel.org
Subject: Re: emergency call for help: raid5 fallen apart
Date: Wed, 24 Feb 2010 18:12:19 +0000	[thread overview]
Message-ID: <20100224181219.GA8043@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <4B856372.6000900@xunil.at>

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

On Wed Feb 24, 2010 at 06:35:46PM +0100, Stefan G. Weichinger wrote:

> Am 24.02.2010 18:09, schrieb Robin Hill:
> 
> > If these are the only disks with up-to-date data, and sda4 is still
> > failing, I can only suggest stopping the array and using dd/dd_rescue to
> > copy sda4 onto a working disk.  You should then be able to reassemble
> > the array with sdb4 and the new disk, then add in a hot spare to
> > recover.
> 
> Currently sdd isn't in use at all.
> 
> So I could
> 
> 
> mdadm --stop /dev/md4
> 
> ddrescue /dev/sda4 /dev/sdd4
> 
> mdadm --assemble --force /dev/md4 /dev/sdb4 /dev/sdd4
> 
> ??
> 
Yes, that'd be what I'd recommend - the ddrescue will only need to make
a single pass across sda4 (except for failed blocks of course), so will
have the lowest risk of exacerbating the disk problems.  Of course, the
practicality of doing the assemble will depend on the number of
unreadable blocks found by ddrescue.

Good luck!
    Robin
-- 
     ___        
    ( ' }     |       Robin Hill        <robin@robinhill.me.uk> |
   / / )      | Little Jim says ....                            |
  // !!       |      "He fallen in de water !!"                 |

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-02-24 18:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 14:54 emergency call for help: raid5 fallen apart Stefan G. Weichinger
2010-02-24 15:05 ` Stefan G. Weichinger
2010-02-24 15:22   ` Robin Hill
2010-02-24 15:32     ` Stefan G. Weichinger
2010-02-24 16:38       ` Stefan G. Weichinger
2010-02-24 16:53         ` Stefan G. Weichinger
2010-02-24 17:02           ` Stefan G. Weichinger
2010-02-25  8:05             ` Giovanni Tessore
2010-02-25 16:27               ` Stefan /*St0fF*/ Hübner
2010-02-25 16:45               ` John Robinson
2010-02-25 17:41                 ` Dawning Sky
2010-02-25 18:31                   ` John Robinson
2010-02-26  2:42                     ` Michael Evans
2010-02-26 20:15                 ` Bill Davidsen
2010-02-28 11:50                 ` Stefan /*St0fF*/ Hübner
2010-02-28 12:52                   ` Stefan /*St0fF*/ Hübner
2010-02-24 17:09           ` Robin Hill
2010-02-24 17:28             ` Stefan G. Weichinger
2010-02-24 17:35             ` Stefan G. Weichinger
2010-02-24 18:12               ` Robin Hill [this message]
2010-02-24 19:54                 ` Stefan G. Weichinger

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=20100224181219.GA8043@cthulhu.home.robinhill.me.uk \
    --to=robin@robinhill.me.uk \
    --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).