linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Soltys <soltys@ziu.info>
To: Michael Guyver <michael.guyver@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Create software RAID from active partition
Date: Mon, 01 Sep 2008 22:03:09 +0200	[thread overview]
Message-ID: <48BC4A7D.8020907@ziu.info> (raw)
In-Reply-To: <c8ce53500809010532h5444a8cckcb1d2cb57d3dc281@mail.gmail.com>

What do:

mdadm -E /dev/sda1
mdadm -E /dev/sdb1
mdadm -E /dev/sda2
mdadm -E /dev/sdb2

show, if anything ?

If they report they belonged once to an array with superblock positioned 
at the end (so either 0.9 or 1.0), you could create RAID1 array missing 
one component. In your case, something like:

umount /dev/mapper/VolGroup00-LogVol00
umount /dev/mapper/VolGroup00-LogVol01
vgchange -an VolGroup00

mdadm  -C /dev/md/1 -l1 -n2 -e0 /dev/sdb2 missing

-e0 assuming it was v0.9 superblock
-e1.0 assuming it was v1.0

and then:

mdadm /dev/md/1 --add /dev/sda2

..wait for resync, then:

vgscan --mknodes
vgchange -ay

..should use /dev/md/1 - but  doublecheck /etc/lvm/lvm.conf as well.


Of course it's potentially risky, so doublecheck everything and if it's 
possible somehow (considering remote location), backup /dev/sdb2 first 
(actually, you could use /dev/sda2 for that, as it's unused at this 
moment anyway).


/dev/sd{a,b}1 case will be difficult w/o physical access, if they were 
part of another raid1 array.

  parent reply	other threads:[~2008-09-01 20:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 12:32 Create software RAID from active partition Michael Guyver
2008-09-01 12:45 ` Steve Fairbairn
2008-09-01 13:14 ` Alan Jenkins
2008-09-01 13:30 ` David Greaves
2008-09-01 14:28   ` Michael Guyver
2008-09-01 20:03 ` Michal Soltys [this message]
2008-09-01 22:42   ` Michael Guyver

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=48BC4A7D.8020907@ziu.info \
    --to=soltys@ziu.info \
    --cc=linux-raid@vger.kernel.org \
    --cc=michael.guyver@gmail.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).