On Sat, 4 Dec 2021 at 20:40, Adam Mercer <ramercer@gmail.com> wrote:
On Sat, Dec 4, 2021 at 7:12 PM Samuel Sieb <samuel@sieb.net> wrote:

> No OS should touch any files it doesn't own in the ESP.  Did it really
> remove the bootloader?  A more likely option is that it changed the BIOS
> boot order.  Can you bring up the boot menu?  Do you see the Fedora
> option there?

That was my initial thought, so I booted into UEFI and the Windows
Boot Manager had been made the default boot option, Fedora was still
listed so I selected that. The grub menu came up with all my kernels
listed but selecting one just resulted in an error about being unable
to find a file or something like that. Also the option in grub for
booting into Windows resulted in a similar error. Hence me trying to
reinstall the bootloader.

This system was originally installed on Fedora 32 or 33 and upgraded
so it may be time for a reinstall, I have backups so nothing will be
lost apart from time.


I have a system upgraded from Fedora 33 to 35 and dual booting
Windows 10.  Fedora 35 was OK for a few days, then I upgraded
to Windows 11 and the system seems to doing something like
Windows fastboot so I never see the grub menu.   I can see a
Fedora entry using the one-time boot option (F12 on my system),
selecting Fedora still goes to Windows.  I can boot a Live USB or
a USB drive with F35 installed. 

After booting the USB install, attempting to reinstall the grub packages
gave

/etc/default/grub: line 6: usb-storage.quirks=0x0bc2:0xab25:e: command not found

warning: %posttrans(grub2-common-1:2.06-8.fc35.noarch) scriptlet failed, exit status 127


On the internal drive, the "usb-storage.quirks" entry had been left outside

the quoted "rhgb quiet" entry in /etc/default/grub.conf. I'm not sure how or

when the usb-storage.quirks entry was added -- still need to find time to

research those values and look for them in backups. I removed the "rhgb

quiet" entry long ago, so it was added by the upgrade..


I've seen some notes that F35 configures the two UEFI grub.conf files
differently from F33.  I'm not sure which way F34 went, but it seems
that F33-->F35 may not be dealing with grub correctly.  :

--
George N. White III