Interface Ethernet Port 0 is down. Check cable!


Recommended Posts

Hello all, 

 

How a power outage due to the tropical storm the other day. I had a UPS on the server, however I am not sure if it did shut down gracefully or not? I booted it up last night, and it appears to have some networking issues? It becomes unresponsive on my local network pretty frequently. Any session I have with it via browser, it drops. Any authentication I have with it, it logs me off.

 

Any help would be greatly appreciated.

 

1949846215_ScreenShot2020-08-06at8_47_56AM.thumb.png.444ef9a030219dbf13a681669fe026d5.png

tower-diagnostics-20200806-0845.zip

Link to comment
39 minutes ago, chris B said:

Is there a log/screen shot I can send you to verify?

network settings should show that

 

Diagnostics show this for interface eth2:

Settings for eth2:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: Symmetric
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised pause frame use: Symmetric
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Speed: 1000Mb/s
	Duplex: Full
	Port: Twisted Pair
	PHYAD: 1
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: on (auto)
	Supports Wake-on: pumbg
	Wake-on: g
	Current message level: 0x00000007 (7)
			       drv probe link
	Link detected: yes

The rest show "link detected: no"

Edited by civic95man
Link to comment
2 hours ago, civic95man said:

network settings should show that

 

Diagnostics show this for interface eth2:


Settings for eth2:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: Symmetric
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised pause frame use: Symmetric
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Speed: 1000Mb/s
	Duplex: Full
	Port: Twisted Pair
	PHYAD: 1
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: on (auto)
	Supports Wake-on: pumbg
	Wake-on: g
	Current message level: 0x00000007 (7)
			       drv probe link
	Link detected: yes

The rest show "link detected: no"

 

Appreciate your help, honestly..

So I went into /config/network.cfg, deleted it.

rebooted

 

Still the same error message.

 

How would I set everything back to eth0?

Link to comment

Need new diagnostics to know for sure.  Did the network cable get moved from one port to another? The interface assignments should be saved to /config/network-rules.cfg on your flash drive. So the interface assignments will remain static and shouldn't hop around from one (re)boot to the next.  Might need to verify that file.

 

Without knowing more about your setup, you should just be able to connect your cable into the eth0 assigned port.

Link to comment
45 minutes ago, civic95man said:

Need new diagnostics to know for sure.  Did the network cable get moved from one port to another? The interface assignments should be saved to /config/network-rules.cfg on your flash drive. So the interface assignments will remain static and shouldn't hop around from one (re)boot to the next.  Might need to verify that file.

 

Without knowing more about your setup, you should just be able to connect your cable into the eth0 assigned port.

 

That's the weird, thing.. The cable was never moved, period...

 

What is also strange, is if it wasn't connected, I shouldn't be able to access via the web right?

Link to comment
14 minutes ago, civic95man said:

you're accessing the webgui from a different computer or from unraid itself in gui mode?  Try a different cable, try another computer on the SAME port of your router/switch.  Just rule out all of the variables first.

 

running ifconfig:

1462378055_ScreenShot2020-08-06at5_21_50PM.thumb.png.d2eb0232e088a295722b0d87aa7a75d7.png

 

Could this be the culprit? I have a few VM's running on it, and it looks like br0 is the one with the IP addr.

Link to comment

The Nic card was dead.

I have the ip assignment so low, that when the power rebooted, all these other devices grabbed that ip. So I could see in the machine I assigned it a static ip, however it couldn't do any DNS look ups..

Either of which I feel like I could have easily fixed on my own. Together, however, while testing, threw me for a spin..

Link to comment
18 minutes ago, chris B said:

I have the ip assignment so low, that when the power rebooted, all these other devices grabbed that ip.

I let everything on my network use DHCP, and if I want specific IP addresses for certain devices, I reserve that IP by MAC in my router. That way it is all managed in one place.

  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.