On 5/13/21 4:40 PM, Lester Petrie wrote:
On 5/13/2021 4:17 PM, George N. White III wrote:
On Thu, 13 May 2021 at 16:56, Lester Petrie <lmpetrie@xxxxxxxxxxxxx
<mailto:lmpetrie@xxxxxxxxxxxxx>> wrote:
Hi all,
The subject says what I want to do. The why is as follows. About a
year
and a half ago I bought a new machine with a 2 Tb SSD and a 2 Tb
hard
drive. It came with Windows on it, which I wanted to keep, so I
found a
Windows program that let me shrink the Windows partitions on both
the
SSD and the HD to 1 Tb, and tried to install Fedora on the free
1Tb SSD.
But at the time the installer would not recognize the SSD, so I
ended up
installing on the HD, with a new EFI partition there. I was then
able to
select between Windows and Fedora from the boot menu. About the
time F33
came out, I learned I needed to disable Raid in the Bios, and then I
installed F33 on the free 1Tb SSD. This added Fedora to the
Windows EFI
partition, and replaced Fedora in the boot menu with the new
version, so
I was still able to select either Windows or Fedora 33 when I
booted.
Did you also disable Windows "fastboot"?
I am able to get to the boot menu the same as always, so I am pretty
sure Windows "fastboot" is not the problem.
And grub conveniently found my old HD installation and included
it in
the grub menu. Then something happened about a week ago, and the
Fedora
entry in the boot menu reverted to the HD entry (which is F31). I
can do
a rescue boot and chroot to F33, and then run efibootmgr, but I
can't
figure out how to create a legitimate, bootable entry for F33. The
files
all seem to still be in the right place, and I can create an
entry in
the menu, but it is not a valid entry. Any help will be greatly
appreciated.
How do define "not valid"? Do you get an error, do you end up in
Windows,
or ...? Did the problem occur after using Windows? Have you checked
the
BIOS settings?
Not valid means that if I select the entry I made from the boot menu,
I get an error message saying it is not valid. I can still select
Windows, or the HD version of Fedora successfully.
Hi Lester
There is a utility Supergrub2 2.04s1 that boots from a USB that finds
all the bootables on the system for a workaround.
From the f31 you can look at the /boot of the f33 and see if the
grub.cfg and grubenv entries in /boot/efi/EFI/fedora have the correct
uuid for the f33. Also the entries in /boot/loader/entries for the kernels
_______________________________________________
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
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
