Upgrade Scripts for non-interactive major release upgrades (2->3, 3->4, 4->5)

Quote from Zoki

I would try to fix the repos in /etc/apt/sources.list and /etc/apt/sources.list./* and upgrade manually, but the info you give is a bit space, so I do not know the state the system is in. The post scripts migrate the database, which may not happen, if you update manually, so you may have to to it manually too.

Fixed the duplicate repos and tried run-parts through the run.d scripts (in hopes of a simple repair) but no upgrades occured. Guess it's off to search on the manual upgrade process. Thanks for the pointers!

apt update should pull omv5 if the repo is correct.

Quote from Zoki

apt update should pull omv5 if the repo is correct.

Well, I had some missing dependencies so naturally I had a beer and clicked through.. and installed Chrony which removed OMV4. *sigh*

If I install OMV5 at this point is it basically a fresh start? No way to transfer the OMV4 settings (not that I had customized much)? I still see my several TB of hosted data, I assume the install won't mess up any existing volumes and I'll just have to re-present them to the network.

root@filer:/etc/apt/sources.list.d# apt-get upgrade openmediavault -s

Reading package lists... Done

Building dependency tree

Reading state information... Done

Calculating upgrade... Done

The following NEW packages will be installed:

openmediavault

0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.

Inst openmediavault (5.6.26-1 openmediavault.org archive:usul [all])

Conf openmediavault (5.6.26-1 openmediavault.org archive:usul [all])

EDIT: dpkg shows 4.x installed, is it possible to do a `dpkg -i openmediavault` to upgrade?

dpkg -s openmediavault

Package: openmediavault

Status: deinstall ok config-files

Priority: optional

Section: admin

Installed-Size: 11983

Maintainer: Volker Theile <volker.theile@openmediavault.org>

Architecture: all

Version: 4.1.36-1

Config-Version: 4.1.36-1

Depends: perl:any, libjs-extjs6, php-fpm, libpam-modules, php-json, php-cgi, php-cli, php-mbstring, php-pam, sudo, ethtool, python3-dialog, acl, ifenslave, resolvconf, iproute2, xfsprogs, jfsutils, ntfs-3g, hdparm, sdparm, ifupdown, mdadm, postfix, libsasl2-modules, bsd-mailx, python3-dbus, cpufrequtils, rsyslog, logrotate, smartmontools, openssl, openssh-server, uuid, tzdata, nfs-kernel-server, proftpd-basic, lsb-release, sshpass, wget, util-linux, samba, samba-common-bin, rsync, apt-utils, wsdd (>= 0.3-2), avahi-daemon, libnss-mdns, iptables, monit, acpid, beep, php-bcmath, gdisk, rrdtool, collectd, cron, anacron, cron-apt, quota, php-xml, quotatool, whiptail, lvm2, watchdog, ca-certificates, perl, libjson-perl, liblocale-po-perl, proftpd-mod-vroot, libjavascript-minifier-xs-perl, coreutils, xmlstarlet, mount, parted, bash, diffutils, lsof, socat, rrdcached, locales, nginx, bash-completion, python3, python3-apt, pm-utils, wpasupplicant, systemd, systemd-sysv, btrfs-progs, samba-vfs-modules, pciutils, python3-pyudev, python3-natsort, jq, ntp, python3-netifaces, udev, apt-transport-https, python3-lxml, debconf (>= 0.5) | debconf-2.0

Conffiles:

/etc/apt/apt.conf.d/99openmediavault-apt-hooks 6f86688582c8e64a1383c69b02ba74e0

...

Just to leave a resolution on my issue, successfully performed the upgrade (apt upgrade openmediavault) and selectively ran files in post.d (skipping deborphan) to restore configuration. Services are working as expected under OMV5 just in time for buster EOL. Will do a fresh install on a new RPi4 once OMV6 goes final.

the update from omv5 to onv6 is very smooth.

Quote from mclardass

Will do a fresh install on a new RPi4 once OMV6 goes final.

OMV6 is final for some time now see https://openmediavault.readthe…o/en/stable/releases.html

Hello guys,

sorry to bother you again with another issue.

I am in the update process from 4 -> 5 with the scripts mentioned at the beginning of this thread.

So i followed the procedure and ended all servicese but ssh,

uninstalled all not used plugins, checked that the grub is still pointing to the right device. I also did the post #9 (omv-extras to github) from

Post

RE: omv-extras repos moving to github

[…]

I wrote a kvm plugin for OMV 5.x that is better than virtualbox (in my opinion). There is even an option to convert the virtualbox vdi disk images to kvm format to create the VM in the plugin. The kvm plugin is fully integrated with OMV as opposed to doing everything in phpvirtualbox (which is not really maintained anymore).

Just because it works fine doesn't mean you should stop moving to newer, supported versions.

I hate giving out these instructions because people will just stop…

ryecoaaron

Jul 8th 2021

Then i startet the update:

First i got the following error 11 and the following errorlog: For me it seems something was still wrong with omv-extras to github.

omv_release_upgrade_to_buster.2022-06-20-223302.txt

Can you check somehow, if omv-extras is switched correctly to github?

Because of the error i uninstalled additionally to the not used plugins my needed plugins, also omv-extras.

Then i started the script again and got a different errorlog, now without bintray. Unfortunately it stops again with code 11

omv_release_upgrade_to_buster.2022-06-21-003152.txt

Another thing is that now all plugins, i uninstalled before, do even not show up anymore in the plugin list. So i don´t know, if this is the reason i got no bintray issues in the log?

i really would appreciate any help on this matter, as i don´t know how to proceed with the update.

thank you so much for your help.

Frank

I'm still on OMV 3, and my omv-extra repo points to bintray. What are my options for upgrading to OMV 5? Thank you.

Quote from ryecoaaron

You should be on OMV 6. So, that would a 3 to 4 to 5 to 6 set of upgrades. I never released an omv-extras 4.x package. You would have to uninstall omv-extras and do the upgrades then reinstall omv-extras. Sure would be easier to do a fresh install of OMV 6.x.

Thank you so much for the advice- I will look into a fresh install

Hi,

i'm thinking about upgrading from OMV 4.1.36-1 and Linux 4.19 to something newer.

I know about the pro's, but my con's are: OMV is running fine, not accessible from the internet and I have only litte time to care about possible problems. Additional services are running as Docker-Container (urbackup, plex, vpn, pihole) but I made some changes to some configs, so I'm not sure if the automatic upgrade process would be painless. Backing up OMV is a given, but restoring could also be risky, although I've done it before.

As preparation i had a look at

debconf-show grub-pc | grep -w grub-pc/install_devices

from the initial post and

debconf-show grub-pc

But those give me no return, just a new promt. - This is not the expected result?

The System is running from a SDD on a Intel Celeron System (amd64). And according to

[ -d /sys/firmware/efi ] && echo UEFI || echo BIOS

booted from efi.

Phew, if you say so yourself.... I wouldn't want to have the very latest version, but a bit newer would be nice for me. But it doesn't make it any easier that the old package sources no longer exist.

If the undertaking is so difficult, I'll stick with 4 and set it up again at some point when I have new hardware.

Because of the effort.

If the upgrades are easy - no problem, then I'll go to the latest version. But if every version jump causes problems, involves breaking changes and requires manual intervention, I simply don't have the time. I don't run OMV as a hobby, but out of necessity.

I would like to come back to my question above.

As far as I understand it, the following command is supposed to provide a return and is a prerequisite to be able to use the upgrade script without problems.

debconf-show grub-pc

But this gives me no return, just an empty promt. Is this expected? (see preceding post #331 for my systems details)

ok, thanks!

I ran the script "omv-release-upgrade-5" but it finished with error code 100, while processing

run-parts: executing /home/openmediavault-upgrade-4.7/run.d/10-apt-update.

There were many "Ign" while fetching new packages and some "Err". The logfile finishes with the following lines:

...
Fetched 23.8 MB in 16s (1468 kB/s)
Reading package lists...
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/omv-extras-org.list:5 and /etc/apt/sources.list.d/omv-extras-org.list:8
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/omv-extras-org.list:5 and /etc/apt/sources.list.d/omv-extras-org.list:8
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/omv-extras-org.list:5 and /etc/apt/sources.list.d/omv-extras-org.list:8
W: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does not have a Release file.
W: The repository 'http://ftp.halifax.rwth-aachen.de/debian stretch Release' does not have a Release file.
W: The repository 'http://ftp.halifax.rwth-aachen.de/debian stretch-updates Release' does not have a Release file.
W: The repository 'http://security.debian.org/debian-security stretch/updates Release' does not have a Release file.
W: The repository 'http://ftp.us.debian.org/debian stretch Release' does not have a Release file.
E: Failed to fetch http://httpredir.debian.org/debian/dists/stretch-backports/main/binary-amd64/Packages  404  Not Found
E: Failed to fetch http://ftp.halifax.rwth-aachen.de/debian/dists/stretch/main/source/Sources  404  Not Found
E: Failed to fetch http://ftp.halifax.rwth-aachen.de/debian/dists/stretch-updates/main/source/Sources  404  Not Found
E: Failed to fetch http://security.debian.org/debian-security/dists/stretch/updates/main/source/Sources  404  Not Found
E: Failed to fetch http://ftp.us.debian.org/debian/dists/stretch/main/binary-amd64/Packages  404  Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/omv-extras-org.list:5 and /etc/apt/sources.list.d/omv-extras-org.list:8
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/omv-extras-org.list:5 and /etc/apt/sources.list.d/omv-extras-org.list:8
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/omv-extras-org.list:5 and /etc/apt/sources.list.d/omv-extras-org.list:8
run-parts: /home/openmediavault-upgrade-4.7/run.d/10-apt-update exited with return code 100

I didn't get the impression that much happened. Therefore, and because I had nothing to lose, I started the script a second time.

This time much more happend, Things were upgraded, configs were changed (nor not, because of manual changes) and I saw "buster" multiple times. Eventually the script finished with the same error as before.

After a reboot OMV was broken. I couldn't log into the GUI due to "software error/wrong password". I cleared the browser cache, tried a different browser, resetted user lock and changed Password with omv-firstaid, but no cure.

At this point I gave up and restored my backup.

If you have a definite tip and a simple solution as to what is causing the errors, I would try again. Otherwise.... not.

I'll help my myself:

The original debain stretch repositorys are no longer available.

I made the edits to /etc/apt/sources.list as described in this post:

Post

RE: Debian repositories no longer have "Release file"

SUCCESS! I'm now on OMV 6.9.12-2, having updated from OMV 5.6.26.

This is a summary of the steps I took to resolve my issues. Here's hoping it helps anyone else with the same or similar issues.

Issue 1: Debian `stretch` repositories have moved

My `/etc/apt/sources.list` had three repositories in it, all of which threw errors when attempting to use `omv-upgrade` or any apt-based upgrade.
(Code, 3 lines)

I replaced these three out-of-date repositories with their archived locations:
(Code, 2 lines)

Note…

ilovecomputers

Jan 20th 2024

Additionally I followed the instructions in this post (RE: omv-extras repos moving to github) literally. I had done this before, but I tried to be smart and didn't delete/rename the file, but edited it because I didn't want to lose the other entries in it. That was wrong. Follow the instructions! The file will be recreated later by OMV anyway.

Now i can run sudo apt-get update without errors. That takes me a small step further.