omv-release-upgrade throws errors & stops

  • apt upgrade started throwing errors, because On March 20, 2019, the Debian project moved the repository jessie-updates to archive.debian.org.


    So today I decided to omv-release-upgrade in an attempt to stay current...




    Basically the same at original apt problem.


    How can I get out of this pickle, and end up with a successful omv-release-upgrade ?



    edit : I'm thinking /etc/apt/sources.list.d/openmediavault-kernel-backports.list
    needs to be edited to contain :
    deb http://archive.debian.org/debian/ jessie-backports main contrib non-free


    But i would like confirmation ?

  • hi


    i just got it started doing this


    (using information from: https://forum.openmediavault.o…?postID=199662#post199662 which refers to https://superuser.com/a/1417751)


    • edit /etc/apt/sources.list -> the only entries are these 2:


      Code
      deb http://deb.debian.org/debian jessie main
      deb http://security.debian.org/debian-security jessie/updates main


    • rename /etc/apt/sources.list.d/openmediavault-kernel-backports.list to "#openmediavault-kernel-backports.list" (basically i could have deleted it as well)
    • started upgrading via omv-release-upgrade
    • it´s running now


    hope that helps and works
    alexander

  • Intend to wait a day or so before I do this on a live system though

    There's no magic involved. Running apt-get update without errors is prerequisite for omv-release-upgrade so as soon as you move the 'offending' files now containing outdated links out of your way it should work.


    BTW: IMO a better alternative to deletion is moving those files so you have some sort of backup: mv /etc/apt/sources.list.d/openmediavault-kernel-backports.list /root/

  • I understand and agree.
    It's just that yesterday I tried all of the above in a VM and never resulted in a functioning / upgraded system.
    Today, starting off from the same 3.0.94 VM, it did work.


    Perhaps/Likely due to @bureau ai 's find : https://superuser.com/question…in-debian/1417751#1417751


    Whatever the reason, and it certainly ain't magic :wink: , I don't see any disadvantage to waiting for a little bit more feedback before pulling the trigger on a real machine.

  • I don't see any disadvantage to waiting for a little bit more feedback before pulling the trigger on a real machine

    It's still as simple as checking whether the modifications one did result in a simple apt-get update working without errors.


    Of course further time is well spent on checking for potential compatibility problems when upgrading from OMV3 to 4.

  • There's no magic involved. Running apt-get update without errors is prerequisite for omv-release-upgrade so as soon as you move the 'offending' files now containing outdated links out of your way it should work.
    BTW: IMO a better alternative to deletion is moving those files so you have some sort of backup: mv /etc/apt/sources.list.d/openmediavault-kernel-backports.list /root/

    I was also testing the whole problem in a VM and i had further problems with omv-extras. As an answer to the qoute: Prior to the error during omv-release-upgrade concerning omv-extras i had apt-get update running without errors.


    But i just finished the release-upgrade in a VM without errors using the tips in this thread.


    • just the 2 entries in the /etc/apt/sources.list
    • deleted the /etc/apt/sources.list.d/openmediavault-kernel-backports.list
    • omv-release-upgrade
  • I did it with my live system. At first everything looked fine, none of the errors I had during the day in testing environment. But then whe my system said "please reboot" it booted into grub rescue mode. This was then also kind of broken and it rescued nothing with the help of google.
    I then booted my normal OS with the help of Super Grub2 Disk. After that i did the steps suggested over at supergrubdisk.org.


    I'm on 4.1.20-1 (Arrakis) now. All my mainly used features are alive.


    Thanks to everyone! Wont miss an EOL date again. :thumbsup:

  • hello all,


    thanks for this !!
    great ...
    I should have looked here before spending ages "playing" with Repositories and scratching my head...


    • just the 2 entries in the /etc/apt/sources.list
    • deleted the /etc/apt/sources.list.d/openmediavault-kernel-backports.list
    • omv-release-upgrade


    congrats and thanks !
    Chris

  • Thanks!
    That helped.

Participate now!

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