May 01 10:53:13 mcp systemd[1]: boot.mount: Mount process exited, code=exited, status=1/FAILURE May 01 10:53:13 mcp systemd[1]: boot.mount: Failed with result 'exit-code'.
and your ZFS mounts confirms that bpool isn‘t mounted. How old if your installation? It seems to be from the 1st of March. My bet is that this system had a faulty boot once, and that was before we introduced https://launchpad.net/ubuntu/+source/zfs- linux/0.8.3-1ubuntu11 which dumps you to emergency state. Then, this prevented bpool to be mounted, and any kernel was populated in your root /boot instead of the bpool one. This is why you don’t load newer kenerls as grub.cfg doesn't see them. The good news is that this now can‘t be unnoticed by the user since our fix. The bad news is that there is still no way to block a boot with systemd from the generator. I start agreeing with jibel that we should « silent » all this by forcing mounting over /boot even if your /boot isn't empty. This is something I don’t rely like but it will prevent this to happen (and you might miss some kernels along the way, but that rather than never noticing not being upgrading…). What do you think JB? PS: you can meanwhile either save your system by copying /boot content over a manually mounted bpool/BOOT/ubuntu_…, copying everything there, and then emptying your /boot (after unmounting /boot/efi and /boot/grub). Final version doesn‘t have that issue at least (unnoticeable state which can screw up your system) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876440 Title: Kernel no longer getting updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
