hi all

 

running 6.2.4

 

I shut down my server to replace a failed HDD

on booting back up i has no network

(it was set to static as 90% of my network is)

 

i have tried a few things while using the gui load and KVM

 

re-seated the 2 nics 1x2 port and 1x1 port

replaced both nics with other known working ones

replaced the 3 cables

replaced the network.cfg file with a blank one from the download and deleted the static details from my router

tried to connect using dhcp

also tried to connect to another router off my main network

 

the onboard nic has never been visible to unraid so i cant use this

 

unraid does know when a link is up or down as it keeps telling me that eth0 eth1 eth2 are unplugged etc

 

i keep getting a 169.254...... range ip

i am not able to ping out or into the server

 

any ideas ?

Sounds as if maybe you have either a network cabling problem or perhaps a port on your router has failed.

i have tried it on 2 separate wired networks with 2 different routers and i get the same 169. ip range

hi all

 

running 6.2.4

 

I shut down my server to replace a failed HDD

on booting back up i has no network

(it was set to static as 90% of my network is)

 

i have tried a few things while using the gui load and KVM

 

re-seated the 2 nics 1x2 port and 1x1 port

replaced both nics with other known working ones

replaced the 3 cables

replaced the network.cfg file with a blank one from the download and deleted the static details from my router

tried to connect using dhcp

also tried to connect to another router off my main network

 

the onboard nic has never been visible to unraid so i cant use this

 

unraid does know when a link is up or down as it keeps telling me that eth0 eth1 eth2 are unplugged etc

 

i keep getting a 169.254...... range ip

i am not able to ping out or into the server

 

any ideas ?

 

The 169 address means that your system is not getting a valid ip address from tis dhcp server..

 

You say that you are using fixed ip addresses, did you check if you indeed have a fixed address entered ?  The 169 should only happen in a dhcp scenario where dhcp is not working..

yes i have tried this

i have tried the following on both routers

 

dhcp on both unraid & router

dhcp on unraid & static on router

Static on both

 

in all instances i am unable to ping router

If you set a static ip address you still get this address back ?  That should not be possible..

Your Network setting isn't static - the 169.x.x.x indicates, that the APIPA-Protocol (Automatic Private IP Addressing) is working. This happens only when the Network is set to DHCP

Try creating a linux live USB drive and booting to Linux to test the network hardware first.

If it works there, then perhaps it is the Unraid instance.  You could back up the flash contents, then do a new build onto the flash drive and restore the config. 

Your Network setting isn't static - the 169.x.x.x indicates, that the APIPA-Protocol (Automatic Private IP Addressing) is working. This happens only when the Network is set to DHCP

 

exactly..

Try creating a linux live USB drive and booting to Linux to test the network hardware first.

If it works there, then perhaps it is the Unraid instance.  You could back up the flash contents, then do a new build onto the flash drive and restore the config.

 

Can you please explain how the backup and restore works?

 

How about all for the shares, permissions and VMS?

 

I had similar problems last week that first showed itself with my unRAID box. Have the 2 LAN ports set up as LACP aggregated on my switch.  unRAID pulled a 169 address, even after each reboot. I tried to break the bond but that didn't help. Then other clients, like my laptop, phone, etc dropped off the network with 169 addresses.

 

Only way I was able to get unRAID back was to set a static IP in network.cfg (unplugged the flash drive and put it in my laptop to change the file). After that, I found the problem was my router (a Ubiquiti Edgerouter Lite), rebooted it and downgraded from a recently applied firmware (which I believe was the root cause). Had to restart all my client devices to pull DHCP.

 

Long story short, as another person said, try manually setting a static IP in unRAID's network.cfg file.

I had similar problems last week that first showed itself with my unRAID box. Have the 2 LAN ports set up as LACP aggregated on my switch.  unRAID pulled a 169 address, even after each reboot. I tried to break the bond but that didn't help. Then other clients, like my laptop, phone, etc dropped off the network with 169 addresses.

 

Only way I was able to get unRAID back was to set a static IP in network.cfg (unplugged the flash drive and put it in my laptop to change the file). After that, I found the problem was my router (a Ubiquiti Edgerouter Lite), rebooted it and downgraded from a recently applied firmware (which I believe was the root cause). Had to restart all my client devices to pull DHCP.

 

Long story short, as another person said, try manually setting a static IP in unRAID's network.cfg file.

 

 

Sadly, i have tried this already

 

i have manually added the ip etc

i have replaced the network.cfg file with a blank standard one

 

i have also turned bonding and bridging off to troubleshoot

 

i also did have a problem with my router and have since replaced it (twice) now using asus rt-ac88u

 

if i shut the server down for a few days then boot it back up it will be seen by my router as an active client, but as soon as you try to ping it.. poof its gone

 

i am looking at ifconfig on the server and noticed lots of dropped packets

then when trying to ping "no buffer space"

 

any ideas ?

 

i have attached screenshot

 

How much RAM memory is installed in your system?

 

How much RAM memory is installed in your system?

 

24gb ecc DDR 3

does anyone have any idea ?

 

its been a few weeks now and still unable to get this up again

 

 

 

i would like to know how to restore all of my settings after i have recreated the usb drive

Your previous picture shows only eth0 (=single port). Is this while both NICs are still installed? If so, remove the 2x1 NIC and test again.

 

Perhaps testing with a single NIC installed might be a good idea anyway.

 

Your previous picture shows only eth0 (=single port). Is this while both NICs are still installed? If so, remove the 2x1 NIC and test again.

 

Perhaps testing with a single NIC installed might be a good idea anyway.

 

this is a dual port nic - i have disabled the other interface

 

i have also tried many single nic cards and another dual nic

the onboard nic is not visible to unraid

 

my original setup was 1x dual nic and 1x single nic

currently there is only the dual nic installed

... currently there is only the dual nic installed

 

That doesn't appear to work correctly, since there is no eth1 or did you disable that port?

 

... currently there is only the dual nic installed

 

That doesn't appear to work correctly, since there is no eth1 or did you disable that port?

 

yes i disabled the port

Can you post your diagnostics. See Tools in the GUI or if the GUI is unavailable then use telnet/ssh or console and type diagnostics from CLI (file is stored on your flash device in folder logs).

Can you post your diagnostics. See Tools in the GUI or if the GUI is unavailable then use telnet/ssh or console and type diagnostics from CLI (file is stored on your flash device in folder logs).

 

ok diagnostics generated

 

which files do you want to see ?

Can you post your diagnostics. See Tools in the GUI or if the GUI is unavailable then use telnet/ssh or console and type diagnostics from CLI (file is stored on your flash device in folder logs).

 

ok diagnostics generated

 

which files do you want to see ?

 

Post the zip file, it allows to make correlations.

 

Can you post your diagnostics. See Tools in the GUI or if the GUI is unavailable then use telnet/ssh or console and type diagnostics from CLI (file is stored on your flash device in folder logs).

 

ok diagnostics generated

 

which files do you want to see ?

 

 

added

 

Post the zip file, it allows to make correlations.

tower-diagnostics-20161231-1642.zip

Both your syslog and lspci output show no installation or recognition of your NIC card.

 

Try to reseat it or use a different PCI slot.

 

Both your syslog and lspci output show no installation or recognition of your NIC card.

 

Try to reseat it or use a different PCI slot.

 

yes i have just noticed this myself, when i booted the system up i changed the pci slot then realised after i had generated the file that it was not discovered

 

i am re attaching another set of diagnostics where the card is detected

 

i also have logs generated from november when i was playing about and everything was working.. do they help ?

tower-diagnostics-20161231-1659.zip