Questions about omv-regen

Quote from Petr_d

Much better would be to check plugin versions at the beginning

I agree, it would be more appropriate to do that check beforehand, but on a clean system you cannot do that check beforehand since omv-extras is not yet installed and the repositories are not configured. If you have any ideas on how to do it, I could try it.

Quote from Petr_d

I decided to go to risk: I rewrite version number in ORB_DpkgOMV file to fool your program a bit.

What you did may end up corrupting the system if the database format is different with the new version of ZFS plugin. That is the reason to do those checks and stop the process if necessary. It may be working fine now but in the future you may have strange problems if some tag is missing in /etc/openmediavault/config.xml

Quote from Petr_d

Proxmox kernel did not download and ZFS plugin works fine with the stock one. The Proxmox kernel was the version 5.4.

Kernel 5.4 is old, it has not been installed because it is not in the list of those currently installed by the omv-kernel plugin. ZFS can work without the proxmox kernel, but the system will have to compile ZFS into the kernel every time there is an update. That's the reason to use a proxmox kernel, ZFS is already built into the kernel because it comes from Ubuntu. I recommend that you install a current proxmox kernel on that system.

Quote from Petr_d

I understand. But the versions differed only in patch number, so I tried to do it with the possible consequences in my mind. At that moment it would have been very difficult to make a new backup on the old system. but I think all went OK and all shares work fine.

For your peace of mind, I just checked that the openmediavault-zfs plugin doesn't have any sections in /etc/openmediavault/config.xml, so I guess you shouldn't have any problems after what you did.

Quote from Petr_d

Final words: Thanks a lot, you saved me a lot of time! Next time I will do backup and regeneration as close as possible.

I'm glad omv-regen helped you

Quote from varro986

Simply updated packages and then it stops

At what point does it stop? Can you look at the log and publish the last lines of that execution?

Quote from varro986

Great work my friend, you deserve a beer

Thank you!

I'm wondering if it would be possible to downgrade the OMV version to an older version. I haven't tried it, but knowing the packages are available could be very useful for omv-regen. https://github.com/openmediava…ool/main/o/openmediavault

Any ideas?

As for the default OMV plugins, it wouldn't be difficult to download a specific package from a previous version and install it, but with the omv-extras plugins I think I can't find the packages from previous versions in the repository. ryecoaaron , do those packages exist or do you just keep the latest version?

Quote from ryecoaaron

Usually a bad idea because the database schema may have changed and downgrading will not fix it.

If the problem is only the database, I think it should not be a concern since the original database would be available, which is the one that will finally be used after the regeneration. How could I do that degradation?

Quote from ryecoaaron

reprepro only keeps the latest version and the omv-extras repo is maintained with reprepro.

Well, I'll have to settle for taking advantage of what Volker keeps from his pluguins.

Quote from ryecoaaron

The best way to do it would have omv-regen download the .deb plugin file and put it in the backup (they are very small). This could be done with apt-get download.

Yes I know. Plugins are no problem, I can schedule the installation of an older version of a plugin if I can download the package. I have done it many times manually, sometimes helping you to test things.

My current question is how to downgrade the openmediavault version.

Quote from ryecoaaron

You don't want to. You would need to install the version you want.

That is to say, it cannot be done. I feared it

As a last solution, I could document how to install a specific version of OMV and have the user do it manually. At least that would make any omv-regen backup more or less usable if it is not too old.

The limit would be not to find an update to critical packages along the way. These are the ones related to the omv-extras file system, of which there is no previous version. zfs, mergerfs, etc.

Another idea is occurring to me. You could have the omv-regen backup include the packages that currently exist in the backup. That way they would be available to install during regeneration. They would have to be downloaded every time a backup is made, of course. And update the system previously. What do you think?

Quote from CGA11

Just registered to say that I think this is an excellent idea.

Thank you.

I think I'll try to schedule this but it will take a lot of time that I don't have right now.