Is there a guide to in place upgrade?

Quote from Soma

There's no failed issues, it should be OK.

If you have a working OS drive backup and no errors on omv-upgrade you can continue with omv-release-upgrade

If running the upgrade remotely, use a screen session to prevent lost connection.

Running locally has no problems.

Display More

Hello

Si I ve made my release upgrade and it seems to be ok. I had to run the command

sudo omv-salt stage run deploy

after the reboot as I was unable to reach the Web gui (Bad gateway)

Every service are working fine so far (rsync, compose, backup etc ...)

Today I had this message:

========================================================================

apticron has detected that some packages need upgrading on:

	omvyvc.local 	[ 172.17.0.1 172.18.0.1 172.19.0.1 172.22.22.189 ]

The following packages are currently pending an upgrade:

	firmware-amd-graphics 20240709-2~bpo12+1
	firmware-atheros 20240709-2~bpo12+1
	firmware-bnx2 20240709-2~bpo12+1
	firmware-bnx2x 20240709-2~bpo12+1
	firmware-brcm80211 20240709-2~bpo12+1
	firmware-cavium 20240709-2~bpo12+1
	firmware-intel-sound 20240709-2~bpo12+1
	firmware-ipw2x00 20240709-2~bpo12+1
	firmware-ivtv 20240709-2~bpo12+1
	firmware-iwlwifi 20240709-2~bpo12+1
	firmware-libertas 20240709-2~bpo12+1
	firmware-linux 20240709-2~bpo12+1
	firmware-linux-nonfree 20240709-2~bpo12+1
	firmware-misc-nonfree 20240709-2~bpo12+1
	firmware-myricom 20240709-2~bpo12+1
	firmware-netronome 20240709-2~bpo12+1
	firmware-netxen 20240709-2~bpo12+1
	firmware-qcom-media 20240709-2~bpo12+1
	firmware-qcom-soc 20240709-2~bpo12+1
	firmware-qlogic 20240709-2~bpo12+1
	firmware-realtek 20240709-2~bpo12+1
	firmware-samsung 20240709-2~bpo12+1
	firmware-siano 20240709-2~bpo12+1
	firmware-ti-connectivity 20240709-2~bpo12+1

You can perform the upgrade by issuing the command:

    apt-get dist-upgrade

as root on omvyvc.local

I am not sure I need to perform this command ... 

Any advice ?

Quote from ryecoaaron

If you see the updates in the Updates tab, you should be fine to install them.

There is no update available in the update tab ... That's why I am a little bit confused ....

I just run this command :

sudo apt update

[sudo] password for yvc:

Get:1 file:/var/cache/openmediavault/archives InRelease

Ign:1 file:/var/cache/openmediavault/archives InRelease

Get:2 file:/var/cache/openmediavault/archives Release

Ign:2 file:/var/cache/openmediavault/archives Release

Get:3 file:/var/cache/openmediavault/archives Packages

Ign:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:5 file:/var/cache/openmediavault/archives Translation-en_US

Ign:5 file:/var/cache/openmediavault/archives Translation-en_US

Get:3 file:/var/cache/openmediavault/archives Packages

Ign:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:5 file:/var/cache/openmediavault/archives Translation-en_US

Ign:5 file:/var/cache/openmediavault/archives Translation-en_US

Get:3 file:/var/cache/openmediavault/archives Packages

Ign:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:5 file:/var/cache/openmediavault/archives Translation-en_US

Ign:5 file:/var/cache/openmediavault/archives Translation-en_US

Get:3 file:/var/cache/openmediavault/archives Packages

Ign:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:5 file:/var/cache/openmediavault/archives Translation-en_US

Ign:5 file:/var/cache/openmediavault/archives Translation-en_US

Get:3 file:/var/cache/openmediavault/archives Packages

Ign:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:5 file:/var/cache/openmediavault/archives Translation-en_US

Ign:5 file:/var/cache/openmediavault/archives Translation-en_US

Get:3 file:/var/cache/openmediavault/archives Packages

Ign:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:5 file:/var/cache/openmediavault/archives Translation-en_US

Ign:5 file:/var/cache/openmediavault/archives Translation-en_US

Get:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:5 file:/var/cache/openmediavault/archives Translation-en_US

Ign:5 file:/var/cache/openmediavault/archives Translation-en_US

Hit:6 http://packages.openmediavault.org/public sandworm InRelease

Hit:7 http://httpredir.debian.org/debian bookworm-backports InRelease

Hit:8 http://security.debian.org/debian-security bookworm-security InRelease

Hit:9 http://debian.ethz.ch/debian bookworm InRelease

Hit:10 http://debian.ethz.ch/debian bookworm-updates InRelease

Get:11 https://download.docker.com/linux/debian bookworm InRelease [43.3 kB]

Hit:12 https://openmediavault.github.io/packages sandworm InRelease

Ign:13 https://get.filebot.net/deb universal InRelease

Get:14 https://openmediavault-plugin-…github.io/packages/debian sandworm InRelease [3,939 B]

Hit:15 https://get.filebot.net/deb universal Release

Fetched 47.3 kB in 1s (37.8 kB/s)

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

24 packages can be upgraded. Run 'apt list --upgradable' to see them.

W: https://get.filebot.net/deb/dists/universal/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

I will wait maybe tomorrow if this update are done during the night

Quote from ryecoaaron

Run sudo omv-upgradeOk

ok it's done. Thank you for your help. Happy new year !

Hello and a happy new year

I also struggle to finally update my Pi4 from 5 to 6, in the beginning due to outdated links/sources.

The salt deploy check always resulted with 1 error in the end (acc. to text color the text block checking NETPLAN was red highlighted - sorry, no copy of the full output available.)

After I tried some tipps from this thread (apt clean I guess?), I could finally run the upgrade command.

I just realized from the copied output, that I used "sudo omv-upgrade" instead of the intended "sudo omv-changebackports NO." - probably copy&paste to putty went wrong.

At first it looked good, but issues with restoring the backup?

after the attached script output, I rebooted - and the last proof of life was my router, assigning a new IP to my NAS once! and that was it.

Always timeout when trying with GUI or SSH, and now even this IP dissappeared. Rebooted by unplug power, but no new or active IP from my NAS visible.

Any ideas how to bring it online again to do some troubleshooting?

My system configuration was very basic; just installed OMV, added sources, drives, volumes, users, rights and that was it; no special plugins oder deeper configurations, just for attaching my big USB HDD to my local network as NAS.

But I would prefer not to start from scratch again.

[of course I did a full backup (the first of the backup options with all partitions) - but mastermind: this backup is still on the NAS attached HDD :)]

Thank you in advance.

Allright, setting up a fresh new SD card with straight jumping to OMV 7 and reconfigure everthing I need was indeed no rocket science and all is running and accessible as desired.

So from my side, my request is closed.

Thank you nevertheless, bye.

Quote from Zoki

Contributions wanted:

1. Backup the OS drive (this is allways a good idea, not only for upgrades)
2. Make sure, you have enough free space on your os drive
3. Check any installed plugins if they have been ported to OMV6
   If you are using plugins which have not been / will not be ported, get rid of the plugins except unionfs / mergefolderfs. These two will automatically be be converted to the newer mergerfs plugin
   (Many plugins can be replaced by docker containers. Do this before upgrading)
4. If you installed software from foreign repos make sure they have a release for bullseye or remove the repos / software
5. Go to the cli (Putty, ssh, keyboard) and run these commands (In case of errors stop and ask on the forum before makingthings worse)
   1. Make sure your current install is correct all configs can be deployed by running sudo omv-salt stage run deploy
   2. Get the current install up to date: sudo omv-upgrade
   3. Do the release upgrade by running sudo omv-release-upgrade
      If you see an error message from patch which says a patch has alredy been applied, ignore it. (this is the only error to be ignored)
6. Wait for the last script to finish and reboot.
7. Refresh/clear browser cache (Crtl-Shift R on most browsers)
8. Check if all services and docker containers are running as you expect.
9. If you see Linux image Updates you can not install on the UI, go to the cli and run omv-upgrade once more.

Edit:

• Added hint to run omv-upgrade if images can not be updated in UI

How can we interpret the output of `sudo omv-salt stage run deploy`? Why is it supposed to show if things were broken? Output is huge!

Quote from VaryingLegwarmer

How can we interpret the output of `sudo omv-salt stage run deploy`?

If it shows "failed" anywhere, then it means something is wrong and need to be sorted.

Quote from votdev

I'm wondering about that. The file should be auto-removed by APT during the upgrade because it is part of the package (not created manually via Salt).

Hello everyone, FYI I discovered via journalctl -p 3 -xb that this file also remained in my recent in-place upgrade from OMV6 to OMV7 in /etc/udev/rules.d/ folder:

-rw-r--r-- 1 root root 1378 Dec 28 2021 99-openmediavault-scheduler.rules

Should I manually remove it? Now running latest OMV7 and get boot errors like:

Jan 15 13:05:35 NUC-NAS (udev-worker)[374]: sdc: /etc/udev/rules.d/99-openmediavault-scheduler.rules:24 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:15.0/usb2/2-2/2-2:1.0/host3/target3:0:0/3:0:0:0/block/sdc/queue/scheduler} ignoring [...]

Thank you all.

P.S. I think this file is from the OMV5 days... on my clean still-running OMV6 server, it doesn't exist in path /etc/udev/rules.d/

So I took the chance and removed it from my OMV7 server, rebooted, no more "scheduler" errors as above.

Hi, i was thinking in upgrade omv6 to 7, when i ran sudo omv-salt stage run deploy

i get this , it said 1 failed, tbh im kinda new on Linux, want to be sure if i can proceed, i do have a plex server and hosting a website, so i don't want surprises .

thanks

Quote from macom

The file seems to be broken. However there is one issue related to timezone. Which timezone did you set in the GUI of OMV? Maybe change it to something else and then change back to the correct one. After that run the omv-salt command again.

If it still fails, post the output again.

And also the output of

cat /etc/timezone

Got it, not sure about time zone, I will check asap

edit: well there was not time zone set somehow, here is the output file

Quote from macom

All good. Nothing failed.

Make a backup of the OS drive and then you are good to run omv-release-upgrade

sweet, any special way to clone/backup the disk?

Quote from macom

For ssd/hdd I use Clonezilla.

For USB thumb drives or sd cards I use usbimager.

upgrade went smooth, everything is working, thanks for your time.