As for the file, I too have it on one of the Pis I use (the one updated from OMV5).
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).
As for the file, I too have it on one of the Pis I use (the one updated from OMV5).
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).
Hi, I want to upgrade too. How should I backup the os disk?
Other than that I don't need to to anything particular right? As stated before I don't need to unplug the other disks
How should I backup the os disk?
I suggest using clonezilla to make a clone or an image.
If you have an USB Thumb drive usbimager is a good alternative.
How should I backup the os disk?
I use dd run out of an automated script that runs daily.
Any backup strategy is worthless unless you have proven to yourself that the backups can be successfully restored. The time to find out that your backups fail to restore is during testing, not when you have experienced a real system drive failure.
The plugins I have installed are: openmediavault-flashmemory 5.0.7 and openmediavault-omvextrasorg 5.6
How do I know if they have been ported to 6?
Thank you
How do I know if they have been ported to 6?
Is my version too old?
Your version is OMV5. You should be able to upgrade to OMV6 by following the instructions in this thread if you don't want to do a fresh install.
Be careful with the omv-extras repositories, they changed to github a long time ago, I think you have them wrong.
I tried to do omv-update but it fails. Also I doesn't have an omv-upgrade command.
In this thread they explain how to solve the repository change.
If you don't have much experience, I recommend that you do a fresh installation of OMV6. I think you will avoid problems.
Contributions wanted:
- Backup the OS drive (this is allways a good idea, not only for upgrades)
- Make sure, you have enough free space on your os drive
- 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)- If you installed software from foreign repos make sure they have a release for bullseye or remove the repos / software
- Go to the cli (Putty, ssh, keyboard) and run these commands (In case of errors stop and ask on the forum before makingthings worse)
- Make sure your current install is correct all configs can be deployed by running sudo omv-salt stage run deploy
- Get the current install up to date: sudo omv-upgrade
- 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)- Wait for the last script to finish and reboot.
- Refresh/clear browser cache (Crtl-Shift R on most browsers)
- Check if all services and docker containers are running as you expect.
- 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
Thank you for this!!! WHY is this not posted on the OMV home page? 1. I was not aware that the upgrade was available. 2. When I found out 6 was out, I looked on the web page, and NOTHING was mentioned about how to upgrade. Usually "how to upgrade" is an important factor in most software systems. Am I missing something???
OMV has been rock solid for our needs, upgrade was extremely smooth.
1. I was not aware that the upgrade was available. 2. When I found out 6 was out, I looked on the web page, and NOTHING was mentioned about how to upgrade. Usually "how to upgrade" is an important factor in most software systems. Am I missing something???
My "it isn't mentioned" complaint is about the upgrade procedure. It is mentioned in the next to last line on that page, but very easy to miss, and unclear.
Also the EOL for v5 should be a sticky on the main page for a few months to make it very clear to everyone. I didn't know it was no longer maintained. I just think it could have been more clear and obvious how to upgrade. I ended up searching the forums and finding the very clear instructions in the second post on this thread.
My "it isn't mentioned" complaint is about the upgrade procedure. It is mentioned in the next to last line
But it is mentioned. And it is in the official docs - https://openmediavault.readthe…n/latest/various/apt.html. And it hasn't changed in all versions of OMV that were upgradable. I personally don't think the home page or blog should have upgrade instructions. There are almost always other questions and the official docs and forum are the best place for those.
Also the EOL for v5 should be a sticky on the main page for a few months to make it very clear to everyone. I didn't know it was no longer maintained
There is a blog announcing it - https://www.openmediavault.org/?p=3259 - and a twitter post. As for a sticky, I can tell you that barely anyone reads those. Trust me. Just remember Volker is one guy. It takes a lot of time to put the info people want in every location they think it should be in.
I just think it could have been more clear and obvious how to upgrade
It is literally one command - omv-release-upgrade. The other posts have more steps when omv-extras is involved. Volker should not be responsible for those steps. The forum is the right place to look for that info.
I agree that the sticking the post in the blog wouldn't solve much. I think it would be better to push a small update on OMV that will prompt the user with a warning "this version is EOL, it will keep working but it won't recieve any new update" or something like that.
I would also add a link to the wiki page for the upgrade just in case.
How to handle this error? Who knows? No ping after finishing update from OMV5 Buster working on odroid HC2.
Try to configure the network interface using omv-firstaid
If that is not working, remove the mentioned file and try again.
Try to configure the network interface using omv-firstaid
If that is not working, remove the mentioned file and try again.
rm /etc/netplan/20-openmediavault-enx001e0632bfca.yaml
sudo omv-salt stage run deploy
Still the same error.
How about omv-firstaid?
No access via ssh.
nano /etc/netplan/20-openmediavault-enx001e0632bfca.yaml
It was enough to put manually MAC in lane:
network:
ethernets:
enx001e0632bfca:
match:
macaddress: HERE
dhcp4: true
dhcp6: false
link-local: []
wakeonlan: true
I have access to my odroid. And after:
I got a message that upgrade was successfull
reboot
but in ssh:
root@OMV:~# uname -a
Linux OMV 4.14.222-odroidxu4 #1 SMP PREEMPT Mon Nov 22 12:13:27 UTC 2021 armv7l GNU/Linux
It's a new version? In GUI system information is empty.
dpkg -l | grep openmediavault
ii openmediavault 5.6.26-1 all openmediavault - The open network attached storage solution
ii openmediavault-backup 5.2.4 all backup plugin for OpenMediaVault.
ii openmediavault-flashmemory 5.0.9 all folder2ram plugin for OpenMediaVault
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
ii openmediavault-omvextrasorg 5.6.6 all OMV-Extras.org Package Repositories for OpenMediaVault
ii openmediavault-resetperms 5.0 all Reset Permissions
Is not.
But why?
Don’t have an account yet? Register yourself now and be a part of our community!