Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 8/2/20 7:51 PM, Pete Biggs wrote: > >> >> You just need to reinstall the kernel and it should work. >> >> > Is it possible to bump the kernel version number to make sure the > kernel gets re-installed on automated installs? Or would this break > the compatibility with RHEL? > Well .. It would break ENVR with RHEL, right? RHEL is not bumping up their kernel version and they had the same issue. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
> > You just need to reinstall the kernel and it should work. > > Is it possible to bump the kernel version number to make sure the kernel gets re-installed on automated installs? Or would this break the compatibility with RHEL? P. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On Sun, 2 Aug 2020 at 18:13, Robert G (Doc) Savage via CentOS wrote: > > -Original Message- > From: Stephen John Smoogen > Reply-To: CentOS mailing list > To: CentOS mailing list > 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 wrote: > > > > > 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
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
-Original Message- From: Stephen John Smoogen Reply-To: CentOS mailing list To: CentOS mailing list 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 wrote: > > 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 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On Sun, Aug 02, 2020 at 07:16:25AM -0700, david wrote: > > > > ... > > > > > 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 j...@labadie.us ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
Il 02/08/20 15:10, Marc Balmer via CentOS ha scritto: Thanks for acting quickly, especially on a weekend. This. +1 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On Sun, 2 Aug 2020 at 11:06, david wrote: > > > 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. > I don't have any access to a Mac Mini to help further than this general help: First I would search google for "how to obtain model version info on mac mini" https://support.apple.com/en-us/HT201894 Then depending on how the mac mini is being booted (using the windows compatibility mode or some other method) I would look for howtos on how to update the firmware. After that it is time to learn the Mac magic key boot sequences. The Mac isn't exactly a PC and its UEFI does not have a standard menu front end like many PC UEFI. https://support.apple.com/en-us/HT201255 https://support.apple.com/en-us/HT202796 -- Stephen J Smoogen. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
> 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 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
At 07:57 AM 8/2/2020, you wrote: On Sun, 2 Aug 2020 at 10:20, david wrote: > > > > > > > > > > >> 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 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On Sun, 2 Aug 2020 at 10:20, david wrote: > > > > > > > > > > >> 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@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
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
>> 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. --- On a Mac-Mini, which got hit by the bug in shim, I re-installed Centos 7 2003 from netinstall, selecting minimal as the software selection. The reboot worked fine. So, I next tried "yum -y update", noticed shim 7-8 got selected. However, at the completion of the update, I did a reboot and got a blank screen. No grub choices. Not good. David ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
>> 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 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 8/2/20 8:47 AM, david wrote: > 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: >> >> > >> >> >> >> >> > >> >> > >> >> > >> >> >> > 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 >> >> >> BaseOS/x86_64/os/Packages/shim-x64-15-15.el8_2.x86_64.rpm >> >> >> >> >> >> For CentOS Linux 7 .. the new files are: >> >> >> >> >> >> x86_64/Packages/mokutil-15-8.el7.x86_64.rpm >> >> >> x86_64/Packages/shim-ia32-15-8.el7.x86_64.rpm >> >> >> x86_64/Packages/shim-unsigned-ia32-15-8.el7.x86_64.rpm >> >> >> x86_64/Packages/shim-unsigned-x64-15-8.el7.x86_64.rpm >> >> >> x86_64/Packages/shim-x64-15-8.el7.x86_64.rpm >> >> >> >> >> >> You need only replace the files you currently have installed, not >> >> >> install every file. >> >> >> >> >> >> Please report both positive and negative results. >> >> >> >> >> >> Thanks, >> >> >> Johnny Hughes >> >> >> >> >> > I updated my Centos 7, and it's awaiting a reboot. The >> version of >> >> shim >> >> > says 15-7, which I presume is the bad one. >> >> > >> >> > What do I need to do? Obviously, a reboot will encounter the >> >> failure. >> >> > Or, should I perform "yum update" periodically and wait for shim >> >> 15-8 to >> >> > appear, and only after that do the reboot? Or is there some >> other >> >> remedy? >> >> > >> >> > And by the way, I'm amazed at the speed with which this problem was >> >> > addressed and a fix provided. You guys work wonders. >> >> > >> >> > David >> >> >> >> It would be best IF the kernel and shim get installed at the same time >> >> if possible .. so I would install the kernel again (since it is not >> >> running yet) with the new shim. >> >> >> >> BTW .. it does not fail on every install .. so it might work w/o >> the new >> >> update. However, no need to chance it at this point. Wait until >> the >> >> new shim is there and install it and reinstall the kernel is my >> advise. >> > >> > Here's what I get... >> > >> > rpm -qa | grep shim >> > shim-x64-15-7.el7_9.x86_64 >> > >> > yum update >> > Loaded plugins: fastestmirror, langpacks, priorities >> > Loading mirror speeds from cached hostfile >> >  * base: mirror.fileplanet.com >> >  * epel: mirror.prgmr.com >> >  * extras: mirror.shastacoe.net >> >  * remi-php73: mirror.sjc02.svwh.net >> >  * remi-safe: mirror.sjc02.svwh.net >> >  * updates: centos-distro.1gservers.com >> > 373 packages excluded due to repository priority protections >> > No packages marked for update >> > >> > >> > >> > Should I just wait for 15-8 to appear? >> > >> > David >> > >> >> 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. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
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: >> > >> >> >> > >> > >> > >> >> > 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 >> >> BaseOS/x86_64/os/Packages/shim-x64-15-15.el8_2.x86_64.rpm >> >> >> >> For CentOS Linux 7 .. the new files are: >> >> >> >> x86_64/Packages/mokutil-15-8.el7.x86_64.rpm >> >> x86_64/Packages/shim-ia32-15-8.el7.x86_64.rpm >> >> x86_64/Packages/shim-unsigned-ia32-15-8.el7.x86_64.rpm >> >> x86_64/Packages/shim-unsigned-x64-15-8.el7.x86_64.rpm >> >> x86_64/Packages/shim-x64-15-8.el7.x86_64.rpm >> >> >> >> You need only replace the files you currently have installed, not >> >> install every file. >> >> >> >> Please report both positive and negative results. >> >> >> >> Thanks, >> >> Johnny Hughes >> >> >> > I updated my Centos 7, and it's awaiting a reboot.àThe version of >> shim >> > says 15-7, which I presume is the bad one. >> > >> > What do I need to do?àObviously, a reboot will encounter the >> failure.à >> > Or, should I perform "yum update" periodically and wait for shim >> 15-8 to >> > appear, and only after that do the reboot?àOr is there some other >> remedy? >> > >> > And by the way, I'm amazed at the speed with which this problem was >> > addressed and a fix provided.àYou guys work wonders. >> > >> > David >> >> It would be best IF the kernel and shim get installed at the same time >> if possible .. so I would install the kernel again (since it is not >> running yet) with the new shim. >> >> BTW .. it does not fail on every install .. so it might work w/o the new >> update. However, no need to chance it at this point. Wait until the >> new shim is there and install it and reinstall the kernel is my advise. > > Here's what I get... > > rpm -qa | grep shim > shim-x64-15-7.el7_9.x86_64 > > yum update > Loaded plugins: fastestmirror, langpacks, priorities > Loading mirror speeds from cached hostfile >  * base: mirror.fileplanet.com >  * epel: mirror.prgmr.com >  * extras: mirror.shastacoe.net >  * remi-php73: mirror.sjc02.svwh.net >  * remi-safe: mirror.sjc02.svwh.net >  * updates: centos-distro.1gservers.com > 373 packages excluded due to repository priority protections > No packages marked for update > > > > Should I just wait for 15-8 to appear? > > David > 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 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
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: >> > >> >> >> > >> > >> > >> >> > 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 >> >> BaseOS/x86_64/os/Packages/shim-x64-15-15.el8_2.x86_64.rpm >> >> >> >> For CentOS Linux 7 .. the new files are: >> >> >> >> x86_64/Packages/mokutil-15-8.el7.x86_64.rpm >> >> x86_64/Packages/shim-ia32-15-8.el7.x86_64.rpm >> >> x86_64/Packages/shim-unsigned-ia32-15-8.el7.x86_64.rpm >> >> x86_64/Packages/shim-unsigned-x64-15-8.el7.x86_64.rpm >> >> x86_64/Packages/shim-x64-15-8.el7.x86_64.rpm >> >> >> >> You need only replace the files you currently have installed, not >> >> install every file. >> >> >> >> Please report both positive and negative results. >> >> >> >> Thanks, >> >> Johnny Hughes >> >> >> > I updated my Centos 7, and it's awaiting a reboot. The version of >> shim >> > says 15-7, which I presume is the bad one. >> > >> > What do I need to do? Obviously, a reboot will encounter the >> failure. >> > Or, should I perform "yum update" periodically and wait for shim >> 15-8 to >> > appear, and only after that do the reboot? Or is there some other >> remedy? >> > >> > And by the way, I'm amazed at the speed with which this problem was >> > addressed and a fix provided. You guys work wonders. >> > >> > David >> >> It would be best IF the kernel and shim get installed at the same time >> if possible .. so I would install the kernel again (since it is not >> running yet) with the new shim. >> >> BTW .. it does not fail on every install .. so it might work w/o the new >> update. However, no need to chance it at this point. Wait until the >> new shim is there and install it and reinstall the kernel is my advise. > > Here's what I get... > > rpm -qa | grep shim > shim-x64-15-7.el7_9.x86_64 > > yum update > Loaded plugins: fastestmirror, langpacks, priorities > Loading mirror speeds from cached hostfile > * base: mirror.fileplanet.com > * epel: mirror.prgmr.com > * extras: mirror.shastacoe.net > * remi-php73: mirror.sjc02.svwh.net > * remi-safe: mirror.sjc02.svwh.net > * updates: centos-distro.1gservers.com > 373 packages excluded due to repository priority protections > No packages marked for update > > > > Should I just wait for 15-8 to appear? > > David > 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. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
At 06:10 AM 8/2/2020, you wrote: On 8/2/20 8:04 AM, david wrote: > >> > > > >> > 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 >> BaseOS/x86_64/os/Packages/shim-x64-15-15.el8_2.x86_64.rpm >> >> For CentOS Linux 7 .. the new files are: >> >> x86_64/Packages/mokutil-15-8.el7.x86_64.rpm >> x86_64/Packages/shim-ia32-15-8.el7.x86_64.rpm >> x86_64/Packages/shim-unsigned-ia32-15-8.el7.x86_64.rpm >> x86_64/Packages/shim-unsigned-x64-15-8.el7.x86_64.rpm >> x86_64/Packages/shim-x64-15-8.el7.x86_64.rpm >> >> You need only replace the files you currently have installed, not >> install every file. >> >> Please report both positive and negative results. >> >> Thanks, >> Johnny Hughes >> > I updated my Centos 7, and it's awaiting a reboot. The version of shim > says 15-7, which I presume is the bad one. > > What do I need to do? Obviously, a reboot will encounter the failure. > Or, should I perform "yum update" periodically and wait for shim 15-8 to > appear, and only after that do the reboot? Or is there some other remedy? > > And by the way, I'm amazed at the speed with which this problem was > addressed and a fix provided. You guys work wonders. > > David It would be best IF the kernel and shim get installed at the same time if possible .. so I would install the kernel again (since it is not running yet) with the new shim. BTW .. it does not fail on every install .. so it might work w/o the new update. However, no need to chance it at this point. Wait until the new shim is there and install it and reinstall the kernel is my advise. Here's what I get... rpm -qa | grep shim shim-x64-15-7.el7_9.x86_64 yum update Loaded plugins: fastestmirror, langpacks, priorities Loading mirror speeds from cached hostfile * base: mirror.fileplanet.com * epel: mirror.prgmr.com * extras: mirror.shastacoe.net * remi-php73: mirror.sjc02.svwh.net * remi-safe: mirror.sjc02.svwh.net * updates: centos-distro.1gservers.com 373 packages excluded due to repository priority protections No packages marked for update Should I just wait for 15-8 to appear? David ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 8/2/20 8:12 AM, Johnny Hughes wrote: > On 8/2/20 8:10 AM, Marc Balmer via CentOS wrote: Please report both positive and negative results. >>> >>> A previously afftected Aures nino POS-terminal boots just fine with CentOS >>> 7 and shim 15.8. >>> >>> Now I will test an affected machine (Aures Twist POS terminal) that runs >>> CentOS 8 (well, usually runs CentOS 8, but not now, since it does not boot >>> ... :=> >> >> The affected machine running CentOS 8 boots fine after upgrading to shim >> 15.15 >> >> Thanks for acting quickly, especially on a weekend. > > Thanks for the reports .. it is not the first weekend spent on this > issue .. not even the first in a row :) > > The CentOS Stream update should be release in a few minutes unless we > hit a snag in testing. > OK .. CentOS Stream update is also now pushed. Same packages as CentOS Linux 8. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 8/2/20 8:10 AM, Marc Balmer via CentOS wrote: >>> >>> Please report both positive and negative results. >> >> A previously afftected Aures nino POS-terminal boots just fine with CentOS 7 >> and shim 15.8. >> >> Now I will test an affected machine (Aures Twist POS terminal) that runs >> CentOS 8 (well, usually runs CentOS 8, but not now, since it does not boot >> ... :=> > > The affected machine running CentOS 8 boots fine after upgrading to shim 15.15 > > Thanks for acting quickly, especially on a weekend. Thanks for the reports .. it is not the first weekend spent on this issue .. not even the first in a row :) The CentOS Stream update should be release in a few minutes unless we hit a snag in testing. Thanks, Johnny Hughes signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 8/2/20 8:04 AM, david wrote: > >> > > > >> > 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 >> BaseOS/x86_64/os/Packages/shim-x64-15-15.el8_2.x86_64.rpm >> >> For CentOS Linux 7 .. the new files are: >> >> x86_64/Packages/mokutil-15-8.el7.x86_64.rpm >> x86_64/Packages/shim-ia32-15-8.el7.x86_64.rpm >> x86_64/Packages/shim-unsigned-ia32-15-8.el7.x86_64.rpm >> x86_64/Packages/shim-unsigned-x64-15-8.el7.x86_64.rpm >> x86_64/Packages/shim-x64-15-8.el7.x86_64.rpm >> >> You need only replace the files you currently have installed, not >> install every file. >> >> Please report both positive and negative results. >> >> Thanks, >> Johnny Hughes >> > I updated my Centos 7, and it's awaiting a reboot. The version of shim > says 15-7, which I presume is the bad one. > > What do I need to do? Obviously, a reboot will encounter the failure. > Or, should I perform "yum update" periodically and wait for shim 15-8 to > appear, and only after that do the reboot? Or is there some other remedy? > > And by the way, I'm amazed at the speed with which this problem was > addressed and a fix provided. You guys work wonders. > > David It would be best IF the kernel and shim get installed at the same time if possible .. so I would install the kernel again (since it is not running yet) with the new shim. BTW .. it does not fail on every install .. so it might work w/o the new update. However, no need to chance it at this point. Wait until the new shim is there and install it and reinstall the kernel is my advise. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
>> >> Please report both positive and negative results. > > A previously afftected Aures nino POS-terminal boots just fine with CentOS 7 > and shim 15.8. > > Now I will test an affected machine (Aures Twist POS terminal) that runs > CentOS 8 (well, usually runs CentOS 8, but not now, since it does not boot > ... :=> The affected machine running CentOS 8 boots fine after upgrading to shim 15.15 Thanks for acting quickly, especially on a weekend. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
> 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 BaseOS/x86_64/os/Packages/shim-x64-15-15.el8_2.x86_64.rpm For CentOS Linux 7 .. the new files are: x86_64/Packages/mokutil-15-8.el7.x86_64.rpm x86_64/Packages/shim-ia32-15-8.el7.x86_64.rpm x86_64/Packages/shim-unsigned-ia32-15-8.el7.x86_64.rpm x86_64/Packages/shim-unsigned-x64-15-8.el7.x86_64.rpm x86_64/Packages/shim-x64-15-8.el7.x86_64.rpm You need only replace the files you currently have installed, not install every file. Please report both positive and negative results. Thanks, Johnny Hughes I updated my Centos 7, and it's awaiting a reboot. The version of shim says 15-7, which I presume is the bad one. What do I need to do? Obviously, a reboot will encounter the failure. Or, should I perform "yum update" periodically and wait for shim 15-8 to appear, and only after that do the reboot? Or is there some other remedy? And by the way, I'm amazed at the speed with which this problem was addressed and a fix provided. You guys work wonders. David ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
> Am 02.08.2020 um 14:34 schrieb Johnny Hughes : > > On 8/2/20 6:59 AM, Johnny Hughes wrote: >>> 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 >> problem. >> What are the conditions that permit the breakage? There is a particular >> configuration (hw/sw) case that match always the problem or it is >> random? >> >> Thank you > > I have two servers running Centos 7 on apple hardware (one mac-mini > and one mac server). They both failed to reboot a few days ago. So > perhaps whatever anti-boot bug hit Centos 8, also hit Centos 7. I > can't tell what version got updated since the system simply fails to > boot. I don't even get a grub screen. I'll have to rebuild the > systems from scratch. > > You should be able to boot off of installation media into rescue mode, and downgrade the grub2* and/or shim* RPMs. -Greg >>> I did the downgrade on a fresh install of c8.2 but yum said that all >>> selected packages (grub2,shim...) are already to the lowest version and >>> the downgrade is not possibile, ending with "nothing to do". >> >> Ok .. We are running through some final testing now for CentOS Linux 8 >> and CentOS Stream .. updates later today for EL8. >> >> For CentOS Linux 7 .. I just pushed the latest shim packages (we had to >> get these signed by Microsoft .. as do all distros that do shim. >> Microsoft is the official CA for secureboot. >> >> So in the next few hours, after the mirrors sync up .. you should be >> able to fix any EL7 machines. >> >> 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 > BaseOS/x86_64/os/Packages/shim-x64-15-15.el8_2.x86_64.rpm > > For CentOS Linux 7 .. the new files are: > > x86_64/Packages/mokutil-15-8.el7.x86_64.rpm > x86_64/Packages/shim-ia32-15-8.el7.x86_64.rpm > x86_64/Packages/shim-unsigned-ia32-15-8.el7.x86_64.rpm > x86_64/Packages/shim-unsigned-x64-15-8.el7.x86_64.rpm > x86_64/Packages/shim-x64-15-8.el7.x86_64.rpm > > You need only replace the files you currently have installed, not > install every file. > > Please report both positive and negative results. A previously afftected Aures nino POS-terminal boots just fine with CentOS 7 and shim 15.8. Now I will test an affected machine (Aures Twist POS terminal) that runs CentOS 8 (well, usually runs CentOS 8, but not now, since it does not boot ... :=> > > Thanks, > Johnny Hughes > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 8/2/20 6:59 AM, Johnny Hughes wrote: > 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 > problem. > What are the conditions that permit the breakage? There is a particular > configuration (hw/sw) case that match always the problem or it is > random? > > Thank you I have two servers running Centos 7 on apple hardware (one mac-mini and one mac server). They both failed to reboot a few days ago. So perhaps whatever anti-boot bug hit Centos 8, also hit Centos 7. I can't tell what version got updated since the system simply fails to boot. I don't even get a grub screen. I'll have to rebuild the systems from scratch. >>> >>> You should be able to boot off of installation media into rescue mode, >>> and downgrade the grub2* and/or shim* RPMs. >>> >>> -Greg >>> >> I did the downgrade on a fresh install of c8.2 but yum said that all >> selected packages (grub2,shim...) are already to the lowest version and >> the downgrade is not possibile, ending with "nothing to do". > > Ok .. We are running through some final testing now for CentOS Linux 8 > and CentOS Stream .. updates later today for EL8. > > For CentOS Linux 7 .. I just pushed the latest shim packages (we had to > get these signed by Microsoft .. as do all distros that do shim. > Microsoft is the official CA for secureboot. > > So in the next few hours, after the mirrors sync up .. you should be > able to fix any EL7 machines. > > 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 BaseOS/x86_64/os/Packages/shim-x64-15-15.el8_2.x86_64.rpm For CentOS Linux 7 .. the new files are: x86_64/Packages/mokutil-15-8.el7.x86_64.rpm x86_64/Packages/shim-ia32-15-8.el7.x86_64.rpm x86_64/Packages/shim-unsigned-ia32-15-8.el7.x86_64.rpm x86_64/Packages/shim-unsigned-x64-15-8.el7.x86_64.rpm x86_64/Packages/shim-x64-15-8.el7.x86_64.rpm You need only replace the files you currently have installed, not install every file. Please report both positive and negative results. Thanks, Johnny Hughes signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 8/2/20 7:06 AM, Robert Heller wrote: > At Sun, 2 Aug 2020 06:59:06 -0500 CentOS mailing list > wrote: > >> >> >> >> 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 >> problem. >> What are the conditions that permit the breakage? There is a particular >> configuration (hw/sw) case that match always the problem or it is >> random? >> >> Thank you > > I have two servers running Centos 7 on apple hardware (one mac-mini > and one mac server). They both failed to reboot a few days > ago. So > perhaps whatever anti-boot bug hit Centos 8, also hit Centos 7. I > can't tell what version got updated since the system simply fails to > boot. I don't even get a grub screen. I'll have to rebuild the > systems from scratch. > > You should be able to boot off of installation media into rescue mode, and downgrade the grub2* and/or shim* RPMs. -Greg >>> I did the downgrade on a fresh install of c8.2 but yum said that all >>> selected packages (grub2,shim...) are already to the lowest version and >>> the downgrade is not possibile, ending with "nothing to do". >> >> Ok .. We are running through some final testing now for CentOS Linux 8 >> and CentOS Stream .. updates later today for EL8. >> >> For CentOS Linux 7 .. I just pushed the latest shim packages (we had to >> get these signed by Microsoft .. as do all distros that do shim. >> Microsoft is the official CA for secureboot. >> >> So in the next few hours, after the mirrors sync up .. you should be >> able to fix any EL7 machines. > > Question: is this only a problem for bare metal w/EFI or are VMs affected? I > have a VPS running CentOS 7: > > sharky4.deepsoft.com% uname -a > Linux sharky4.deepsoft.com 3.10.0-1127.13.1.el7.x86_64 #1 SMP Tue Jun 23 > 15:46:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux > sharky4.deepsoft.com% rpm -qa grub\* shim\* > grub2-tools-extra-2.02-0.81.el7.centos.x86_64 > grub2-pc-modules-2.02-0.81.el7.centos.noarch > grub2-tools-minimal-2.02-0.81.el7.centos.x86_64 > grub2-2.02-0.81.el7.centos.x86_64 > grub2-tools-2.02-0.81.el7.centos.x86_64 > grubby-8.28-26.el7.x86_64 > grub2-common-2.02-0.81.el7.centos.noarch > grub2-pc-2.02-0.81.el7.centos.x86_64 > sharky4.deepsoft.com% > > I have these (pending) updates: > > sharky4.deepsoft.com% sudo /usr/bin/yum check-update > Loaded plugins: fastestmirror > Loading mirror speeds from cached hostfile > * base: mirror.es.its.nyu.edu > * epel: mirror.math.princeton.edu >* extras: mirror.facebook.net > * updates: mirror.atlanticmetro.net > > fail2ban.noarch 0.11.1-9.el7.2epel > fail2ban-firewalld.noarch0.11.1-9.el7.2epel > fail2ban-sendmail.noarch 0.11.1-9.el7.2epel > fail2ban-server.noarch 0.11.1-9.el7.2epel > fail2ban-systemd.noarch 0.11.1-9.el7.2epel > grub2.x86_64 1:2.02-0.86.el7.centosupdates > grub2-common.noarch 1:2.02-0.86.el7.centosupdates > grub2-pc.x86_64 1:2.02-0.86.el7.centosupdates > grub2-pc-modules.noarch 1:2.02-0.86.el7.centosupdates > grub2-tools.x86_64 1:2.02-0.86.el7.centosupdates > grub2-tools-extra.x86_64 1:2.02-0.86.el7.centosupdates > grub2-tools-minimal.x86_64 1:2.02-0.86.el7.centosupdates > kernel.x86_643.10.0-1127.18.2.el7 updates > kernel-headers.x86_643.10.0-1127.18.2.el7 updates > kernel-tools.x86_64 3.10.0-1127.18.2.el7 updates > kernel-tools-libs.x86_64 3.10.0-1127.18.2.el7 updates > python-perf.x86_64 3.10.0-1127.18.2.el7 updates > > Is it "safe" for me to to do a yum update or should I wait? > > > This shim issue should only impact cold iron machines with secureboot enabled. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
At Sun, 2 Aug 2020 06:59:06 -0500 CentOS mailing list wrote: > > > > 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 > problem. > What are the conditions that permit the breakage? There is a particular > configuration (hw/sw) case that match always the problem or it is > random? > > Thank you > >>> > >>> I have two servers running Centos 7 on apple hardware (one mac-mini > >>> and one mac server).ÃÂÃÂ They both failed to reboot a few days > >>> ago.ÃÂÃÂ So > >>> perhaps whatever anti-boot bug hit Centos 8, also hit Centos 7.ÃÂÃÂ I > >>> can't tell what version got updated since the system simply fails to > >>> boot.ÃÂÃÂ I don't even get a grub screen. I'll have to rebuild the > >>> systems from scratch. > >>> > >>> > >> > >> You should be able to boot off of installation media into rescue mode, > >> and downgrade the grub2* and/or shim* RPMs. > >> > >> -Greg > >> > > I did the downgrade on a fresh install of c8.2 but yum said that all > > selected packages (grub2,shim...) are already to the lowest version and > > the downgrade is not possibile, ending with "nothing to do". > > Ok .. We are running through some final testing now for CentOS Linux 8 > and CentOS Stream .. updates later today for EL8. > > For CentOS Linux 7 .. I just pushed the latest shim packages (we had to > get these signed by Microsoft .. as do all distros that do shim. > Microsoft is the official CA for secureboot. > > So in the next few hours, after the mirrors sync up .. you should be > able to fix any EL7 machines. Question: is this only a problem for bare metal w/EFI or are VMs affected? I have a VPS running CentOS 7: sharky4.deepsoft.com% uname -a Linux sharky4.deepsoft.com 3.10.0-1127.13.1.el7.x86_64 #1 SMP Tue Jun 23 15:46:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux sharky4.deepsoft.com% rpm -qa grub\* shim\* grub2-tools-extra-2.02-0.81.el7.centos.x86_64 grub2-pc-modules-2.02-0.81.el7.centos.noarch grub2-tools-minimal-2.02-0.81.el7.centos.x86_64 grub2-2.02-0.81.el7.centos.x86_64 grub2-tools-2.02-0.81.el7.centos.x86_64 grubby-8.28-26.el7.x86_64 grub2-common-2.02-0.81.el7.centos.noarch grub2-pc-2.02-0.81.el7.centos.x86_64 sharky4.deepsoft.com% I have these (pending) updates: sharky4.deepsoft.com% sudo /usr/bin/yum check-update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.es.its.nyu.edu * epel: mirror.math.princeton.edu * extras: mirror.facebook.net * updates: mirror.atlanticmetro.net fail2ban.noarch 0.11.1-9.el7.2epel fail2ban-firewalld.noarch0.11.1-9.el7.2epel fail2ban-sendmail.noarch 0.11.1-9.el7.2epel fail2ban-server.noarch 0.11.1-9.el7.2epel fail2ban-systemd.noarch 0.11.1-9.el7.2epel grub2.x86_64 1:2.02-0.86.el7.centosupdates grub2-common.noarch 1:2.02-0.86.el7.centosupdates grub2-pc.x86_64 1:2.02-0.86.el7.centosupdates grub2-pc-modules.noarch 1:2.02-0.86.el7.centosupdates grub2-tools.x86_64 1:2.02-0.86.el7.centosupdates grub2-tools-extra.x86_64 1:2.02-0.86.el7.centosupdates grub2-tools-minimal.x86_64 1:2.02-0.86.el7.centosupdates kernel.x86_643.10.0-1127.18.2.el7 updates kernel-headers.x86_643.10.0-1127.18.2.el7 updates kernel-tools.x86_64 3.10.0-1127.18.2.el7 updates kernel-tools-libs.x86_64 3.10.0-1127.18.2.el7 updates python-perf.x86_64 3.10.0-1127.18.2.el7 updates Is it "safe" for me to to do a yum update or should I wait? > > I'll post here again once we have pushed the EL8 and CentOS Stream updates. > > Content-Description: OpenPGP digital signature > > -BEGIN PGP SIGNATURE- > > iF0EARECAB0WIQTn6goIPoKGmzXde4tMqQyCasFjswUCXyaqigAKCRBMqQyCasFj > swMtAKCIljOaB6o0mxnvIUqA0pP2l16hUwCgnmSj3aPKOym7s58ismQ0mDKfwus= > =S/HK > -END PGP SIGNATURE- > > MIME-Version: 1.0 > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > > > > -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software-- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
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 problem. What are the conditions that permit the breakage? There is a particular configuration (hw/sw) case that match always the problem or it is random? Thank you >>> >>> I have two servers running Centos 7 on apple hardware (one mac-mini >>> and one mac server). They both failed to reboot a few days ago. So >>> perhaps whatever anti-boot bug hit Centos 8, also hit Centos 7. I >>> can't tell what version got updated since the system simply fails to >>> boot. I don't even get a grub screen. I'll have to rebuild the >>> systems from scratch. >>> >>> >> >> You should be able to boot off of installation media into rescue mode, >> and downgrade the grub2* and/or shim* RPMs. >> >> -Greg >> > I did the downgrade on a fresh install of c8.2 but yum said that all > selected packages (grub2,shim...) are already to the lowest version and > the downgrade is not possibile, ending with "nothing to do". Ok .. We are running through some final testing now for CentOS Linux 8 and CentOS Stream .. updates later today for EL8. For CentOS Linux 7 .. I just pushed the latest shim packages (we had to get these signed by Microsoft .. as do all distros that do shim. Microsoft is the official CA for secureboot. So in the next few hours, after the mirrors sync up .. you should be able to fix any EL7 machines. I'll post here again once we have pushed the EL8 and CentOS Stream updates. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
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 problem. What are the conditions that permit the breakage? There is a particular configuration (hw/sw) case that match always the problem or it is random? Thank you I have two servers running Centos 7 on apple hardware (one mac-mini and one mac server). They both failed to reboot a few days ago. So perhaps whatever anti-boot bug hit Centos 8, also hit Centos 7. I can't tell what version got updated since the system simply fails to boot. I don't even get a grub screen. I'll have to rebuild the systems from scratch. You should be able to boot off of installation media into rescue mode, and downgrade the grub2* and/or shim* RPMs. -Greg I did the downgrade on a fresh install of c8.2 but yum said that all selected packages (grub2,shim...) are already to the lowest version and the downgrade is not possibile, ending with "nothing to do". ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
Don't forget that EL 7 (non-UEFI systems) & 8 support booting from LVM snapshot (a.k.a BOOM Boot Manager) , so revert is 2 steps away: - boot from the snapshot (grub menu) - revert from the lvm snapshot - reboot and wait for the revert to complete Best Regards, Strahil Nikolov На 1 август 2020 г. 23:58:27 GMT+03:00, david написа: >At 01:03 PM 8/1/2020, you wrote: >>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 >problem. What are the conditions that permit the breakage? There is a >particular configuration (hw/sw) case that match always the problem or it is >random? Thank you >>> >>>I have two servers running Centos 7 on apple >>>hardware (one mac-mini and one mac >>>server). They both failed to reboot a few >>>days ago. So perhaps whatever anti-boot bug >>>hit Centos 8, also hit Centos 7. I can't tell >>>what version got updated since the system >>>simply fails to boot. I don't even get a grub >>>screen. I'll have to rebuild the systems from scratch. >>> >> >>You should be able to boot off of installation >>media into rescue mode, and downgrade the grub2* and/or shim* RPMs. >> >>-Greg > >This is a good idea, if I knew how to >"downgrade...". But in any event, I had decided >to rebuild from scratch, which of course failed >as soon as I did an yum update. So, I'm >installing 7.8.2003 with no updates until I see >the "all clear -- updates will no longer make >your system unbootable" message from the Centos team. > >In my many years of blindly updating my >installations, starting from the free Redhat >distributions, through Whitehat and onto Centos, >this is the first disaster, and luckily, it >didn't hit all my systems. Let's hope there aren't many more. > >David > >___ >CentOS mailing list >CentOS@centos.org >https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
At 01:03 PM 8/1/2020, you wrote: 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 problem. What are the conditions that permit the breakage? There is a particular configuration (hw/sw) case that match always the problem or it is random? Thank you I have two servers running Centos 7 on apple hardware (one mac-mini and one mac server). They both failed to reboot a few days ago. So perhaps whatever anti-boot bug hit Centos 8, also hit Centos 7. I can't tell what version got updated since the system simply fails to boot. I don't even get a grub screen. I'll have to rebuild the systems from scratch. You should be able to boot off of installation media into rescue mode, and downgrade the grub2* and/or shim* RPMs. -Greg This is a good idea, if I knew how to "downgrade...". But in any event, I had decided to rebuild from scratch, which of course failed as soon as I did an yum update. So, I'm installing 7.8.2003 with no updates until I see the "all clear -- updates will no longer make your system unbootable" message from the Centos team. In my many years of blindly updating my installations, starting from the free Redhat distributions, through Whitehat and onto Centos, this is the first disaster, and luckily, it didn't hit all my systems. Let's hope there aren't many more. David ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
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 problem. What are the conditions that permit the breakage? There is a particular configuration (hw/sw) case that match always the problem or it is random? Thank you I have two servers running Centos 7 on apple hardware (one mac-mini and one mac server). They both failed to reboot a few days ago. So perhaps whatever anti-boot bug hit Centos 8, also hit Centos 7. I can't tell what version got updated since the system simply fails to boot. I don't even get a grub screen. I'll have to rebuild the systems from scratch. You should be able to boot off of installation media into rescue mode, and downgrade the grub2* and/or shim* RPMs. -Greg ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
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 problem. What are the conditions that permit the breakage? There is a particular configuration (hw/sw) case that match always the problem or it is random? Thank you I have two servers running Centos 7 on apple hardware (one mac-mini and one mac server). They both failed to reboot a few days ago. So perhaps whatever anti-boot bug hit Centos 8, also hit Centos 7. I can't tell what version got updated since the system simply fails to boot. I don't even get a grub screen. I'll have to rebuild the systems from scratch. David ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
I got 5 CentOS 8.1 VMs minimal install. When I did the update I got 1 that had dnf issues and corrupted rpm DB and another 1 that didn't boot. Restore from snapshot and again update -> no issues. For me it looks more like a random issue. Best Regards, Strahil Nikolov На 1 август 2020 г. 18:28:09 GMT+03:00, Lamar Owen написа: >On 8/1/20 11:02 AM, Lamar Owen wrote: >> ... >> [lowen@localhost ~]$ rpm -qa | grep ^kernel|grep 147 >> kernel-devel-4.18.0-147.8.1.el8_1.x86_64 >> kernel-4.18.0-147.8.1.el8_1.x86_64 >> kernel-modules-4.18.0-147.8.1.el8_1.x86_64 >> kernel-core-4.18.0-147.8.1.el8_1.x86_64 >> [lowen@localhost ~]$ > >Well, I sure fat-fingered that command let's try it again: > >[lowen@localhost ~]$ rpm -qa | grep ^kernel|grep 193.14 >kernel-headers-4.18.0-193.14.2.el8_2.x86_64 >kernel-devel-4.18.0-193.14.2.el8_2.x86_64 >kernel-modules-4.18.0-193.14.2.el8_2.x86_64 >kernel-tools-4.18.0-193.14.2.el8_2.x86_64 >kernel-core-4.18.0-193.14.2.el8_2.x86_64 >kernel-tools-libs-4.18.0-193.14.2.el8_2.x86_64 >kernel-4.18.0-193.14.2.el8_2.x86_64 >[lowen@localhost ~]$ uname -a >Linux localhost.localdomain 4.18.0-193.14.2.el8_2.x86_64 #1 SMP Sun Jul > >26 03:54:29 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux >[lowen@localhost ~]$ > > >___ >CentOS mailing list >CentOS@centos.org >https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On Sat, Aug 1, 2020 at 8:58 PM Lamar Owen wrote: > On 8/1/20 11:02 AM, Lamar Owen wrote: > > ... > > [lowen@localhost ~]$ rpm -qa | grep ^kernel|grep 147 > > kernel-devel-4.18.0-147.8.1.el8_1.x86_64 > > kernel-4.18.0-147.8.1.el8_1.x86_64 > > kernel-modules-4.18.0-147.8.1.el8_1.x86_64 > > kernel-core-4.18.0-147.8.1.el8_1.x86_64 > > [lowen@localhost ~]$ > > Well, I sure fat-fingered that command let's try it again: > > [lowen@localhost ~]$ rpm -qa | grep ^kernel|grep 193.14 > kernel-headers-4.18.0-193.14.2.el8_2.x86_64 > kernel-devel-4.18.0-193.14.2.el8_2.x86_64 > kernel-modules-4.18.0-193.14.2.el8_2.x86_64 > kernel-tools-4.18.0-193.14.2.el8_2.x86_64 > kernel-core-4.18.0-193.14.2.el8_2.x86_64 > kernel-tools-libs-4.18.0-193.14.2.el8_2.x86_64 > kernel-4.18.0-193.14.2.el8_2.x86_64 > [lowen@localhost ~]$ uname -a > Linux localhost.localdomain 4.18.0-193.14.2.el8_2.x86_64 #1 SMP Sun Jul > 26 03:54:29 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux > [lowen@localhost ~]$ > > > > RedHat fixes. https://access.redhat.com/errata/RHBA-2020:3265 https://access.redhat.com/errata/RHBA-2020:3262 -- Lee ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 8/1/20 11:02 AM, Lamar Owen wrote: ... [lowen@localhost ~]$ rpm -qa | grep ^kernel|grep 147 kernel-devel-4.18.0-147.8.1.el8_1.x86_64 kernel-4.18.0-147.8.1.el8_1.x86_64 kernel-modules-4.18.0-147.8.1.el8_1.x86_64 kernel-core-4.18.0-147.8.1.el8_1.x86_64 [lowen@localhost ~]$ Well, I sure fat-fingered that command let's try it again: [lowen@localhost ~]$ rpm -qa | grep ^kernel|grep 193.14 kernel-headers-4.18.0-193.14.2.el8_2.x86_64 kernel-devel-4.18.0-193.14.2.el8_2.x86_64 kernel-modules-4.18.0-193.14.2.el8_2.x86_64 kernel-tools-4.18.0-193.14.2.el8_2.x86_64 kernel-core-4.18.0-193.14.2.el8_2.x86_64 kernel-tools-libs-4.18.0-193.14.2.el8_2.x86_64 kernel-4.18.0-193.14.2.el8_2.x86_64 [lowen@localhost ~]$ uname -a Linux localhost.localdomain 4.18.0-193.14.2.el8_2.x86_64 #1 SMP Sun Jul 26 03:54:29 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [lowen@localhost ~]$ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 7/31/20 6:35 AM, 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. ... The main point of this message is to make people aware of the problem and suggest admins don't run 'yum update' until they understand the problem and have a fix at hand. I posted, on 7/30, to CentOS-devel the following after my similar experience (booting an mSATA SSD on my M6700, with two 2.5 SATA drives (a 1TB and a 2TB), and the mSATA is not /dev/sda on this hardware, FWIW): "Moral of the story? Have the install DVD on a USB stick and available to boot into rescue mode, know how to boot rescue mode (from the installer boot menu select 'troubleshooting' then 'rescue' and option 1 once the menu shows), know how to activate network interfaces in text mode (either nmcli or nmtui works fine for this), and know a few basic dnf commands. And have an alternate means of doing basic web searches available; my android phone this morning was used for that." I was able to recover with the install DVD on a USB stick and using rescue mode on a laptop with only WiFi (nmtui does a great job for this sort of thing, booted into rescue mode and chrooted onto /mnt/sysimage). ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 8/1/20 5:54 AM, Alessandro Baggi wrote: You said that in the centos infrastructure only one server got the problem. What are the conditions that permit the breakage? There is a particular configuration (hw/sw) case that match always the problem or it is random? I experienced the issue on a Dell Precision M6700 (UEFI, Core i7-3740QM) on the first attempt at update; I recovered by rolling back and reinstalling grub2-*; I then updated on the command line with dnf update and now that same hardware that crashed out the first time is working fine with the same package versions. It seems to be intermittent, and I can't reproduce it. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 8/1/20 5:00 AM, Johnny Hughes wrote: I would wait and install everything as a group. We should have something soon. First off, Johnny and all of the rest of the CentOS team, thank you for your efforts! Second, to all with this problem, I too experienced the issue (I posted on the CentOS-Devel list my findings). To those who seem to think more testing could have prevented the issue, let me just say that while the FIRST update to the new shim-x64, grub2, and kernel stack failed for me (and that update was done with the GUI updater that reboots for the actual update), I WAS able to recover using the install media's rescue mode tools as documented in my posts on CentOS-devel. I'm glad to provide any and all logs of the processes I did, but the short of it is that after I successfully downgraded grub2 it still wouldn't boot, but I was able to do a reinstall of grub2 (81, the older version) to get it to boot with the old grub2, the new shim-x64, and the new kernel, and then I was able to successfully update grub2 with dnf on a command line. So I have the following installed: [lowen@localhost ~]$ rpm -q shim-x64 shim-x64-15-13.el8.x86_64 [lowen@localhost ~]$ rpm -qa | grep ^grub2 grub2-common-2.02-87.el8_2.noarch grub2-tools-2.02-87.el8_2.x86_64 grub2-efi-x64-2.02-87.el8_2.x86_64 grub2-tools-extra-2.02-87.el8_2.x86_64 grub2-pc-2.02-87.el8_2.x86_64 grub2-tools-efi-2.02-87.el8_2.x86_64 grub2-tools-minimal-2.02-87.el8_2.x86_64 grub2-pc-modules-2.02-87.el8_2.noarch grub2-efi-x64-modules-2.02-87.el8_2.noarch [lowen@localhost ~]$ rpm -qa | grep ^kernel|grep 147 kernel-devel-4.18.0-147.8.1.el8_1.x86_64 kernel-4.18.0-147.8.1.el8_1.x86_64 kernel-modules-4.18.0-147.8.1.el8_1.x86_64 kernel-core-4.18.0-147.8.1.el8_1.x86_64 [lowen@localhost ~]$ And this is on a machine that previously crashed during boot with the exactly the same packages. So even on the same hardware the same update (done a bit differently) had different results. It's quite possible, based on my experience with this particular issue, that if I had the whole system rolled back to where it was before the GUI update and if I then updated it again that it could just simply work ok afterwards. It's very hard to test for intermittent issues! ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
Hi Johnny, thank you very much for clarification. You said that in the centos infrastructure only one server got the problem. What are the conditions that permit the breakage? There is a particular configuration (hw/sw) case that match always the problem or it is random? Thank you Il Sab 1 Ago 2020, 05:20 Johnny Hughes ha scritto: > On 7/31/20 11:24 AM, Alessandro Baggi wrote: > > > > 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. > >>> > >>> After some hours I managed to modify another bootable partition > >>> (containing older software) and boot it from there. > >>> > >>> After that, I found out it is a known problem. > >>> > >>> The main point of this message is to make people aware of the problem > >>> and suggest admins don't run 'yum update' until they understand the > >>> problem and have a fix at hand. > >>> > >>> See 'UEFI boot blank screen post update' for a solution and directions > >>> to the redhat article. > >>> > >>> Regards > >>> > >>> Alan > >>> > >> I have been punished by this bug - it is/was very nasty. > >> > > Me too. Luckily it happened on a test machine. > > > > Sorry but seems that those packages were not tested before pushing them > > in the update repo. Would be great to know what happened to the > > mainstream chains and how a package like grub reached the update repo > > when it has serious problem (genuine curiosity but not to blame them). > > Of course it was tested before it was pushed. Obviously this is not a > problem with every install. Surely you don't think we push items > without doing any testing. Certainly not items as important as this > update. > > The CentOS infrastructure has hundreds of servers, most of them were > not impacted (as an example). In fact, we seem to have had this happen > on only one machine in those hundreds so far. It is a problem, obviously. > > 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 installing this until we release the new fixes. > > > > > In my case, the restore procedure reported by RH in case of reboot does > > not work and reports that the packages are already at the lowest version > > and that the downgrade is not possibile. I don't know why. > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 8/1/20 1:59 AM, Jon LaBadie wrote: > 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 installing this until we release the new fixes. >> > > On a system that does not use any of the shim packages, would you > recommend updating the grub2 and mokutil packages or holding off? > > Jon > I would wait and install everything as a group. We should have something soon. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
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 installing this until we release the new fixes. > On a system that does not use any of the shim packages, would you recommend updating the grub2 and mokutil packages or holding off? Jon -- Jon H. LaBadie j...@labadie.us ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 7/31/20 11:20 PM, Johnny Hughes wrote: On 7/31/20 11:24 AM, Alessandro Baggi wrote: 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. After some hours I managed to modify another bootable partition (containing older software) and boot it from there. After that, I found out it is a known problem. The main point of this message is to make people aware of the problem and suggest admins don't run 'yum update' until they understand the problem and have a fix at hand. See 'UEFI boot blank screen post update' for a solution and directions to the redhat article. Regards Alan I have been punished by this bug - it is/was very nasty. Me too. Luckily it happened on a test machine. Sorry but seems that those packages were not tested before pushing them in the update repo. Would be great to know what happened to the mainstream chains and how a package like grub reached the update repo when it has serious problem (genuine curiosity but not to blame them). Of course it was tested before it was pushed. Obviously this is not a problem with every install. Surely you don't think we push items without doing any testing. Certainly not items as important as this update. The CentOS infrastructure has hundreds of servers, most of them were not impacted (as an example). In fact, we seem to have had this happen on only one machine in those hundreds so far. It is a problem, obviously. 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 installing this until we release the new fixes. In my case, the restore procedure reported by RH in case of reboot does not work and reports that the packages are already at the lowest version and that the downgrade is not possibile. I don't know why. It tanked my machine. I managed to get it to boot into emergency mode where I eventually got it to boot on an old kernel as shown in the paste below. After getting it to boot I used grubby to set the default kernel to the oldest one on the machine. Surprisingly enough neither of the two most recent kernels would boot even though the machine was running on the second oldest kernel when I ran the update that tanked it. That adds credence to the comment above that the problem was not the new kernel since it trashed both the new kernel and the one before. Both were from the same series. The 147 kernel works but neither of newer ones would. CentOS Linux release 8.2.2004 (Core) enp5s0 IP Address = 192.168.15.131 Linux localhost.localdomain 4.18.0-147.8.1.el8_1.x86_64 #1 SMP Thu Apr 9 13:49:54 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Number of cores = 32 00:55:13 up 8:37, 1 user, load average: 0.31, 0.48, 0.44 amdgpu-pci-0900 Adapter: PCI adapter vddgfx: +0.83 V fan1: 771 RPM (min =0 RPM, max = 3700 RPM) temp1:+45.0°C (crit = +94.0°C, hyst = -273.1°C) power1: 31.07 W (cap = 125.00 W) acpitz-virtual-0 Adapter: Virtual device temp1:+16.8°C (crit = +20.8°C) temp2:+16.8°C (crit = +20.8°C) amdgpu-pci-0400 Adapter: PCI adapter vddgfx: +0.72 V fan1: 768 RPM (min =0 RPM, max = 3700 RPM) temp1:+39.0°C (crit = +94.0°C, hyst = -273.1°C) power1: 30.10 W (cap = 125.00 W) -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
On 7/31/20 11:24 AM, Alessandro Baggi wrote: > > 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. >>> >>> After some hours I managed to modify another bootable partition >>> (containing older software) and boot it from there. >>> >>> After that, I found out it is a known problem. >>> >>> The main point of this message is to make people aware of the problem >>> and suggest admins don't run 'yum update' until they understand the >>> problem and have a fix at hand. >>> >>> See 'UEFI boot blank screen post update' for a solution and directions >>> to the redhat article. >>> >>> Regards >>> >>> Alan >>> >> I have been punished by this bug - it is/was very nasty. >> > Me too. Luckily it happened on a test machine. > > Sorry but seems that those packages were not tested before pushing them > in the update repo. Would be great to know what happened to the > mainstream chains and how a package like grub reached the update repo > when it has serious problem (genuine curiosity but not to blame them). Of course it was tested before it was pushed. Obviously this is not a problem with every install. Surely you don't think we push items without doing any testing. Certainly not items as important as this update. The CentOS infrastructure has hundreds of servers, most of them were not impacted (as an example). In fact, we seem to have had this happen on only one machine in those hundreds so far. It is a problem, obviously. 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 installing this until we release the new fixes. > > In my case, the restore procedure reported by RH in case of reboot does > not work and reports that the packages are already at the lowest version > and that the downgrade is not possibile. I don't know why. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
I would add,
RedHat is recomending also to blacklist grub, shim and mokutil in
yum.conf until the problem is resolved.
Il 31/07/20 18:26, Laack, Andrea P ha scritto:
RedHat is recommending not to patch.
https://access.redhat.com/solutions/5272311
Andrea
-Original Message-
From: CentOS On Behalf Of Alessandro Baggi
Sent: Friday, July 31, 2020 11:25 AM
To: centos@centos.org
Subject: {EXTERNAL} Re: [CentOS] 8.2.2004 Latest yum update renders machine
unbootable
CAUTION: This email originated outside of BSWH; avoid action unless you know
the content is safe. Send suspicious emails as attachments to
badem...@bswhealth.org.
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.
After some hours I managed to modify another bootable partition
(containing older software) and boot it from there.
After that, I found out it is a known problem.
The main point of this message is to make people aware of the problem
and suggest admins don't run 'yum update' until they understand the
problem and have a fix at hand.
See 'UEFI boot blank screen post update' for a solution and
directions to the redhat article.
Regards
Alan
I have been punished by this bug - it is/was very nasty.
Me too. Luckily it happened on a test machine.
Sorry but seems that those packages were not tested before pushing them in the
update repo. Would be great to know what happened to the mainstream chains and
how a package like grub reached the update repo when it has serious problem
(genuine curiosity but not to blame them).
In my case, the restore procedure reported by RH in case of reboot does not
work and reports that the packages are already at the lowest version and that
the downgrade is not possibile. I don't know why.
___
CentOS mailing list
CentOS@centos.org
https://urldefense.com/v3/__https://lists.centos.org/mailman/listinfo/centos__;!!JA_k2roV-A!TZ0vdQBvu-4qe6spakWlZ8WocsAa0gEznp4zChtxB-6LsI9T5wEvaXV3KZzeSmSp4Q$
**
The information contained in this e-mail may be privileged and/or confidential, and
protected from disclosure, and no waiver of any attorney-client, work product, or other
privilege is intended. If you are the intended recipient, further disclosures are
prohibited without proper authorization. If you are not the intended recipient (or have
received this e-mail in error) please notify the sender immediately and destroy this
e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail
is strictly forbidden and possibly a violation of federal or state law and regulations. The
sender and Baylor Scott & White Health, and its affiliated entities, hereby expressly
reserve all privileges and confidentiality that might otherwise be waived as a result of an
erroneous or misdirected e-mail transmission. No employee or agent is authorized to
conclude any binding agreement on behalf of Baylor Scott & White Health, or any
affiliated entity, by e-mail without express written confirmation by the CEO, the Senior
Vice President of Supply Chain Services or other duly authorized representative of Baylor
Scott & White Health.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
RedHat is recommending not to patch.
https://access.redhat.com/solutions/5272311
Andrea
-Original Message-
From: CentOS On Behalf Of Alessandro Baggi
Sent: Friday, July 31, 2020 11:25 AM
To: centos@centos.org
Subject: {EXTERNAL} Re: [CentOS] 8.2.2004 Latest yum update renders machine
unbootable
CAUTION: This email originated outside of BSWH; avoid action unless you know
the content is safe. Send suspicious emails as attachments to
badem...@bswhealth.org.
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.
>>
>> After some hours I managed to modify another bootable partition
>> (containing older software) and boot it from there.
>>
>> After that, I found out it is a known problem.
>>
>> The main point of this message is to make people aware of the problem
>> and suggest admins don't run 'yum update' until they understand the
>> problem and have a fix at hand.
>>
>> See 'UEFI boot blank screen post update' for a solution and
>> directions to the redhat article.
>>
>> Regards
>>
>> Alan
>>
> I have been punished by this bug - it is/was very nasty.
>
Me too. Luckily it happened on a test machine.
Sorry but seems that those packages were not tested before pushing them in the
update repo. Would be great to know what happened to the mainstream chains and
how a package like grub reached the update repo when it has serious problem
(genuine curiosity but not to blame them).
In my case, the restore procedure reported by RH in case of reboot does not
work and reports that the packages are already at the lowest version and that
the downgrade is not possibile. I don't know why.
___
CentOS mailing list
CentOS@centos.org
https://urldefense.com/v3/__https://lists.centos.org/mailman/listinfo/centos__;!!JA_k2roV-A!TZ0vdQBvu-4qe6spakWlZ8WocsAa0gEznp4zChtxB-6LsI9T5wEvaXV3KZzeSmSp4Q$
**
The information contained in this e-mail may be privileged and/or confidential,
and protected from disclosure, and no waiver of any attorney-client, work
product, or other privilege is intended. If you are the intended recipient,
further disclosures are prohibited without proper authorization. If you are not
the intended recipient (or have received this e-mail in error) please notify
the sender immediately and destroy this e-mail. Any unauthorized copying,
disclosure or distribution of the material in this e-mail is strictly forbidden
and possibly a violation of federal or state law and regulations. The sender
and Baylor Scott & White Health, and its affiliated entities, hereby expressly
reserve all privileges and confidentiality that might otherwise be waived as a
result of an erroneous or misdirected e-mail transmission. No employee or agent
is authorized to conclude any binding agreement on behalf of Baylor Scott &
White Health, or any affiliated entity, by e-mail without express written
confirmation by the CEO, the Senior Vice President of Supply Chain Services or
other duly authorized representative of Baylor Scott & White Health.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
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. After some hours I managed to modify another bootable partition (containing older software) and boot it from there. After that, I found out it is a known problem. The main point of this message is to make people aware of the problem and suggest admins don't run 'yum update' until they understand the problem and have a fix at hand. See 'UEFI boot blank screen post update' for a solution and directions to the redhat article. Regards Alan I have been punished by this bug - it is/was very nasty. Me too. Luckily it happened on a test machine. Sorry but seems that those packages were not tested before pushing them in the update repo. Would be great to know what happened to the mainstream chains and how a package like grub reached the update repo when it has serious problem (genuine curiosity but not to blame them). In my case, the restore procedure reported by RH in case of reboot does not work and reports that the packages are already at the lowest version and that the downgrade is not possibile. I don't know why. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
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. > > After some hours I managed to modify another bootable partition > (containing older software) and boot it from there. > > After that, I found out it is a known problem. > > The main point of this message is to make people aware of the problem > and suggest admins don't run 'yum update' until they understand the > problem and have a fix at hand. > > See 'UEFI boot blank screen post update' for a solution and directions > to the redhat article. > > Regards > > Alan > I have been punished by this bug - it is/was very nasty. I will chase up your reference but attach my trouble shooting in case its useful to anyone John 31.07.2020 Tried, successfully, to fix the boot problems on maui (Centos 7.8) To get maui to boot at all an F32 USB stick was used and the first F32 boot option edited for every boot attempt. The changes required are summarised below. insmod part_gpt insmod ext2 linux (hd2, gpt3)/vm ... 18 ... root=/dev/sda5 iinitrd (hd2, gpt3)/initramfs ... 18 ... The above booted OK with a 90 second delay if /global & /home SSDs were not plugged in. fstab was subsequently edited and the nfs related entries temporarily commented out. //--- The following rpms were reinstalled - it is not known if this was necessary - probably not. grub2-efi-x64 efibootmgr efivar-libs fwupdate-efi shim-x64 grub.cfg was re-created but has never been used. grub2-mkconfig -o ~/grub.cfg_post_2020_07_30 cp /boot/efi/EFI/centos/grub.cfg /boot/efi/EFI/centos/grub.cfg_pre_2020_07_30 The old grub.cfg has not been over written yet as the boot does not get that far! //--- The use of efibootmgr was investigated and a corrupt looking entry removed. A new entry was also created. efibootmgr -v To list entries efiboot mgr -b 2 -B 2 To remove entry 2 say efibootmgr -t 10To increase time to edit efibootmgr -c -d /dev/sda -p1 -L ja_C7 -l '\EFI\centos\grubx64.efi' -c create new entry -d Device -p vfat partition number -L Label -l boot loader The choice for the "boot loader" option would seem to be shimx64.efi shimx64-centos.efi shim.efi grubx64.efi Which version is correct is unknown, but '\EFI\centos\grubx64.efi' was the first tried and works! The resultant entries look like this: [root@maui:/boot/efi/EFI/centos]$ efibootmgr -v BootCurrent: 0006 Timeout: 10 seconds BootOrder: 0002,0001,,0005,0006 Boot* Fedora HD(2,GPT,7c336c1e-9b29-4297-9b6f-ad7afc651a43,0x1000,0x20)/File(\EFI\FEDORA\SHIMX64.EFI) Boot0001* Fedora HD(2,GPT,7c336c1e-9b29-4297-9b6f-ad7afc651a43,0x1000,0x20)/File(\EFI\FEDORA\shimx64.efi) Boot0002* ja_C7 HD(1,GPT,751f986e-faf4-407e-9db0-caef0c8cd546,0x800,0x64000)/File(\EFI\centos\grubx64.efi) Boot0005* UEFI OS HD(1,GPT,751f986e-faf4-407e-9db0-caef0c8cd546,0x800,0x64000)/File(\EFI\BOOT\BOOTX64.EFI)..BO Boot0006* UEFI OS HD(2,GPT,7c336c1e-9b29-4297-9b6f-ad7afc651a43,0x1000,0x20)/File(\EFI\BOOT\BOOTX64.EFI)..BO Conclusion The above restored maui to a normal boot state. It is probable that the "EFI BIOS" became corrupted somehow. The file \EFI\BOOT\BOOTX64.EFI in menu entry 5 does exist but this option has not been tested yet! ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
