search for omv-regen.
Beiträge von ryecoaaron
-
-
will stay for now on OMV6 and try to install OMV7 from scratch.
Once you have it working on OMV 6, you should upgrade to omv7.
-
I have a test version of the compose plugin that has a couple of new features.
- The backup works with compose files that use an environment variable in the path
- Added option to import a single compose file
wget https://omv-extras.org/testing/openmediavault-compose_7.0.11_all.deb -O openmediavault-compose_7.0.11_all.deb
sudo dpkg -i openmediavault-compose_7.0.11_all.deb
-
If you have backups, you might as well try to:
sudo rm -rf /var/lib/docker /var/lib/containerd
This does assume you didn't change the docker storage path on the Settings tab.
-
Let me check
Not much to check. I haven't released anything yet. It might be a couple of days.
-
Did <arrays> already exist in the previous version?
If you had enabled the testing repo and installed 6.2.x version of the snapraid plugin for the short time it was available. It looks like you did that. That version was not very well tested. So, when you upgrade to OMV 7.x, it isn't doing any upgrade for array support and you have invalid parity numbers. There are a couple of options:
Delete the drives and re-add them in the same order in the plugin
Manually edit the paritynum field setting it to 1 for non-parity drives and 1 thru 6 for the parity drives.
-
-
I wasn't saying the SD card is failing. Just something to look at.
-
Your post-upgrade fix fails as there is no pve repo post update. The OMV6/7 upgrade deletes the pve repo and AFAIK the only thing that installs a pve repo on OMV is when omv-installproxmox is run.
I installed the 6.5 kernel before doing that. I guess that step was assumed no matter what the solution. I guess I could make omv-release-upgrade stop deleting it but my energy to test it is very low.
4. Via the WebUI System omv-extras enable backports.
If the packages are newer in the Debian backports repo, this could still lead to the zfs packages being updated and dkms/zfs-dkms being installed. I could have something (zfs plugin or kernel plugin) create an apt preferences file but it would be very confusing due to the number of options possible. I think the safest thing to do is leave backports disabled. I don't think it is needed for anything on OMV 7.x currently anyway.
-
is something broken with the compose addon?
Why the tag? There are plenty of people on the forum that can help with this.
The plugin for OMV 6.x hasn't been changed in four months. And all it does is make sure docker is installed. It wouldn't have anything to do with containerd not starting.
I cannot start the containerd service, cannot reinstall docker. Cannot change the storage destination. I restored old backups and updated the docker but its useless. I cant start the containers, cannot see anymore images.
I would apt-get remove openmediavault-compse and apt-get purge docker-ce containerd.io. then reboot and reinstall the plugin. Removing the plugin won't delete the database (purging will). If you are using an SD card, it might be starting to fail.
-
This has been added - https://github.com/OpenMediaVa…c1edafc799bb4e26641dbdd2e
I am still testing the other new change (support backups for paths using environment variables) but it will be released after that.
-
It seems like the plugin didn't install correctly. What is the output of:
dpkg -l | grep -E "iperf|openme"
sudo omv-showkey iperf3
-
Please note that the output above includes modifications that I have done to snapraid.conf and config.xml after realizing that I can't save any changes from the Snapraid UI. I have a backup of the original config.xml prior to the upgrade from OMV 6 to 7.
I need the config in the broken state. I guess if you post the omv6 config prior to the upgrade, i can figure something out.
-
o there is no possibility to import a single compose file. If i point out to the root folder with all of the compose files, but part of them are already available in the database, are they gonna be overwritten by the once being jmported
No. It will NOT overwrite anything already in the database. It only imports things that are not in the database. I can look at something that will only import one.
-
-
This is not what i see. In my compose folder I do have a folder named filebrowser which has filebrowser.yml and filebrowser.env . Whar i point the folder filebrowser in the import browsing window, the import seem to complete successfuly. No error message appear however i can not see a new filebrowser entry in the gui. Tested a few times
You don't want to point to the filebrowser folder. You want to point to the filebrowser parent folder. The import is currently designed to import everything in that folder not necessarily a single folder.
-
The problem is that backports is most likely enabled and backports has a newer version of zfs-zed and zfsutils-linux than what is in the proxmox kernel. When these debian packages are installed, the depend on zfs-dkms.
So, people could disable backports before upgrading (I didn't test that) OR you can fix it after the upgrade with:
omv-changebackports no
apt-get install zfs-zed=2.2.2-pve2 zfsutils-linux=2.2.2-pve2
apt-get purge zfs-dkms dkms
No need to remove the plugin.
-
is the importing expected to create the corresponding compose file in the database ?
Yes. Its only function is to read compose files that do not exist in the database already and put them in the database.
-
Could you give a short explanation what exactly will be copied and where.
You select the File that you want to sync the database from the compose file on the filesystem. That's it. It is syncing from the same place that the plugin writes to.
Also if a compose file does not exist in the gui but are available in the compose/backup folder what should i do in order to get it available in the gui as well
Use the Import feature on the Files tab. It will import anything it finds that is not already in the database.
-
The restore process doesn't make any database changes. If you want the restore yml file changes in the database, I would recommend using the "Sync changes from file" from the Files tab. This will put the changes in the yml files in the database.