On Sat, 23 Nov 2019 17:03:19 -0500
sean darcy <seandarcy2@xxxxxxxxx> wrote:
> On 11/23/19 10:36 AM, stan via users wrote:
> > On Fri, 22 Nov 2019 17:15:58 -0500
> > sean darcy <seandarcy2@xxxxxxxxx> wrote:
> >
> >> So I chroot'd into the old installation. BIOs boot, not EFI. No
> >> entries at all in grub.cfg.
> >
> > Are you trying to convert from bios/mbr boot to uefi boot on the
> > upgrade? I think if you already have a bios/mbr boot system, it
> > would be better to upgrade with the same method of boot, and once
> > the upgrade is complete pursue the conversion. I vaguely remember
> > that there was a conversion to snippets around F28 to F30, and that
> > changed the boot process as well.
> >
> >> ran grub2-mkconfig. No entries again in output. It can't find the
> >> f29 and f30 in /boot.
> >
> > If it is bios/mbr boot, it should be using the grub.cfg in
> > /boot/grub2/grub.cfg.
> > Is there anything in that file?
> >
> > Can you post the output of
> > ls /boot
> > and
> > ls /boot/grub2/
> > and
> > ls /boot/efi/EFI/fedora
> >
> >> Tried grub2-install /dev/sda2, but that died because no EFI grub
> >> files.
> >
> > Are you using a gpt formatted disk? UEFI needs two extra
> > partitions, but no record in the mbr.
> >
> >> The a bugzilla on this which was closed NOTABUG. The EFI files
> >> are not installed om purpose to keep people from using
> >> grub2-install. You can dnf install the efi modules. Which is a
> >> great suggestion for a broken upgrade, where dnf is not available.
> >>
> >
> > I am not sure, but I don't think it is possible to update a system
> > using an mbr boot to a uefi boot. I think you will have to install
> > uefi from an installer booted in uefi. i.e. fresh install Maybe
> > someone else can give better information.
> >
> >> There's a grub.cfg.rpmsave which seems to have been generated by
> >> anaconda. I'm going to try to use that to boot. It only has the f29
> >> kernel. My plan is to reinstall the f30 kernel. Maybe anaconda will
> >> actually work correctly.
> >
> > I confess that I'm confused, and we're in areas that I have only
> > passing acquaintance with. For some reason, you are a corner case,
> > and I can't understand why from the information I have.
>
> # ls /boot
> config-5.2.18-100.fc29.x86_64
> config-5.2.18-200.fc30.x86_64
> config-5.3.11-200.fc30.x86_64
> efi
> extlinux
> grub
> grub2
> initramfs-0-rescue-ef65454e1a334e1e93f8ff6b0000000f.img
> initramfs-5.2.18-100.fc29.x86_64.img
> initramfs-5.2.18-200.fc30.x86_64.img
> initramfs-5.3.11-200.fc30.x86_64.img
> initrd-plymouth.img
> loader
> lost+found
> System.map-5.2.18-100.fc29.x86_64
> System.map-5.2.18-200.fc30.x86_64
> System.map-5.3.11-200.fc30.x86_64
> vmlinuz-0-rescue-ef65454e1a334e1e93f8ff6b0000000f
> vmlinuz-5.2.18-100.fc29.x86_64
> vmlinuz-5.2.18-200.fc30.x86_64
> vmlinuz-5.3.11-200.fc30.x86_64
>
> ls /boot/grub2
> device.map fonts grub.cfg-bad -> the cfg left by anaconda
> grubenv themes
> device.map.anacbak grub.cfg -> this is a copy of rpmsave
> grub.cfg.rpmsave i386-pc locale
>
> # ls /boot/efi/EFI/fedora/
> #
>
> grub.cfg has the f29 entries |
>
> grep menuentry grub.cfg
> menuentry 'Fedora (5.2.18-100.fc29.x86_64) 29 (Twenty Nine)'
> --class fedora --class gnu-linux --class gnu --class os
> --unrestricted $menuentry_id_option
> 'gnulinux-4.19.5-200.fc28.x86_64-advanced-89afb6ff-4fb2-4602-94b5-99dbf022b100'
> {
> menuentry 'Fedora (5.2.7-100.fc29.x86_64) 29 (Twenty Nine)'
> --class fedora --class gnu-linux --class gnu --class os
> --unrestricted $menuentry_id_option
> 'gnulinux-4.19.5-200.fc28.x86_64-advanced-89afb6ff-4fb2-4602-94b5-99dbf022b100'
> {
Are these pointing to the right partition on the disk? Is the kernel
boot line using the right uuid and boot options?
> but the grub.cfg left by anaconda has no menuentry's:
>
> grep menuentry grub.cfg-bad
> if [ x"${feature_menuentry_id}" = xy ]; then
> menuentry_id_option="--id"
> menuentry_id_option=""
> export menuentry_id_option
>
> The problem is that installing or reinstalling an f30 kernel does not
> add the kernel to grub.cfg.
>
> FYI:
>
> cat /etc/default/grub
> GRUB_TIMEOUT=5
> GRUB_DISTRIBUTOR="Fedora"
> GRUB_DEFAULT=saved
> GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0
> SYSFONT=latarcyrheb-sun16 KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8
> rd.driver.blacklist=vboxdrv pti=off spectre_v2=off l1tf=off
> nospec_store_bypass_disable no_stf_barrier"
> #GRUB_THEME="/boot/grub2/themes/system/theme.txt"
> GRUB_GFXPAYLOAD_LINUX=keep GRUB_GFXPAYLOAD_LINUX=text
> GRUB_ENABLE_BLSCFG=true
>
> How do I get grub.cfg updated ?
You can edit the grub.cfg in /boot/grub2, copy and paste a boot stanza
from F29, and change it to use the F30 kernel. The F30 kernel is
installed, so it should boot once it is in the menu. Even after
looking at the info you provided, I don't understand why this didn't
work, though.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
