From: Ram Ramesh <rramesh2400@gmail.com>
To: Reindl Harald <h.reindl@thelounge.net>,
Wol <antlists@youngman.org.uk>,
Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Renaming md raid and moving md raid to a different machine.
Date: Mon, 20 Mar 2023 17:23:02 -0500 [thread overview]
Message-ID: <e85fed01-f50f-21da-d09f-fa40da35ef7a@gmail.com> (raw)
In-Reply-To: <86bd2ef7-64f8-70c9-96a2-47bd3915bea6@thelounge.net>
On 3/20/23 03:35, Reindl Harald wrote:
>
>
> Am 20.03.23 um 01:34 schrieb Ram Ramesh:
>> Yes the names must be in the metadata of the md because I populate
>> mdadm.conf after every change by actually using the output from mdadm
>> --detail -scan. Since that comes up with md0/md1/md2, I assume somehow
>> mdadm simply finds them again and again with exact same name.
>>
>> I do not ever get md127
>
> no - your mdadm.conf is in the initrd because how else should the rootfs
> could live on the array containing mdadm.conf
Agreed. After I moved the rootfs of the old system to new hardware (a
new machine with is two nvme raid1), I booted into it and it did show
that the rootfs is on md127. However, after making mdadm.conf entries
and update-initramfs, md name changed to /dev/md0. So, it must be what
you said.
Regards
Ramesh
prev parent reply other threads:[~2023-03-20 22:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f237651e-536a-e305-8c1c-475e4c14d906@gmail.com>
2023-03-19 18:58 ` Renaming md raid and moving md raid to a different machine Ram Ramesh
2023-03-19 19:29 ` Reindl Harald
2023-03-19 19:52 ` Ram Ramesh
2023-03-19 22:51 ` Wol
2023-03-19 23:29 ` Ram Ramesh
2023-03-20 0:01 ` Wol
2023-03-20 0:34 ` Ram Ramesh
2023-03-20 8:00 ` Wols Lists
2023-03-20 14:53 ` Ram Ramesh
2023-03-20 8:35 ` Reindl Harald
2023-03-20 22:23 ` Ram Ramesh [this message]
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=e85fed01-f50f-21da-d09f-fa40da35ef7a@gmail.com \
--to=rramesh2400@gmail.com \
--cc=antlists@youngman.org.uk \
--cc=h.reindl@thelounge.net \
--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).