I installed the recent update and followed the reboot process. Now, the system doesn’t boot and gets stuck on falling back to noaveu drivers (nvidia kernel module missing). When I go to the emergency mode, the following shows up. I have never had problems with updating before, that’s my first time 
It is terrible that it locks you out from the recovery console like that. You’ll probably have to use a Live CD and run fsck on your ESP (the partition that is mounted at /boot/efi).
I ran the command and it looks like no errors were found.
What does the fstab file on your root filesystem look like? Does the UUID of the ESP match what is listed in your fstab? Better yet, can you extract the fstab from your initramfs and make sure that it looks correct?
The “easiest” workaround might be to add init=/bin/bash to your kernel parameters and then generate a new initramfs that can mount the ESP to /boot/efi.
P.S. If you generate a new initramfs, be sure to set the root account password first so that you will be able to get into rescue mode in the future if you need to.
Edit: It looks like the fstab isn’t stored in the initramfs. In that case, you might be able to fix things from your Live CD just by editing the fstab on your root filesystem.
Edit2: As a workaround to get your system booted, you could add nofail to the list of mount options on the line that contains /boot/efi in /etc/fstab. That is just a temporary workaround though. You’ll need to get /boot/efi mounting correctly in order for things like firmware updates to work again.
It looks like I misplaced a disk number.
Here is the result of fsck on EFI partition:
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
65:01/00
- Copy original to backup
- Copy backup to original
- No action [1237q]? |
Pick option 3. Then it should prompt about a “dirty bit” and you should select the option to clear it. Then see if your system will boot.
Didn’t work, freezes on the same place.
If I run the command again after a reboot, it shows the same error.
I will try going the “easiest” route for now.
The worst thing is that it happened right before the start of a semester))
1 Like
I put easiest in quotes because it may not be all that easy. You’ll have to remount the rootfs in read-write mode and also manually mount /boot and /boot/efi before running the dracut command to regenerate your initramfs. Good luck. I don’t know whose idea it was to lock the root account like that instead of prompting the user to set a password for it during the initial system install, but IMO, that was a bad design choice. 
1 Like