CentOS7 not booting after “yum update” mokListRT fails

bootcentos7grub2

I updated CentOS 7 via yum update

Didn't know about shim and mokutils so didn't exclude that from yum.

Now I can't boot it, I can recover the files on it using another live distro (e.g. ubuntu), but when I try to run the rescue mode from a CentOS USB key it gives me the same error:

Failed to set MokListRT: Invalid Parameter
Something has gone seriously wrong: import_mok_state()
failed: Invalid Parameter

Typical solution found is to:

cp grubx64.efi shimx64.efi

But the folder in which this file should be ( /boot/efi/EFI/centos ) is completely empty (actually, /boot is empty itself, like not even grub is installed)

Anything else that I can try?

I can at least retrieve the files… but nothing more than that.

Best Answer

As noted in the CentOS bug report, this was fixed with the following updates:

mokutil.x86_64 15-2.el7.centos updates
shim-ia32.x86_64 15-2.el7.centos updates
shim-unsigned-ia32.x86_64 15-2.el7.centos updates
shim-unsigned-x64.x86_64 15-2.el7.centos updates
shim-x64.x86_64 15-2.el7.centos updates

Related Solutions

Ubuntu server, gpt partition table, mdadm, grub boot fail

Solution is to use a bios_grub partition, which is not the same as the /boot partition.

By default the bios_grub partition is 1MiB, and it must be flagged bios_grub. Mine is the first partition on my disk. If your partition 2 is actually /boot as parted suggests, that would not be correct and you should make another 1MiB partition.

With GPT and GRUB2 the minimum filesystem has three partitions: bios_grub, root, swap. (not perfectly sure swap is required)

Why does grub fail to boot after simply running "grub-install"?

Unknown... You'd think it wouldn't modify anything if it says clearly it cannot embed so it can't work.

Why does it say "file not found"?

/vmlinuz is a symlink that uses the boot partition, and the boot partition is corrupt. The bios_grub code was written on top of its ext3 structure. This probably meant that /boot was not mounted, and the grub files seen there were actually on the root system, which didn't contain the kernel.

Why doesn't grub want to install without this setting I set with parted

A GPT partition table has no space for a bootloader, unlike MBR. So a specific partition must be created to hold the boot code. Before running "grub-install", specify this partition with the command:

    parted /dev/sda set 1 bios_grub on

I thought all I needed was a separate /boot. How does the Ubuntu CD installer install it without the bios_grub setting?

This requirement seems to be all that is needed for the Ubuntu installer, but it creates an unstandard system which is broken easily.

When GRUB says "This GPT partition label has no BIOS Boot Partition", it means the bios_grub partition, not /boot.

Python-augeas, yum update error in CentOS7

Setting /usr/lib/python2.7/site-packages/ to have perms 777 is not a good solution. I am also suspicious that this was the fix because by using sudo you are running as superuser and should have permissions on that directory no matter what (excluding more complicated ACLs).

This error can also happen if the python module was installed a different way. Is the module in pip list? If yes, then running sudo pip uninstall augeas before installing it with yum should resolve the problem.

You don't want to mix package managers if you can help it.

Best Answer

Related Solutions

Ubuntu server, gpt partition table, mdadm, grub boot fail

Python-augeas, yum update error in CentOS7

Related Topic