From: Goswin von Brederlow <goswin-v-b@web.de>
To: Miles Fidelman <mfidelman@traversetechnologies.com>
Cc: Goswin von Brederlow <goswin-v-b@web.de>, linux-raid@vger.kernel.org
Subject: Re: rebuilding raided root partition
Date: Sun, 05 Apr 2009 23:35:55 +0200 [thread overview]
Message-ID: <87vdpibx6s.fsf@frosties.localdomain> (raw)
In-Reply-To: <49D8B2B3.7050903@traversetechnologies.com> (Miles Fidelman's message of "Sun, 05 Apr 2009 09:31:31 -0400")
Miles Fidelman <mfidelman@traversetechnologies.com> writes:
> Goswin von Brederlow wrote:
>> Ar you sure your / is actualy /dev/md2? Maybe you booted from
>> /dev/sda3 or /dev/sdc3? I recommend booting a rescue/life CD and
>> then look for a partition containing an active drive for md2 so you
>> can rebuild your raid.
>>
> pretty sure - there's a physical LVM volume defined on top of
> /dev/md2, and / is a LV defined on top of that - the machine comes up
> and runs
The lvm can just as easily run of sda3 or sdc3 if it does not check
for the raid signature (option in lvm.conf). Since it is a raid1 that
totaly works. Since you can boot your data seems to be still there,
somewhere. Just not in the raid.
>> Also did you know that you can run a raid1 with 3 active drives? That
>> way you are potected against 2 drive failures and don't need to wait
>> for the spare drive to resync before having fault tolerance if one
>> drive fails.
>>
>>
> Can you elaborate on how to do that, particularly how to add a new
> active volume to an existing array? It seems like mdadm wants to add
> new disks as spares.
mdadm --add /dev/md2 /dev/new/disk
mdadm --grow -n 3 /dev/md2
MfG
Goswin
prev parent reply other threads:[~2009-04-05 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 2:31 rebuilding raided root partition Miles Fidelman
2009-04-05 6:54 ` Goswin von Brederlow
2009-04-05 13:31 ` Miles Fidelman
2009-04-05 21:35 ` Goswin von Brederlow [this message]
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=87vdpibx6s.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=linux-raid@vger.kernel.org \
--cc=mfidelman@traversetechnologies.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).