Updates fail with Proxmox kernel 6.14

1st Official Post

    Hello everyone,


    There was another major update of OMV7 today. I installed it, restarted the PC, and it wouldn't boot. Then I see that it can't load Proxmox kernel 6.14. It says the kernel isn't installed.


    If I select Proxmox kernel 6.11-2 in the boot menu, I can boot with it.


    I've now tried uninstalling 6.14 via the web GUI. It also seems to be gone, but it's still in the blue startup screen, blocking my boot, and causing an error. I've also cleaned up GRUB.




    What went wrong with this new update that it doesn't work anymore?


    Thank you for your help.


    Regards,

    Mic.

    • Official Post

    update-grub runs after installing or removing a kernel. If the grub menu isn't updating, it is likely updating grub on the wrong drive. Hard to say why your system is updating the wrong drive. Did you add an old boot drive to your system?

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.6 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.5 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    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!

    • Official Post

    6.14 is still the test kernel.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.6 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.5 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    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!

    Similar experience, but I am not disappointed since my intent, was not to try to install it!.

    I saw it was getting installed during the update. Then when I rebooted REFind tried to boot I think from boot/efi until I changed the icon to boot to /efi/EFI and of course 6.14 is not to be found in the plugin Kernel list. I jjust had to compile again NVIDIA in the 6.8.11 kernel.

    • Official Post
    Quote from Nefertiti

    I saw it was getting installed during the update

    What was getting installed?

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.6 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.5 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    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!

    Quote from Nefertiti

    Similar experience, but I am not disappointed since my intent, was not to try to install it!.

    I saw it was getting installed during the update. Then when I rebooted REFind tried to boot I think from boot/efi until I changed the icon to boot to /efi/EFI and of course 6.14 is not to be found in the plugin Kernel list. I jjust had to compile again NVIDIA in the 6.8.11 kernel.

    NVIDIA not work fine on promox 6.14 and probably broke my install: I Lose my grub menu and only have Memtest to boot

    Quote from ryecoaaron

    update-grub runs after installing or removing a kernel. If the grub menu isn't updating, it is likely updating grub on the wrong drive. Hard to say why your system is updating the wrong drive. Did you add an old boot drive to your system?

    I did all this stuff. Nothing worked out. On the command line it is removed but in start screen it is still thete. OMV7 does something strange her.

    • Official Post
    Quote from Mic2024

    I did all this stuff. Nothing worked out. On the command line it is removed but in start screen it is still thete. OMV7 does something strange her.

    Did all what stuff? I didn't give you anything to try. And you didn't answer if you added a drive that may have previously been a boot drive. OMV does nothing with grub and didn't cause this. A grub package update might have detected the wrong boot drive if there is more than one and caused this.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.6 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.5 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    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!

    • Official Post
    Quote from Nefertiti

    I meant 6.14 was in the list of update to be performed

    Why is 6.14 installed if you don't use it? I really shouldn't have added 6.14...

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.6 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.5 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    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!

    Hello,


    The problem seems to be a change in GRUB. I actually have two SATA SSDs with two almost identical OMV systems connected to my mini PC via USB. The idea is to have a backup system that I can automatically boot from if the main system fails.


    So far, the PC has always booted from System 1 without any problems, even when System 2 was connected. Now, when both SATA SSDs are connected, it suddenly can't find the current Proxmox kernel. Strangely, I can boot from the old Proxmox kernel 6.11-2.


    When I disconnect the second system SSD the Kernel 6.14 is found properly.


    Although this may seem like a somewhat strange configuration, I would like to keep it. So how do I fix the problem? Or can you provide another update that fixes the problem? And I want to use 6.14.


    Thank you very much!


    Regards,

    Mic.

    Quote from ryecoaaron

    Why is 6.14 installed if you don't use it? I really shouldn't have added 6.14...

    Because when they are some update in OMV | Update Management | updates I cannot pick and chose.

    Actually I found 6.14 in the plugin in download menu, sorry it was what I meant.

    So is not installed but available.

    • Official Post

    You won't see updates for 6.14 in the Update Management window if 6.14 isn't installed. If you are having a grub issue like the OP, then it is possible the 6.14 kernel doesn't show in the kernel plugin list since it is reading from /boot/grub/grub.cfg.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.6 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.5 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    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!

    • Official Post

    What is the output of: dpkg -l | grep proxmox

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.6 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.5 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    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!

    I tried uninstalling kernel 6.14, then I cleaned up and rebuilt Grub (sudo update-grub). I thought it was the 6.14 kernel, but I wanted to uninstall it, but it kept appearing in the blue boot menu. Strangely, the PC boots when I manually select kernel 6.11 in the blue boot menu.


    A brief summary of what I tested:

    - Adjusted GRUB configuration: Attempted to explicitly specify the correct boot partition using the UUID.

    - Rebuilt GRUB (update-grub): To ensure the changes were applied.

    - Checked the boot order in UEFI: In case GRUB doesn't recognize the correct SSD.

    - Manually started GRUB: Attempted to load the correct partition and kernel via the GRUB console.

    - Analyzed kernel update: Checked if the OMV update with the Proxmox headers caused any problems.

    - Switched back to Proxmox 6.11: As a test, to check if the older kernel still works.

    - Reinstalled GRUB (grub-install /dev/sda): To ensure the bootloader is set correctly.


    I've now restored my old backup (created on Sunday before performing the updates) and the system boots with both SSDs connected.


    The second SSD has always been there. I didn't plug it in or add it later. If you want to recreate the scenario, set up an OMV7 installation with Proxmox 6.14 (and possibly with ZFS support). Clone the SSD to an identical second SSD (two USB sticks might work). Then reboot the system.


    PS.: We should not mix-up two topics here. 😉

    • Official Post
    Quote from Mic2024

    We should not mix-up two topics here

    Thanks but I can handle the mod duties. I am trying to figure out what the real issue is here and if everyone is having the same problem. At least two of you do but it isn't caused by the 6.14 kernel. There must have been a grub upgrade that install grub on a second drive.

    Quote from Mic2024

    I thought it was the 6.14 kernel, but I wanted to uninstall it, but it kept appearing in the blue boot menu

    That means you have grub installed on two drives.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.6 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.5 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    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!

    Quote from ryecoaaron

    What is the output of: dpkg -l | grep proxmox

Participate now!

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

Register Yourself Login