Added an network bond via cli - now omv is broken

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Added an network bond via cli - now omv is broken

      Heya all!
      So I managed to break OMV on my first install!
      I was not able to boot my and based machine to install from USB, the graphical error is typical a sign of to old kernel that can't handle my build in GPU.
      Oh well I installed Debian 9 and installed OMV from there.
      From the GUI I wasn't able to setup and bond, yes I have a switch that supports it, the add popup was kind of grey and I wasn't able to add anything.
      So I dived into the command line and made my bond there instead.

      Restarted the machine, omv answers on the bond ip but looks like this: ibb.co/cLHptC2

      How do I save OMV?
      --
      Storage server: Ryzen 3 2400G, 16 Gb RAM, 12 TB storage, SSD for system.
    • You are using the wrong user to log into the UI. Use the user “admin”.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • ratnose wrote:

      I do not think so, I used the same user login as before the bond creation.
      I am sure you are using the wrong user account. The content of the UI has absolutely nothing to do with your network settings.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • So now I have reinstalled the whole she-bang, started with Debian 9, updated the kernel and configured the network as a bond.
      After that I used to two shell-scripts found here on the forums to install OMV4, no problem there either.
      Only thing is that I dont get to see my bond, network section is empty and system diagnostics is empty to.

      Need to check this out.
      --
      Storage server: Ryzen 3 2400G, 16 Gb RAM, 12 TB storage, SSD for system.
    • ratnose wrote:

      So now I have reinstalled the whole she-bang, started with Debian 9, updated the kernel and configured the network as a bond.
      After that I used to two shell-scripts found here on the forums to install OMV4, no problem there either.
      Only thing is that I dont get to see my bond, network section is empty and system diagnostics is empty to.

      Need to check this out.
      The network section will not display real data, it displays the configuration data. And if there is no network that is configured via UI, the stats for the network can't be collected and displayed.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • ratnose wrote:

      gives me a constant stream from the server at 10 mb/s
      That's 'Fast Ethernet' so we're not talking about performance anyway. With Gigabit Ethernet you should see ~100 MB/s without LACP and the same value with LACP since this mechanism doesn't change link speeds but only distributes individual client-server connections over the available links.

      If you really just achieve 10 MB/s there's something seriously wrong unless you use still Fast Ethernet gear. At least LACP is not the solution for this problem.