Excellent OMV6 -> 7 upgrade experience and Thank You!

I also just run an upgrade from OMV-6 to 7.. No issues, no problems, easiest/smoothest upgrade I have seen in OMV. THANKS to votdev and ryecoaaron for an outstanding work.

I concur. I always have been afraid of omv upgrades and would put them off. But security pushes me all the time

This time, amazingly smooth transition.

Thanks!

same here. I started the upgrade and it went through super smoothly without any problems. Big thanks for the great work.

Ich möchte mich gerne mit in die Reihe der problemlosen upgrader begeben. Wie sah eure Vorgehensweise aus?

-> reicht das Kommando "omv-release-upgrade" ?

Oder ist hier mehr zu beachten?

Gelesen habe ich dass im nachhinein in den Plugins "openmediavault-md" zu installieren sei?

Vielen Dank

____ ... __________

I would like to join the ranks of problem-free upgraders. What was your approach?

-> is the command “omv-release-upgrade” enough?

Or is there more to consider here?

I read that later in the plugins "openmediavault-md" should be installed?

Thank you

question for all the people who had a smooth upgrade experience, what plugins / services are you running?

did everything work out with docker, disk-encryption, media-shares and so on or did anything cause manual fine tuning?

Just to add my Thanks here too.

But at first it didn't go well, two attempts (using steps in the guide mentioned above) failed, still left with ver 6 then unable to access at all. These attempts I ran the commands from WeTTY within the web browser, I noticed that some actions stopped due to file being in use!?!.

So the third & successful attempt I ran commands from the server screen login (after reinstalling my os drive backup).

So did having the web browser Dashboard open cause the errors?

Hi folks!

i followed this Guide, when i entered "sudo omv-upgrade" i got a lot of errors about public keys.

I googled and "sudo omv-aptclean repos" solved my problem. No clue what it was..

After that, i could update and upgrade withour any issues.

Thanks for your great work!

I love the drive-temperatures on the dashboard!

Greets from germany, Tom

Migration from OMV 6 to OMV 7 failed, encountered some issues. How to resolve them?


I need assistance.

It's terrible, I didn't see this article earlier and directly executed the [tt]omv-release-upgrade[/tt] command, which resulted in unrecoverable errors.

Can anyone help me resolve this?

Updating from omv6 to 7 on rpi4 went very smoothly. No problems at all - thanks all!

Same here upgrade from v6 to v7, so smooth. v5 to v6 was not the same case.

Really late to the party, but I just did the upgrade and it was really seamless - no issues whatsoever! Thank you for all the efforts, it is much appreciated!

As I am using Software RAID management, I ran the following commands (after creating a backup of course):

1. sudo omv-upgrade
2. sudo omv-release-upgrade
3. sudo apt install openmediavault-md (right after the installation, i.e. before rebooting:)
4. sudo reboot

I'm also late and wanted to follow the linked guide. However, after executing sudo omv-salt stage run deploy nothing happens. No output at all. I cancelled it after several minutes.

Shall I risk executing sudo omv-release-upgrade or do I need to trouble shoot something?

Thanks, it now did something after some time and failed with...

[ERROR   ] Command 'blkid' failed with return code: 2
[ERROR   ] retcode: 2
[ERROR   ] Command 'blkid' failed with return code: 2
[ERROR   ] output: 

I've an suspicion. One of my configured HDDs is not installed. OMV complains that one file system does not exist (unable to read filesystem state). In the web interface, one file system is marked as missing. However, when I try to edit it, I get an error message fsname: The value "" does not match exactly one schema of [{"type":"string","format":"fsuuid"},{"type":"string","format":"devicefile"},{"type":"string","format":"dirpath"}]. .

How can I fix it?