From: Wols Lists <antlists@youngman.org.uk>
To: linux-raid@vger.kernel.org
Subject: Grub2/raid quickie ...
Date: Thu, 30 Oct 2014 00:08:43 +0000 [thread overview]
Message-ID: <5451818B.6010809@youngman.org.uk> (raw)
After my last shenanigans, I've now got my main system booting
successfully from a raid / partition. HOWEVER.
I'm somewhat puzzled by grub.cfg, and this is in part behind why my dev
system won't boot raid properly, I think. Grub uses two different UUIDs!?!?
One of them, (mduuid/...) is dead easy to find, "mdadm -D" gives the md
uuid of the array. But the other one, the "root=UUID=...", I'm damned if
I can find that id anywhere! Does anyone know a command, that will tell
me what that id is, so I can fix grub.cfg on my development system?
(As an aside, how do I retrospectively force a name onto an array so
that I can guarantee it will be called /dev/md100, or /dev/mdhome, or
whatever? I daren't use the /dev/mdxxx name at the moment, because they
change and the result is a system that fails to boot, or is unusable, or
some other malarkey. Dead easy for me to fix, but my wife will go spare!)
Cheers,
Wol
next reply other threads:[~2014-10-30 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 0:08 Wols Lists [this message]
2014-10-30 1:03 ` Grub2/raid quickie NeilBrown
2014-10-30 1:21 ` Chris Murphy
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=5451818B.6010809@youngman.org.uk \
--to=antlists@youngman.org.uk \
--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