Losing Ethernet with Latest OMV Update

  • This is more just to broadcast my problem in the hope there might be someone else with the same experience. I'm running headless and therefore diagnostics are complicated.


    I updated to latest OMV last night and appeared to lose ethernet after saving network changes. Started from scratch again just now and following update, after saving the default config changes from updating I lose ethernet again.


    Anyone else?

    OMV 7 | 64 bit | 6.6.62 Armbian kernel | Rpi Zero 2 (Headless) | compose 7.2.16 | cputemp 7.0.2 | downloader 7.0 | shairport 7.0-2

    Edited once, last by ojtindrum ().

  • ojtindrum

    Changed the title of the thread from “Losing Ethernet with the latest update” to “Losing Ethernet with Latest OMV Update”.
  • Scratch install, update then dismiss config changes and I'm ok


    I realise this is not ideal but borking a fresh install with a config save is not ideal either

    OMV 7 | 64 bit | 6.6.62 Armbian kernel | Rpi Zero 2 (Headless) | compose 7.2.16 | cputemp 7.0.2 | downloader 7.0 | shairport 7.0-2

    • New
    • Official Post

    I realise this is not ideal but borking a fresh install with a config save is not ideal either

    Just updated five systems and not a single problem

    omv 7.5.0-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.15 | compose 7.3.2 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Just updated five systems and not a single problem

    That's great Arron, but I've just done a fresh install and replicated the issue I had following an update with a system that's been problem free for a couple of months

    OMV 7 | 64 bit | 6.6.62 Armbian kernel | Rpi Zero 2 (Headless) | compose 7.2.16 | cputemp 7.0.2 | downloader 7.0 | shairport 7.0-2

    • New
    • Official Post

    That's great Arron, but I've just done a fresh install and replicated the issue I had following an update with a system that's been problem free for a couple of months

    Thanks for telling me my results are worthless and yours are correct. One of the systems I updated, I installed yesterday. But just to waste more time, I installed a brand new VM and it didn't have any problems. I have no idea what you are doing to cause this.

    omv 7.5.0-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.15 | compose 7.3.2 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Thanks for telling me my results are worthless and yours are correct

    Is that what I've done? How curious.


    I thought this was a support forum as distinct from an I don't have your problem forum

    OMV 7 | 64 bit | 6.6.62 Armbian kernel | Rpi Zero 2 (Headless) | compose 7.2.16 | cputemp 7.0.2 | downloader 7.0 | shairport 7.0-2

    • New
    • Official Post

    Is that what I've done? How curious.

    That is usually what "great" is followed by saying you had it on all of your systems.


    I thought this was a support forum as distinct from an I don't have your problem forum

    Really? I and others have never supported you? I made one smartass comment to your irritated sounding response.


    When I said "I have no idea what you are doing to cause this", that is trigger to tell us what we could do to reproduce this. I don't even know what to ask otherwise.

    omv 7.5.0-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.15 | compose 7.3.2 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • It seems to me that Armbian systems have characteristics that are particular to Armbian systems. If that's true (and it may not be true at all), a need to attempt replication of an issue on an Armbian system would necessarily require such testing to be made on an Armbian system. I'm not in a position to judge wether it is necessary to make such an attempt, I'm only speculating that if a problem on an Armbian system was in need of diagnosis via an attempt to replicate said problem on a test system that test system would need to be an Armbian system before said problem might be dismissed out of hand.


    I'm just speculating and clearly have no real idea. I'd imagine providing support on a forum like this would take a particular suite of skills that'd need to be operating in concert more or less constantly otherwise it's become so damn tedious it'd likely be a distinct threat to cognitive equilibrium and general mental health. As before, just speculating. Clearly I have no idea.

    OMV 7 | 64 bit | 6.6.62 Armbian kernel | Rpi Zero 2 (Headless) | compose 7.2.16 | cputemp 7.0.2 | downloader 7.0 | shairport 7.0-2

  • Hello,


    Just updated and apply + reboot my OMV 7 on my Pi4. The ethernet of it is completely lost, ping has no responses.



    However, it still shows connected.



    Right now, I can't even login or access via SSH - headless.

  • The ethernet of it is completely lost

    Thanks, appreciate your sharing this here


    I can't even login or access via SSH

    I found the same thing happened again on a fresh install after update but if you cancel out the config changes after updating it's ok.


    run omv-firstaid on the network eth0. After that the network came back

    Thanks, great to know there's a solution with keyboard and screen


    same issue

    As above, try cancelling out from the config updates and you should be ok if headless otherwise as Mrbroo says omv-firstaid can get your ethernet back

    OMV 7 | 64 bit | 6.6.62 Armbian kernel | Rpi Zero 2 (Headless) | compose 7.2.16 | cputemp 7.0.2 | downloader 7.0 | shairport 7.0-2

  • Same issue here. :(

    Is there any other way to set a config value on the disk? I have a monitor, but no functional keyboard atm. I can mount the drive when I put my PiBox in a different mode and access the files on the disk. Only not remote and through a keyboard.

  • looks like this might be solved over here


    • New
    • Official Post

    It comes out that the update is NOT responsible for that issue. The following might have happened to your system:


    The network interface name has been changed because:

    • a new PCI device has been added to the system which might lead to a renaming of the NIC device name. E.g. enp4s1 becomes enp5s1 because the new PCI device gets bus ID number 4 and the NIC number 5.
    • the NIC configuration was created at a time the UDEV named the device ens18, but with newer kernels and UDEV package versions the name of the device is now enp3s18.
    • the netplan config was created at a time when OMV has used the MAC address of the NIC to identify it. This behaviour has been changed mid 2023. Since then the name of the device is used in the netplan config.

    I all situations running omv-firstaid should be used to recreate the network configuration.


    The issue is tracked via https://github.com/openmediavault/openmediavault/issues/1888.

  • As said before. I had the same issue here. I have PiBox with a Pi4 CM.

    I run the official OMV installation on RaspberryPi OS Lite I believe. I set it up using the instructions on the OMV website. All according to plan. It ran always just fine. Even the updates never caused problems.

    Today I updated from 7.4.x to 7.5.0. After that the Ethernet connection completely disappeared. Had the same issue some others here. I could not ping the NAS and did not see it in the connected device list.

    Eventually I was able to borrow a keyboard. I had a monitor. When I booted the system I noticed that the system boot took really long because it tried to get a network connection. However, it seems DCHP, IPv4 and IPv6 were not set at all. So it took about 2 minutes before the system continued to boot without an ethernet connection.

    I was able to run omv-firstaid. I setup IPv4 and IPv6 (don't use it) for ETH0. Saving took really long too. About two to three minutes too. After it saved I rebooted my device and then I could access the NAS again.

    Hopefully this helps debugging for future updates and other users.

    • New
    • Official Post

    I was able to run omv-firstaid. I setup IPv4 and IPv6 (don't use it) for ETH0.

    This naming scheme (e.g. eth0 or ethX) is not used anymore by Debian. Don't know why your image is using that. OMV still supports that, but you should look for why predictable device names are not used on your system. The new device names should be named like enp3s1 for example.

  • Same here, two Pi 5 headless omv7 installs. No backups, so I'm screwed. Any help is much appreciated!
    This update was OMV, docker compose plugin, and I think some eeprom for rpi5?
    Didn't even look too closely.. Not the smartest move from me, but I thought these should just work, as they have before..

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!