From: Shaun Jackman <sjackman@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Migrating from non-RAID to RAID-1
Date: Tue, 9 Aug 2005 18:42:57 -0700 [thread overview]
Message-ID: <7f45d9390508091842473da782@mail.gmail.com> (raw)
In-Reply-To: <42F93FB5.1040901@h3c.com>
2005/8/9, Mike Hardy <mhardy@h3c.com>:
> This was asked not but a few days ago. While not intending to be rude, I
> believe searching the archives will turn up step by step guidance
>
> -Mike
Thanks for the pointer, Mike. I was using Google's mailing list
archive, but it seems woefully incomplete.
http://groups.google.ca/group/mlist.linux.raid
Another linux-raid archive had the message you mentioned:
http://marc.theaimsgroup.com/?l=linux-raid&m=112318177226599
The directions were...
sfdisk -d /dev/sda > /tmp/sda.part
sfdisk /dev/sdb < /tmp/sda.part
read the Software RAID-HowTo, and look for the Root-RAID section
Cheers,
Shaun
next prev parent reply other threads:[~2005-08-10 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 23:41 Migrating from non-RAID to RAID-1 Shaun Jackman
[not found] ` <42F93FB5.1040901@h3c.com>
2005-08-10 1:42 ` Shaun Jackman [this message]
2005-08-10 3:52 ` Christopher Smith
2005-08-10 23:39 ` Shaun Jackman
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=7f45d9390508091842473da782@mail.gmail.com \
--to=sjackman@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).