Failing to boot after update (can't mount /efi)

General system Newbie
21

It looks like you deleted /etc/kernel/cmdline at some point.

Can you provide the contents of /etc/fstab in text format?

22

If so, that was an accident. And, I have no idea how I could have done that or where. I haven’t touched configs in a long while.

Here is fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=AA36-F841                            /efi      	vfat    defaults,noatime 0 2
UUID=564916d1-466c-468d-ad2e-163c047b1f9b /              ext4    defaults,noatime 0 1
23

In at least two of the screenshots, there are complaints about a BIOS “bug”. One of the screenshots says “latencies out of order” which might indicate a hardware problem. I don’t know, just trying to help…

24

I started seeing that when these issues came. Before the update I didn’t have them, when I rebooted I started seeing them.

I’m also afraid that it might be something hardware related. Computer is not that old though.

EDIT: Read up a bit on this and it seems this comes when there’s an error with the firmware. Such as mine where the kernel can’t be found. Does not seem to be hardware related.

25

I have to go to a meeting but after that, I should be able to build you a working kernel options line.

26

Edit one of those entries. Change the options line to read like this:

options    nvme_load=YES rw root=UUID=564916d1-466c-468d-ad2e-163c047b1f9b

Delete /etc/kernel/cmdline if it exists.

Now reboot. Select the entry you modified from the boot menu.

If it works, run sudo reinstall-kernels to fix all your entries.

27

My goodness!
That seems to have solved it. Ran the reinstall-kernel and it still works fine. I can now boot both mainline and LTS kernel.
Thanks a lot!

Any idea why this happened? Why were there so much crap in the options line?

28

That happens if you delete /etc/kernel/cmdline and then run reinstall-kernels/kernel-install from a chroot while booted off the ISO.

That probably wasn’t the original problem. It likely was something created while trying to solve the initial problem.