From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29312@debbugs.gnu.org
Subject: bug#29312: GRUB with multiple partitions with identical bzImage
Date: Thu, 16 Nov 2017 08:13:05 -0800 [thread overview]
Message-ID: <87k1yq2odq.fsf@aikidev.net> (raw)
In-Reply-To: <87a7zmfg8x.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2292 bytes --]
On 2017-11-16, Ludovic Courtès wrote:
> Vagrant Cascadian <vagrant@debian.org> skribis:
> Indeed. You can force GuixSD to use a file system label or a UUID by
> declaring your file system with a label/UUID. So you would write:
>
> (file-system
> ;; …
> (mount-point "/")
> (title 'uuid)
> (device (uuid "f549617a-07b0-430a-9723-36c43b98c748")))
Yes, this fixed it for me!
> or:
>
> (file-system
> ;; …
> (mount-point "/")
> (title 'label)
> (device "my-root"))
>
> When you do that, the generated grub.cfg searches the file system by
> label/UUID, which should be more reliable as you write.
>
> Would that work for you?
Using UUID worked; didn't test using a label, but I imagine it would
also resolve the issue.
>> A quick workaround might be to also add a search line for the initrd
>> after loading the kernel:
...
> The assumption is that there’s only one /gnu/store that matters and that
> it contains both the kernel and the initrd. So I think the real
> solution is for the first ‘search’ command to be appropriate.
Agreed.
For the record, spelling it out, apparently the issue wasn't searching
in each menu entry, but:
# Set 'root' to the partition that contains /gnu/store.
search --file --set /gnu/store/0lwyzz8ayixwvdm1b3xhh26mlh0jz36b-grub-2.02/share/grub/unicode.pf2
Where it set the initial root.
After updating to mount by UUID, the corresponding search line became:
search --fs-uuid --set 1234ab-cdef-...1234ab
So it then only loaded files from the appropriate filesystem.
Since this is an issue caused by configuration, perhaps the
documentation could clarify the importance of using UUID or filesystem
labels rather than raw devices:
https://www.gnu.org/software/guix/manual/html_node/Proceeding-with-the-Installation.html#Proceeding-with-the-Installation
I guess all of the install examples use labels:
http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/system/examples/
And I'm not sure how many people have multiple GuixSD installs on their
systems, so perhaps it's just me putting myself into a corner case. :)
> Thanks for your report!
Thanks for the prompt response and solution!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-11-16 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 23:36 bug#29312: GRUB with multiple partitions with identical bzImage Vagrant Cascadian
2017-11-16 14:30 ` Ludovic Courtès
2017-11-16 16:13 ` Vagrant Cascadian [this message]
2017-11-16 21:50 ` Ludovic Courtès
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=87k1yq2odq.fsf@aikidev.net \
--to=vagrant@debian.org \
--cc=29312@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.