After updating from 4.7 to unRAIDServer-5.0-i386 the server will not connect to my network.  I can see from the system log that the IP is being assigned but drops the connection a second later.  Reverting back to 4.7 does correct the issue.  I have using MSI E3501-E45 mobo which uses the RTL811E chipset.  I am not very experienced with anything but the basics of unraid, any help would be greatly appreciated!

syslog.txt

This could be related:

 

Sep 18 21:30:20 Tower dhcpcd: eth0: MTU set to 576

 

Did you configure the MTU setting in you router or anywhere else?

No settings were changed anywhere on the network.  I prepped the thumb drive, moved files iaw the setup notes, reinstalled drive and powered up.  Do I need to adjust the MTU in the router in order for this version to connect?

IDK, it's just odd.

As dgaschk noted the MTU setting is odd. The unRAID wiki, "Improving unRAID Performance" states MTU settings can be specified in the file /boot/config/network.cfg. Maybe that file had been modified in the past with a MTU=576 statement?

 

When I open the syslog you posted I get an character encoding error message in my text editor, gedit in Ubuntu. But, on these lines the string ends with some odd character '\FF', and it's only showing on the lines that end with 192.168.1.1.

Sep 18 21:23:39 Tower dhcpcd[1037]: eth0: acknowledged 192.168.1.104 from 192.168.1.1 `\FF'

It seems odd to me that they are showing up this way and you are having a problem with carrier loss from that interface. It may mean nothing.

 

As an alternative why not try setting a fixed IP address in unRAID and see if you continue to lose carrier.

TY for your suggestions!  I set the IP to a static address and now connected, but will only connect 10/100.  So making progress.  I'm guessing that the issue now is the network driver?  From the posts that I have seen the realtek seems to be a real PITA!