Power Cut - No configured network interfaces

[Charlie Gilman]

Hello,

I have a HP N54L Microserver with 8GB RAM installed.

Today I had a power cut at my house, happens occasionally and usually it's fine, however after this one the machine wouldn't respond to pings or anything.

Connected it up to a monitor and there are numerous messages saying that "no configured interfaces were found", when I go to "Configure Network Interfaces" there are no interfaces listed, hmm.

Used the shell to type the ifconfig command and this is returned:

Tried a loopback address ping (127.0.0.1), it responds.
Tried a LAN and external address ping and they both fail.

Other things I've tried:
- All combinations of things typed into the "Configure network interfaces", menu, including (blank), 1, and any of the network interfaces listed from the ifconfig.

Any help would be really appreciated,
Charlie

 

[Fraoch]

This will sound obvious but what's the state of your switch and/or router after the power cut? Maybe the FreeNAS server came up before your DHCP server? Is the switch/router indicating a proper connection? If so, just try rebooting.

 

[Charlie Gilman]

This will sound obvious but what's the state of your switch and/or router after the power cut? Maybe the FreeNAS server came up before your DHCP server? Is the switch/router indicating a proper connection? If so, just try rebooting.

Thanks for your reply.

It was initially connected directly to the router and has been for almost a year, I removed it from there when I noticed the connection problems.
Router itself is fine, all other wired and wireless devices are working.

It's now in my room for testing, it is wired to a 5 port gigabit switch along with my desktop PC and Xbox. Both these devices are working perfectly on the same switch.

It has also been rebooted about 4 times, at both locations.

 

[cyberjock]

Well, the output of ifconfig is much longer than what you see... so you need to post the rest of the output. Try "ifconfig | more" and take pictures of that. ;)

 

[Charlie Gilman]

Well, the output of ifconfig is much longer than what you see... so you need to post the rest of the output. Try "ifconfig | more" and take pictures of that. ;)

Thought someone might mention that, I've literally spent the last 20 minutes trying to type the pipe symbol, got it eventually, where the tilde is for some reason haha.

It goes on for pages and pages (listing bridge1-5 and epair1-5a), but I think I've found the relevant part, the lo0 interface, though why can I not see a MAC address...?

Edit: just swapped this image for the one in the main thread too.

 

[cyberjock]

Yep.. i want to see all 5 pages. The ones posted are useless to me. lo0 is loopback, bridges and epairs are for jails and such.

 

[depasseg]

Or SSH into it and copy and paste the whole ifconfig output at one time.

 

[cyberjock]

He can't ssh in... his network is down.

 

[depasseg]

Whoops! My bad.

 

[Charlie Gilman]

Yep.. i want to see all 5 pages. The ones posted are useless to me. lo0 is loopback, bridges and epairs are for jails and such.

I'd say the rest is probably useless then as it's all bridges and epairs... from the top to the bottom:

 

[Charlie Gilman]

To me it looks like I'm gonna need a new NIC, any one have any ideas?

 

[cyberjock]

Yep.. looks like a new NIC is going to be in your future. It's not detecting your NIC at all. You could try looking at the dmesg output after a bootup and see if it says something that makes it obvious the NIC is even detected and the driver is failing to load. But in either case the answer is probably "your hardware is broken".

 

[Ericloewe]

Check the BIOS to see if the NIC was randomly disabled, first.

 

[Charlie Gilman]

Check the BIOS to see if the NIC was randomly disabled, first.

No go, just not detected at all :/

Yep.. looks like a new NIC is going to be in your future. It's not detecting your NIC at all. You could try looking at the dmesg output after a bootup and see if it says something that makes it obvious the NIC is even detected and the driver is failing to load. But in either case the answer is probably "your hardware is broken".

Looks like it, gone ahead and ordered the gigabit TP Link one on Amazon with 4.5 stars, can't go wrong for £6. Thanks very much for your help :)

 

[gpsguy]

If/when the "new" one fails to work, buy this one for about £27.

Intel EXPI9301CTBLK PRO1000 Network Card CT PCIex Bulk

Looks like it, gone ahead and ordered the gigabit TP Link one on Amazon with 4.5 stars, can't go wrong for £6.

I tried to include a link to Amazon .UK, but the forum software kept changing the post.

 

[Ericloewe]

The TP-Link one is almost certainly Realtek. Unfortunately, you can go wrong with Realtek.

Intel is the go-to GbE solution around here.

 

[cyberjock]

Yeah.. Can I bet money that the TP Link won't work? ;)

 

[rogerh]

Personally I would unplug the machine, remove the battery, clear the CMOS, reset BIOS defaults, and review all the settings before giving up the onboard NIC.

 

[Charlie Gilman]

Installed the new NIC today, no problems at all, up and running perfectly again.

For future reference this was the TP Link TG-3468.

 

[cyberjock]

What driver does it use? Is it recognized as an re(x) device?