Oh the indignity of my first post being a problem...

 

But anywho, I can't get my newly built UnRAID server to recognize my lan connection.  I have searched, seen the volume label fix, the network.cfg in wrong place fix, and tried assigning a static IP vice DHCP from my router to the server.  I started with 5.0b4, and downgraded to 4.7.  No Joy.  The board is the Supermicro X8SIL-F-O, which has two gigabit and one IPMI port.  The IPMI works, and I can get the LAN ports to work when connected to a wireless bridge I have set up in the living room.  But my server isn't in the living room, and it doesn't really get a good IP that way anyway.

 

When I connect and boot up, nothing LAN-related happens at all.  The router doesn't light up, the ports don't light up, and when I run ifconfig eth0, I get the same error others have had, where the MAC address shows up, but no inet address.  Anything you guys can suggest?  Attached is my syslog.txt for reading pleasure.  Thanks in advance!!

syslog.txt

Try a different cable. AFAIK, that while both ports support IPMI only one supports LAN traffic.

Try this thread for some commands on getting eth0 up and running.

 

I am still not quite understand the problem though.  You say that IPMI is working and that you can get the LAN ports working.  Try to more clearly explain the problem so we can help better.

Sorry, I should clarify.

 

There are three ports.  One for IPMI and two LAN ports.  I have excluded the cable, it works on my other computers.  If I plug the cable from the router into the IPMI port it recognizes it, but that port does not do LAN traffic. 

 

If bring this giant computer into the living room and connect it to the router I have set up as a wireless bridge, it gets an IP just fine.  Switch the cable to the router, no joy.  To reiterate, I can get an IP just fine with the same cable and my macbook just by plugging it in.

 

Studying further now, prostuff.  Thanks!

I tried the eth0 down and up, it says no carrier detected on eth0, reducing DHCP timeout to 10 sec.  Then it waits and kicks me back to #, no better off.  Maybe my router is doing something stupid?

Are your sure that your using the eth0 port?

I am, if I connect the other router/bridge, it works fine.  I've tried ifdown/ifup to no avail, just says no carrier detected.  If I run ethtool, it shows all modes available and autonegotiable, but none work.  I tried forcing gigabit/full duplex, autoneg off with ethtool -s, no luck.  What the deuce?!

 

 

I have used this board in client builds and not had a problem with them (save for one that had bad IPMI firmware, but I got a replacement no problem).

 

I plugged a single cable into the eth0 port and then plugged that into my router.  IPMI and Ethernet traffic went over that one port.  I did also have the IPMI and eth0 port hooked up to my router separately and it worked just fine.

 

It sounds like something funky is going on with your router.

Funky indeed.  It makes no sense, does my router just have it out for linux?  My ubuntu HTPC connects fine.  I upgraded the router firmware and tried a reboot, no luck.  I also tried plugging the cable into every RJ-45 jack on the board.  Let's just, for the sake of making sure I'm not a complete idiot, eth0 is which port?

It's the one on the left (not including the IPMI port, of course), at least on my X8SIL-F.

Thanks, that's what I have, just making sure!

the Dedicated IPMI is off to one side.  The eth0 port if the one closest to the IPMI port.

 

I suggest plugging into eth0 and restarting the machine.  Make sure there is no jumper set improperly on the board to disable that port.  Also make sure that in the BIOS it is not disabled.  And one last thing, check in the network.cfg file in the config folder of the flash drive.  Make sure that DHCP=yes is set, and nothing else.

Ok, I rebooted, checked jumpers, checked BIOS, doublechecked ports, checked network.cfg, everything is set as it should be.  I asked for a new IP (dhcpcd), checked the interface with ethtool, still no go.  I still get nothing but my MAC address, UP BROADCAST MULTICAST, and the rx/tx stuff.  No inet.  I upgraded router firmware, but the router doesn't even see the server.  It's not listed in the DHCP client table, light's not on on the router.  I guess I could flash dd-wrt onto the linksys...ugh this is frustrating!

How can I tell if network.cfg has the correct cr/lf markings at the end of the line?  If I'm in mcedit, they have a ^M.  Just a shot in the dark.

How can I tell if network.cfg has the correct cr/lf markings at the end of the line?  If I'm in mcedit, they have a ^M.  Just a shot in the dark.

they do on my server too.  I think that file, and the "go" script are both processed through "fromdos" before being used by unRAID.

 

Joe L.

Do you have a static IP, or is it using DHCP?

 

And just to confirm, the board will get an IP when connected to the bridge, correct? Just not when attached to the router. And that same router (and port) will supply an IP to a different computer when connected?

Problem solved, and we're preclearing!

 

I ended up flashing dd-wrt to the router, and it still didn't work.  SO, after drying my tears, I decided to see if a different cable would work.  Now before I actually hear all of you groan, I verified that my cable worked before.  I tried it with TWO other computers and it worked fine.  But as a wise man said, if you eliminate the impossible, all that remains must be the answer.  There was just NOTHING else to try!

 

So I picked up the computer and took it into the bedroom with the router and plugged in a 6-foot ethernet cable.

 

And it works.  Face.  Palm.

 

Thank you all very much for helping this noob!  Off to the Pimp My Rig forum for the build pictures...

Not to laugh at your pain and suffering or anything but... hehehe

 

I probably speak for more than a few when we say we have been there and done that.  Good only knows the number of times I have "verified" a cable on multiple machines only to find out it does not like the one I am working with.

 

Glad you are up and running and I hope you enjoy your unRAID server.

Thanks prostuff, I would love to be enjoying my server, but it seems i still have a network problem.  I precleared my 2 2tb EARS drives, finishing late sunday night, and went to work on Monday morning leaving it alone.  When I got home, couldn't access the server at all.  Checked the router, and the lights are still on and everything, but it can't get an IP address.  Router says it isn't asking for one.

 

I tinkered all last night, but to no avail.  The syslog is saying that the DHCP request times out (I'll post that as soon as I get home) so I tried manually requesting with dhcpcd, eth0 up and down, retried the static IP stuff with the router and the cfg file, sacrificed a goat, scrutinized each of a thousand settings on every page of dd-wrt and am no further on my way.

 

On the progress front though, the box says I have the network at 1000T full duplex and ethtool shows the connection.  It's on there, just doesn't get an IP.  The dedicated port for IPMI can get one, as I have had to connect to it to work on the machine. 

 

I also tried plugging into eth1, but no dice there either.

 

Oh, I also switched cables.  I'm running out of them now. 

Right.  So I fixed the problem after about 4 days of staring at the interwebs and typing in anything from the syslog I found useful.  DHCP server not responding.  Cannot connect to DHCP server.  IP address drops.  And so on.  I post this update (with keywords) so that others, if they end up with the same problem, can search and discover this, cause I might be the only genius who's done it so far.

 

During my attempt to fix the finicky cable, I flashed and reflashed three different firmwares onto my router.  In my haste, I failed to re-set them up properly.  There are 2 Windows laptops, 2 Macbook Pros, and (now) 2 Linux/Slack boxes in my house, so networking is a challenge.  I, until discovering the unRAID, had been using the Win7 machine as a web server/download server (since it can run .NET for the scrapers/media managers/renamers).  To simplify my life, I had set a DHCP reservation on my router, and told Windows it had a static IP.

 

You can see where this is going...

 

After flashing and reflashing and rereflashing, that reservation was no longer in the router.  I failed to, however, return my Windows PC to DHCP.  Apparently, it started acting as if it was a DHCP server, confusing and generally ignoring the unRAID server.  Interestingly enough, none of the other computers were affected by this.  So, if I rebooted the router to stock settings, it would briefly give the unRAID an IP until Windows decided to stick its nose in.

 

Troublemakers.

 

I will say though, it took me FOREVER to find an article somewhere that was talking about common/uncommon DHCP stuff in the Windows support databases that had useful information.  I had to return to the Source... 

 

I thank you all again for your help to me, and help to others that helped me.

I always set an assigned IP address to a MAC address in the router. Then, the router will always give out the same IP address to that computer. By doing it this way, there are no devices with fixed IP addresses that can mess-up the network.

 

In my network, the router always assigns the same IP address to the server. The other computers get whatever address is given to them.

 

Peter