February 10, 20251 yr Community Expert As you can see in the screenshot the system freezes when picking Unraid OS GUI Mode. I just made a fresh flash disk. At first it worked, but after a reboot this happened. Is this after the OS is loaded to RAM? How can I know if there is something wrong with the flash drive? It's a Samsung FIT Plus - 64GB so it should be of decent quality. But I have used it for a year. Steps to reproduce: Make an Unraid 7 flash disk with "unraid-usb-creator-1.0.1.exe". Boot from the device. Select Unraid OS GUI Mode Notice how the system freezes. IPMI Remote shows me this: Edited February 10, 20251 yr by Bob-omb
February 10, 20251 yr Community Expert https://docs.unraid.net/unraid-os/getting-started/manual-install-method/
February 10, 20251 yr Author Community Expert Here is an update: I reinstalled the USB creator tool. Installed Unraid on a different flash disk of the same kind with (DHCP) Was working but there was no network. I moved the server to another mesh node on my network. Booted from IPMI. Selected "Unraid OS GUI Mode". Now it is complaining about SSL certificate for unraid.net being deprecated. I go to Settings ➜ Network: Now it says "Interface Ethernet Port 1 is down. Check Cable." even though the computer is connected to the router.
February 10, 20251 yr Community Expert 15 minutes ago, Bob-omb said: Interface Ethernet Port 1 is down. Check Cable. Try another cable or port.
February 10, 20251 yr Author Community Expert I changed the cable and changed the port to the other Intel 2.5Gb Ethernet port. The server still does not appear on my router even though the LAN LED indicator is green (indicating that it is linked).
February 10, 20251 yr Community Expert 1 hour ago, Bob-omb said: Now it is complaining about SSL certificate for unraid.net being deprecated. Check the server date and time.
February 10, 20251 yr Community Expert 5 hours ago, Bob-omb said: changed the port to the other Intel 2.5Gb Ethernet port. The server still does not appear on my router Did you try changing the router port? Also, check the pins in the ports to make sure none are bent out-of-place.
February 11, 20251 yr Author Community Expert Thanks for helping so far. Really appreciated. Here is an update. I switched out the LAN cable and tried a different port on the router and a different port on the server. The router still does not seem to detect the server. However, if I connect my laptop to that same cable I get internet instantly, so there is probably nothing wrong with the cable or the router, which is what I expected. I loaded optimized defaults on my BIOS. I installed Unraid 6.12.15 on a flash drive (as opposed to Unraid 7) just to see if it made a difference. The server is not given an IP, but I am not sure if it is because it is not asking for it yet. If I boot into BIOS this is what it says: However both says: I have literally no idea what is going on. I am so lost. My next options are: Completely reset the router. Install Windows to see if it resolves. Edited February 11, 20251 yr by Bob-omb
February 11, 20251 yr Community Expert Solution It's an issue with the virtual NIC, the solution is to blacklist the driver, but if you don't mind, try this first to see if it also works, open a terminal windows and type: mkdir -p /boot/config/udev echo 'SUBSYSTEM=="net", DRIVER=="cdc_ether", NAME:="usb0"' >>/boot/config/udev/70-persistent-net.rules Then reboot and post new diagnostics. If you still don't have a network, then type: echo "blacklist cdc_ether" > /boot/config/modprobe.d/cdc_ether.conf Reboot and that should solve it for sure.
February 11, 20251 yr Author Community Expert 2 hours ago, JorgeB said: It's an issue with the virtual NIC Thanks. I will try that, but what do you mean by issue with the NIC? Issue? Like in a known bug? Edited February 11, 20251 yr by Bob-omb
February 11, 20251 yr Community Expert It's a known Linux kernel issue with some virtual (IPMI) NICs, it affects some Asrock and Asus boards, and also some Dell servers.
February 11, 20251 yr Author Community Expert I see. But I am not using the IPMI card for Unraid. Actually the IPMI card works fine, but the NIC on the MB doesn't. Neither of the two LAN pors on the backplate of the MB works it seems. Also, this has been working for a year. I even ran Unraid 7 since it was released. So I am kind of confused 😕 I am installing Windows right now, but I will test your solution after that.
February 11, 20251 yr Community Expert 4 minutes ago, Bob-omb said: But I am not using the IPMI card for Unraid. It doesn't matter, the problem is that the virtual NIC always gets loaded as eth0, and it cannot be changed.
February 11, 20251 yr Author Community Expert I installed Windows and without drivers the network interface was not detected. After installing the "DRV_LAN_Intel_I226_UWD_TP_W10_64_V11443_20240710R.zip" driver it was recognized. This leads me to believe that the NIC is buggy after some BIOS update or something. I update the BIOS from 4001 to 4001. In Unraid GUI I used Terminal to enter: mkdir -p /boot/config/udev Then: echo 'SUBSYSTEM=="net", DRIVER=="cdc_ether", NAME:="usb0"' >>/boot/config/udev/70-persistent-net.rules I shutdown Unraid. Started it again. Still no IP for the network. Did a diagnostics. Attached it here Edited March 20, 20251 yr by Bob-omb
February 11, 20251 yr Author Community Expert Since I had no luck so far I entered this in the Terminal: echo "blacklist cdc_ether" > /boot/config/modprobe.d/cdc_ether.conf I restarted. I still get the "Interface Ethernet Port 1 is down. Check Cable." message, but at least now I can access the web interface with hostname or IP. Can I ask some questions out of curiosity? Why is this not patched by Lime if it is a known bug? I spent two days on this. If it had not been for @JorgeB I would have given up on Unraid. Where is this kernel bug tracked? Why is it still saying "Interface Ethernet Port 1 is down. Check Cable." Is it possible to add a configuration change to the flash disk instead of having to type these commands after boot? Btw here is the new diagnostics file after I added the blacklist command. Edited March 20, 20251 yr by Bob-omb
February 11, 20251 yr Community Expert Thanks for testing. 39 minutes ago, Bob-omb said: Why is this not patched by Lime if it is a known bug? They are looking into a solution, hence the first thing I asked you to try, unfortunately it doesn't work, but note that this is a Linux kernel issue, not an Unraid issue, LT is looking for a workaround, but possibly, they will need to just blacklist the driver by default. 42 minutes ago, Bob-omb said: Where is this kernel bug tracked? It's mentioned here: https://lore.kernel.org/netdev/[email protected]/T/ 44 minutes ago, Bob-omb said: Why is it still saying "Interface Ethernet Port 1 is down. Check Cable." Do you have a cable connected to eht1? I only see a link being detected in eth2, they are in a bond. 45 minutes ago, Bob-omb said: Is it possible to add a configuration change to the flash disk instead of having to type these commands after boot? Yes, those are just txt files in the flash drive.
February 11, 20251 yr Author Community Expert Thanks so much @JorgeB Unfortunately because of all this mess I decided to make a new flash drive. I have not lost my config because I have a backup of the old flash drive. I really want to avoid setting up the config (users, passwords, shares, user scripts etc...) all over again. How can I restore the old flash drive and apply this workaround? I have never restored an Unraid flash disk. Also, how should I go about applying this workaround? Should I just copy the "70-persistent-net.rules" and "cdc_ether.conf" to their respective folder?
February 11, 20251 yr Community Expert config folder from flash or flash backup is all you need to get going again with all of your configuration on a new install.
February 11, 20251 yr Community Expert 3 minutes ago, Bob-omb said: and "cdc_ether.conf" to their respective folder? Just need this one.
February 11, 20251 yr Author Community Expert And... It's back! 😊👍 Fully restored using the config folder. Thanks a whole bunch @JorgeB and @trurl. Without your help I would have given up or bought a new computer. Lime should probably mention this issue somewhere though. I am not exactly using an obscure NIC or anything. Although this was technically a kernel issue most users are not going to care. They just want to plug and pay. I am happy it is solved now after two full days of troubleshooting.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.