Is there a guide to in place upgrade?

Quote from MatJed

Can anyone help me with these errors? Thanks in advance

Err:7 https://download.mono-project.com/repo/ubuntu stable-bionic InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A6A19B38D3D831EF

W: GPG error: https://download.mono-project.com/repo/ubuntu stable-bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A6A19B38D3D831EF
E: The repository 'https://download.mono-project.com/repo/ubuntu stable-bionic InRelease' is not signed.

Search the files under /etc/apt/sources.list.d/ and remove that REPO wherever it's mentioned.

After run and post the output of:

omv-update (or omv-upgrade, never remember which one is it)

Quote from Soma

Code

Err:7 https://download.mono-project.com/repo/ubuntu stable-bionic InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A6A19B38D3D831EF

W: GPG error: https://download.mono-project.com/repo/ubuntu stable-bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A6A19B38D3D831EF
E: The repository 'https://download.mono-project.com/repo/ubuntu stable-bionic InRelease' is not signed.

Search the files under /etc/apt/sources.list.d/ and remove that REPO wherever it's mentioned.

After run and post the output of:

omv-update (or omv-upgrade, never remember which one is it)

Here omv-upgrade after deleting the REPO with that error.

No more errors. Am I ready to upgrade?

Quote from MatJed

No more errors. Am I ready to upgrade?

If you have a working clone of the OS system, yes.

Quote from Soma

If you have a working clone of the OS system, yes.

Upgraded and broke plex and pihole container. Already fix it and everything good to go!

Thanks

I tried to upgrade from omv6 to omv7 twice, both times at the end there was a message that the upgrade was successful, but after the reboot I'm still on omv6 and bullseye.

I rum OMV on OdroidXU4 with armbian.

The sudo omv-salt stage run deploy command passed without error the first time, but now it throws a bunch of incomprehensible characters. After the omv-upgrade command I get a warning:

The following packages have been kept back: armbian-bsp-cli-odroidxu4 samba-common sources.list is like this:

# deb http://deb.debian.org/debian bookworm main contrib non-free
# deb-src http://deb.debian.org/debian bookworm main contrib non-free

deb http://deb.debian.org/debian bookworm-updates main contrib non-free
# deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free


#deb http://security.debian.org/ bookworm/updates main contrib non-free
## deb-src http://security.debian.org/ bookworm/updates main contrib non-free

Oh wow, someone still using XU4. Have you tried running the fix script?

wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/fix6to7upgrade | sudo bash

I would also post in THIS thread. It is a more general one where people that had issues have been posting.

I did, but I still have the same problem.
I decided to go with fresh install of openmwdiavault 7

Hi,

Just upgraded OMV 6 to 7 today after reading your posts. First I run: omv-upgrade and after omv-release-upgrade
In my Box I have a 500Gb SSD system disc and a raid of five 5,46 Tb disks (around 21,74Tb for data)

During upgrade system suggest me to install the plugin: openmediavault-md, I do it and all runs perfectly after upgrade !!

Thanks a lot for your help.

Hey Guys,

I am trying to do an update to the current version of OMV from 6.9.16-1 and I ran the first step:

sudo omv-salt stage run deploy

Looks like things are ready as I see:

Summary for debian

------------

Succeeded: 2 (changed=2)

Failed: 0

However, I just wanted to understand the following errors that I received at the very end after the total run time is displayed:

[ERROR ] Command 'mount' failed with return code: 11

[ERROR ] stderr: Remounting is not supported at present. You have to umount volume and then mount it once again.

[ERROR ] retcode: 11

[ERROR ] {'umount': 'Forced remount because options (big_writes) changed'}

[ERROR ] Command 'mount' failed with return code: 11

[ERROR ] stderr: Remounting is not supported at present. You have to umount volume and then mount it once again.

[ERROR ] retcode: 11

[ERROR ] {'umount': 'Forced remount because options (big_writes) changed'}

Any ideas on what these errors could be related to?

Followed instructions posted by Zoki in post #2 of this thread. Coming from OMV6. No issues at all.

System is N95 CPU. Had a clean install of OMV6 from about a year ago.

Thanks!!

I'm on a 10 year old Intel Xeon with ZFS and docker plugins. Used Zoki instructions in post #2 of this thread and am now on 7.4. Only had to touch the keyboard twice during the massive upgrade, and then reboot at the end. Everything seems solid. Very nice!

Quote from Blueman2

Followed instructions posted by Zoki in post #2 of this thread. Coming from OMV6. No issues at all.

System is N95 CPU. Had a clean install of OMV6 from about a year ago.

Thanks!!

Display More

Same here. Kept putting off the upgrade since I was afraid of something breaking but everything went smoothly.

Hi everyone, thank you for your valuable input in the upgrade process, I am still on latest OMV6 and wanted to ask you the following:

• Anyone did an on-device upgrade like that, whilst using a USB stick to boot the system? (I have SATA for pure data storage and boot OMV6 from an expensive USB flash disk)
• The plugins and OMVExtras will also be automatically updated, or at least, will OMVExtras will remain enabled for user-updating the extras later?

Many thanks

Thanks for your confirmation macom so my upgrade on my lesser complex OMV6 Intel NUC (Celeron J3455 with 8GB RAM) also went smooth, I'd just like to report a couple of things for people to be aware during update. I migrated from 6.9.16-1 to latest 7.4.10-1 with my boot drive being a Samsung Fit Plus 64GB (USB 3.1).

1. Logged in as root and performed sudo omv-salt stage run deploy and there were no issues except the following related to WireGuard enabled on my OMV:

[...] Summary for debian
------------
Succeeded: 2 (changed=2)
Failed:    0
------------
Total states run:     2
Total run time: 132.303 s

[WARNING ] State for file: /etc/wireguard/wgnet1.conf - Neither 'source' nor 'contents' nor 'contents_pillar' nor 'contents_grains' was defined, yet 'replace' was set to 'True'. As there is no source to replace the file with, 'replace' has been set to 'False' to avoid reading the file unnecessarily.

[WARNING ] State for file: /etc/wireguard/wgnet_client1.conf - Neither 'source' nor 'contents' nor 'contents_pillar' nor 'contents_grains' was defined, yet 'replace' was set to 'True'. As there is no source to replace the file with, 'replace' has been set to 'False' to avoid reading the file unnecessarily.

[WARNING ] State for file: /etc/wireguard/wgnet_client2.conf - Neither 'source' nor 'contents' nor 'contents_pillar' nor 'contents_grains' was defined, yet 'replace' was set to 'True'. As there is no source to replace the file with, 'replace' has been set to 'False' to avoid reading the file unnecessarily.

Not sure what this means as I couldn't decipher this warning and upon examining the configs, I could not detect an issue.

2. I stopped all Docker containers, updated to latest current OMV with sudo omv-upgrade then started the process with sudo omv-release-upgrade

3. At some point during the upgrade, I got 2 e-mail notifications which are likely sent when PHP was I being upgraded I guess?

Subject: Monitoring alert -- Execution failed php-fpm
Service:     php-fpm
Event:       Execution failed
Description: failed to start (exit status 1) -- '/bin/systemctl start php7.4-fpm': Failed to start php7.4-fpm.service: Unit php7.4-fpm.service is masked.

Subject: Monitoring restart -- Does not exist php-fpm
Service:     php-fpm
Event:       Does not exist
Description: process is not running

4. The process ended without errors, rebooted as instructed and I was welcomed in OMV7

All configuration, users, scheduled tasks were there, OMV Extras up-to-date. I only needed to start my two Docker containers.

5. This was done remotely via SSH and "root" user, not near the device (thankfully no issues occurred!)

Thank you all for your help in this thread, if anyone can comment on the two above, would be useful to know for other people.

EDIT: Question:

In folder /etc/ a few files of extension *.distrib.dpkg-dist were left there, are they to be removed-deleted? Examples are:

hdparm.conf.distrib.dpkg-dist
logind.conf.distrib.dpkg-dist
mdadm.distrib.dpkg-dist
monit.distrib.dpkg-dist
monitrc.distrib.dpkg-dist
smartd.conf.distrib.dpkg-dist
smartmontools.distrib.dpkg-dist
watchdog.conf.distrib.dpkg-dist
wsdd.distrib.dpkg-dist

The actual config files, obviously, remained.

Thanks.

Quote from Konsti

EDIT: Question:

In folder /etc/ a few files of extension *.distrib.dpkg-dist were left there, are they to be removed-deleted? Examples are:

I think those are there because the update process was instructed to save the old files. Whenever a conf file is updated, you should be normally asked about what you want to do. My machine does not have any of those files, but I updated from an older 6.x to an older 7.x.

It might be helpful to add the link tot he fix6tp7update script. Here some information I found on another post to resolve an issue I had when upgrading and there was a plugin missing, openmediavulat-md from the list of available plugins.

clearing your browser cacherun the fix6to7upgrade script

wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/fix6to7upgrade | sudo bash

Thank you

Rob