Problem with OMV 7.0.4-1 (Sandworm) update

  • Hello! I have a problem updating the OMV system. After clicking, check for updates via webgui and cmd (sudo apt update). I'm getting strange errors that I don't understand. I use my OMV via webgui all the time and everything has always updated correctly until today. I don't know if it's a general fault and the servers from which OMV wants to download updates are not working or what's going on? Thank you very much in advance for helping me solve the problem.



  • chente

    Hat das Thema freigeschaltet.
    • Offizieller Beitrag

    The repository 'http://apt.armbian.com buster Release' does not have a Release file. in /usr/share/openmediavault/engined/rpc/apt.inc:255

  • I guess it worked because when checking for updates no more errors appear in webgiu or in the cmd console.


    In the file "/etc/apt/sources.list.d/armbian.list" I untag the following phrase:


    Code
    deb http://apt.armbian.com bullseye main bullseye-utils
    • Offizieller Beitrag

    Just change bullseye to bookworm

    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!

    • Offizieller Beitrag

    For now I have untagged "deb http://apt.armbian.com bullseye main bullseye-utils"


    If there are any problems with updates, I will do as you write and change the names from bullseye to bookworm

    I assume "untagged" means commented out? If so, you should not do that because you will not get an armbian updates like kernels. Your system is bookworm based on the other repos and changing to bookworm will fix the issue of the bullseye repos not being available.

    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!

  • This is probably not good practice. Because how I changed


    Code
    deb http://apt.armbian.com bullseye main bullseye-utils


    on


    Code
    deb http://apt.armbian.com bookworm main bookworm-utils


    this gives me an error again



    • Offizieller Beitrag

    This is probably not good practice.

    Well, that is exactly how upgrades are done...


    Fix your system with


    wget -qO - http://fi.mirror.armbian.de/apt/armbian.key | sudo apt-key add -

    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!

  • After executing the below command in cmd


    Code
    wget -qO - http://fi.mirror.armbian.de/apt/armbian.key | sudo apt-key add -


    and untag


    Code
    deb http://apt.armbian.com bookworm main bookworm-utils


    found me an update in omv webgui without errors Thank you very much for your help :)


    JteuYeB.png

  • macom

    Hat das Label gelöst hinzugefügt.
  • macom

    Hat das Label OMV 7.x hinzugefügt.
  • Well, that is exactly how upgrades are done...


    Fix your system with


    wget -qO - http://fi.mirror.armbian.de/apt/armbian.key | sudo apt-key add -

    Today I got a notification from cron that this key is stored in the older trust.gpg key file. I don't know if I should ignore it?


    Code
    <root@serwer> if test -x /usr/sbin/apticron; then /usr/sbin/apticron --cron; else true; fi
    
    W: http://apt.armbian.com/dists/bookworm/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
    • Offizieller Beitrag

    Today I got a notification from cron that this key is stored in the older trust.gpg key file. I don't know if I should ignore it?

    Yes, you can ignore it.

    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!

Jetzt mitmachen!

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