William <willbilly@fedora.email> writes:
> Hello.
>
> I'm currently trying to add a menu entry on GRUB through the Guix
> system declaration to boot another GNU+Linux system but I don't have
> much clue how to do it with this setup.
>
> The other system currently has three partitions, one for "/boot",
> one for "/" and one for "/home", I tried defining a menu entry like
> this:
>
> ```
> (menu-entry
> (label "GNU/Linux")
> (device (uuid
> "d757ca6e-ae43-41b7-bc73-7e80cd270e05" 'ext4))
> (linux "/vmlinuz-linux")
> (linux-arguments
> '("root=UUID=da4c92d2-099f-4046-ab1d-1695860f33f0
> rw net.ifnames=0 quiet"))
> (initrd "/intel-ucode.img /amd-ucode.img
> /initramfs-linux.img"))
> ```
>
> As you can see, it contains two different UUIDs, this is intended, as
> one UUID is for the "/boot" partition, the other one is for the "/"
> partition, I copied these values from the grub.cfg menu entry generated
> by os-prober during the installation of this system, and they look the
> same on the menu entry defined by Guix.
This looks fine to me.
>
> However, this entry does not work, when I try to boot the system
> from the GRUB menu, it says it couldn't find the device by UUID
> "d757ca6e-ae43-41b7-bc73-7e80cd270e05", which is the "/boot" partition.
The error seems from "search --fs-uuid --set
d757ca6e-ae43-41b7-bc73-7e80cd270e05"
You can press 'c' in the GRUB to enter its command line, and then run
'ls -l' to see if it actually find a partition with the correct UUID.
Maybe the UUID reported by os-prober is wrong...
