Bootentry not updated ZFS on root

[bkw777]

Bootentry not updated ZFS on root

[bkw777]

This app does not touch the bootloader. dpkg does that, following instructions contained in .deb package files, which are written by the ubuntu mainline kernel maintainers.

We can sometimes fail to install a deb package at all, because if failing to download or failing to manage tmp/cache files robustly.

But that's all we do, either install a .deb, or not. We don't touch the system directly at all.

So can you say, did it install the kernel and fail to update grub? Or did it fail to install the linux-image*.deb package at all? The messages in the terminal window during the install should show if one or more of the .deb pacakges encountered an error.

If the package was installed and failed to add a boot entry, then the problem report goes to the package author, which is the mainline kernel maintainers. The only way I know to reach them is by their mail list.

If the package failed to install at all, that is us. We sometimes fail to download, or fail to manage the tmp/cache files properly, and sometimes fail to track errors like installing some but not all 3 or 4 related .deb packages for a given kernel version (for instance, installing the modules and headers packages but not the linux-image package). I have been improving that over time, and it does still need more work. Lately I have improvements that aren't posted yet because they are in a big refactor branch that changes way too much stuff and it's all broken right now.

Generally, with the current version, the cache is pretty good if you start over with cache deleted and do not run the app as root. Just install and run as a user and let it ask for root itself just when installing/removing a kernel.

I have no idea the state of the .deb packages support for zfs. Maybe it's a known limitation of the mainline kernel packages? I have root on xfs myself and I had to do special things to make that work myself, manually copying grub xfs modules to the EFI boot filesystem and manually fixing the grub.conf files to load that copied module. But that is all limitations of the grub2 package, not the kernel packages or this app.

[tomvanderlee]

Thanks for your answer. I think the problem is in the packages then. The package was installed successfully, it just did not upgrade grub.

[tomvanderlee]

Also judging by this post, it wouldn't have worked anyway.
https://askubuntu.com/a/1256017