I was previously running 4.3.3 with zero issues. I upgraded to 4.4.2 and unRAID is no longer seeing/connecting to the network. Downgrading back to 4.3.3 fixes the issue, but I'm trying to stay up to date. Syslog is below. Please let me know if there is any more info i can provide.

 

syslog is posted here:http://www.joshualevin.com/syslog-2009-02-23.txt

I was previously running 4.3.3 with zero issues. I upgraded to 4.4.2 and unRAID is no longer seeing/connecting to the network. Downgrading back to 4.3.3 fixes the issue, but I'm trying to stay up to date. Syslog is below. Please let me know if there is any more info i can provide.

 

syslog is posted here:http://www.joshualevin.com/syslog-2009-02-23.txt

 

I would try restarting the router, it can't hurt.

 

I will take a closer look through the log but hopefully RobJ or someone more adept at reading these will chime in

no joy on router restart

RESOLVED!

 

Problem was with the Marvell LAN. I disabled it and now everything is working.

RESOLVED!

 

Problem was with the Marvell LAN. I disabled it and now everything is working.

 

Glad to see you got it fixed.

 

I had just finished looking through the syslog too.  I noticed that the eth0 was not getting a signal which is what lead me to my initial assumption and suggestion to restart the router.  I guess the fact that there was no return signal also could have meant that no signal was even getting sent.

You beat me!

 

The Linux kernel in unRAID v4.4.2 found and setup the Yukon-Lite network chipset (used in a number of motherboards and cards such as Marvell) before it found and setup the onboard nVidia LAN chipset.  The kernel in v4.3-beta6 found them in the reverse order.  unRAID always uses the first one, as eth0.

 

So you could either switch the network cable to the other port, or turn off one in the BIOS, which you did.  Good detective work!

funny thing is, i think i'm getting better transfer rates on the NV LAN.