From: "Mike Black" <mblack@csi-inc.com>
To: Danilo Godec <danci@agenda.si>, linux-raid@vger.kernel.org
Subject: Re: Multiple disk failure - recover?
Date: Wed, 10 Jul 2002 09:17:33 -0400 [thread overview]
Message-ID: <02e301c22814$27779300$f6de11cc@black> (raw)
In-Reply-To: Pine.LNX.4.30.0207101505480.25329-100000@duplo.agenda.si
You don't say why two disks were kicked or when it happend so sdc may be out-of-whack a bit. Sounds like sdc got kicked first.
So...I would do a bad-block scan on sdb2 so it can remap the bad section and re-build as you've been trying to do.
If you REALLY want to use sda and sdc just rebuild the array with --create and leave sdb out of it. You shouldn't lose much data if
sdc is current.
----- Original Message -----
From: "Danilo Godec" <danci@agenda.si>
To: <linux-raid@vger.kernel.org>
Sent: Wednesday, July 10, 2002 9:10 AM
Subject: Multiple disk failure - recover?
> Hi!
>
> I have (had) a three disk RAID5 array. One of the disks (sdb2) has failed,
> however, under circumstances, two of the diskes were kicked out of the
> array.
>
> I tried re-assembling the array using 'mdadm --assemble --force /dev/md1
> /dev/sda2 /dev/sdc2 /dev/sdb2', but it always takes the sdc2 & sdb2 as OK
> disks and sda2 as failed.
>
> Of course, when the reconstruction hits the bad area on sdb2, it all fails
> again.
>
> How can I tell mdadm that /dev/sda2 and /dev/sdc2 are the disks I want as
> 'good'!?
>
> Thanks, D.
>
>
>
> -
> 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:[~2002-07-10 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 11:25 Setting a buffer_heads 'real_device' Mario Vodisek
2002-07-10 13:10 ` Multiple disk failure - recover? Danilo Godec
2002-07-10 13:17 ` Mike Black [this message]
2002-07-10 13:36 ` Neil Brown
2002-07-10 13:43 ` Danilo Godec
2002-07-10 13:55 ` Neil Brown
2002-07-10 14:13 ` Danilo Godec
2002-07-10 14:30 ` Neil Brown
2002-07-10 13:42 ` Danilo Godec
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='02e301c22814$27779300$f6de11cc@black' \
--to=mblack@csi-inc.com \
--cc=danci@agenda.si \
--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).