Re: Grub menu entry for a system on a second drive.
On Thu 24 Oct 2024 at 12:52:59 (-0700), peter@easthope.ca wrote:
> root@imager:~# grep PROBER /etc/default/grub
> GRUB_DISABLE_OS_PROBER=true
>
> Also,
>
> root@imager:~# cat /etc/grub.d/40*
> #!/bin/sh
> exec tail -n +3 $0
> # This file provides an easy way to add custom menu entries. Simply type the
> # menu entries you want to add after this comment. Be careful not to change
> # the 'exec tail' line above.
> #
> menuentry "Void linux"{
> insmod part_gpt
> insmod ext2
> set root=(hd1,gpt6) reboot=bios
> linux /boot/vmlinuz-6.6.56_2 root=UUID=e5c7eb47-8d4c-49da-9038-09c27e8e8
> 990 ro single
> echo 'Loading ramdisk.'
> initrd /boot/initramfs-6.6.56_2.img
> }
So you've got a stable/testing/unstable system on hd1?
> Then,
>
> root@imager:~# update-grub
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-5.10.0-24-amd64
> Found initrd image: /boot/initrd.img-5.10.0-24-amd64
And a 14-month old bullseye system on hd0, which is currently running?
> Warning: os-prober will not be executed to detect other bootable partitions.
> Systems on them will not be added to the GRUB boot configuration.
> Check GRUB_DISABLE_OS_PROBER documentation entry.
> done
>
> /boot/grub/grub.cfg has the menu entry.
>
> ### BEGIN /etc/grub.d/40_custom ###
> # This file provides an easy way to add custom menu entries. Simply type the
> # menu entries you want to add after this comment. Be careful not to change
> # the 'exec tail' line above.
> #
> menuentry "Void linux"{
> insmod part_gpt
> insmod ext2
> set root=(hd1,gpt6) reboot=bios
> linux /boot/vmlinuz-6.6.56_2 root=UUID=e5c7eb47-8d4c-49da-9038-09c27e8e8
> 990 ro single
> echo 'Loading ramdisk.'
> initrd /boot/initramfs-6.6.56_2.img
> }
> ### END /etc/grub.d/40_custom ###
>
> So far, good, but when booting the Void entry is absent.
> https://easthope.ca/GrubMenu.jpg
>
> Ideas?
The system has booted into a bookworm Grub (deb12u1). It would appear
that your MBR/UEFI has booted into a grub.cfg that isn't the one
created above, ie on the other disk. After all, that Grub menu looks
as if it was created on a system that (a) isn't bullseye, and (b) ran
os-prober to produce its bullseye lines 3 and 4.
Cheers,
David.
Reply to: