I did an upgrade last Thursday night, left the unraid server running for a few more hours then proceeded to reboot.
After the reboot, the UI never came up.

When I tried to ping the host, it was not pinging.

 

I connected monitor and keyboard and was pleased to see the login prompt.

 

After login in, I can see (via ethtool) that my network device does have "Link".

But when I check the arp table, its not fully populated. Most importantly, the arp entry for my router is incomplete.

 

In one of my many changes, I did get the web-ui to become accessible but was not really usable. None of the hardrives were present and the UI was "hollow", I could see the sections of the UI but there was no content (words/characters).

I had a fiber NIC and I did remove the NIC, this was in efforts to delete/remove the bond0 interface, but after this I'm still on the same spot.... System is up, I can login directly on the system but its not pingable, i can't ssh into it, I can't reach the web-ui.

 

I read another post that mentioned I could delete the network.cfg and network-rules.cfg to get the system to DHCP back as this was its default. After doing this, I still see the same issues. And the network.cfg file lists bond0 again.

 

I would like to try and fully disable/unconfigure the bond0 interface and the br0 too if possible. I only run a few (6) containers on my Unraid server, so I'm fine disabling docker altogether. I do not really create VMs on Unraid, so that functionality can also be disabled/turned off.

 

I'm also concerned about moving the USB device in which Unraid (and my license) is installed on, since I've read the license is tied to the physical usb device. Other than me being afraid to lose my license, there is nothing that makes me think there is anything wrong with the USB, just FYI.

 

Any pointers will be greatly appreciated.

 

Cheers,

 

Is your main nic still eth0?  I've had some get reassigned to eth1, 2, etc for reasons I didn't know.  

  Agree to want to turn off bonding.

  Bridging you may want to consider keeping active.

Please post the diagnostics.
 

Here is the diagnostic file

milk-diagnostics-20241218-1812.zip

See the release notes or:

https://forums.unraid.net/topic/180687-unraid-os-version-61214-available/page/2/#findComment-1492212

 

Thanks @JorgeB, I had not noticed that plugin was installed.

 

With the web-ui not available, is deleting the directory for r8160-plugin from the plugins directory enough?

 

1 minute ago, tokynet said:

is deleting the directory for r8160-plugin from the plugins directory enough?

Nope, since it also blacklists the stock driver, if you can boot using the GUI mode, you can uninstall the plugin from there, if not, it's also possibly to do it manually.

Apologies, but i'm not following your answer.

 

If by "GUI" you mean the web-ui, I do not have access to that, since the network interface is failing.

If there is a way to bring up a gui like x11 or wayland, I'm not aware of how to do that.

 

This sounds like what i'm looking for "...if not, it's also possibly to do it manually", how could I do this?

 

Thanks again for your help.

1 hour ago, tokynet said:

If there is a way to bring up a gui like x11 or wayland, I'm not aware of how to do that.

If you have a keyboard+monitor attached to the server then there is the option to boot into GUI mode on the Unraid Boot menu which runs the GUI on the locally attached monitor.

@itimpi not sure if its because the monitor i have available for this server is too old, but by the time the monitor starts displaying output, i'm already seeing the OS boot output, I do not see any menu.

 

If anyone else finds themselves in this situation, I just moved the realtek-plugin directory from the /boot/config/plugins to /boot/config/plugins-removed.

 

Also the command to bring up the GUI is "slim" (although for me, all I got was a black screen)

 

Thanks @JorgeB and @jcofer555 (in the discord channel)

44 minutes ago, tokynet said:

not sure if its because the monitor i have available for this server is too old, but by the time the monitor starts displaying output, i'm already seeing the OS boot output, I do not see any menu.

I guess it could be - the blue Boot Menu is normally the first thing displayed but it has a timeout of 5 seconds before proceeding with the default options..  You could change this timeout if you wanted by editing the syslog/syslog.cfg file on the flash drive if you want to experiment with that.