On 7 Mar 2021 at 9:40, Ed Greshko wrote:
From: Ed Greshko <ed.greshko(a)greshko.com>
To: users(a)lists.fedoraproject.org
Subject: Re: grubby fatal error can't find theme??
Date sent: Sun, 7 Mar 2021 09:40:30 +0800
Send reply to: Community support for Fedora
users <users(a)lists.fedoraproject.org>
On 07/03/2021 09:12, Michael D. Setzer II via users wrote:
>
> That seems to be the only error. The kernel seems to install just fine, just that
grubby fails to update it to the default boot kernel.
>
> Looking at dnf.rpm.log on one machine find these 12 lines with grubby on them. lines
before and after seem to be other things that install just fine.
>
> 2020-09-03T05:37:15Z SUBDEBUG Upgrade: grubby-deprecated-8.40-40.fc32.x86_64
> 2020-09-03T06:43:02Z SUBDEBUG Upgraded: grubby-deprecated-8.40-36.fc31.x86_64
> 2020-09-03T06:43:04Z SUBDEBUG Upgraded: grubby-8.40-36.fc31.x86_64
> 2020-09-03T07:43:20Z INFO grubby fatal error: unable to find a suitable template
> 2020-10-01T05:00:34Z INFO grubby fatal error: unable to find a suitable template
> 2020-11-16T04:46:35Z INFO grubby fatal error: unable to find a suitable template
> 2020-12-02T00:59:19+1000 INFO grubby fatal error: unable to find a suitable
template
> 2021-01-16T21:30:45+1000 INFO grubby fatal error: unable to find a suitable
template
> 2021-01-22T18:07:25+1000 INFO grubby fatal error: unable to find a suitable
template
> 2021-02-02T08:37:10+1000 INFO grubby fatal error: unable to find a suitable
template
> 2021-02-20T14:56:16+1000 INFO grubby fatal error: unable to find a suitable
template
> 2021-03-07T08:40:55+1000 INFO grubby fatal error: unable to find a suitable
template
>
> Seems to be only file with info. Is there some other file that might contain more
info??
Are you saying you're still using Fedora 31?
No, machine was upgraded to Fedora 32 some time ago.
Those are just the lines in the file that go back farther
than the upgrade to Fedora 32?
If the grubby has a fatal error, but grub2-mkconfig works,
why doesn't the process automatically call mkconfig. Just
had noticed on the 5 fedora machines I have at home,
sometimes a kernel upgrade results in the new kernel
being active on next boot, but other times not.
Have gotten in the habit of just running mkconfig after a
dnf upgrade that shows a new kernel. But if one doesn't
watch the reboot, or check which kernel is actually
loaded, they could be running an older kernel than what
they think?
I'd use "dnf history" to find if a transaction occurred on 9/3/2020.
Taking note that it seems
what is in the log is a timestamp of GMT+0000 (Z).
Also, check the output of...
rpm -q grubby-deprecated grubby
--
People who believe they don't make mistakes have already made one.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor
(Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+