Re: 8.2.2004 Latest yum update renders machine unbootable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



RedHat is recommending not to patch.
https://access.redhat.com/solutions/5272311

Andrea

-----Original Message-----
From: CentOS <centos-bounces@xxxxxxxxxx> On Behalf Of Alessandro Baggi
Sent: Friday, July 31, 2020 11:25 AM
To: centos@xxxxxxxxxx
Subject: {EXTERNAL} Re:  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 BadEmail@xxxxxxxxxxxxx.


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@xxxxxxxxxx
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@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos




[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]


  Powered by Linux