Posts by FatherRandom

    I've updated my OMV installation as well. I noticed a KVM package being held back. So I enabled backports in OMV extras as per instruction here to be able to finish the updates. Unfortunately, that caused my zfs file system to vanish. The server boots fine from the separate SSD, but everything from the zfs pool on the two data storage SSDs is inaccessible. The drives themselves are fine according to SMART.


    I fear to make the wrong steps and kill something permanently if that's not already happened. Is my problem related to the abovementioned? Or shall I open a new thread?


    Attempting to access the zfs pool yields:

    I'd be very grateful for assistance!

    Code
    ***@server:~$ grep -ir forward /etc/sysctl.d/*
    /etc/sysctl.d/99-sysctl.conf:# Uncomment the next line to enable packet forwarding for IPv4
    /etc/sysctl.d/99-sysctl.conf:#net.ipv4.ip_forward=1
    /etc/sysctl.d/99-sysctl.conf:# Uncomment the next line to enable packet forwarding for IPv6
    /etc/sysctl.d/99-sysctl.conf:#net.ipv6.conf.all.forwarding=1
    /etc/sysctl.d/ip_forward.conf:net.ipv4.ip_forward=1

    Another interesting result of the test: After uncommenting the IPv6 deactivation line, saving the conf file and rebooting the server - the vm would autostart again. UnfortunateIy, I forgot to perfom the second part of mcking230 suggestion after editing sysctl.config:

    Quote
    Code
    sysctl -p

    This prevented me from loggin in via RDP again. So I executed sysctl -p, rebooted and was able to log in to the vm with RDP again. Dunno whether that is of some diagnostic value to the experts.

    Commenting out the configuration line to deactivate IPv6 brought back the error messages for the vm. Consequently, it did not autostart. So I will disable IPv6 again to get it working again - at least for the time being.

    Would you like me to test this by commenting out the statement to disable IPv6? Or is it not just as easy as this to revert to the former configuration? And when would the new version of the package (?) be available for installation? Incidently, I was notified about an update for KVM only today. This got something to do with your change?

    Code
    ip a

    as user root yields the following result:

    The mini server is hooked up to a FritzBox and gets its ip address via DHCP. The FritzBox is configured to provide always the same to this machine.

    Hello everyone, after 3 versions of OMV over the years I decided to join the forum. First off - thanks very much to all the dedicated contributors of this great software!


    I was having the same troubles as mcking230. The vm wouldn't autostart, Spice wasn't activated and later it showed the same red error message upon the attempt to remove it from the vm.

    Find solution by disabling (disgusting) ipv6

    in /etc/sysctl.conf add the following lines at end


    Code
    # Turn off IPv6
    net.ipv6.conf.all.disable_ipv6 = 1

    then

    Code
    sysctl -p

    and reboot for success

    This worked for me as well.


    As a sidenote: After the deactivation of IPv6 I could connect to my vm (Debian 12 with Xfce4 and xRDP) via RDP from a windows machine. That was impossible before.