On Mon, 1 Jun 2020 11:20:31 +0200
"Patrick Dupre" <pdupre(a)gmx.com> wrote:
If I run
grubby --info=ALL
I get only the boot system available on the mounted system
What bothers me also is the date of /boot/efi/EFI/fedora/grub.cfg
-rwx------. 1 root root 15119 Jun 9 2019
I can regenerate it and I have
set default_kernelopts="root=/dev/mapper/VolSys_1-root ro
rd.lvm.lv=VolSys_1/root " I guess from
cat /etc/default/grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys_1/root"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
But the rest of /boot/efi/EFI/fedora/grub.cfg is not coherent:
There is no menuentry matching the kernels which are on this disk.
There are mixing which old kernels (fc28) from other disks.
Now,
I boot on another disk (fc30)
There is no
/boot/efi/EFI/fedora/grub.cfg
It means that after update of the kernel,
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
has not been run.
Thus, I am confuse.
In case of multidisks, what does what?
I do not fully understand this, but Chris Murphy explained that there
is only the *one* /boot/efi/ per system and only *one* entry for fedora
in /boot/efi/EFI/. As I understand it, this is because of the efi
standard. So, if booting more than one version of fedora using efi,
the grub.cfg in /boot/efi/EFI/fedora has to be changed to point to the
correct /boot/loader/entries for that fedora. You could have several
versions of the grub.cfg and just swap them to boot other versions.
Messy. Apparently, this can be solved by using systemd bootctl, an
alternative to grub2, but fedora does not use that and I haven't
investigated further.