Re: grub-mkconfig grub 1:2.02.beta2-6

[Andrei Borzenkov]

On Wed, Jun 15, 2016 at 12:05 AM, dragonchild
<address@hidden> wrote:
> version: grub 1:2.02.beta2-6
> Distro: Arch
> setup: default
>
> system: x86_64-efi
> system layout:
> hd0,gpt1  EFI Fat32 mounted /boot   (NOT /boot/efi)
> grub directory: /boot/grub          (on the EFI partition)
>
> hd0,gpt5  /   ext4 Arch distro
>               /linuz-warp, /initramfs-warp in the root directory (warp
>               is just an id for this setup
>
> hd0,gpt7  /    ext4 Arch distro
>              /linuz-arch, /initramfs-arch in the root directory (arch
>               is just an id for this setup
>
> Problem generation:
>         with (hd0,gpt7) mounted as root:
>         run: grub-mkconfig -o /boot/grub.cfg
>
> produces: (edited)
>  menuentry 'Arch Linux' --class arch .... ;this is hd0,gpt7, /dev/sda7
>         linux   /vmlinuz-arch
>                 root=UUID=bb79802f-749e-4fa2-8135-80a7ef9f98dc
>
>
>  menuentry 'Arch (on /dev/sda5)' --class .... ;discovered by prober
>         linux /vmlinuz-warp root=/dev/sda5
>
> Problem: the second entry is using /dev/sdX notation instead of UUID
>

GRUB puts there exact string it gets from os-prober. What bootloader
is used by OS on sda5? Please attach its configuration (menu.lst,
grub.cfg or whatever) and grub.cfg from sda7..

> This fails when grub-mkconfig is run directly from a usb stick or
> chrooted into (hd7,gpt)/. The /dev/sdX may not be set
> correctly which will render the partition unbootable.
>
> happy hunting,
> jan
>
> _______________________________________________
> Bug-grub mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/bug-grub