similar to: Centos 7 shim fix failed

-----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>

At 07:11 AM 8/17/2020, you wrote: >On 8/13/20 11:23 PM, Mark LaPierre wrote: > > Hey All, > > > > Is it safe to allow the 193 series kernel update now?? Last time I tried > > that my system refused to boot.? I had to roll back to the 4.18.0-147 > > kernel to get my machine to reboot. > > > > Since that happened I've been watching this mail list

><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

On 8/4/2020 11:20 AM, Jonathan Billings wrote: >> Running transaction >> Installing : kernel-3.10.0-1127.el7.x86_64 1/1 >> >> at which point the process appeared to hang. No further output happened for >> five minutes. I opened a different terminal and entered "shutdown -r now". >> The result is an unbootable system. >> >> >>

After trying several paths, some suggested on this list, here's my results. 1) Fixing a unbootable system wasn't practical in my case. Fortunately, all my systems can be rebuilt from scratch. 2) When I was lucky enough to catch an updated system before reboot, backing out the defective updates wasn't possible. Yum said there were no prior versions. 3) The most reliable method I

At 05:01 PM 8/4/2020, you wrote: >Am 05.08.20 um 01:27 schrieb david: >>At 04:18 PM 8/4/2020, you wrote: >>>Am 05.08.20 um 01:09 schrieb david: >>>>At 01:54 PM 8/4/2020, you wrote: >>>>>On Tue, 04 Aug 2020 13:44:05 -0700 >>>>>david wrote: >>>>> >>>>> > After all the updates, the system was NOT bootable.

Hello all-- These instructions are somewhat OK but my messed up box is the only one I've got basically to help with this problem. Where can we find "correction" instructions using a "rescue" CD or flash drive? I understand RedHat provided detailed instructions to supported customers. Thanks. _______________________ Sent from MzK's phone. ---------- Forwarded message

Hi all, I had the same problem with my UEFI bios machine and I fixed it so for Centos 7: 1) Boot from an rescue linux usb 2) When the rescue system is running: ??? 2.1) #chroot /mnt/sysimage 3) Config network: ??? 3.1) # ip addr add X.X.X.X/X dev X ??? 3.2) # ip route add default via X.X.X.X??? <--- default router 4) And finally: ??? #yum downgrade shim\* grub2\* mokutil ???

At 04:18 PM 8/4/2020, you wrote: >Am 05.08.20 um 01:09 schrieb david: >>At 01:54 PM 8/4/2020, you wrote: >>>On Tue, 04 Aug 2020 13:44:05 -0700 >>>david wrote: >>> >>> > After all the updates, the system was NOT bootable. >>> >>>How long did you wait for it to boot, and what >>>did it do when it failed to boot?? What text

On Tue, Aug 04, 2020 at 10:54:50AM -0700, david wrote: > Yum got up to the point: > > Running transaction > Installing : kernel-3.10.0-1127.el7.x86_64 1/1 > > at which point the process appeared to hang. No further output happened for > five minutes. I opened a different terminal and entered "shutdown -r now". > The result is an unbootable system. > >

Once upon a time, Johnny Hughes <johnny at centos.org> said: > The issues should now be resolved. > > If you just mount /mnt/sysimage, set an ip address and upgrade (to get > th new shim) .. then: > > yum reinstall <latest-version> I'm curious - why does the kernel need to be reinstalled? The shim-x64 package installs its files directly to the EFI partition

><snip> > > I'll post here again once we have pushed the EL8 and CentOS Stream updates. > >OK .. I have also now pushed the CentOS Linux 8 update .. you should see >an update to SHIM .. the new versions are: > >PowerTools/x86_64/os/Packages/shim-unsigned-x64-15-8.el8.x86_64.rpm >BaseOS/x86_64/os/Packages/shim-ia32-15-15.el8_2.x86_64.rpm

<snip> >Your system was most likely rebuilding the initrd, and you interrupted >it leaving you with a broken initrd. > >Try booting off a rescue disk and chroot into the install, and run: > >dracut -f -v > >to regenerate all the initrds. > >Also, you don't need to reinstall the kernel but just do a 'yum >update' to get everything up to the latest

At 06:10 AM 8/2/2020, you wrote: >On 8/2/20 8:04 AM, david wrote: > > > >> <snip> > > > > > > > >> > I'll post here again once we have pushed the EL8 and CentOS Stream > >> updates. > >> > >> OK .. I have also now pushed the CentOS Linux 8 update .. you should see > >> an update to SHIM .. the new

On Fri, Jul 31, 2020 at 10:20:28PM -0500, Johnny Hughes wrote: ... > > The issue seems to be with the shim package (not the grub or kernel > packages) and we are currently working with Red Hat on a fix. This > issue happened in many Linux OSes and even Windows, not just RHEL and > CentOS. > > We will push a fix as soon as one is available. > > I would hold off on

On 8/2/20 2:04 AM, Alessandro Baggi wrote: > > Il 01/08/20 22:03, Greg Bailey ha scritto: >> On 8/1/20 6:56 AM, david wrote: >>> At 02:54 AM 8/1/2020, Alessandro Baggi wrote: >>>> Hi Johnny, >>>> thank you very much for clarification. >>>> >>>> You said that in the centos infrastructure only one server got the >>>>

This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that is, the one from the latest installation media. I am running on an x86_64 architecture (see uname -i). Please use the correct shim file for your architecture

Hey All, Is it safe to allow the 193 series kernel update now? Last time I tried that my system refused to boot. I had to roll back to the 4.18.0-147 kernel to get my machine to reboot. Since that happened I've been watching this mail list for acknowledgement that the problem has been corrected while refusing the kernel update. I may have missed the announcement that the issue was

Il 31/07/20 13:08, ja ha scritto: > On Fri, 2020-07-31 at 22:35 +1200, Alan McRae via CentOS wrote: >> I am running an Intel x64 machine using UEFI to boot an SSD. >> >> Installing the latest yum update which includes grub2 and kernel >> 4.18.0-193.14.2.el8_2.x86_64 renders the machine unbootable, blank >> screen where grub should be, no error messages, just hangs.

At 06:37 AM 8/2/2020, Johnny Hughes wrote: >On 8/2/20 8:30 AM, david wrote: > > At 06:10 AM 8/2/2020, you wrote: > >> On 8/2/20 8:04 AM, david wrote: > >> > > >> >> <snip> > >> > > >> > > >> > > >> >> > I'll post here again once we have pushed the EL8 and CentOS Stream > >>