I am also struggling with that same issue, but it is not that simple. And it should not be marked not resolved.
I installed dnsmasq but it is in conflict with systemd-resolved. Both want to listen to port 53.
systemd-resolved is started prior dnsmasq when you reboot. If you install dnsmasq it will fail to start with "Jan 19 09:46:47 openmediavault.local dnsmasq: failed to create listening socket for port 53: Address already in use".
You can disable systemd-resolved, but I am ot sure the effect on OMV and Debian uner it.
Best resource and some convoluted - for me! - solutions I found are here https://unix.stackexchange.com…masq-and-systemd-resolved
So, basically using Cockpit out of the box is not working. Any suggestions form the wiser people?
Thanks for the replies.
From all that I get the idea that downgrading is not a wise approach, right?
Another argument to go to 4.x is the plugins. For example, there is no VPN on 5.x
Why not try to fix the issues in OMV 5?
What are they? It's running quite stable for me. Might be easier than downgrading.
The DLNA plugin seem not working with my other devices and I wanted to make sure it is not the OMV. (I didn't have time to dive into it)
I deleted some unused containers via Portainer and I lost the DNS configuration on the OMV network interface. o.0
This scared me thinking 5.x is not yet ready. I have very limited time and I don't want to spend it on the OMV core.
But maybe downgrading will eat more time? Is it even a sane thing to do?
Edit: Also, I saw post about OMV 6 web interface. This made me think the effort on 5.x. is low and it will be generally unstable version...
Hi all and a Happy New Year!
I tried to install the official OMV 4.1.22 (openmediavault_4.1.22-amd64.iso).
I manged to boot once OK. After some plaing around I rebooted and the machine hanged during boot (2 sec in the process) with
"AMD-Vi: Unable to write to IOMMU perf counter...". (I dont remember the exact fault - I lost my photo of the boot screen)
I reinstalled multiple times 4.1.22 from the USB, but never managed to boot afterwards.
At the end I gave up and installed the 5.x beta. And it worked.
But now I have some issues and I would like to go to a stable version.
I suspect that the kernel of 4.1.22 was not able to deal with my HW ( mP = AMD Ryzen 3 3200G, MoBo = Asus PRIME B450M-A)...
I think my option now is to downgrade the 5.0.5 to a 4.x using this procedure
Shall I pick using one openmediavault_4.1.22-1_all.deb (from http://packages.openmediavault…ol/main/o/openmediavault/)
Will i keep my current kernel?
Or shall I pick the latest 4.1.30? (openmediavault_4.1.30-1_all.deb)
Any other advice?