similar to: 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

Hello there, Dell XPS-15-9560 laptop (SSD drive, UEFI, secure boot off).. Windows 10 pre-installed, CentOS7 installed in a separate partition and running for months w/o issue. Don't know what happened but at reboot yesterday (not even booted in Windows, just rebooted), grub has disappeared, booted in Windows by default, which apparently has taken over the UEFI boot. By booting from a USB

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.

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

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

Hello Chris, On Thu, 01 Feb 2018 17:00:03 +0000 Chris Murphy <lists at colorremedies.com> wrote: > You can to use efibootmgr for this. NVRAM boot entry is what changed, not > the contents of the EFI System partition. > > efibootmgr -v > > Will list all entries and Boot Order. You need to use --bootorder to make > sure the CentOS entry is first. Interesting.. thanks

At Mon, 28 May 2018 19:30:25 -0400 CentOS mailing list <centos at centos.org> wrote: > > On May 28, 2018, at 18:25, Robert Heller <heller at deepsoft.com> wrote: > > > I tried to run efibootmgr, but it wants a model named efivars loaded, but > > there is no such module available. > > Are you not running a CentOS kernel? That module should be available.

Morning all, I have a HP Envy dual boot system (Win8 for serious stuff, i.e. Train Sim and Flight Sim) and Centos 7 for everything else. In the past I've had the occasional problem where an update on the windows side has updated the UEFI boot sequence but using efibootmgr has always fixed it. On Friday I discovered that my HDD was failing so I tried using Clonezilla to move it on to a new

On Tuesday 28 May 2019 19:52:02 Jonathan Billings wrote: > I suggest running 'blkid' and 'efibootmgr -v', and double-check that > the UUID for the CentOS boot entry matches the UUID of the EFI disk. > > You can delete and recreate the boot entry with 'efibootmgr', which > will likely solve the problem. > > It depends on the UEFI implementation, but

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

We have a working PXE setup. I've tried to adapt it to UEFI as per RHEL6 manual, but the client won't boot. Strangely, tcpdump shows that the client tries to download all files via tftp from the dhcp server rather than the tftp server (they are different). next-server is pointing to the tftp server. Any clues?

-----Original Message----- From: Stephen John Smoogen <smooge at gmail.com> Reply-To: CentOS mailing list <centos at centos.org> To: CentOS mailing list <centos at centos.org> Subject: Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable Date: Sun, 2 Aug 2020 10:57:49 -0400 On Sun, 2 Aug 2020 at 10:20, david <david at daku.org> wrote: > > <snip>

On 8/1/20 11:02 AM, Lamar Owen wrote: > ... > [lowen at 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 at localhost ~]$ Well, I sure fat-fingered that command.... let's try it again: [lowen at

hi guys I've one box where I just yesterday upgraded Centos. I wonder if that kernel upgrade process might somewhat troublesome. After that upgrade UEFI boot fails with: Failed to set MokListRT: Invalid Parameter Something has gone seriously wrong: import_mok_state() failed : Invalid Parameter Has anybody seen that? And maybe know to fix it? many thanks, L.

Hello All, updating from Centos7.3 to Centos7.4 rendered one of our laptops unbootable. EM: Failed to open \EFI\BOOT\grubx64.efi - Not Found Failed to load image \EFI\BOOT\grubx64.efi: Not Found start_image() returned Not Found How could this occur because of an update and how to fix this? What I tried is booting from centos usb, chroot to /mnt/sysimage and gave command: efibootmgr

At Mon, 28 May 2018 20:49:54 -0700 CentOS mailing list <centos at centos.org> wrote: > > On 05/28/2018 06:20 PM, Robert Heller wrote: > > The UUID in the BIOS is NOT VFAT volume. It is something completely > > different. I have no clue what it is -- it does not correspond to anything I > > can find. > > > It should be the UUID of the partition, not of

----- Original Message ----- | On Thu, Aug 18, 2016 at 11:57 AM, James A. Peltier <jpeltier at sfu.ca> wrote: | > Hi All, | > | > I have a Dell R710 that has 6x1TB in a RAID-5 configuration. | | | This is hardware RAID 5? Because it's pretty screwy how this ends up | working when using software RAID and might take additional | troubleshooting. Yes, it's a Dell R710XD |

----- Oorspronkelijk bericht ----- Van: "Adrian Jenzer" <a.jenzer at herzogdemeuron.com> Aan: "CentOS mailing list" <centos at centos.org> Verzonden: Dinsdag 9 januari 2018 16:56:57 Onderwerp: Re: [CentOS] update to Centos7.4: Failed to open \EFI\BOOT\grubx64.efi - Not Found -----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of

Am 16.06.20 um 22:04 schrieb Fabian Arrotin: > On 16/06/2020 15:06, Leon Fauster via CentOS wrote: >> Hi all, >> >> I updated a Dell XPS laptop from CentOS 8.1 (1911) to 8.2 (2004). >> >> Installed kernels are >> kernel-4.18.0-147.5.1.el8_1.x86_64 >> kernel-4.18.0-147.8.1.el8_1.x86_64 >> kernel-4.18.0-193.6.3.el8_2.x86_64 >> >>

I have a IBM System x3600 series server with UEFI. I managed to compile the xen EFI (xen-4.2-unstable.efi). The machine is currently running Ubuntu with grub2. I can see a grubx64.efi in /boot/efi/EFI/ubuntu/grubx64.efi Where should I put the xen efi ? I tried creating a efi/EFI/xen/xen-4.2-unstable.efi and added it as a boot option using efibootmgr. All I get in that case is a blank screen. I