3.0.99 (Erasmus) Update issues

  • Hi,


    since I while I miss the latest Plex update. So I tried to check manually, but get a very long error message/report beginning:


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; apt-get update 2>&1' with exit code '100': Ign file: InRelease Ign file: Release.gpg Ign file: Release Ign file: Translation-en Hit http://packages.openmediavault.org erasmus InRelease Hit http://packages.openmediavault.org erasmus/partner amd64 Packages Ign http://ftp.de.debian.org jessie InRelease Hit http://packages.openmediavault.org erasmus/main amd64 Packages Ign http://ftp.de.debian.org jessie-updates InRelease Hit https://openmediavault.github.io erasmus InRelease Hit http://ftp.de.debian.org jessie Release.gpg Get:1 https://openmediavault.github.io erasmus/main Translation-en [9339 B] Ign http://ftp.de.debian.org jessie-updates Release.gpg Ign http://httpredir.debian.org jessie-backports InRelease Hit http://security.debian.org jessie/updates InRelease Hit https://openmediavault.github.io erasmus/main amd64 Packages Get:2 https://dl.bintray.com jessie InRelease Ign https://dl.bintray.com jessie InRelease Get:3


    I attached two text files with the full error message and one with the detailed information.


    I am an amateur in Linux and usage of Openmediavault. Hopefully this is a common error message and you can help.


    Many thanks and best regards


    Dietmarupdate-error-details.txt

  • I'm thinking /etc/apt/sources.list.d/openmediavault-kernel-backports.list
    should show deb http://archive.debian.org/debian/ jessie-backports main contrib non-free
    instead of deb http://httpredir.debian.org/debian jessie-backports main contrib non-free


    But I would like confirmation, so do not just do this without knowing what's going on.

  • I'm thinking /etc/apt/sources.list.d/openmediavault-kernel-backports.list
    should show deb http://archive.debian.org/debian/ jessie-backports main contrib non-free
    instead of deb http://httpredir.debian.org/debian jessie-backports main contrib non-free


    But I would like confirmation, so do not just do this without knowing what's going on.

    Don´t think there is anything I can do without a far deeper knowledge of Debian Linux itself - and the Openmediavault port.
    So, if you have any idea how to fix it without deep expert knowledge- it is really appreciated.
    Already thought about upgrading to 4.xx hoping the update error isn´t with that release version.
    Anyway: Is it recommened to upgrade from 3.0.99 to 4.xx?


    best regards and many thanks
    Dietmar

  • Yes. Not sure if Volker will change the url for backports since 3.x is EOL'd.

    I have the same error messages and I'm on 3.xx too.


    Of course I know one shouldn't ask for release dates but is OMV5 already usable?
    The reason I ask: I'm thinking of skipping OMV4 and doing a clean OMV5 installation as I have no special jobs for my OMV except some basic NAS stuff. And I remember ryecoaaron (not sure if it was him though) telling me I could already use OMV3 when it still was beta a couple of years ago.
    I'd like avoiding installing and arranging my system twice.

    Usul 5.5.17-2

    running on

    Mobo: Asus H87I-Plus (C2) Socket 1150
    RAM: 4GB (1x 4096MB) Kingston ValueRAM DDR3-1600 DIMM CL11 Single
    CPU: Intel Pentium G3220 2x 3.00GHz So.1150 BOX
    PS: 300 Watt be quiet! System Power 7 Bulk Non-Modular 80+ Bronze
    OS: 64GB SanDisk Solid State Disk (SDSSDP-064G-G25)
    Data: 2x 4000GB WD Red WD40EFRX
    Case: Chenbro SR30169 mini ITX (4 bay) - but removed that crappy backplane :)

  • If Volker would not change the url, will the suggestion of Tii fix the problem?
    I don't think exchanging lines in the /etc/apt/sources.list.d/openmediavault-kernel-backports.list would be too hard.

    Easy to change but many changes made in the OMV web interface would overwrite it. If you change it in /usr/share/openmediavault/mkconf/apt.d/20kernel_backports, it should stay since there probably won't be any OMV 3.x updates. Just run omv-mkconf apt after fixing it.


    Of course I know one shouldn't ask for release dates but is OMV5 already usable?

    Nope and most of the omv-extras plugins haven't been ported. Debian 10 hasn't even been released that OMV 5 is based on.

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • I'm thinking /etc/apt/sources.list.d/openmediavault-kernel-backports.list
    should show deb http://archive.debian.org/debian/ jessie-backports main contrib non-free
    instead of deb http://httpredir.debian.org/debian jessie-backports main contrib non-free


    But I would like confirmation, so do not just do this without knowing what's going on.


    This is the outcome after that change:


    I totally missed the EOL status of OMV3, my bad. :(
    I hope that this problem does not block the omv-release-upgrade like in the other thread from Tii.


    Are there any tips what to disable before starting the release upgrade? I have a few plugins from omv-extras 3 that are also available in the omv-extras 4 except for pyload.
    What happens to a mergerfs unionfilesystem with 3 disk?


    I'm scared. :D


    best regards
    Max


    EDIT: Found something that took my fear from upgrade, only issue is still Tii's thread about his problem during omv-release-upgrade.

  • I've commented out but getting error below and no further progress.


    Have I missed one as I thought I'd found them all.


    The help is much appreciated.


    Upgrading system to 4.0 (Arrakis) ...
    '/etc/openmediavault/config.xml' -> '/etc/openmediavault/config.xml.3x.bak'
    Ign file:InRelease
    Ign file:Release.gpg
    Ign file:Release
    Ign file:Translation-en
    Ign http://ftp.uk.debian.org stretch InRelease
    Hit http://packages.openmediavault.org arrakis InRelease
    Get:1 http://ftp.uk.debian.org stretch-updates InRelease [91.0 kB]
    Hit http://archive.debian.org jessie-backports InRelease
    Get:2 http://ftp.uk.debian.org stretch Release.gpg [2434 B]
    Hit https://downloads.plex.tv ./public InRelease
    Get:3 http://packages.openmediavault.org arrakis/main amd64 Packages [6494 B]
    Get:4 http://security.debian.org stretch/updates InRelease [94.3 kB]
    Hit http://ftp.uk.debian.org stretch Release
    Get:5 https://dl.bintray.com stretch InRelease
    Ign https://dl.bintray.com stretch InRelease
    Get:6 https://dl.bintray.com stretch InRelease
    Ign https://dl.bintray.com stretch InRelease
    Get:7 http://ftp.uk.debian.org stretch-updates/main Sources/DiffIndex [8116 B]
    E: Release file for http://archive.debian.org/debi…essie-backports/InRelease is expired (invalid since 36d 16h 28min 51s). Updates for this repository will not be applied.

  • OK - if I start the release upgrade - anything I need to do in advance for preparation? I read all plug-ins need to be deactivated? Plex also?

    Just plugins that aren't available on OMV 4.x.


    Have I missed one as I thought I'd found them all.

    All occurrences of jessie should be changed to stretch. You can find it with grep jessie /etc/apt/sources.list.d/*

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • What about preparing an omv-release-upgrade now to switch from an EOL OMV version to a supported one: omv-release-upgrade throws errors & stops

    I've been putting it off because omv3 has been flawless and stable and the risk of breaking something has me sticking with 3. The biggest question I have with migrating is will VM's (vbox plugin) continue to function as before? I'm running a DNS server in a VM so if that goes down i'll have no internet until I get it back up.

  • I've been putting it off because omv3 has been flawless and stable and the risk of breaking something has me sticking with 3. The biggest question I have with migrating is will VM's (vbox plugin) continue to function as before? I'm running a DNS server in a VM so if that goes down i'll have no internet until I get it back up.

    The virtualbox plugin in present in the Extras repo for OMV 4.x , so that shouldn't hold you back from updating.


    You will not have DNS during the upgrade from 3.x to 4.x , personally I would setup another device as DNS just in case. Those 30 seconds spent configuring a basic dns, might save the bacon.

  • If you do omv-release-upgrade


    It *should* update both Debian and OMV...

    I've been putting it off because omv3 has been flawless and stable and the risk of breaking something has me sticking with 3. The biggest question I have with migrating is will VM's (vbox plugin) continue to function as before? I'm running a DNS server in a VM so if that goes down i'll have no internet until I get it back up.

    Unfortunately when you do that however, you risk having the problems you're having now (ie, a box that you didn't upgrade for stability, but now no longer is stable).


    You should always keep your machines regularly updated and adapt to changes.

  • The virtualbox plugin in present in the Extras repo for OMV 4.x , so that shouldn't hold you back from updating.
    You will not have DNS during the upgrade from 3.x to 4.x , personally I would setup another device as DNS just in case. Those 30 seconds spent configuring a basic dns, might save the bacon.

    Agreed, that is probably what I'll do.


    If you do omv-release-upgrade


    You should always keep your machines regularly updated and adapt to changes.


    Meh. Updated, yes. Release updates I tend to avoid as it seems the process is rarely seamless. I've had issues with Ubuntu releases on my desktop box, so I switched to Arch a few years ago. No more problem staying updated.

  • Same problem here.
    I have not updated for a while and haven't done anything to my OMV installation.
    Today I decided to update and got this long error.
    So what is the solution?
    I can't comprehend this thread as you guys are mixing topics, talking about upgrades to new OMV releases and other stuff.
    Is there a fix or not?

Participate now!

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