Newly upgraded kernel not being used on reboot

  • Hi,


    I have recently upgraded to omv 8. Except a temporary missing zfs.ko.xz issue everything else went smoothly.


    Then I experience an issue on kernel upgrades: when a new Debian kernel is available for upgrades, omv will prompt for a reboot. But after reboot it was still using the previously used old kernel instead of the new kernel. I need to manually select the new kernel and reboot for the new kernel to be used. IIRC this was not the case in my previous omv 7 installation.


    I did some quick digging, and found that in "/etc/default/grub", it sets "GRUB_DEFAULT=saved" now, which explains the behavior.


    I wonder whether this is the intended behavior for omv 8? I think this kind of defeats the purpose of prompting for a reboot after a kernel upgrade because it will still use the older kernel :/


    EDIT: grammar

  • I get the same reboot prompts after a kernel "upgrade."


    But in my case it is explainable because I am running the pve kernel and the "upgrade" kernels are the ordinary but unused amd64 kernels.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    Edited once, last by gderf ().

    • Official Post

    If you have the kernel plugin installed and you set a kernel to boot, it will stay on that kernel. This is why I added an "Unset default kernel" button in the latest release of the kernel plugin.

    omv 8.2.6-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.2.4 | compose 8.1.12 | cterm 8.0 | borgbackup 8.1.9 | tempmon 8.0.3 | mergerfs 8.0.1 | scripts 8.0.3 | writecache 8.1.10


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • If you have the kernel plugin installed and you set a kernel to boot, it will stay on that kernel. This is why I added an "Unset default kernel" button in the latest release of the kernel plugin.

    Ah, I guess that's why: when I first encountered the issue, I manually "set boot" on the new kernel, which probably changed GRUB_DEFAULT to saved. Clicking "Unset default kernel" changed it back to 0. I guess it'll work for future upgrades.


    It would still be great to document "Unset default kernel" better to make the intention clearer (e.g. "This will use the highest versioned kernel on next boot"). Thanks again!

    • Official Post

    It would still be great to document "Unset default kernel" better to make the intention clearer

    It takes time for the folks who maintain the docs to do that. I am curious what you thought the button does? To me, it is doing the opposite of setting a default kernel.

    omv 8.2.6-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.2.4 | compose 8.1.12 | cterm 8.0 | borgbackup 8.1.9 | tempmon 8.0.3 | mergerfs 8.0.1 | scripts 8.0.3 | writecache 8.1.10


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!