OMV 4.1.36-1 (Arrakis) not fetching updates

Please consider installing the system with OMV6 from scratch. Debian 9 + OMV4 and Debian 10 + OMV5 are EOL. This means for Debian that the package repositories have been archived and their URLs have been changed. OMV has not adapted this because OMV4 and OMV5 are also EOL and not maintained anymore. You can do all manually if you know what you are doing, but a clean installation is prefered.

Did not read the pastebin text. The formatting is bad. But yes, you have not updated in more than two years. OMV4 is end of life for an even longer time.

This might help you, but you should really do a fesh install using OMV6.

Thread

omv-extras repos moving to github

Because Bintray is dropping their repo hosting service (https://jfrog.com/blog/into-th…gocenter-and-chartcenter/) on 2021-05-01, I have moved the omv-extras repos to github. omv-extras 5.5 will change the repos to point to github. This package is in the testing repo now. People will have until bintray is shutdown to upgrade. I will move the 5.5 package of omv-extras to the regular OMV 5.x repo in a few days. I might release an OMV 4.x package with the updated repos but I am not releasing a…

ryecoaaron

Feb 10th 2021

Quote from VicMaccie

I think I face the same problem, still on OMV4, what brings me to the follow-up question:

Every time OMV gets to the next major version, should one do a clean install from scratch? I find this very frustrating and also a little bit scary, as there is a lot of stuff on my NAS, like docker and encrypted files/drives for them to work with the next major version...

Personally, with virtually everything on my server running in docker... i find it easier to just do a clean install.. of course this means making sure all the paths for your containers stay consistent, etc. (this is why I switched exclusively to symlinks for my docker volume paths).

Now, I could buy all new hardware, drives, etc.. and it's a relatively simple procedure and i"ll be right back where I started (obviously the only thing not included here, is moving data to the new drives).

1. Install OMV

2. Install OMV-extras and do some minor setup stuff (static IP, change passwords, setup users, etc)

3. Set up my Shared Folders

4. Set up my Symlinks (this is the only critical step, as all your symlinks need to be the same as they were on the old system.. so usually before starting, I take a screenshot of my symlinks setup)

5. Install docker and make sure it's pointed at my old containers folder.

6. At that point, all my containers should be backup like nothing.

Now I just go through and setup my network shares (be they NFS, SMB, whatever)

and I'm done.

Quote from VicMaccie

Every time OMV gets to the next major version, should one do a clean install from scratch? I find this very frustrating and also a little bit scary, as there is a lot of stuff on my NAS, like docker and encrypted files/drives for them to work with the next major version...

OMV4 to OMV5 was tricky. OMV5 to OMV6 went very smoothly for me and others without reinstall. As I understand the upgrade from OMV6 to OMV7 is also expected to be painless. But let's see. It is some time ahead.

But yes, some prefer to do a fresh install. I would always give it a try and do a reinstall only if it fails.

Quote from VicMaccie

can you point out some guides or references to learn doing this? especially the part about symlinks seems rather advanced/confusing for me

Symlinks -> https://wiki.omv-extras.org/do…mv6:omv6_plugins:symlinks

An alternative way to do this is to use global environment variables in docker. The openmediavault-compose plugin allows you to do this in a simple way and has more utility than just simplifying paths. https://wiki.omv-extras.org/do…l_environmental_variables

Quote from VicMaccie

can you point out some guides or references to learn doing this? especially the part about symlinks seems rather advanced/confusing for me

Other than the guide on symlinks, not really a "guide" per se. It's a process I came up with on my own.

The keys really are

Keep your docker paths consistent. I symlink all of my "/config" folders symlinked under /NAS/AppData, this includes (before the new plugin) a /data folder for Portainer so all my stacks are saved, etc.

All of my Media, is symlinked under /NAS/Media/ (ie, /NAS/Media/TV, /NAS/Media/Movies, /NAS/Media/eBooks, etc.).

Then I just slowly work my way through my containers, and make sure all of my volumes are pointing at those symlink locations

Then of course, make sure your containers are not stored at /var/lib/docker and are on one of your data drives.

Once you're that far and you've got all your containers working from the symlinked location.. you just follow what I said above, in that order.

Obviously the fact I'm not really using very many plugins, helps this process, as virtually everything on my server is managed via docker.