[Solved] Regular update resulted in kernel panic

    Hey guys,


    I just ran a regular upgrade on my OMV7 system. I haven't updated my system for some time so it was due. The update ran without producing any apparent errors. I was asked to apply it on the workbench and rebooted my system. So far, so good. It came up again. I went back into the upgrade section of the web-UI. It showed 7 more updates, so I applied them again. This time the upgrade failed posting some 505 error. As I cannot debug through the Web-UI, I sshed into my server and ran omv-upgrade instead. I could see apt-get update fail, as some public keys were missing for my Coral TPU. I added the keys and ran omv-upgrade again. It again failed, this time on different sources. I noticed that things started to look strange. It seemed that the sources were a mix of bookworm and sandworm references. So I thought that something was wrong with the configuration and that it may be fixed by a controlled reboot. When I rebooted then, the server was dead.


    I connected keyboard and monitor to the server and saw that it ran into a kernel panic. I don't think I ever saw this with OMV. Luckily I was able to boot an old kernel, which allowed me to recover the system. But how do I take it from here? I'd appreciate any advice on how to move forward...


    Edit: For completion:

    I'm now running the (old) Kernel: Linux 6.1.0-32-amd64

    The Kernel: 6.12.12+bpo-amd64 panicked.

    My OMV version is 7.7.3-1.

  • m4tt0

    Added the Label resolved

  • m4tt0

    Added the Label OMV 7.x

  • m4tt0

    Changed the title of the thread from “Regular update resulted in kernel panic” to “[Solved] Regular update resulted in kernel panic”.

    Figured it out: The problem was indeed caused by the Coral Edge TPU drivers, which interrupted the omv-upgrade process and prevented the creation of a proper kernel.


    I had to:

    • Remove all coral TPU-related references from the apt-sources
    • Purge the gasket-dkms and the libedgetpu1-std packges from my system
    • Run omv-aptclean
    • Run omv-upgrade

    After rebooting my system the 6.12.12 kernel worked flawlessly. There was someone with a similar problem caused by an NVIDIA driver, which helped me solve it. In any case, the problem is not related to OMV. Maybe this helps others...

    Hello! I ran into the same problem - today I installed Open Media Vault 7. I have no Coral driver installed but still after following the steps on their website i received the error:

    Error! Bad return status for module build on kernel: 6.12.12+bpo-amd64 (x86_64)

    Consult /var/lib/dkms/gasket/1.0/build/make.log for more information.

    dpkg: error processing package gasket-dkms (--configure):

    installed gasket-dkms package post-installation script subprocess returned error exit status 10

    Processing triggers for libc-bin (2.36-9+deb12u10) ...

    Errors were encountered while processing:

    gasket-dkms

    E: Sub-process /usr/bin/dpkg returned an error code (1)

    Quote from m4tt0

    Figured it out: The problem was indeed caused by the Coral Edge TPU drivers, which interrupted the omv-upgrade process and prevented the creation of a proper kernel.


    I had to:

    • Remove all coral TPU-related references from the apt-sources
    • Purge the gasket-dkms and the libedgetpu1-std packges from my system
    • Run omv-aptclean
    • Run omv-upgrade

    After rebooting my system the 6.12.12 kernel worked flawlessly. There was someone with a similar problem caused by an NVIDIA driver, which helped me solve it. In any case, the problem is not related to OMV. Maybe this helps others...



    I followed the provided steps, but I'm still hitting the same issue.

    Solutions identified for this Coral TPU Driver/Linux Kernel issue are:

    1. Build the updated driver yourself
    2. Install the pre-built Debian driver with fixes for later kernel versions. I'm tracking this repo for that purpose: https://github.com/feranick/ga…ver/releases/tag/1.0-18.2 (would be helpful if someone could verify this works and provide step by step instructions)
    3. Revert Kernel to previous version using OMV UI and Kernel Plugin: https://github.com/google-cora…2#issuecomment-2801258244

Participate now!

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

Register Yourself Login