I know it exists that is why I did not remove or purge it in the first place.
But during the dist-upgrade it was saying that openmediavault-nut could not be configured because openmediavault is not configured....
I know it exists that is why I did not remove or purge it in the first place.
But during the dist-upgrade it was saying that openmediavault-nut could not be configured because openmediavault is not configured....
I know it exists that is why I did not remove or purge it in the first place.
But during the dist-upgrade it was saying that openmediavault-nut could not be configured because openmediavault is not configured....
That is a problem with your system. I'm guessing it could be fixed without uninstalling the plugin. I will see if I can reproduce.
Is there no backports kernel in omv 5 anymore?
Only the promoxkernel?
Is there no backports kernel in omv 5 anymore?
Only the promoxkernel?
No there is both. backports are enabled by default. If you have the 5.4.x kernel, you have the backports kernel.
zram is compressed ramdisk. This is what armbian uses to reduce writes on flash media.
Thanks.
It's the first time i see it in filesystem tab. It was not present for me in OMV4. Suppose it's ok now.
Apologies if this is a stupid question. Will these steps work with a Helios4?
The reason I ask is because the initial steps I followed on their forum was to install Armbian Stretch (Debian 9) and then install OMV4 afterwards using armbian-config.
Looking forward to using OMV5! Thanks
Alles anzeigenOn a test OMV 4.x system with the flashmemory plugin installed, this is all I did to upgrade it to OMV 5.x (as root):
apt-get purge openmediavault-cups openmediavault-dnsmasq openmediavault-docker-gui openmediavault-domoticz openmediavault-duplicati openmediavault-eyefi openmediavault-ldap openmediavault-letsencrypt openmediavault-mysql openmediavault-nginx openmediavault-openvpn openmediavault-pxe openmediavault-remotedesktop openmediavault-route openmediavault-shellinabox openmediavault-syncthing openmediavault transmissionbt openmediavault-urbackup-server openmediavault-vdo openmediavault-virtualbox openmediavault-webdav
sed -i "s/stretch/buster/g" /etc/apt/sources.list
sed -i "s/stretch/buster/g" /etc/apt/sources.list.d/*
sed -i "s/arrakis/usul/g" /etc/apt/sources.list.d/*
sed -i "/[Dd]ocker/d" /etc/apt/sources.list.d/omv-extras-org.list
apt-get update
apt-get dist-upgrade
reboot
apt-get purge openmediavault-omvextrasorg resolvconf
wget -O - https://github.com/OpenMediaVa…ckages/raw/master/install | bash
apt-get update
apt-get dist-upgradeomv-salt deploy run nginx
omv-salt deploy run phpfpm
Clear your browser cache after upgrading!
Apologies if this is a stupid question. Will these steps work with a Helios4?
The reason I ask is because the initial steps I followed on their forum was to install Armbian Stretch (Debian 9) and then install OMV4 afterwards using armbian-config.
yes. While it didn't back then, armbian-config actually uses my install script now.
yes. While it didn't back then, armbian-config actually uses my install script now.
Thank you for replying. Just to clarify when I said "the initial steps I followed" I was referring to how I initially installed OMV4 on my Helios4 back in September last year. As such will using your steps now to upgrade (not armbian-config) work?
I'll give it a go this weekend. But will ensure that I have a backup of the OS just in case
Just to clarify when I said "the initial steps I followed" I was referring to how I initially installed OMV4 on my Helios4 back in September last year
Yep, I understood that. That is why I said "while it didn't back then"
As such will using your steps now to upgrade (not armbian-config) work?
The upgrade steps on page 2 of this thread should work on any normal OMV 4.x system. armbian-config doesn't do anything non-normal.
The upgrade steps on page 2 of this thread should work on any normal OMV 4.x system. armbian-config doesn't do anything non-normal.
I wasn't too sure if armbian-config did things differently to other systems, so I appreciate your response. Thank you for confirming that those upgrade steps should work.
Happy Easter!
Hello from Spain!
I allready have updated omv to omv 5. It has been flawless and all I have installed is working perfectly without a loss
Thank you very much
Did I have to activate backports. I've activated extras repo
Hello,
I've done this upgrade. seems to be ok in the console BUT i can't log in the GUI... i have a mistake somewhere (but don't know where)
this is what i have :
{"response":null,"error":{"code":0,"message":"Failed to connect to socket: No such file or directory","trace":"OMV\\Rpc\\Exception: Failed to connect to socket: No such file or directory in \/usr\/share\/php\/openmediavault\/rpc\/rpc.inc:141\nStack trace:\n#0 \/var\/www\/openmediavault\/rpc\/session.inc(56): OMV\\Rpc\\Rpc::call('UserMgmt', 'authUser', Array, Array, 2, true)\n#1 [internal function]: OMVRpcServiceSession->login(Array, Array)\n#2 \/usr\/share\/php\/openmediavault\/rpc\/serviceabstract.inc(123): call_user_func_array(Array, Array)\n#3 \/usr\/share\/php\/openmediavault\/rpc\/rpc.inc(86): OMV\\Rpc\\ServiceAbstract->callMethod('login', Array, Array)\n#4 \/usr\/share\/php\/openmediavault\/rpc\/proxy\/json.inc(97): OMV\\Rpc\\Rpc::call('Session', 'login', Array, Array, 3)\n#5 \/var\/www\/openmediavault\/rpc.php(45): OMV\\Rpc\\Proxy\\Json->handle()\n#6 {main}"}}
I ve try to see if a plugin was the problem...
thanks from France
i've done a
wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash more and it seems to work !!!
thanks for this tuto
I just updated from OMV4-OMV5 on my Helios4 using the instructions here (Note: as mentioned previously by another user here there were configuration files that were found to be modified by either myself or a script since installation. For all of these options I selected the default action as was advised. This was to keep my current version).
Whilst the update/upgrade went well I just have a couple of questions/comments:
root@helios4:~# systemctl status sys-oled.service
* sys-oled.service - System Starting on OLED Display
Loaded: loaded (/etc/systemd/system/sys-oled.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-04-13 11:20:32 AEST; 35min ago
Process: 1136 ExecStart=/usr/bin/python3 /usr/local/bin/sys-oled --display ${display_model} (code=exited, status=1/FAILURE)
Main PID: 1136 (code=exited, status=1/FAILURE)
Apr 13 11:20:30 helios4 systemd[1]: Started System Starting on OLED Display.
Apr 13 11:20:32 helios4 python3[1136]: Traceback (most recent call last):
Apr 13 11:20:32 helios4 python3[1136]: File "/usr/local/bin/sys-oled", line 10, in <module>
Apr 13 11:20:32 helios4 python3[1136]: from luma.core import cmdline, error
Apr 13 11:20:32 helios4 python3[1136]: ModuleNotFoundError: No module named 'luma'
Apr 13 11:20:32 helios4 systemd[1]: sys-oled.service: Main process exited, code=exited, status=1/FAILURE
Apr 13 11:20:32 helios4 systemd[1]: sys-oled.service: Failed with result 'exit-code'.
Alles anzeigen
Otherwise, everything appears to be working well. Thanks for the clear and detailed instructions
- I have heard a lot of talk about Shared Folders being deprecated. After successfully completing the update I can still see Access Rights Management -> Shared Folders in the Web GUI. Is this expected and correct?
You misunderstood what was deprecated. What is discontinued is having the shares populating /sharedfolders/
You misunderstood what was deprecated. What is discontinued is having the shares populating /sharedfolders/
Thanks for clarifying that! Much appreciated.
With /sharedfolders/ Are you referring to the Relative path for each share? Or the physical location in storage?
I am referring to the /sharedfolders directory on the rootfs.
I am referring to the /sharedfolders directory on the rootfs.
Again, thanks. Checking the rootfs /sharedfolders still exists and contains my 4 Shared Folders. What should I do?
Again, thanks. Checking the rootfs /sharedfolders still exists and contains my 4 Shared Folders. What should I do?
/sharedfolders, and the subdirectories will continue to exist. However the contents of any subdirectories (those having the same name as your defined shares) will be empty.
I suppose you could delete the now unused directories, but leaving them there hurts nothing.
Also, it is possible to revert the system back to the previous behavior of having the shares bind mounted into those subdirectories. Information on how to do this is on the forum somewhere.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!