[Odroid HC2] [Armbian] Stretch upgrade, OMV error

    • OMV 4.x
    • Resolved
    • Upgrade 3.x -> 4.x
    • [Odroid HC2] [Armbian] Stretch upgrade, OMV error

      Today I wanted to upgrade from jessie to stretch, I'm following this website.
      After changing the word jessie to stretch in /etc/apt/sources.list and in every file in /etc/apt/sources.list.d/* I noticed that changing the omv-extras-org.list from:

      Source Code

      1. # OMV-Extras.org
      2. deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus jessie main
      3. # OMV-Extras.org Testing
      4. deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus-testing jessie main
      5. to
      6. # # OMV-Extras.org
      7. deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus stretch main
      8. # OMV-Extras.org Testing
      9. deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus-testing stretch main


      causes apt-get update to throw errors. So I decided to leave jessie in there for now.
      Ok now apt-get update precedes until the line:

      Source Code

      1. Get:23 http://httpredir.debian.org stretch/non-free armhf Packages [71,2 kB]
      2. Fetched 10,7 MB in 8s (1.310 kB/s)
      and leaves me with a plain cursor.
      Now if I hit Ctrl+C I get the following output on screen:

      Source Code

      1. root@hc2:~# Traceback (most recent call last):
      2. File "/usr/sbin/omv-mkaptidx", line 113, in <module>
      3. "uri": pkg.candidate.uri,
      4. File "/usr/lib/python3/dist-packages/apt/package.py", line 567, in uri
      5. return next(iter(self._uris()))
      6. File "/usr/lib/python3/dist-packages/apt/package.py", line 550, in _uris
      7. yield indexfile.archive_uri(self._records.filename)
      8. File "/usr/lib/python3/dist-packages/apt/package.py", line 309, in _records
      9. if self.package._pcache._records.lookup(self._cand.file_list[0]):
      10. KeyboardInterrupt
      I see some python and omv error :(

      Can anyone help? I hoped for a painless upgrade and the first problems are appearing even before the "main course" :D

      Edit: Ok, I read some stuff but wanted to make sure: To upgrade from debian jessie to stretch, do I also have to upgrade from omv 3.0.99 to omv 4?
      If yes, is omv-release-upgrade the right way to do so? If I have to update, will I loose any of @tkaiser 's great tweaks that came with install via armbian config?

      Dear god plz let @tkaiser answer this post :D
    • trohn_javolta wrote:

      Today I wanted to upgrade from jessie to stretch, I'm following this website
      This is your first problem. Debian and OMV need to be updated at the same time.

      trohn_javolta wrote:

      Can anyone help? I hoped for a painless upgrade and the first problems are appearing even before the "main course"
      I hope you have a backup.

      trohn_javolta wrote:

      do I also have to upgrade from omv 3.0.99 to omv 4?
      Yep.

      trohn_javolta wrote:

      will I loose any of @tkaiser 's great tweaks that came with install via armbian config?
      No.

      trohn_javolta wrote:

      If yes, is omv-release-upgrade the right way to do so?
      Yep.

      Now you have a system in a weird state. Assuming you have no backup, change all occurrences of erasmus to arrakis in the files in /etc/apt/sources.list.d/. Then apt-get update and apt-get dist-upgrade. It might work but it is hard to say what state your system is in. Might be easier to just write a new HC2 image to your sd card.
      omv 4.1.11 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • trohn_javolta wrote:

      How is the right way to update debian with omv?
      First do omv-release-upgrade? And later change sources?
      If you do omv-release-upgrade the sources will be updated automatically as part of the upgrade.
      This is for the case you have a backup and you can start over from that point before any upgrade attempt.
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • macom wrote:

      trohn_javolta wrote:

      How is the right way to update debian with omv?
      First do omv-release-upgrade? And later change sources?
      If you do omv-release-upgrade the sources will be updated automatically as part of the upgrade.This is for the case you have a backup and you can start over from that point before any upgrade attempt.
      :/ || I do have an up to date backup via rsnapshot, but now I tried to restore it and it doesn't work ||
      I checked the log, the initial backup went through without any errors.

      Now I tried to restore the backup to a spare sd card using this command:

      Source Code

      1. rsync -aAXvP --stats --numeric-ids --log-file=/home/fabi/Downloads/rsynclog.txt root@hc2.home:/srv/dev-disk-by-id-ata-WDC_WD60EFRX-68MYMN1_WD-WX21DC42EXYZ-part2/backups/hc2/daily.1/localhost/ /media/fabi/1ec000f3-2252-4dda-beda-e5b3a21894a6/
      This also finishes without any errors, however inserting the sd card into odroid hc2 I just get a red light. :huh:

      I never had to restore a backup before, don't know what's wrong.
    • As ryecoaaron wrote:

      ryecoaaron wrote:

      Assuming you have no backup, change all occurrences of erasmus to arrakis in the files in /etc/apt/sources.list.d/. Then apt-get update and apt-get dist-upgrade. It might work but it is hard to say what state your system is in.
      Seems you best option at the moment.

      If it does not work, you can still start from scratch.
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • macom wrote:

      As ryecoaaron wrote:

      ryecoaaron wrote:

      Assuming you have no backup, change all occurrences of erasmus to arrakis in the files in /etc/apt/sources.list.d/. Then apt-get update and apt-get dist-upgrade. It might work but it is hard to say what state your system is in.
      Seems you best option at the moment.
      If it does not work, you can still start from scratch.
      Finally I was able to restore my update and do the upgrade with omv-release-upgrade.
      Seems everything worked, systemctl --failed shows no failed units.

      Only when I do apt-get update I get couple of these warnings:

      Source Code

      1. W: Target Contents-deb (non-free/Contents-all) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1
      I remember adding the backports in sources.list some time ago.
      Should I keep the line in openmediavault-kernel-backports.list and delete it in sources.list?