Losing Ethernet with Latest OMV Update

Did you set to static IP before updating?

Teschbert is fully right. His solution hint for Pi installation works.

1. take out SD card and put it in a USB reader

2. add the parameter "net.ifnames=0" to cmdline.txt on boot partition

3. save file and put it back in your Pi.

4. update and enjoy

Cheers

Quote from ojtindrum

On my system?

IP is set to static in my modem prefs so yeh always the same ip (the pi was not getting an IP at all)

Sure it makes sense to set a static IP for servers. Nevertheless there are also other ways to fix the IP. E.g. I can setup my DHCP server to always provide the same IP to a certain MAC address. Or you can work with the hostnames in your network, not with IP addresses at all.

So it looks for me that the issue does only occur when setting a static IP. DHCP setups are not affected.

Quote from ojtindrum

You've lost me there, it's my thread

I run headless, do not have a wired keyboard. I play with a lot of hardware which means a lot of installs from scratch. Knowing what IP I'm using before I get into OMV has a ton of utility for me but further to that, it's unlikely everyone who's posted in this thread is setting static IP in their router ergo this is likely a problem unrelated to router settings

I must be the one of those "oddballs" that use static IP as well as MAC address on my pfSense firewall/router to identify OMV. I also use static IP in OMV network settings. All is working fine.

Quote from votdev

I hope not too often. 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.

No idea what you mean with old configuration. I bought my N100 9 months ago. OMV fucked up that's about it.

Are the network interface names in OMV configured via systemd?

If so, then one could do

# cat /etc/systemd/network/10-enp1s0.link 
[Match]
MACAddress=aa:bb:cc:dd:ee:ff
Type=ether

[Link]
Name=enp1s0

for all network interfaces to keep them fixed at their current name (obviously the interface name is different depending on the used hardware, this is just to illustrate the configuration). I have done the same when Proxmox VE updated their base Debian distribution and was hit by the same issue there.

I had exactly the same issue last night - OMV had a list of updates it required which I installed on final reboot it seemed not to connect to my network (set with static IP) on investigation the latest update managed to change the IP.

Had to connect up KVM to discover the IP now was completely outside of my network range. Used omv-firstaid to correct the IP address and all was okay after, but was scary for the first few minutes, thinking "when did my last whole system backup run!"

I have only been using OMV for about 6 months.

Raspberry Pi 5 8Mb with 4 x 2Tb SATA SSD, which runs and performs like a dream, but it did scare me for a few minutes!

Just some updates; solved mine a while back but in a strange way.

Lucky I did have a mini-HDMI cable (for my Fuji camera) to connect my monitor, keyboard and mouse to solve this by running "omv-firstaid" without connecting to a network (the firstaid progress was never complete due maybe it was not connected physically to a network). Then I unplugged it and move it back to my network stack, fixed it.

Quote from Lennyz1988

No idea what you mean with old configuration. I bought my N100 9 months ago. OMV fucked up that's about it.

I literally just performed an update on my N100 (asrock n100m), no issues for me (fortunately).

Hello everyone,

could my problem have the same cause?

However, I can't get past the initial configuration:

OMV on Raspi 5

During configuration via Web-Gui, the connection is interrupted after data transfer (yellow prompt).

The Pi is then only accessible via HDMI.

After the crash, end0 no longer has an IP V4 address, or is completely gone.

I have now run through this 4 times, even without touching the network configuration.

I have replaced the SD card and also the NT. Always with the same result.

To rule out sources of error, I have also tested without an additional drive.

The Pi is new, there was no working configuration yet.

Updates installed before OMV installation, then also updated in OMV Gui.

Pi5 / 8GB

OMV 7.5.0-1

I am grateful for any help.

I would have to redirect terminal output to a USB stick in order to make it available here.

Please advise how to do this if needed.

Thank you very much!

I had the same loss of IP connection problem on my (very) old intel based desktop server. I resolved the problem with monitor, keyboard, and omv-firstaid network configuration.