October 5, 201213 yr Okay, I don't get it. I built a new server with a SuperMicro X8SIL-F board and had the same issue there. Tonight I am trying to upgrade my 4.7 to 5.0rc8a and I cannot get the NIC to grab an IP address. Everything works like a charm in 4.7. (Supermicro X5DAL-TG2 motherboard) When I get to 5.0, the syslog has lots of dhcp reconnections, and eventually, I get to the console with no eth0 access to the network, even though everything else appears fine. Syslog attached. I must be missing something since this has happened with both servers, but I can't find results yet. Any ideas would be gratefully received. Thanks in advance. syslog.txt.zip
October 5, 201213 yr Happened to me too. My [PCI] Intel NIC wouldn't give me access to my server either after upgrading to 5.0rc8a from 4.7 tonight. I swapped the CAT cable to the onboard Realtek NIC on my mobo and it worked right away. I'll check my syslog for DHCP errors.... I'll report back with my findings.
October 5, 201213 yr Author Happened to me too. My [PCI] Intel NIC wouldn't give me access to my server either after upgrading to 5.0rc8a from 4.7 tonight. I swapped the CAT cable to the onboard Realtek NIC on my mobo and it worked right away. I'll check my syslog for DHCP errors.... I'll report back with my findings. Hmm, maybe Intel NICs aren't the way to go? I've got a Pro1000GT NIC to try, too, but I remember it not working as well as the Realtek on my previous motherboard.
October 6, 201213 yr The network system is having a major argument over MTU size, cannot tell exactly who the players are. One entity is insisting on MTU=576, the other wants 1500, but unfortunately when the network chipset attempts to change from one to the other, the network goes down, and comes back up with what it already had, which the other party still wants to change. Perhaps it's a network driver issue? Or a router or switch that is trying to force the MTU size? This battle is stopping any effective use of the network.
October 11, 201213 yr Author Thanks Robj and Frank for your responses... I need to use (one of) the onboard NICs unless I put in a PCI(e) one, but as yet I have found no need. By setting a static IP on the servers, I can get it to work just fine. The MTU issue is intriguing but I cannot find a culprit. My network consists of a router and a switch connected together (Internet comes in via the WAN port on the router). A printer and several computers are connected on the LAN side, all Windows 7 and XP clients, along with two unRAID boxes. No VLANs, no crazy NAT setup or other advanced stuff. I keep it simple where I can. I have changed the Jumbo frame setting to disabled on the switch (router hasn't any such setting for the LAN side of things), then shut down and restarted both servers and power-cycled all network hardware, to no avail. If I leave unRAID settings to find IP and DNS automatically, I get no access to my server, and eth0 does not come up with an IP address using ifconfig. (Further, if I use ifconfig to assign one, it reports back that it has one, but no access is still the result.) It's very strange to me that this should not work, as it worked flawlessly in 4.7. I'd like to find the answer, but I will just use static IP settings for now so I can get access to my files over the network.
Archived
This topic is now archived and is closed to further replies.