From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: changing MD device
Date: Wed, 14 Jan 2004 23:02:00 +0100 [thread overview]
Message-ID: <20040114220159.GM26406@percy.comedia.it> (raw)
In-Reply-To: <4005B847.5090306@netscape.net>
On Wed, Jan 14, 2004 at 04:44:39PM -0500, Aaron Gee wrote:
>I have a system up and running, the root directory is mounted on device
>/dev/md0 which is a raid1 of 2 IDE drives. My question is, how can I
>change it so that the my raid device is /dev/md1 not /dev/md0 and not
>loose the data. Originally I was thinking of booting with a rescue
>disk, breaking the raid1, and rebooting. Once rebooted create the raid
>device again as /dev/md1. Is there a simpler way to do this?
if your rescue disk contains mdadm you can use the
mdadm -A -U super-minor /dev/md1 /dev/hd?? once and the array will be
started and the minor updated
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2004-01-14 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 21:44 changing MD device Aaron Gee
2004-01-14 22:02 ` Luca Berra [this message]
2004-01-15 19:36 ` Aaron Gee
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=20040114220159.GM26406@percy.comedia.it \
--to=bluca@comedia.it \
--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).