OMV in Virtualbox - No Network Interface

    • OMV 3.x
    • Resolved
    • OMV in Virtualbox - No Network Interface

      After loading an new OMV 3.X guest into Virtual Box (using the "bridged" network adapter mode):

      On the first boot, OMV's boot dialog stated; " No network interface" or " No Interface Found ", or something to that effect. (Normally, DHCP assigns an IP address which is shown in the terminal console.) Rebooting the OMV guest had no effect on this condition.

      The solution was simple.
      As root, on the command, type in omv-firstaid and select 1. Simply configuring the adapter attached to eth0, even for DHCP, corrects this issue.

      (Provided for searches)

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.13, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • It was odd behavior that I'd only seen with OMV as a new guest (fresh build), and a reboot or two had no effect. I've booted several times before, using DHCP with a VM, and haven't seen this. The new OMV build, in a newer version/install of Virtual Box, sent me down a blind alley.

      In any case, motd before the IP makes sense.

      Thanks

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.13, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk