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?