From: Drew <drew.kay@gmail.com>
To: Jim Santos <iluvgadgets@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Moving RAID1 disks between systems
Date: Fri, 24 May 2013 11:30:05 -0700 [thread overview]
Message-ID: <CACJz6Qt-zULSobEDqo306gow4wAvx1LQdXBf3K5XHm36rDKE4Q@mail.gmail.com> (raw)
In-Reply-To: <CAGPLN=s0nBeuHk75KSaKV2LS1MxYrdVmXjG7eM+dP36bOSbA-A@mail.gmail.com>
Hi Jim,
You should have no troubles reassembling the array on a new machine.
From what I understand, md raid doesn't depend on device names for
assembling arrays, it has some internal UUID's to distinguish which
array a member disk belongs to.
mdadm --assemble --scan is pretty much all you need (and won't break
anything in the process)
--
Drew
"Nothing in life is to be feared. It is only to be understood."
--Marie Curie
"This started out as a hobby and spun horribly out of control."
-Unknown
next prev parent reply other threads:[~2013-05-24 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 16:53 Moving RAID1 disks between systems Jim Santos
2013-05-24 18:30 ` Drew [this message]
2013-05-24 21:58 ` Jim Santos
2013-05-25 19:44 ` Roy Sigurd Karlsbakk
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=CACJz6Qt-zULSobEDqo306gow4wAvx1LQdXBf3K5XHm36rDKE4Q@mail.gmail.com \
--to=drew.kay@gmail.com \
--cc=iluvgadgets@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).