Losing Ethernet with Latest OMV Update

Quote from Mrbroo

I had the same issue with the update on my Pi4.

I had to login to the pi with a keyboard and screen and run omv-firstaid on the network eth0. After that the network came back

Yes, this fixed it for me as well, but I had to get a usb keyboard and travel to my servers with an external display. I really, really hope future upgrades won’t break network functionality like this again.. Thanks for the tips!

Hi, I have the same issue. I updated OMV on my RPi and now the IP address is nothing like my network so can't access it.

I have connected a screen and keyboard and have tried to run omv-firstaid. I can log in and bring up omv-firstaid but it just keeps saying permission denied when I try to do anything from omv-firstaid.

Any ideas?

Thanks

Thank you I forget that one so often.

All working again.

Much appreciated.

My system is based on RPi4 and is configured with eth0 as NW-adapter.

I could manage to update to 7.5.0 without messing up NW config.

What I did:

- talked to a Linux/OMV expert asking for help

- she understood the problem by reading the issue on Github and gave me the following cookbook:

1- create a copy of current system disk and boot from it (to work on a copy, just for safety reasons)

2- add parameter net.ifnames=0 to /boot/cmdline.txt (forcing kernel to use old if-names like eth0)

3- restart system to activate parameter

4- Start update

Result: Working w/o any issues!

Only question left from myside: how to switch system safely from eth0 to end0?

Top !!

Quote from Canda

Hi, I have the same issue. I updated OMV on my RPi and now the IP address is nothing like my network so can't access it.

I have connected a screen and keyboard and have tried to run omv-firstaid. I can log in and bring up omv-firstaid but it just keeps saying permission denied when I try to do anything from omv-firstaid.

Any ideas?

Thanks

Display More

use sudo:

sudo pmv-firstaid

Quote

use sudo:

sudo pmv-firstaid

If there's no access by SSH there's no sudo doing something.

Ditto, just happened to me after applying the updates. Dusted off the old monitor and keyboard and was back up in 5 mins with the omv-firstaid, thanks!

Quote from ojtindrum

Seems at lot as though all the units experiencing this issue are rpis

Is there anyone who has had this problem running other hardware?

Running OMV on a N100. Server is down since upgrading. I am going to troubleshoot in a few hours.

Quote from ojtindrum

Thanks, be interesting to know if it's a networking issue or something else

Network issues. Resetting the network interface fixed it.

Hey!

I am new to OMV. I have a lot of experience with Bash, so a fix like this wouldn't be a problem for me. But since I specifically chose a ready-made system like OMV to obtain a certain level of reliability, I wonder: How often do such showstoppers occur?

Thank you, Volker.

So with a fresh setup this specific issue wouldn't affect me anyways.

Grüße aus Mannheim

Quote from votdev

The problem here was that many systems have been using an old configuration for ages. In the course of time, however, changes in the kernel and UDEV have resulted in the device names now being completely different than they were back then. These were changes over which the OMV project has no influence.

P.S. Wouldn't it make sense to warn about a certain risk of 'braking changes' in the Blog and how to fix it in the case of emergency? At least for the 7.5.0 update.

Blog | openmediavault

When updating Home Assistant e.g., I have the feeling that the list of braking changes is longer than the actual improvements.