Had to install a new motherboard on my unraid 4.7 machine.

 

Boots OK but no network access.  ifconfig shows only local loopback. The machine boots fine into Ubuntu and the network works fine in ubuntu.

 

I've seen this before but long ago and can't remember how to fix it.

 

Have attached the network.cfg and system log.  The network.cfg is the same as the old mother board. I've had to truncate the log file as it is full of errors about wrong disk assignments and therefore to big to upload.  Hope I truncated the right bits.

 

Any help much appreciated

network.cfg

syslog-20121005-015642.txt

Delete the following line from the network.cfg file

HWADDR=00:E0:81:D2:1C:B8

Otherwise you'll be forcing the MAC address. (and possibly causing a duplicate if the original MB is used elsewhere on your LAN)

 

Then, reboot your router...  It knows the old MAC address.  Make sure there is nothing else on your LAN with the same IP address, and finally....

Is the network chipset in your new MB recognized at all by unRAID?    It might not be supported. (Might have support in newest 5.0rc8a, but that might complicate your MB upgrade process. )

 

You could try booting 5.0rc8a, though, just to make sure.  Just use a different flash drive and do not assign any drives, as all you are checking at that point is the networking chipset.  If there is more than one LAN connector on the MB, try the other one.

 

Joe L.

Network chipset seems to be recognized in boot messages

Oct  5 01:55:00 Tower kernel: e100: Intel® PRO/100 Network Driver, 3.5.24-k2-NAPI

Oct  5 01:55:00 Tower kernel: e100: Copyright© 1999-2006 Intel Corporation

Oct  5 01:55:00 Tower kernel: Broadcom NetXtreme II CNIC Driver cnic v2.0.1 (Oct 01, 2009)

 

But no network connection is detected;

Oct  5 01:55:00 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig lo 127.0.0.1

Oct  5 01:55:00 Tower logger: /etc/rc.d/rc.inet1:  /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo

Oct  5 01:55:00 Tower ifplugd(eth0)[1726]: ifplugd 0.28 initializing.

Oct  5 01:55:00 Tower ifplugd(eth0)[1726]: Using interface eth0

Oct  5 01:55:00 Tower ifplugd(eth0)[1726]: Initialization complete, link beat not detected.

 

Does your new MB have multiple network ports?  A quick google check based on your sig seems to show it has three ethernet ports?  http://www.tyan.com/product_board_detail.aspx?pid=645

If so, have you tried the other two ports?

Thanks for the replies.

 

Tried the mods suggested by Joe L but they did not help.  Then I tried booting with a V5 release as suggested and it worked.  That left me in a bit of a dilemma with a new motherboard to configure and an update to V5 at the same time.  Not for the feint hearted. 

 

As I had all my data backed up anyway, I decided to go for it.  Amazingly the update sorted out all my drive placements correctly and everything worked great on first start up.

 

The old motherboard had been causing all sorts of problems but I was reluctant to change it with all the potential problems I envisaged that might cause.  Well I need not have worried.  Turned out to be so easy.  I have done this before with a windows machine and what a major hassle that was. 

 

Thumbs up once again for UNRAID.

this is because unraid is basically installed every boot, not just loaded up.

 

windows is installed once and loaded up each boot.

 

imagine how long your computer would take to start if windows installed each boot like unraid!