From: "David C. Rankin" <drankinatty@suddenlinkmail.com>
To: mdraid <linux-raid@vger.kernel.org>
Subject: moving arrays from MBR part table install to GPT? Possible?
Date: Sun, 16 Aug 2015 01:31:10 -0500 [thread overview]
Message-ID: <55D02E2E.1080909@suddenlinkmail.com> (raw)
All,
I suffered a controller failure on my server housing a 2-disk/4-partition
raid1 mdraid array under Archlinux with MBR partition table. The original
motherboard was non-UEFI, of course everything now is. I am getting conflicting
information whether my existing arrays are usable with the new UEFI board. I
don't know if this is the best place to ask, but heck, there is a lot of
collective wisdom regarding mdadm here.
I am planning to set the BIOS on the new board to Legacy and attempt to use
my existing arrays by booting the Arch install media, assembling the arrays,
then chrooting and rebuilding initramfs to preserve the existing setup. Is there
any reason that can't work?. (I haven't dealt with the UEFI fun before)
If that will not work, I'm left with installing to new drives. If I do end up
with a full install, I'm left with the MBR or GPT partition table choice. I will
install to 2 new drives that I want to again be setup as raid1 arrays with
mdadmin. Does mdadmin/mdraid require a MBR partition type? Or, can I create a
GPT partition table and use mdadm to manage the array?
If GPT is fine, then is there anyway to migrate my existing array to a GPT
partition table in the new box without having to install to new drives with a
GPT table and then mount one of the existing drives to copy the data to the new
array?
If these questions are already answered in a link somewhere, I apologize, I
haven't found it. Thanks for any help/advise you can provide.
--
David C. Rankin, J.D.,P.E.
next reply other threads:[~2015-08-16 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 6:31 David C. Rankin [this message]
2015-08-16 12:27 ` moving arrays from MBR part table install to GPT? Possible? Wols Lists
2015-08-17 6:28 ` David C. Rankin
2015-08-17 14:32 ` Wols Lists
2015-08-17 15:50 ` Wilson, Jonathan
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=55D02E2E.1080909@suddenlinkmail.com \
--to=drankinatty@suddenlinkmail.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).