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

What do you mean you are lookinf for ssh and webpanel?

Do you mean sshd and nginx are not running on your OMV?

Did you check systemctl. status nginx.service

thanks, ryecoaaron gave me an answer on a topic i've created for this, but still doesn't work No SSH , No Web interface

my networks problem are fixed now, i just have to fix the shared folders issues and my omv is back online.

To thanks all help i received, i made a little donation

Sorry, dumb question, Is this topic about "omv-release-upgrade" or some other utility? I wanted to read about what omv-release-upgrade does in prep for an omv5 to 6 upgrade and I'm having a hard time finding any documentation. I take it from comments this script will do both the debian upgrade and the omv upgrade. Do I run the version in my omv5 install or pull a new one somehow from omv6 to run? I'm hesitant to run any script until I understand what it's going to do :-).

steve

Ok, thanks! It looks like the omv5 script will default to 6.0/shaitan so I just use the script in the 5.0 installation. How do I tell which plugins are ready for 6? I see all the plugins on github. I guess if something has a 5.x branch then master must be for 6, but does that mean it is ready?

Perfect, thanks again.

Thanks for the script, at the end it worked, however some obstacles. Those might be useful to know for more readers and/or the creator of the script. I upgraded (rather late ...) from OMV 4 to OMV 5 on HP Microserver.

Sorry, if this is a repetition, honestly, I did not check all the messages of the 16 page thread.

0. [I'll write about this later, to have the stuff, that might be of more general interest at the front]

1. Error:

Reading package lists...
E: The repository 'https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch Release' does no longer have a Release file.
run-parts: /root/openmediavault-upgrade-4.7/run.d/10-apt-update exited with return code 100

I could solve this, by following omv-extras repos moving to github and restart the upgrade.

Then it succeeded. I rebooted, sort of ok.

2. After upgrade, the hostname was openmediavault, before the upgrade, the hostname was hpms (for HP Microserver). I changed the hostname by the OMV-GUI under System->General->Network->Hostname (I am using a German system, so these are my translations - possibly in an English configuration, the phrases are slightly different.) I rebooted the system by the GUI. When it was booted, it was not accessibly by the net anymore. My router did not find it. The ILO Interface of the Server showed N/A for the NICs. I could still connect to the console by the ILO. I looked at dmesg | grep eth, did not save the output. I rebooted again (no big hope), still no network. omv-firstaid helped here.

a) It seems, that renaming the hostname is yielding in a system without accessability by the network (at least in my environment)

b) It seems the upgrade script will not preserve the hostname. (Sorry, when I have missed this in the docs)

3. I have a strange HD (by USB, NTFS), with a space in the label. This never worked without warnings in OMV, but it did not really influence functionality. I believe some quoting was missing (and some probably still is missing in OMV5, or it might be a consequence of the upgrade path). Now, during booting, I receive a warning:

[    5.592588] systemd[1]: /etc/systemd/system/sharedfolders-SeagateED.mount:7: RequiresMountsFor= path is not absolute, ignoring: Expansion
[    5.592664] systemd[1]: /etc/systemd/system/sharedfolders-SeagateED.mount:7: RequiresMountsFor= path is not absolute, ignoring: Drive

And the file:
 cat /etc/systemd/system/sharedfolders-SeagateED.mount
# This configuration file is auto-generated.
[Unit]
Description=Mount shared folder SeagateED to /sharedfolders/SeagateED
DefaultDependencies=no
After=zfs-mount.service
Wants=sysinit.target
Conflicts=umount.target
RequiresMountsFor=/srv/dev-disk-by-label-Seagate Expansion Drive
AssertPathIsDirectory=/sharedfolders
AssertPathIsMountPoint=/srv/dev-disk-by-label-Seagate Expansion Drive
AssertPathIsDirectory=/srv/dev-disk-by-label-Seagate Expansion Drive

[Mount]
What=/srv/dev-disk-by-label-Seagate Expansion Drive
Where=/sharedfolders/SeagateED
Type=none
Options=bind,nofail

[Install]
WantedBy=basic.target

So, it looks like missing quoting here.

0. The first error, which might be related to my stupid disk with a space in the label (it was delivered like this).

Remounting is not supported at present. You have to umount volume and then mount it once again.
run-parts: /root/openmediavault-upgrade-4.7/pre.d/20-remount-ro exited with return code 11

I had disabled all the services according to the documentation before. The solution for me seemingly was, to plug out the USB-connected disks, reboot, and rerun the upgrade scripts.

4. I know, that my setup never was totally clean in one other sense. I have 4 external USB-Disks mounted, mainly for Backup purposes. To save energy, I usually have them powered off. Still, they always have been configured inside OMV. It was working for me. Now, I seemingly have to pay a significant startup time penalty, when the disks are powered off during reboot (that penalty was not there in OMV 4). Any idea, how to circumvent this?

Oops, I am very sorry, my fault, embarrassing enough!

(I really did read for a couple of hours about upgrade procedures, and I did find several sources. I believe, I had carefully read https://github.com/dleidert/op…-upgrade/blob/4/README.md, where I did not see the contents of that red sentences at the start of this thread).

I hope, 0. and 2.-4. from my message make more sense.

Hi, thanks for these scripts.

I am a little confused about warnings you wrote in first posts.

I have 3 OMV 5. which have been installed on OMV 4 servers. As i use HP raid cards or LSI or 3ware cards for the volumes, i deleted all partitions on the OS drive which is installed on SSD, and i installed from scratch new OMV5.

But i have also a few OMV 4.x systems which could be upgraded to OMV 5.x with the relevant script.

I have already ran the omv-extra fix (github) on a few OMV 4 and it works fine.

So what is the best way ?

running omv4->5 script on OMV 4.x already set (shares, etc.) like this:

wget -qO- https://github.com/dleidert/openmediavault-upgrade/archive/v4.7.tar.gz | tar -xz
cd openmediavault-upgrade-4.7
sudo ./omv-release-upgrade-5

or, as i have already done in the past, installing OMV5 straigthly on fresh and empty ssd? (or OMV6 !)

thanks.

Have a backup of your os disk and try. if it faile you can go back easily and do a fresh install.

Soem have problems some don't,depending how much non-standard things have been done to the system.

Zitat von Zoki

Have a backup of your os disk and try. if it faile you can go back easily and do a fresh install.

Soem have problems some don't,depending how much non-standard things have been done to the system.

hi,

thanks. I use backup function on all my omv systems, but i never use the restore function from one backup. Thanks for your simple idea.

i m going to run the script OMV 4->5 on a OMV 4 test system. i ll learn this.

Thanks.

hey guys, tried to upgrade from 4 to 5 and got that output.

Edit: Any suggestions ho i can fixe that? sorry absolute noob here

run-parts: executing /root/openmediavault-upgrade-4.7/check.d/01-debian-version
run-parts: executing /root/openmediavault-upgrade-4.7/check.d/02-root
run-parts: executing /root/openmediavault-upgrade-4.7/check.d/10-dpkg
Your package management reports packages in a failed state.


The following packages are missing the md5sums control file in the
database, they need to be reinstalled:
 fdk-aac              Package created with checkinstall 1.6.2
 ffmpeg               Package created with checkinstall 1.6.2
 lame-ffmpeg          Package created with checkinstall 1.6.2
 libopus              Package created with checkinstall 1.6.2
 libvpx               Package created with checkinstall 1.6.2
 pyload-cli           pyLoad without GUI dependencies, fast and lightweight Dow


Fix those first before proceeding.
run-parts: /root/openmediavault-upgrade-4.7/check.d/10-dpkg exited with return code 1

Zitat von rudesounds

The following packages are missing the md5sums control file in the
database, they need to be reinstalled:
fdk-aac Package created with checkinstall 1.6.2
ffmpeg Package created with checkinstall 1.6.2
lame-ffmpeg Package created with checkinstall 1.6.2
libopus Package created with checkinstall 1.6.2
libvpx Package created with checkinstall 1.6.2
pyload-cli pyLoad without GUI dependencies, fast and lightweight Dow

Alles anzeigen

reinstall can be done via be repeating below steps for each package in the list displayed as user root or by pre-pending "sudo"

1. apt uninstall <Package from list>
2. apt install <Package from list>

Just set aside time to perform the 4>5 upgrade this morning and after successful completion, the webgui keeps asking to apply configuration changes and failing on: omv-salt deploy run --no-color samba 2>&1' with exit code '1'

This is the output that appears to be the problem:

openmediavault.config.database.DatabaseQueryNotFoundException: No such object: //system/fstab/mntent[uuid='482424a9-286f-4de3-9a0d-655e9588536e']

All drives that were present in the system before the upgrade are still present after the upgrade, so I don't know where to look.

Copy/paste of the error window in the webgui is attached. What should I do next?

failed.txt

Long-time listener, first time caller. Tried the v4 to 5 upgrade (using script v4.7) after removing all plugins and disabling all services other than SSH. Made sure omv-extrasorg was not installed, dpkg openmedia* only showed openmedia and keyrings.

Script ran for quite a while but failed on updating apt-show-versions:

Error: No information about packages! (Maybe no deb entries?)

dpkg: error processing package apt-show-versions (--configure):

installed apt-show-versions package post-installation script subprocess returned error exit status 255

Processing triggers for man-db (2.8.5-2) ...

Errors were encountered while processing:

apt-show-versions

E: Sub-process /usr/bin/dpkg returned an error code (1)

All further attempts to munge packages just threw an error of "Error: No information about packages! (Maybe no deb entries?)".

Was finally able to get apt-show-versions installed properly and package info updated by using:

rm /etc/apt/apt.conf.d/20apt-show-versions
apt-get purge apt-show-versions
rm /var/lib/apt/lists/*lz4
apt-get -o Acquire::GzipIndexes=false update
apt-get install apt-show-versions

Looks like Debian was successfully upgraded but now unsure how to continue the OMV upgrade. Started running the post.d files in order but 70-ovm-salt fails. Re-running the upgrade script just states that I'm not running stretch so upgrade is not possible.

~/openmediavault-upgrade-4.7# lsb_release -a

No LSB modules are available.

Distributor ID: Debian

Description: Debian GNU/Linux 10 (buster)

Release: 10

Codename: buster

~/openmediavault-upgrade-4.7# dpkg -l |grep openmed

ii openmediavault 4.1.36-1 all openmediavault - The open network attached storage solution

ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive

Running an `apt update` at this point gives me errors like the following:

All packages are up to date.

W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 and /etc/apt/sources.list.d/stretch.list:7

Any suggestions on how to continue?

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.