Hi Chris, On Fri, Jul 05, 2019 at 02:53:08PM -0600, Chris Murphy wrote: > > Post the contents of the following files somewhere (I'm not sure > they'll attach to the list but you can give it a shot if you want) > > /boot/grub2/grub.cfg This evening I went through this carefully, and spotted a few inconsistent partition ids. My / is on /dev/sdc2 (no separate /boot partition), but some of the entries had 'hd1,msdos2' while others correctly had 'hd2,msdos2'. Fixing them led to the BLS config files getting picked up correctly. I think I know how this happened. Sometime back I added a new disk. That must have messed up the ordering. > And also what was the original Fedora installation version? I don't recall exactly, I assembled this machine in March 2018. So my guess is F28/27. > On x86 > BIOS, GRUB is installed by 'grub2-install' only upon installation. > Even when the package is updated and upgraded through major versions, > the actual installed bootloader becomes stale over time because > there's no automatic 'grub2-install' run again. (I'm of the opinion > that Fedora needs to keep it up to date, at least with major upgrades. > Too many problems arise over time as it becomes stale. I agree. > Meanwhile on > UEFI, the bootloader is being updated, even within minor version > updates, whenever the shim or grub packages get updated.) I have never quite understood how UEFI worked. Initially I stayed away from it because of secure boot issues. Do you think I should put in the effort to move to UEFI? If so, would you be able to point me where to start? Thanks a lot for your helpful comments, -- Suvayu Open source is the future. It sets us free. _______________________________________________ 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
