On Mon, 2019-05-06 at 17:00 -0600, Chris Murphy wrote:
I see two minor anomalies:
/boot is XFS, should not be a problem.
NVRAM contains dup entries, Boot0001 and Boot0008.
Boot0001 is pointing to the new naming for shim, and it's also the
default and current boot. Therefore, Boot0008 can be deleted. It's
not
causing the problem, so you can also just leave it alone.
I had a hell of a time getting Windows 10 installed and then Fedora
working. Originally I was doing the Fedora install first, but
eventually I realized I was setting up the dual boot incorrectly. I
wiped the drives and started again with Windows 10 first.
I have no idea how the dupe entries got there except maybe I didn't
wipe the drives correctly.
What's the URL you get for this command?
$ sudo cat /boot/efi/EFI/fedora/grub.cfg | fpaste
Empty. That is, I get back nothing.
And also this:
$ mount | grep vfat
https://paste.ofcode.org/JbTd7BHQ9aNAwtprsLBEee
A faster way to get where I'm going, but will erase any evidence
of
why you're stuck, is to just create a new grub.cfg and then reinstall
the kernel you want.
$ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
I do want to just fix it, but I want to know what's going on more. :)
Also, question, have you recently run 'grub2-install' on
this
computer? Don't do it. I'm just wondering if you have done it, it
could be related.
No, I didn't do that. All I've done is the release upgrade from F28 to
F29 (no errors, no left over rpms) and then my first F29 update, which
caused the grub problem.
--
Ranbir