CentOS - Aug 2020 - 8.2.2004 Latest yum update renders machine unbootable

><snip>


> >> Yes .. it should be on mirror.centos.org now .. you could change
the
> >> repo where your updates come from.?  OR .. wait for that mirror to
get
> >> updated.
> >
> >
> > I just did
> > yum clean all
> > yum update
> >
> > and 15-8 showed up.?  Maybe the 'clean all' 
> did it, or maybe just showed up.
> >
> > I applied the update (yum update), rebooted and...
> > no boot.?  Just a blank screen.
> >
> > Hardware is a Mac-Mini :-(
> >
> > This is not an essential machine, so I could re-install (from
> > netinstall) if you think it's worth the effort.
> >
> > Or what?
> >
> > David
>
>You just need to reinstall the kernel and it should work.
>
Sorry for being so ignorant, but I don't 
understand "just reinstall the kernel".  I don't 
know how to translate that into a specific yum or rpm command.

However, since this is a crash-and-burn system, 
I'm going back to a virgin install with 
netinstall of 7 2003.  I'll let you know what the results are.

David

On Sun, 2 Aug 2020 at 10:20, david <david at daku.org>
wrote:
>
>
> ><snip>
>
>
>
>
> > >> Yes .. it should be on mirror.centos.org now .. you could
change the
> > >> repo where your updates come from.?  OR .. wait for that
mirror to get
> > >> updated.
> > >
> > >
> > > I just did
> > > yum clean all
> > > yum update
> > >
> > > and 15-8 showed up.?  Maybe the 'clean all'
> > did it, or maybe just showed up.
> > >
> > > I applied the update (yum update), rebooted and...
> > > no boot.?  Just a blank screen.
> > >
> > > Hardware is a Mac-Mini :-(
> > >
> > > This is not an essential machine, so I could re-install (from
> > > netinstall) if you think it's worth the effort.
> > >
> > > Or what?
> > >
> > > David
> >
> >You just need to reinstall the kernel and it should work.
> >
>
> Sorry for being so ignorant, but I don't
> understand "just reinstall the kernel".  I don't
> know how to translate that into a specific yum or rpm command.
I agree  it is a lot of shorthand because of expectations. In the end
we (the list) don't know what you have on your system or what state it
is in. In order to get that information to help we would need you to
try the following:

1. boot using a working USB/cdrom/netboot path and installer
2. choose the rescue mode
3. have the rescue mount the disks as local and chroot into the
system. << if possible have the system also bring up networking >>

Then
yum list kernel shim grub2 mokutil

It would also help to know which kind of Mac Mini it is (year, model,
firmware versions). Apple changes the internal hardware of these
things and how they boot so if there it may be that a particular model
is more affected than others.


> However, since this is a crash-and-burn system,
> I'm going back to a virgin install with
> netinstall of 7 2003.  I'll let you know what the results are.
>
> David
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos


-- 
Stephen J Smoogen.

At 07:57 AM 8/2/2020, you wrote:
>On Sun, 2 Aug 2020 at 10:20, david <david at daku.org> wrote:
> >
> >
> > ><snip>
> >
> >
> >
> >
> > > >> Yes .. it should be on mirror.centos.org now .. you
could change the
> > > >> repo where your updates come from.??  OR 
> .. wait for that mirror to get
> > > >> updated.
> > > >
> > > >
> > > > I just did
> > > > yum clean all
> > > > yum update
> > > >
> > > > and 15-8 showed up.??  Maybe the 'clean all'
> > > did it, or maybe just showed up.
> > > >
> > > > I applied the update (yum update), rebooted and...
> > > > no boot.??  Just a blank screen.
> > > >
> > > > Hardware is a Mac-Mini :-(
> > > >
> > > > This is not an essential machine, so I could re-install
(from
> > > > netinstall) if you think it's worth the effort.
> > > >
> > > > Or what?
> > > >
> > > > David
> > >
> > >You just need to reinstall the kernel and it should work.
> > >
> >
> > Sorry for being so ignorant, but I don't
> > understand "just reinstall the kernel".  I don't
> > know how to translate that into a specific yum or rpm command.
>
>I agree  it is a lot of shorthand because of expectations. In the end
>we (the list) don't know what you have on your system or what state it
>is in. In order to get that information to help we would need you to
>try the following:
>
>1. boot using a working USB/cdrom/netboot path and installer
>2. choose the rescue mode
>3. have the rescue mount the disks as local and chroot into the
>system. << if possible have the system also bring up networking
>>
>
>Then
>yum list kernel shim grub2 mokutil
>
>It would also help to know which kind of Mac Mini it is (year, model,
>firmware versions). Apple changes the internal hardware of these
>things and how they boot so if there it may be that a particular model
>is more affected than others.

How does one obtain that information?  There's nothing written on the box.

David

> From: david
> Sent: Sunday, August 2, 2020 10:16 AM
> > >> Yes .. it should be on mirror.centos.org now .. you could
change the
> > >> repo where your updates come from.?  OR .. wait for that
mirror to get
> > >> updated.
> > >
> > >
> > > I just did
> > > yum clean all
> > > yum update
> > >
> > > and 15-8 showed up.?  Maybe the 'clean all'
> > did it, or maybe just showed up.
> > >
> > > I applied the update (yum update), rebooted and...
> > > no boot.?  Just a blank screen.
> > >
> > > Hardware is a Mac-Mini :-(
> > >
> > > This is not an essential machine, so I could re-install (from
> > > netinstall) if you think it's worth the effort.
> > >
> > > Or what?
> > >
> > > David
> >
> >You just need to reinstall the kernel and it should work.
> >
> 
> Sorry for being so ignorant, but I don't
> understand "just reinstall the kernel".  I don't
> know how to translate that into a specific yum or rpm command.
A quick google -
https://ma.ttias.be/reinstall-the-linux-kernel-on-centos-or-rhel/

But I think this is easier:

yum install --downloadonly --downloaddir=~/ kernel
- OR -
wget your kernel version...

then

rpm -Uvh kernel-*.rpm --replacepkgs

On Sun, Aug 02, 2020 at 07:16:25AM -0700, david wrote:
> 
> > <snip>
> 
...
> 
> > 
> > You just need to reinstall the kernel and it should work.
> > 
> 
> Sorry for being so ignorant, but I don't understand "just
reinstall the
> kernel".  I don't know how to translate that into a specific yum
or rpm
> command.
> 
> However, since this is a crash-and-burn system, I'm going back to a
virgin
> install with netinstall of 7 2003.  I'll let you know what the results
are.
Using dnf instead I would get my latest installed kernel version number:

  $ dnf list installed kernel
  Installed Packages
  kernel.x86_64         3.10.0-1127.el7               @base   
  kernel.x86_64         3.10.0-1127.8.2.el7           @updates
  kernel.x86_64         3.10.0-1127.10.1.el7          @updates
  kernel.x86_64         3.10.0-1127.13.1.el7          @updates
  kernel.x86_64         3.10.0-1127.18.2.el7          @updates

Then do:

  $ sudo dnf reinstall kernel*3.10.0-1127.18.2*

HTH
jon
-- 
Jon H. LaBadie                  jcu at labadie.us

-----Original Message-----
From: Stephen John Smoogen <smooge at gmail.com>
Reply-To: CentOS mailing list <centos at centos.org>
To: CentOS mailing list <centos at 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 <david at 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.


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?


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?


Or should I just leave well enough alone and wait for tonight's auto-update
to fix things?


--Doc Savage
    Fairview Heights, IL