unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jesse Gibbons <jgibbons2357@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 44717@debbugs.gnu.org
Subject: bug#44717: ISO grub config points to nonexistent drive UUID.
Date: Wed, 18 Nov 2020 08:22:44 -0700	[thread overview]
Message-ID: <06cf1bea-3e7b-5601-9614-e7bb644ce65f@gmail.com> (raw)
In-Reply-To: <87wnyjlzwk.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2818 bytes --]


On 11/18/20 3:31 AM, Ludovic Courtès wrote:
> Hi,
>
> Jesse Gibbons <jgibbons2357@gmail.com> skribis:
>
>> I generated the iso with the command
>> `guix system disk-image -t iso9660
>> --root=installer.BaNl/install-x86.iso --system=i686-linux
>> gnu/system/install.scm`
>> and flash the sd card with the command
>> `sudo bash -c "echo success" && time sudo dd if=install-x86.iso of=/dev/sdc`
>>
>> When I inspect the GRUB menu, I see the option
>> --root=31393730-3031-3031-3139-333534353239
>> but in the gnome disk utility on my main laptop I do not see the above
>> UUID in any of the partitions on the SD card I'm using, still with the
>> freshly built install iso flashed onto it. Instead I see the UUIDs
>> 1970-01-01-19-49-46-83 for partition 1 and 3495-32E0 for partition 2.
> The option in the GRUB menu uses the “DCE” format for the UUID, but if
> you convert it to an ISO-9660 UUID, it looks almost the same:
>
> --8<---------------cut here---------------start------------->8---
> scheme@(guile-user)> ,use(gnu system uuid)
> scheme@(guile-user)> (string->uuid "31393730-3031-3031-3139-333534353239")
> $60 = #vu8(49 57 55 48 48 49 48 49 49 57 51 53 52 53 50 57)
> scheme@(guile-user)> (bytevector->uuid $60 'iso9660)
> $61 = #<<uuid> type: iso9660 bv: #vu8(49 57 55 48 48 49 48 49 49 57 51 53 52 53 50 57)>
> scheme@(guile-user)> (uuid->string $61)
> $62 = "1970-01-01-19-35-45-29"
> --8<---------------cut here---------------end--------------->8---
>
> The ISO UUID is computed in a deterministic fashion.  Are you sure
> you’re looking at the same ISO?
>
> For example, if you pick
> <https://alpha.gnu.org/gnu/guix/guix-system-install-1.2.0rc1.x86_64-linux.iso.xz>,
> it boots just fine.  In the GRUB menu entry (type ‘e’ in the menu), you
> can see both the DCE UUID for ‘--root’ and the ISO UUID for ‘search.fs’,
> which are actually the same.
>
> HTH!
>
> Ludo’.

When I posted this initial bug report, I reported what happened when I 
flashed the built iso to an SD card and tried it on another laptop. Just 
to be sure, I remade the image (in the same directory as my guix checkout)

guix system disk-image -t iso9660 --root=$(mktemp -p /tmp -d 
install.XXX)/install-x86.iso --system=i686-linux gnu/system/install.scm

and I mounted the ISO itself and took a look at it. The grub.conf 
specifies both UUIDs as you described.

When I try it on a VM, it opens a repl with a completely different error 
which I'm too lazy to type out by hand. See attached screenshot.

When I download the iso you linked and run it on a vm, it works just 
fine. Just to see if it has anything to do with the architecture, I also 
decided to try a vm with the i686-linux counterpart. It also works fine.

I do not have access to any of those old laptops right now, so I can't 
experiment further.

[-- Attachment #2: Screenshot_guix-1.1_2020-11-18_07:57:16.png --]
[-- Type: image/png, Size: 10338 bytes --]

  reply	other threads:[~2020-11-18 15:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18  4:56 bug#44717: ISO grub config points to nonexistent drive UUID Jesse Gibbons
2020-11-18 10:31 ` Ludovic Courtès
2020-11-18 15:22   ` Jesse Gibbons [this message]
2020-11-18 17:17     ` Ludovic Courtès
2020-11-18 18:03       ` Jesse Gibbons
2020-11-18 21:31       ` Jesse Gibbons
2021-05-15  3:33         ` Maxim Cournoyer
2020-11-18 18:09 ` Bengt Richter
2020-11-18 19:17   ` Jesse Gibbons
2020-11-18 20:55     ` Bengt Richter

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=06cf1bea-3e7b-5601-9614-e7bb644ce65f@gmail.com \
    --to=jgibbons2357@gmail.com \
    --cc=44717@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).