Using backport kernel by omv-extra

  • Hello,

    I'm using omv since (I think) V 2.x and I allways use the backport kernel.

    But on both of my OMV 5 systems I can't get it up to run. Or better: On one of them it dosn't work any more ... That Server is up to 5.9.0-0.bpo.2-amd64, but I think it's not the Last one.


    The other Server was upgraded yesterday from omv 4 to 5

    (By using this deb https://github.com/dleidert/openmediavault-upgrade/tree/4 )


    The switch in omv-extra config for "backport" is set on both server.


    In the File: /etc/apt/sources.list.d/openmediavault-kernel-backports.list

    Is this Adress: deb http://httpredir.debian.org/debian buster-backports main contrib non-free

    On both server ...


    I get stuck ...


    I'm looking for some help or hints to get it done by my self

    Here in this forum I found a hint for a Howto for that problem, but I can't find it, probably searched for the wrong keywords ;)


    Anyway, Thanks for reading!


    Greetings

    Turbo

  • macom

    Hat das Thema freigeschaltet.
  • 1) If you used my scripts, you'll have to remove the APT::Default-Release entry in /etc/apt/apt.conf.

    2) What does apt-cache policy linux-image-`dpkg --print-architecture` on both systems say?

  • Hello dleudert,

    1) If you used my scripts, you'll have to remove the APT::Default-Release entry in /etc/apt/apt.conf.

    Code
    cat /etc/apt/apt.conf
    APT::Default-Release "buster";

    That's the only entry in there, is that correct?

    So delete the hole file, or yust make it empty?

    Zitat

    2) What does apt-cache policy linux-image-`dpkg --print-architecture` on both systems say?


    Ok, here is the Output you want to see:

    Ok the Data, I posted above are from the Server it was upgraded whith your script. Btw. Thank's for that it worked great!


    The other one was alredy set up in version 5 and here are the data from there:

    There ist no /etc/apt/apt.conf!

    Code
    apt-cache policy linux-image-`dpkg --print-architecture`
    linux-image-amd64:
      Installed: (none)
      Candidate: 5.10.13-1~bpo10+1
      Version table:
         5.10.13-1~bpo10+1 500
            100 http://httpredir.debian.org/debian buster-backports/main amd64 Packages
         4.19+105+deb10u9 500
            500 http://deb.debian.org/debian buster/main amd64 Packages
            500 http://security.debian.org/debian-security buster/updates/main amd64 Packages

    But now, I'm unsure what to do ...

    Would you please give me a hint?


    Thank's!


    Greetings,

    Turbo

    • Offizieller Beitrag

    Would you please give me a hint?

    apt-get -t buster-backports install linux-image-amd64

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    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!

  • Good Morning ryecoaaron,

    apt-get -t buster-backports install linux-image-amd64

    Ok I tried on the upgraded server and it worked! Thank you!

    Now I'm up to:

    5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) x86_64


    Do I have to do now something more to get it work automaticly?

    Or do I have to do it now all the time manualy?


    Did I something wrong on that?

    I have to upgrade 3 more server ;)


    Thank's again for Help!


    Geetings,

    turbo

  • Do I have to do now something more to get it work automaticly?

    No. It shall get updates to this kernel package from backports now. But if you want to install another package from backports, you'll have to do the same thing, except you remove the APT::Default-Release entry (you can remove the file as well if it is empty afterwards). Then all repositories will have a pin priority of 500 (== are equal). With this setting though, the repositories get different pin-priorities and backports have the lowest with 100 (see the number in front of the URL when using apt-cache policy <package>). To understand what you did, please read about pinning (man apt_preferences or the Debian Wiki).

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!