Thanks,
Actually, I am lost.
I am upgrading one of the systems on a multi-disks system.
1) I realized that one system is not efi, while the other ones are.
2) After I upgraded this system. I can boot it, but it is weird.
a) There was no update of the grub menu (I boot fc32, while the invitation
is still fc30)
b) grub2-mkconfig has not been run
c) grub2-mkconfig (manually) did not recognized by the booted system except through
set root='hd2,msdos3', but no menuentry for this system.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
===========================================================================
> Sent: Monday, June 01, 2020 at 2:55 PM
> From: "stan via users" <users(a)lists.fedoraproject.org>
> To: users(a)lists.fedoraproject.org
> Cc: "stan" <upaitag(a)zoho.com>
> Subject: Re: boot/grub
>
> 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.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>