My server was up and running then my internet crashed. I ended up having to switch my router to the stock modem/router all in one (I have Starry for ISP if that matters at all). Ever since I have been getting this on boot:

 

IPv4 address: not set

IPv4 address: not set

 

I saw another thread saying to change BONDING to NO in the network.cfg file. This didn't appear to change anything. I tried recreating the boot USB to start fresh and nothing changed either. I'm not concerned with saving any data as all I had was a few dockers installed, this is a new NAS build.

 

I'm not sure what to do from here and any help is appreciated! I attached the diagnostics file from the most recent boot.

tower-diagnostics-20191109-0726.zip

Edited November 9, 20196 yr by pmiller1673

Check cables and connections including plugs and ports.

Tried that, still nothing. Swapped the cords and ports with my desktop and they work just fine there.

Your diagnostics show that the interface is not connected.

Settings for eth0:
	Supported ports: [ TP AUI BNC MII FIBRE ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: Symmetric Receive-only
	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 Receive-only
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Speed: Unknown!
	Duplex: Unknown! (255)
	Port: MII
	PHYAD: 0
	Transceiver: internal
	Auto-negotiation: on
	Supports Wake-on: pumbg
	Wake-on: g
	Current message level: 0x00000033 (51)
			       drv probe ifdown ifup
	Link detected: no

Usually this is a cable problem.

I feel like an ninny but i got it to work. Pulled ethernet cables from everything and used compressed air on all ports. Works now!