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.

 

tower-diagnostics-20200806-0845.zip

Try using one of the other NICs, also you appear to have a failing DIMM, check system event log, it might have more info on which one it is.

10 minutes ago, chris B said:

the tropical storm

Have you tried another port on your router / switch?

7 minutes ago, trurl said:

Have you tried another port on your router / switch?

Good suggestion, not it.

20 minutes ago, johnnie.black said:

Try using one of the other NICs, also you appear to have a failing DIMM, check system event log, it might have more info on which one it is.

Hey good suggestion, tried another nic, no dice.. Any other thoughts?

What if I blew away all my network config info in /config, and rebooted the machine? Does anyone feel that might make a difference?

It won't hurt to try, I would also get rid of the bond, simplify the LAN as much as possible.

diagnostics show that interface eth2 link is active.  Did everything jump ship to that?

2 minutes ago, civic95man said:

diagnostics show that interface eth2 link is active.  Did everything jump ship to that?

I am not sure. I have tried messing with it a bit. Is there a log/screen shot I can send you to verify?

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 August 6, 20205 yr by civic95man

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?

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.

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?

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.

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:

 

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.

I plugged in several ethernet cables, I have multiple ethernet adapters. With 2 cables plugged in, eth0 never propagates. I see eth1, and br0..

Spent more time on it, not sure what else it could be. Is there anything else anyone would suggest? Thinking about doing a fresh install and see if that helps.

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..

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.