Unable to boot on iMac, likely because of UUIDs

  • Open
  • quality assurance status badge
Details
3 participants
  • Danny Milosavljevic
  • Francisco Gómez
  • pelzflorian (Florian Pelz)
Owner
unassigned
Submitted by
Francisco Gómez
Severity
normal
F
F
Francisco Gómez wrote on 22 May 2019 13:10
(address . bug-guix@gnu.org)
1558523401.20880.0@kydara.com
When I have inserted a device recorded with a GuixSD image in my Late
2009 iMac (EFI, not UEFI) during boot, the computer gets stuck in a
loop and doesn't respond. I believe this is due to a lack of, or
duplication, of UUIDs (not to be confused with PARTUUIDs) on some
partitions, as manually assigning them allows my computer to properly
detect the attached devices and boot from the GuixSD one (although not
successfully).

> udisksctl loop-setup -rf guix-system-install-1.0.1.x86_64-linux.iso
Mapped file guix-system-install-1.0.1.x86_64-linux.iso as /dev/loop0.

> sudo blkid -o list | grep ^/dev/loop0 | cut -d" " -f1 | sort
/dev/loop0
/dev/loop0p1
/dev/loop0p2
/dev/loop0p3
/dev/loop0p4

> sudo blkid -s UUID | grep ^/dev/loop0
/dev/loop0: UUID="1970-01-01-19-49-46-83"
/dev/loop0p2: UUID="C920-B8AE"
P
P
pelzflorian (Florian Pelz) wrote on 22 May 2019 16:09
(name . Francisco Gómez)(address . espectalll@kydara.com)(address . 35856@debbugs.gnu.org)
20190522140908.oy47v5u5ww3kgkrc@pelzflorian.localdomain
On Wed, May 22, 2019 at 11:10:00AM +0000, Francisco G�mez wrote:
Toggle quote (27 lines)
> When I have inserted a device recorded with a GuixSD image in my Late 2009
> iMac (EFI, not UEFI) during boot, the computer gets stuck in a loop and
> doesn't respond. I believe this is due to a lack of, or duplication, of
> UUIDs (not to be confused with PARTUUIDs) on some partitions, as manually
> assigning them allows my computer to properly detect the attached devices
> and boot from the GuixSD one (although not successfully).
>
> > udisksctl loop-setup -rf guix-system-install-1.0.1.x86_64-linux.iso
> Mapped file guix-system-install-1.0.1.x86_64-linux.iso as /dev/loop0.
>
> > sudo blkid -o list | grep ^/dev/loop0 | cut -d" " -f1 | sort
> /dev/loop0
> /dev/loop0p1
> /dev/loop0p2
> /dev/loop0p3
> /dev/loop0p4
>
> > sudo blkid -s UUID | grep ^/dev/loop0
> /dev/loop0: UUID="1970-01-01-19-49-46-83"
> /dev/loop0p2: UUID="C920-B8AE"
>
>
>
>
>
>

Unfortunately Danny pushed his patch after the 1.0.1 release got
branched off.

Can you try an ISO built from current Guix git master?

Regards,
Florian
P
P
pelzflorian (Florian Pelz) wrote on 22 May 2019 16:35
(name . Francisco Gómez)(address . espectalll@kydara.com)(address . 35856@debbugs.gnu.org)
20190522143513.pw3tas4ewynlump3@pelzflorian.localdomain
On Wed, May 22, 2019 at 04:09:09PM +0200, pelzflorian (Florian Pelz) wrote:
Toggle quote (3 lines)
> Can you try an ISO built from current Guix git master?
>

If this ISO works, then this still-ongoing GRUB mailing list thread
described your issue as well:


Regards,
Florian
D
D
Danny Milosavljevic wrote on 22 May 2019 19:23
(name . Francisco Gómez)(address . espectalll@kydara.com)
20190522192308.578ebf11@scratchpost.org
Toggle quote (2 lines)
> Can you try an ISO built from current Guix git master?

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlzlhXwACgkQ5xo1VCww
uqVEvAgAh8GvEA/WsiZoOcmiba3XI4hxhMOjRfFXe4bt9r4RArMDsfHlb8pjdfIY
pdANeo7ajlM0IuJy5HKkrVqBmH7u8B1vF3qRHGBB//iINi9lpO+EUW4bhrneGhox
Icmzz++CZyFK1Sd0s5bvcVMv1nuoTcav+ogyqfkkkd2yv/NGtahU0+mrp3HnDuT6
d8E3tMWf3/e2zSM6kv+GBce1JVgKMpzU/w8E+KtWFzJC26DaBTuCp1sBQv6tzSar
fjK2xWWOKyJEdiu2lfnD9ws3jy+2Zzy0nGQNKwwAp2KQXucLGSNWVdApkCl6y9+V
wLRCYc4ZLG/tCcmKcaW5VoDwgIysjA==
=le/A
-----END PGP SIGNATURE-----


P
P
pelzflorian (Florian Pelz) wrote on 23 May 2019 22:18
(name . Francisco Gómez)(address . espectalll@kydara.com)(address . 35856@debbugs.gnu.org)
20190523201827.p5l3kik3nvlj2ds5@pelzflorian.localdomain
On Thu, May 23, 2019 at 03:12:44PM +0200, Francisco G�mez wrote:
Toggle quote (3 lines)
> Built an image after doing `guix pull`, it works! Thanks!
>

Thank you for reporting back. Please respond to 35856@debbugs.gnu.org
as well next time. I will mention your observations on UUIDs on the
grub-devel mailing list.

Regards,
Florian
P
P
pelzflorian (Florian Pelz) wrote on 23 May 2019 22:24
(name . Francisco Gómez)(address . espectalll@kydara.com)(address . 35856@debbugs.gnu.org)
20190523202411.xmq67guaxfct2wrm@pelzflorian.localdomain
On Thu, May 23, 2019 at 10:18:27PM +0200, pelzflorian (Florian Pelz) wrote:
Toggle quote (4 lines)
> I will mention your observations on UUIDs on the
> grub-devel mailing list.
>

No, I will not report there. They know enough.
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 35856@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 35856
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch