Posts by hsb

    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:

    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'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.

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

    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.