Question: I have a CentOS 7 VPS. I have not yet had this problem -- I have
not yet done an update since this problem showed up. Will this problem affect
my server? *I* don't have access to the bare metal -- it is a cloud VPS I am
renting.
At Sun, 2 Aug 2020 14:21:58 +1200 Alan McRae ,
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
Questions re this statement in the ZDNET article --
"In all cases, users reported that downgrading systems to a previous
release to reverse the BootHole patches usually fixed their problems."
A previous release of what? GRUB2
So that's my first question.
Second. I'm assuming the the
My system was happy UNTIL I rebooted. ThenBZZT!!!
On Sat, Aug 1, 2020, 17:02 Schatzi Olsen wrote:
> And for whatever reason, both my centos 7 and 8 survived this apparently
> with flying colors. Actually, this is out of character for how fate has
> been dealing the cards recently.
>
>
And for whatever reason, both my centos 7 and 8 survived this apparently
with flying colors. Actually, this is out of character for how fate has
been dealing the cards recently.
I'm very leary about rebooting either, now, though.
On Sat, Aug 1, 2020 at 12:50 PM Kay Schenk wrote:
> Totally
Mike --
Thanks for the clarification and more information.
___
Sent from MzK's phone.
On Sat, Aug 1, 2020, 15:42 Mike McCarthy, W1NR wrote:
> It appears that it is affecting multiple distributions including Debian
> and Ubuntu so it looks like the grub2 team messed up. See
I use debian buster on my old notebook, an asus f3ja and I have not grub
throuble. I try a virtual mschine with testing and unstable, and both boot
regularly
Il dom 2 ago 2020, 00:42 Mike McCarthy, W1NR ha scritto:
> It appears that it is affecting multiple distributions including Debian
> and
Another ZDNet story on the issue:
https://www.zdnet.com/article/red-hat-enterprise-linux-runs-into-boothole-patch-trouble/
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
" UEFI-related updates have had a history of making devices unusable, and
vendors will need to be very cautious."
https://eclypsium.com/2020/07/29/theres-a-hole-in-the-boot/
The fix for this vulnerability is complex and the fix will have different
results on different machines. The volunteers
It appears that it is affecting multiple distributions including Debian
and Ubuntu so it looks like the grub2 team messed up. See
https://www.zdnet.com/article/boothole-fixes-causing-boot-problems-across-multiple-linux-distros/
Mike
On 8/1/2020 6:11 PM, Marc Balmer via CentOS wrote:
>
>
>> Am
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 август
> Am 01.08.2020 um 23:52 schrieb Leon Fauster via CentOS :
>
> Am 01.08.20 um 23:41 schrieb Kay Schenk:
>> Well misery loves company but still...just truly unfathomable!
>> Time for a change.
>
>
> I can only express my incomprehension for such statements!
>
> Stay and help. Instead running
Am 01.08.20 um 23:41 schrieb Kay Schenk:
Well misery loves company but still...just truly unfathomable!
Time for a change.
I can only express my incomprehension for such statements!
Stay and help. Instead running away or should I say out of the
frying pan and into the fire? :-)
--
Leon
Well misery loves company but still...just truly unfathomable!
Time for a change.
___
Sent from MzK's phone.
On Sat, Aug 1, 2020, 13:04 david wrote:
> At 12:50 PM 8/1/2020, Kay Schenk wrote:
> >Totally and completely on my HP microfiber. Wouldn't get past anything to
>
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
At 12:50 PM 8/1/2020, Kay Schenk wrote:
Totally and completely on my HP microfiber. Wouldn't get past anything to
even get me into the grub menu. NOT AMUSED!
___
Kay Schenk
I was going to confirm the same, but the system that became
unbootable was my mail system :-(
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
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
Totally and completely on my HP microfiber. Wouldn't get past anything to
even get me into the grub menu. NOT AMUSED!
___
Kay Schenk
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On 7/31/20 4:40 PM, Bee.Lists wrote:
However the service isn’t starting because the ownership of the parent
directory, pgbouncer:pgbouncer results in some permissions issues:
2020-07-31 04:58:34.089 EDT [3682] FATAL could not open pidfile
'/var/run/pgbouncer/pgbouncer.pid': Permission
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 г.
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
> >
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
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,
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
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
Hello
I take backups while virtual machines are running live. For this,
first I takes snapshot. Then I back up the original disk. But when I
look at the snapshot list (1595157757,1595162592). I see that it is
passive. I cannot delete them either.
What would be the reason ?
Name
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
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
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.
>
>
30 matches
Mail list logo
