omv-release-upgrade throws errors & stops

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • 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

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

      Display Spoiler

      Source Code

      1. root@backup-nas:/etc/apt# omv-release-upgrade
      2. Upgrading system to 4.0 (Arrakis) ...
      3. Ign file: InRelease
      4. Ign file: Release.gpg
      5. Ign file: Release
      6. Ign stretch InRelease
      7. Hit stretch-updates InRelease
      8. Hit syncthing InRelease
      9. Hit arrakis InRelease
      10. Get:1 stretch InRelease
      11. Ign stretch InRelease
      12. Get:2 stretch InRelease
      13. Ign stretch InRelease
      14. Ign file: Translation-en
      15. Hit stretch Release.gpg
      16. Hit stretch Release
      17. Hit stretch Release.gpg
      18. Ign jessie-backports InRelease
      19. Hit stretch/updates InRelease
      20. Get:3 stretch-updates/main Sources/DiffIndex [7624 B]
      21. Get:4 stretch-updates/main amd64 Packages/DiffIndex [7624 B]
      22. Ign jessie-backports Release.gpg
      23. Hit stretch Release.gpg
      24. Get:5 stretch-updates/main Translation-en/DiffIndex [4672 B]
      25. Get:6 syncthing/release amd64 Packages [1245 B]
      26. Hit stretch-updates/contrib Sources
      27. Hit stretch-updates/non-free Sources
      28. Hit stretch-updates/contrib amd64 Packages
      29. Hit stretch-updates/non-free amd64 Packages
      30. Hit stretch-updates/contrib Translation-en
      31. Hit stretch-updates/non-free Translation-en
      32. Ign jessie-backports Release
      33. Hit stretch Release
      34. Hit arrakis/main amd64 Packages
      35. Ign syncthing/release Translation-en
      36. Hit stretch/main Sources
      37. Hit stretch/main amd64 Packages
      38. Ign jessie-backports/main amd64 Packages/DiffIndex
      39. Hit stretch/main Translation-en
      40. Ign arrakis/main Translation-en
      41. Get:7 stretch/updates/main Sources [197 kB]
      42. Hit stretch Release
      43. Ign jessie-backports/contrib amd64 Packages/DiffIndex
      44. Get:8 stretch/updates/contrib Sources [1384 B]
      45. Ign jessie-backports/non-free amd64 Packages/DiffIndex
      46. Get:9 stretch/updates/non-free Sources [1216 B]
      47. Get:10 stretch/updates/main amd64 Packages [481 kB]
      48. Get:11 stretch/updates/contrib amd64 Packages [1760 B]
      49. Get:12 stretch/updates/non-free amd64 Packages [1600 B]
      50. Get:13 stretch/updates/contrib Translation-en [1759 B]
      51. Get:14 stretch/updates/main Translation-en [213 kB]
      52. Get:15 stretch/main amd64 Packages [22.1 kB]
      53. Get:16 stretch/main Translation-en
      54. Get:17 stretch/updates/non-free Translation-en [691 B]
      55. Get:18 stretch/main amd64 Packages [760 B]
      56. Get:19 stretch/main Translation-en
      57. Get:20 stretch/main Translation-en
      58. Get:21 stretch/main Translation-en
      59. Get:22 stretch/main Translation-en
      60. Get:23 stretch/main Translation-en
      61. Get:24 stretch/main Translation-en
      62. Get:25 stretch/main Translation-en
      63. Get:26 stretch/main Translation-en
      64. Ign stretch/main Translation-en
      65. Get:27 stretch/main Translation-en
      66. Ign stretch/main Translation-en
      67. Ign jessie-backports/contrib Translation-en
      68. Ign jessie-backports/main Translation-en
      69. Ign jessie-backports/non-free Translation-en
      70. Err jessie-backports/main amd64 Packages
      71. 404 Not Found
      72. Err jessie-backports/contrib amd64 Packages
      73. 404 Not Found
      74. Err jessie-backports/non-free amd64 Packages
      75. 404 Not Found
      76. Fetched 42.8 kB in 4s (9031 B/s)
      77. W: Failed to fetch 404 Not Found
      78. W: Failed to fetch 404 Not Found
      79. W: Failed to fetch 404 Not Found
      80. E: Some index files failed to download. They have been ignored, or old ones used instead.
      81. root@backup-nas:/etc/apt#
      Display All

      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 jessie-backports main contrib non-free

      But i would like confirmation ?

      The post was edited 1 time, last by Tii: possible solution ? ().

    • hi

      i just got it started doing this

      (using information from:…?postID=199662#post199662 which refers to

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

        Source Code

        1. deb jessie main
        2. deb 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
    • Tii wrote:

      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 :…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.
    • tkaiser wrote:

      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

      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 !
    • Users Online 2

      1 Member and 1 Guest