I sped it up to near normal by setting multiple tasks to unbind/bind all ports.
The unbind/bind also works on the second RPI4 NAS. The remote mounts are now present that was tied to the dongle NIC hang.
raspberry pi 5 usb 2.5g NIC and OMV 7 - USB NIC is not persistent
-
-
Ok, I give up. I can't find a better solution. I do think it is the kernel though. I was not able to have the usb nic not show up when I was running my RPi4 on the 6.1 kernel. As soon as I moved to the 6.6 kernel (desktop environment or not), I was able to recreate it. Just be careful with the bind/unbind. You will make your system inaccessible if the storage the OS is running from is plugged in a usb3 port with the usb nic.
-
I've performed literally dozens of boot cycles and it seems robust, so I'm fine with this being the solution. At least you can conclude this is not something broken within OMV. Good point about care applied to the bind handling on the ports.
Thanks to Chente for the solution and thanks for you working with the dongle. Donation on the way.
-
-
thanks for you working with the dongle.
Now, I want to test it on an x86 box with 6.8 kernel.
-
-
the NIC visibility is not the biggest issue in our case
the real thing do you still see the USB NIC after reboots ? or do you have to unplug and re-plug the USB NIC ? ( which Barney calls "dongle dance"))
-
-
the NIC visibility is not the biggest issue in our case
Yes, agree! There was never a functionality issue with Bookworm/OMV7, the NIC dongle operates at full duplex bandwidth. The issue is a sequence/initialization at this point. Although the links are very interesting and I will make a point of following those. Maybe it's indirectly related.
-
the NIC visibility is not the biggest issue in our case
the real thing do you still see the USB NIC after reboots ? or do you have to unplug and re-plug the USB NIC ? ( which Barney calls "dongle dance"))
Yeah man, all is great, I can shutdown, reboot, everything is working as one could hope for!
-
Yeah man, all is great, I can shutdown, reboot, everything is working as one could hope for!
Reading the second thread https://forums.raspberrypi.com/viewtopic.php?t=369285. I believe OMV did remove Network Manager in the past. It sounds like you reinstalled it and then configured the NIC and that is where you are now?
-
-
Reading the second thread https://forums.raspberrypi.com/viewtopic.php?t=369285. I believe OMV did remove Network Manager in the past. It sounds like you reinstalled it and then configured the NIC and that is where you are now?
Oh so I was correct in my assumption on it being maybe OMV which did delete that feature.
And now I understand why tbh,.. cause I did archive what I wanted but I learned last night the hard way... trying to do anything in GUI when it comes to the network interface will totally locked one out of the system it seems.
So I'm locked out cause last night after posting here I went in there and clicked around, by that I mean I click show details, did'nt apply any changes what so ever, or add or search for any device. Clicked my way around just cause I was curious and then the system stopped responding, OMV outputted the failure message you know and since then I cant get back into my system!
So I would suggest if anyone goes down that path I did, just do not even enter the network interface parts of OMV GUI.
Ps, I have specified static IP for each of the NIC's using their MAC addresses with in my router, I can't ping any of them after the system crash, have rebooted, tried to remove nic and disconnect during, after, before boot, run two cables to both ports and I know I have a link on each, tried one and disconnected the other and so on, it dose not matter what I do, system have me locked out.
So it's either to start from scratch, or connect in my case Pi5 to a monitor and then use NM to activate the interface I want cause I'm feeling like OMV maybe have inactivated both or perhaps deleted them.
-
I believe OMV did remove Network Manager in the past
OMV doesn't remove it. The install script does. OMV uses systemd-networkd for networking. network-manager is not needed. network-manager isn't going to perform the unplug/plug equivalent to get this working either.
-
OMV doesn't remove it. The install script does. OMV uses systemd-networkd for networking. network-manager is not needed. network-manager isn't going to perform the unplug/plug equivalent to get this working either.
Ok thank you for clarifying that.
Ok, so maybe in my case I should used systemd-networkd and then this situation I'm in would or could be avoided. At one fast first glance I don't see if systemd will allow or can manage the actual interfaces but rather "just" modify and configure the available connections, right?
-
-
Ok, so maybe in my case I should used systemd-networkd and then this situation I'm in would or could be avoided. At one fast first glance I don't see if systemd will allow or can manage the actual interfaces but rather "just" modify and configure the available connections, right?
I'm not sure what you are trying to do. Just setup networking from the OMV web interface. It will configure netplan to use systemd-networkd. Follow post #9 in this thread to make sure the system can "see" the adapter. Done.
-
I'm not sure what you are trying to do. Just setup networking from the OMV web interface. It will configure netplan to use systemd-networkd. Follow post #9 in this thread to make sure the system can "see" the adapter. Done.
Well that plan was..., when I go for a clean install then I would want to make sure that my system is only using the 2.5 NIC as my main and only interface, and so I thought I need to set that up before installing OMV, that being my plan, I thought I go and see/ask around on the pi-forums and see how to go about that initial setup and configuration work. One thing led to another and the rest is well history by now
Maybe my approach is totally wrong and the end goal is not even realizable but now that I'm forced into it I will do it from with in OMV!
-
Got a HDMI adapter and thought I could gain access to the Pi5 and reconfigure the network and what not, but no, it’s reboots like 2 times when system fails to lunch OMV and then idles like this (see attached).
Everything passes beside the starting up of “systemd-networkd-wait-online-service” this is the only service that has failed status.
Is there any chance there is something to be done at this point?
-
-
try from the console
Codeomv-firstaidYeah did but no luck there when I try to “configure network interface” it exits and give error (see attached).. I think it’s because the NIC was never setup with in omv (or not there when I installed omv).
I had no luck with systemd-networkd cause I lack the understanding of it I guess so I tried nmtui, attached Ethernet cables to both NIC’s and made sure they where activated, then restarted in there again and both where activated still so I turn the system off, disconnect the cable from the built in NIC and booted up once more and got a boot with one fault*.. and now can access OMV again.
The boot error had a reference something like see details “systemctl” in which I found
systemd-networkd-wait-online.service | loaded failed failed | wait for network to be configured
Tried several more reboots and shutdowns and omv is still accessible so the GUI “works” (haven’t tried anything to see if any of the containers run or anything like that)
So access but it feels like that I need to start from scratch and do a proper configuration cause this feels so darn unstable tbh 😅
-
So access but it feels like that I need to start from scratch and do a proper configuration cause this feels so darn unstable tbh
You should go this way.
There's already a known situation with this that is prevented by following the install guide for Pis:
omv7:raspberry_pi_install [omv-extras.org]
Code
Display MoreBefore installing OMV, update, upgrade and prepare Raspberry PI OS using the following commands, executed one at at time: sudo apt-get update sudo apt-get upgrade -y wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/preinstall | sudo bash When the above commands are complete, type; sudo reboot PuTTY will disconnect – this is expected. Wait 3 to 5 minutes and reopen a new PuTTY SSH window and log in again.That will sort the issues with NICs and Debian 12 on the Pi
-
-
try from the console
Codeomv-firstaidI try to “configure network interface” it exits and give error (see attached)..
you need to be logged in as root , or try sudo before you run the command
-
So access but it feels like that I need to start from scratch and do a proper configuration cause this feels so darn unstable tbh
I have the same opinion as Soma . I think you should reinstall. Unless someone digs into your configuration and guides you correctly to repair it.
OMV has its own network configuration system using netplan. Everything you did from the Raspberry forum is probably breaking something in OMV.
NIC is visible in OMV.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!