From: Shaun Jackman <sjackman@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Migrating from non-RAID to RAID-1
Date: Tue, 9 Aug 2005 16:41:24 -0700 [thread overview]
Message-ID: <7f45d93905080916414e291a87@mail.gmail.com> (raw)
I have a single non-RAID SATA drive with Debian (Sarge) installed and
data on it. I also have a duplicate blank drive. I would like to
migrate from my non-RAID system to a RAID-1 (mirrored) system for
redundancy, with each disk being an exact duplicate of the other. Is
it possible to do this without having to wipe the first drive clean?
I'd appreciate a pointer to a HOWTO or recipe if it answers this
specific question.
Any recommendations for a friendly RAID and LVM management tool?
Please cc me in your reply. Thanks,
Shaun
next reply other threads:[~2005-08-09 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 23:41 Shaun Jackman [this message]
[not found] ` <42F93FB5.1040901@h3c.com>
2005-08-10 1:42 ` Migrating from non-RAID to RAID-1 Shaun Jackman
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=7f45d93905080916414e291a87@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).