Seemingly cannot update and upgrade anymore due to repository having no release file (OMV6 on Armbian on Odroid HC1)

1. offizieller Beitrag

    Hardware: Odroid HC2 (as in "Home Cloud")

    OS: OMV 6.9.14-1 on top of Armbian Bullseye (the variant for the Odroid XU4 / HCx). Ran for a while now.


    User Goal: Get AirPlay 2 support introduced in shairport-sync 4.1. So far I only have shairport-sync 3.3.7. $ shairport-sync -V gives

     3.3.7-libdaemon-OpenSSL-Avahi-ALSA-jack-pa-dummy-stdout-pipe-soxr-convolution-metadata-mqtt-dbus-mpris-sysconfdir:/etc 


    Indirect User Goal: Upgrade OMV 6.x and its plugins to their newest state, and in the progress hopefully also get shairport-sync 4.1 or newer.


    Problem: I seemingly cannot update and upgrade anymore due to "repository having no release file".

    Whenever I try  $  sudo apt update  I almost always get E: The repository 'http://apt.armbian.com bullseye Release' does not have a Release file.

    • Has been like this for a while. Once though, update worked and the amount of upgrade-able packages increased. But when I wanted to run the upgrade it again failed particularly when fetching the Armbian related stuff.
    • Also in the Web UI (Workbench): OMV 6 → System → Update Management → Updates: Showed nothing mostly. But one time it showed available upgrades, and I used that opportunity.


    Suspicion: Something with my repo / sources.list setup got corrupted or in the repository some hard change was performed which cut off users like me.

    • Note: I am in the EU. Possibly some GDPR policy resulted in a repo change which has then "cut me off" somewhen?


    System Genesis:


    Repository Setup investigation

    • sudo armbian-config → Personal Timezone, language, hostname → Mirrors Reconfigure APT mirrors
    • Shows only the option "0 Automated". No other options.


    source.list investigation



    omv-sysinfo


    Odroid HC2 - Armbian 24 Bookworm - OMV7

    Einmal editiert, zuletzt von porg ()

    If you look at http://apt.armbian.com/dists, you'll see that bullseye is no longer listed.


    When this happened to me the last time, it was what prompted me to upgrade from OMV5 to OMV6. I'm trying to figure out now what I should do.

    Radxa ROCK 4A running OMV6 on armbian bullseye

    Einmal editiert, zuletzt von imnlfn ()

    Thanks for the info! So OMV 6 is still the stable release, but the OS below it, Armbian, got its version Bullseye deprecated.


    What's the correct upgrade procedure in this case now?


    Please tell me which parts (OMV, plugins, Armbian) shall be updated in what order. And what manual interventions may be necessary (in this unlucky state), and what inbetween states may have errors, which I can ignore, due to the final stage the update plan foresees.

    Thanks!

    Odroid HC2 - Armbian 24 Bookworm - OMV7

    It looks like the available options are to upgrade to OMV 7 or hang tight with OMV 6 and forgo OS updates.


    I saw a post from an admin in response to someone's failed attempt to install OMV 6 on Debian 12 that said each version of OMV is tied to a specific release of Debian.

    Radxa ROCK 4A running OMV6 on armbian bullseye

    • Offizieller Beitrag
    Zitat von porg

    OMV 6 is still the stable release

    OMV 7 is now - https://www.openmediavault.org/?p=3663

    Zitat von porg

    What's the correct upgrade procedure in this case now?


    Please tell me which parts (OMV, plugins, Armbian) shall be updated in what order. And what manual interventions may be necessary (in this unlucky state), and what inbetween states may have errors, which I can ignore, due to the final stage the update plan foresees.

    You upgrade both at the same time with omv-release-upgrade.


    Zitat von imnlfn

    hang tight with OMV 6 and forgo OS updates.

    OMV 6 is Debian 11 and even though it is an armbian image, it will keep getting Debian 11 updates likely until Debian 13 is out. I recommend upgrading to OMV 7 though.


    Zitat von imnlfn

    I saw a post from an admin in response to someone's failed attempt to install OMV 6 on Debian 12 that said each version of OMV is tied to a specific release of Debian.

    OMV 6.x must be on Debian 11.

    OMV 7.x must be on Debian 12.

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

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.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!

    Zitat von ryecoaaron

    OMV 7 is now [the stable release]

    Please update the forum tag colors accordingly. Thanks!

    Zitat von ryecoaaron

    You upgrade both at the same time with omv-release-upgrade.

    Relieved to read this! So I as the user don't have to overthink it. 🙂


    So I better ask one more time now to be save:

    • If I run omv-release-upgrade both Armbian and OMV and the plugins will get updated, and the sources.list will be sufficient as is and automatically look for the next newer release. Right?
    • I have made backups of data and system. If you give me the green lights I would run omv-release-upgrade then.

    Odroid HC2 - Armbian 24 Bookworm - OMV7

    • Offizieller Beitrag
    Zitat von porg

    Please update the forum tag colors accordingly. Thanks!

    I can't. But the color doesn't mean stable to me.


    Zitat von porg

    If I run omv-release-upgrade both Armbian and OMV and the plugins will get updated, and the sources.list will be sufficient as is and automatically look for the next newer release. Right?

    Yes. Plenty of threads about this. The OMV upgrade process hasn't changed in a very long time.


    Zitat von porg

    If you give me the green lights I would run omv-release-upgrade then.

    I haven't upgraded an Armbian install from OMV 6.x to 7.x recently. But since you have backups, I think you should be good to go.

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

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.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!

    1. $ ssh root@odroid.local
    2. $ omv-release-upgrade
    3.  Do you really want to upgrade your system to release version 7.0 (Sandworm)? Please ensure that all your installed plugins are available for this release. Yes / No 
      • I chose YES. I ran into the same error "repository does not have a Release file" again:


    So I can neither upgrade within 6.x nor upgrade to the new release 7.x.

    Seems I'm stuck. Seems this needs some intervention (edit the source list).


    But how?

    Odroid HC2 - Armbian 24 Bookworm - OMV7

    • Offizieller Beitrag
    Zitat von porg

    So I can neither upgrade within 6.x nor upgrade to the new release 7.x.

    Seems I'm stuck. Seems this needs some intervention (edit the source list).


    But how?

    This is because the armbian mirror your system is connecting to is down. I'm sure you could point it at a different armbian mirror if you can find the list of mirrors.

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

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.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!

    Bash
    ...
...
Hit:14 http://deb.volian.org/volian scar InRelease
Ign:13 http://fi.mirror.armbian.de/apt bullseye InRelease
Err:15 http://fi.mirror.armbian.de/apt bullseye Release
404  Not Found [IP: 65.21.120.247 80]
Reading package lists... Done
E: The repository 'http://apt.armbian.com bullseye Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


    1) I have no idea where the mirrors come from. I do not recall that I set up anything custom. As I wrote in my original post my "mirror repair attempt" failed: sudo armbian-config → Personal Timezone, language, hostname → Mirrors Reconfigure APT mirrors: Shows only the option "0 Automated". No other options shown. It's quite evident to me that something is broken (by whatever cause...?) and needs to be fixed manually (in which config file(s) ?).


    2) Mirror responding with HTTP 404: If I open http://fi.mirror.armbian.de/apt in a web browser I get a directory listing. Just no bullseye listed there anymore. The question is: Why is bullseye even requested when my intention is to upgrade to the next version (bookworm)??? Something in the upgrade logic (or config) is flawed here, which keeps me stuck. I do not understand what's going on behind the scene, and hence I cannot comprehend what fails. I hope that the following info provides the necessary clues:


    My source.list files:


    /etc/apt/sources.list

    EMPTY FILE is that normal that it's empty?


    /etc/apt/sources.list.d/armbian.list:

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


    /etc/apt/sources.list.d/box86.list:

    deb [signed-by=/usr/share/keyrings/box86.gpg] https://itai-nelken.github.io/weekly-box86-debs/debian/ /


    /etc/apt/sources.list.d/nala.list:

    deb [signed-by=/usr/share/keyrings/nala.gpg] http://deb.volian.org/volian/ scar main


    /etc/apt/sources.list.d/omvdocker.list:

    deb [signed-by=/usr/share/keyrings/docker.gpg arch=armhf] https://download.docker.com/linux/debian bullseye stable


    /etc/apt/sources.list.d/omvextras.list:

    deb [signed-by=/usr/share/keyrings/omvextras.gpg arch=armhf] https://openmediavault-plugin-developers.github.io/packages/debian shaitan main



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

    deb [signed-by=/usr/share/keyrings/debian-archive-bullseye-automatic.gpg] http://httpredir.debian.org/debian bullseye-backports main contrib non-free


    /etc/apt/sources.list.d/openmediavault-local.list:

    deb [trusted=yes] file:/var/cache/openmediavault/archives /


    /etc/apt/sources.list.d/openmediavault-os-security.list:

    Code
    deb [signed-by=/usr/share/keyrings/debian-archive-bullseye-security-automatic.gpg] http://security.debian.org/debian-security bullseye-security main contrib non-free
deb-src [signed-by=/usr/share/keyrings/debian-archive-bullseye-security-automatic.gpg] http://security.debian.org/debian-security bullseye-security main contrib non-free


    /etc/apt/sources.list.d/openmediavault.list:

    Code
    deb [signed-by=/usr/share/keyrings/openmediavault-archive-keyring.gpg] http://packages.openmediavault.org/public/ shaitan main
deb [signed-by=/usr/share/keyrings/openmediavault-archive-keyring.gpg] https://openmediavault.github.io/packages/ shaitan main
# deb [signed-by=/usr/share/keyrings/openmediavault-archive-keyring.gpg] http://downloads.sourceforge.net/project/openmediavault/packages/ shaitan main

    Odroid HC2 - Armbian 24 Bookworm - OMV7

    • Offizieller Beitrag
    Zitat von porg

    It's quite evident to me that something is broken (by whatever cause...?) and needs to be fixed manually (in which config file(s) ?).

    That means the repo decided to delete the older releases it seems. If you can't find a mirror list, there is nothing to fix.


    Zitat von porg

    Why is bullseye even requested when my intention is to upgrade to the next version (bookworm)??? Something in the upgrade logic (or config) is flawed here, which keeps me stuck. I do not understand what's going on behind the scene, and hence I cannot comprehend what fails. I hope that the following info provides the necessary clues:

    The upgrade tries to make sure the system is fully up to date before starting the upgrade - https://github.com/openmediava…n/omv-release-upgrade#L62 This is a good idea because it will ensure the latest omv-release-upgrade and modules are installed.


    You could try changing ONLY the armbian repo to bookworm and hope it doesn't update too much. Or you could remove the line I linked to above in omv-release-upgrade.

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

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.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!

    Einmal editiert, zuletzt von ryecoaaron ()

    Zitat von ryecoaaron

    That mean decided to delete the older releases it seems. If you can't find a mirror list, there is nothing to fix.

    I could not comprehend sentence 1 grammatically:

    • "That man" (the maintainer?) decided…
    • "That means". A means is not a subject, hence cannot decide anything.

    Anyways I interpreted it that way: I missed the window of opportunity to update while the relevant apt manifest and source files were still online. Meanwhile those legacy files got deleted. So no way to upgrade unless I find a mirror which still offers those legacy files.


    1) Is this what you meant? If so which of my listed source list files would need the manual addition of a mirror server which still offers the bullseye files?


    2) I hope that approach 1 won't even be necessary. I am sure at least once today the update & upgrade went through (seems some mirror server rotation is in place, and at least once I was lucky, and it pointed to a mirror which still had the bullseye stuff, I assume). Today in OMV 6 → System → Update Management → Updates: Many packages were listed. And I ran all those upgrades.

    So I think it is safe to forego the omv-release-upgrade script with the preceding omv-upgrade line outcommented


    Could you please look at 2024-03-04--1220--OMV-GUI--System--Update-Management--Update-ran.txt and/or my omv-sysinfo which I had run thereafter, and tell me whether that looks like an up to date OMV 6.x? So that I can run an omv-release-upgrade with the omv-upgrade line outcommented with a good certainty/probability to succeed. Thanks!

    Odroid HC2 - Armbian 24 Bookworm - OMV7

    I'm a user experience designer. As such I have a learning and recommendation from today's use case too, which I want to share:


    The following use case is currently not supported:

    1. You don't update your OMV for a while.
    2. Finally you have some time to take care of it. But now you can:
      • neither a) omv-upgrade (due to necessary files not being hosted anymore, as I understand it)
      • nor b) omv-release-upgrade (as this includes a omv-upgrade implicitly)
    3. You have put yourself into a dead end.

    Maybe the UX of this scenario can be improved within reasonable limitations?


    To me 0.5-1.5 years of update inactivity seems acceptable for a NAS only active in your LAN, if this has hobby purposes only. That this puts you in a dead end repository-wise feels a bit too harshly limited. I don't expect hosting in perpetuity! But keeping versions that are 2 years old feels not too far stretched. But maybe I'm underestimating the hosting requirements for this (given all the architecture variations, distro variants, etc, this possible gets "quite exponential" soon, I don't know it honestly). So for the case you are indeed outside of a "reasonable repo archiving" period, then possibly offer a omv-release-upgrade --without-prior-omv-upgrade option. Curiosity question: Shouldn't a release upgrade work mostly independent of the prior system state?

    Odroid HC2 - Armbian 24 Bookworm - OMV7

    • Offizieller Beitrag
    Zitat von porg

    So I think it is safe to forego the omv-release-upgrade script with the preceding omv-upgrade line outcommented

    I would just try it. Even if the system is out of date, there isn't much we can do about it.

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

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.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!

    • Offizieller Beitrag
    Zitat von porg

    The following use case is currently not supported:
    You don't update your OMV for a while.

    Hard to say. In this case, it was only an Armbian repo. That would most likely mean you have out of date Armbian packages on the previous release that would get updated once the system is on the next version. I really don't see this as much of a problem and is unlikely to cause a problem.


    You are never at a dead end. You can always install fresh. There are many things that do no support upgrades.


    0.5 years of not updating a NAS even if not on the internet is not acceptable. You have other systems (likely windows) that are most likely are on the internet. If one of those systems gets a virus, many viruses will scan your network for vulnerable systems. 90 days is the max in my opinion and the rule at my work.

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

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.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!

    omv-release-upgrade ended in a broken system: Got an updated Armbian system but all OMV specific packages gone!

    • Immediately noticeable:
      • Opening hostname in web browser: Instead of Workbench GUI I get generic "403 Forbidden" nginx error page.
      • Accessing with SSH: Credentials still work, but no typical welcome screen.
    • What caused the OMV removal?
      • Possibly due to the system state from which I started omv-release-upgrade?
      • Or worse, possibly omv-release-upgrade has not robust enough exception handling (repo answering with HTTP 502 resulting in package removal?) — I doubt this to be the case — But at least publicly share this possibility to avoid other users going through that upgrade path to suffer the same fate, should this be true indeed — Because some parts of the script output gave me that possible interpretation:


    Anyhow here's my full omv-release-upgrade.log, I redacted/changed the private parts, such as usernames with generic names "me", "wife", "daughter" or the output of my Samba Share Configuration:


    Odroid HC2 - Armbian 24 Bookworm - OMV7

    The output indicates everything remained on OMV v6:



    Any chances to fix from here?


    If not I will be able to restore the SD card to the OMV 6 system from my most recent openmediavault-backup in fsarchiver format by help of SystemRescue and FSArchiver.

    Odroid HC2 - Armbian 24 Bookworm - OMV7

    Zitat von porg

    Any chances to fix from here?

    You can start by checking the repos lists under /etc/apt/sources.list.d/ and the /etc/apt/sources.list itself to see how they look like.

    Post their output to see if they need changing.


    Maybe you can re-run the install script but better wait to see if ryecoaaron has an idea how to recover that.

    Should be possible since the configs are there (rC).

    The upgrade was simply interrupted.

Jetzt mitmachen!

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

Benutzerkonto erstellen Anmelden