On Sun, 2 Aug 2020 at 18:13, Robert G (Doc) Savage via CentOS
<centos@centos.org> wrote:
>
> -----Original Message-----
> From: Stephen John Smoogen <smo...@gmail.com>
> Reply-To: CentOS mailing list <centos@centos.org>
> To: CentOS mailing list <centos@centos.org>
> Subject: Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
> Date: Sun, 2 Aug 2020 10:57:49 -0400
>
> On Sun, 2 Aug 2020 at 10:20, david <da...@daku.org> wrote:
> > > <snip>
>
> I agree  it is a lot of shorthand because of expectations. In the endwe (the 
> list) don't know what you have on your system or what state itis in. In order 
> to get that information to help we would need you totry the following:
> 1. boot using a working USB/cdrom/netboot path and installer2. choose the 
> rescue mode3. have the rescue mount the disks as local and chroot into 
> thesystem. << if possible have the system also bring up networking >>
> Thenyum list kernel shim grub2 mokutil
> John,
>
>
> I have a CentOS 8.2.2004 system running on an EPYC-equipped SuperMicro 
> motherboard. I assume it uses EFI boot. I have it set to auto-update with 
> cron.daily, so it almost certainly has the buggy package(s) installed. I'm 
> loath to try rebooting it just to see.
>

The buggy package is the shim package. If you don't have it on your
system then you should not be affected.

>
> When I run "yum list kernel shim grub2 mokutil" all I get back are the three 
> installed kernel packages. Reverting to the old fashioned "rpm -qa | grep 
> kernel-4 ; rpm -qa | grep shim ; rpm -qa | grep grub2 ; rpm -qa | grep 
> mokutil" I get:
>
>
> kernel-4.18.0-147.8.1.el8_1.x86_64
> kernel-4.18.0-193.14.2.el8_2.x86_64
> kernel-4.18.0-193.6.3.el8_2.x86_64
> grub2-tools-2.02-87.el8_2.x86_64
> grub2-pc-2.02-87.el8_2.x86_64
> grub2-pc-modules-2.02-87.el8_2.noarch
> grub2-common-2.02-87.el8_2.noarch
> grub2-tools-efi-2.02-87.el8_2.x86_64
> grub2-tools-minimal-2.02-87.el8_2.x86_64
> grub2-tools-extra-2.02-87.el8_2.x86_64
>
>
> I apparently do not have either shim or mokutil packages installed. I'm not 
> sure what this means. Am I not using EFI boot?
>
>

use the df command. If you are using EFI then it will report /boot/EFI
as a partition. If it doesn't then I would assume you are using BIOS.


> I have local copies of the earlier v2.02-81 grub2 packages. Would it be 
> worthwhile to replace my v2.02-87 grub2 packages, then add this line to 
> /etc/dnf/dnf.conf:
>
>
> exclude=grub shim mokutil
>
>
> as previously advised?
>

Since the problem is the shim package and you don't seem to have it..
I would say exclusion is not needed.

>
> Or should I just leave well enough alone and wait for tonight's auto-update 
> to fix things?
>
>
> --Doc Savage
>     Fairview Heights, IL
>
>
>
>
>
>
>
>
> _______________________________________________
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos



-- 
Stephen J Smoogen.
_______________________________________________
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Reply via email to