After Update unable to boot: Mounting /boot/efi & proc-sys-fs-binfmt_misc fails

Ask Fedora
, , ,
1

Hello there, I need some help.

Yesterday, I did a normal offline update, but after completing the update it would not boot.

Rebooting (and checking the logs while it does) show that there is suddenly a warning about AMD Overdrive (even though I did not even turn it on?) and mounting seemed to fail. I first tried the other grub entries (with older kernels), but the outcome was the same.

So I booted into rescue mode and looked at the output of journalctl -xb. I went through the whole thing and found the following parts that seemed to indicate failure:

systemd-modules-load[955]: Failed to find module i2c-dev
systemd-modules-load[955]: Failed to find module fuse
systemd-modules-load[955]: Failed to find module i2c_dev
systemd-modules-load[955]: Failed to find module msr
systemd-modules-load[955]: Failed to find module i2c-devel
systemd-modules-load[955]: Failed to find module ntsync

systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway

systemd[1]: boot-efi.mount: Mount process exited, code=exited, status=32/n/a
systemd[1]: boot-efi.mount: Failed with result exit-code
systemd[1]: Failed to mount boot-efi.mount - /boot/efi

systemd[1]: proc-sys-fs-binfmt_misc.mount: Mount process exited, code=exited, status=32/n/a
systemd[1]: proc-sys-fs-binfmt_misc.mount: Failed with result exit-code
systemd[1]: Failed to mount proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System
systemd-binfmt.service: Failed to check if /proc/sys/fs/binfmt_misc/ is mounted: No such device
systemd[1]: systemd-binfmt.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: systemd-binfmt.service: Failed with result exit-code
systemd[1]: Failed to start systemd-binfmt.service - Set Up Additional Binary Formats

I think the main issue is that /boot/efi can’t be mounted, but I am not sure and also don’t know why this suddenly happened.

So my question is: What to do? Is this fixable or should I go for recovering my /home and reinstall Fedora?

(Mentioning, since it might be relevant: Before I could enter rescue mode, I had to set my root account using live media. However, the USB stick, that I also originally used to install Fedora, seemed to be corrupted, so I had to get a new one to be able to set my root account.)

2

This may be a side-effect rather than the cause of the issue.

It’s not actually necessary to mount /boot/efi during normal operation of the system. Its purpose is to allow GRUB to be loaded, and you obviously got past that step.

This Red Hat support article (free registration required to read the whole thing) suggests that it can occur from overly strict SELinux settings.

3

Thank you, that helped me solve the issue.

Running getenforce returns Enforcing, so I edited /etc/selinux/config for it to be permissive instead. Next reboot worked without any failures. The update, which broke my system the first place, was not applied, so I redid it and it worked this time without any issues.

1 Like