`apt upgrade` fails with "Error! Bad return status for module build on kernel: 6.12.9+bpo-amd64 (x86_64)"

1st Official Post

    I see that there are other similar threads to my issue, but none of them seem to quite fit my situation and/or I don't fully understand them.

    When I run `apt upgrade`, I get this output:

    I just recently upgraded from omv6 to omv7.

    Please let me know what other information I can provide for troubleshooting! Thanks

    • Official Post

    Your gasket kernel module doesn't build on the 6.12 kernel. I would install the kernel plugin and try the 6.8 or 6.11 proxmox kernel.

    omv 7.7.9-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.6 | compose 7.6.6 | cterm 7.8.5 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.2


    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 ColdShoulderMedia

    That's my Coral gasket driver?

    yes


    Quote from ColdShoulderMedia

    Attempting to install "openmediavault-kernel 7.1.4" via the gui results in the same error from the original post.

    Edit, on reboot my system no longer boots.

    You should've removed the 6.12 kernel with the kernel plugin


    You will have to plug a keyboard and monitor into the system and pick the 6.1 kernel to boot from.

    omv 7.7.9-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.6 | compose 7.6.6 | cterm 7.8.5 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.2


    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 ColdShoulderMedia

    I couldn't install the kernel plugin.

    Why?

    omv 7.7.9-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.6 | compose 7.6.6 | cterm 7.8.5 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.2


    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 ColdShoulderMedia

    Attempting to install "openmediavault-kernel 7.1.4" via the gui results in the same error from the original post.

    You needed to remove the 6.12 kernel since your module won't compile under it.

    omv 7.7.9-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.6 | compose 7.6.6 | cterm 7.8.5 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.2


    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!

    Thanks for the info! I do at least know OMV is Debian. :)

    `apt-get --purge remove` wasn't suggested as a solution, so I didn't want to go ruining things further.


    There was one issue I had after setting things back up, after pointing the compose plugin at my compose shared folder, it wasn't able to "see" my previous compose files and when I created a new portainer compose, it rewrote the previous portainer.yaml. Is there something that could cause this issue?

    • Official Post
    Quote from ColdShoulderMedia

    There was one issue I had after setting things back up, after pointing the compose plugin at my compose shared folder, it wasn't able to "see" my previous compose files

    This is expected. The plugin doesn't look at the filesystem for compose files. It looks at the OMV database. There is an option to import compose files from the filesystem if they are in the format created by the plugin.


    Quote from ColdShoulderMedia

    and when I created a new portainer compose, it rewrote the previous portainer.yaml.

    Also expected since the the OMV database is the source of truth. This is how almost all of OMV works.

    Quote from ColdShoulderMedia

    Is there something that could cause this issue?

    purging the plugin deletes the omv database and would look like this.

    omv 7.7.9-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.6 | compose 7.6.6 | cterm 7.8.5 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.2


    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!

    Like 1

    Ouch. I see what I got hit with. Also using Coral TPU. Thank you for the link!


    So do we have to wait for Google to update things? That github link with steps to build it ourselves feels a bit out of scope for me.

    yestothis I was looking at the manual build for my M.2 Coral as well, but I was also intimidated and concerned about stability. I'm using a CPU decoder for now.

    I've decided to just go ahead and buy the USB Coral ($60US) since Frigate has USB drivers built into the container. The new USB version is in the mail now, I'll post an update if it's successful.

    When/If google updates the M.2/PCIe drivers, I'll likely switch back? Please let me know how you handle the issue, I would love to get more input on the situation.

    I got a dual edge TPU so I really don't want to switch out 2 accelerators for a USB solution. I think the way I'll try to go about it is to downgrade to last working kernel. But I'm now unable to install/re-install the older working gasket driver because it keeps trying to pull the new kernel update.


    Is there a way to go back to the previous Linux 6.1.0-30-amd64 and not have the gasket installer try to pull the newer kernel? I'm already using the Kernel OMV plugin to stay on 6.1.0-30, but unsure of how to pin the gasket install to stay on this one too I guess.

    Quote from yestothis

    Is there a way to go back to the previous Linux 6.1.0-30-amd64 and not have the gasket installer try to pull the newer kernel? I'm already using the Kernel OMV plugin to stay on 6.1.0-30, but unsure of how to pin the gasket install to stay on this one too I guess.

    Sorry, I wish I knew, probably worth making a new thread for this specific question.

    I received the USB TPU and after changing my compose to pass USB and my frigate config for a usb coral detector, it's working just fine.

    Quote from ryecoaaron

    Your gasket kernel module doesn't build on the 6.12 kernel. I would install the kernel plugin and try the 6.8 or 6.11 proxmox kernel.

    Following ryecoaaron instructions from 2nd post, installed the kernel module and retried everything I've done so far on the 6.11 proxmox.... other than manually load the module using sudo modprobe apex (and then add it to /etc/modules), everything worked

    Here's the full list of commands:

    Code
    git clone https://github.com/google/gasket-driver.git
cd gasket-driver/
sudo apt-get install devscripts build-essential lintian debhelper 
debuild -us -uc -tc -b
cd ..
sudo dpkg -i gasket-dkms_1.0-18_all.deb

    My process for resolving this started with disabling backports - since that's where the new kernel was coming from to begin with.

    1. Disable backports via Kernel in OMV UI
    2. Set old kernel to boot via Kernel in OMV UI
    3. apt clean
    4. apt update
    5. apt upgrade
    6. apt autoremove (should remove the unconfigured kernels that were broken)

    TODO: explore/test using pre-built .deb here with backports are enabled: https://github.com/feranick/gasket-driver/releases

Participate now!

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

Register Yourself Login