tower-diagnostics-20170918-2349.zip

 

Hi,

 

I've been using unraid for a couple of years now and never had any real issues.

Earlier today I was transferring about 40 Gigs of files from my unraid server to a Synology box.

In the same time I was doing some work on a Windows 10 VM I'm running on the unraid server.

When I came back to the VM after a few hours it had lost it's network connection. I ran the Windows Network Problem Solver without success.

 

I could not ping 192.168.0.1

I had no access to my unraid box from within the VM. The unraid box has one ethernet cable running to a switch.

I could not connect to my unraid box from an external laptop of iPad.

 

I restarted the VM - No result

I reset the switch - No result

I reset my router/modem - No result

I could connect to my Synology box, which is connected to the same switch.

I checked the ethernet cable with my cable tester - it showed no errors.

I plugged the cable in a different port on both sides - No result.

I'm using the ones on the motherboard, I have no PCI network card.

 

I updated to 6.3.5 a few days ago.

 

Attached is my diagnostics file. I'm curious about the following lines that repeat over and over again.

 

Sep 18 23:49:33 Tower kernel: device eth1 entered promiscuous mode
Sep 18 23:49:33 Tower kernel: bond0: first active interface up!
Sep 18 23:49:33 Tower kernel: br0: port 1(bond0) entered blocking state
Sep 18 23:49:33 Tower kernel: br0: port 1(bond0) entered forwarding state
Sep 18 23:49:34 Tower kernel: igb 0000:05:00.1 eth1: igb: eth1 NIC Link is Down
Sep 18 23:49:34 Tower kernel: bond0: link status definitely down for interface eth1, disabling it
Sep 18 23:49:34 Tower kernel: device eth1 left promiscuous mode
Sep 18 23:49:34 Tower kernel: bond0: now running without any active interface!
Sep 18 23:49:34 Tower kernel: br0: port 1(bond0) entered disabled state
Sep 18 23:49:42 Tower kernel: igb 0000:05:00.1 eth1: igb: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Sep 18 23:49:42 Tower kernel: igb 0000:05:00.1 eth1: Link Speed was downgraded by SmartSpeed
Sep 18 23:49:42 Tower kernel: bond0: link status definitely up for interface eth1, 100 Mbps full duplex
Sep 18 23:49:42 Tower kernel: bond0: making interface eth1 the new active one
Sep 18 23:49:42 Tower kernel: device eth1 entered promiscuous mode
Sep 18 23:49:42 Tower kernel: bond0: first active interface up!
Sep 18 23:49:42 Tower kernel: br0: port 1(bond0) entered blocking state
Sep 18 23:49:42 Tower kernel: br0: port 1(bond0) entered forwarding state
Sep 18 23:49:43 Tower kernel: igb 0000:05:00.1 eth1: igb: eth1 NIC Link is Down
Sep 18 23:49:43 Tower kernel: bond0: link status definitely down for interface eth1, disabling it
Sep 18 23:49:43 Tower kernel: device eth1 left promiscuous mode
Sep 18 23:49:43 Tower kernel: bond0: now running without any active interface!
Sep 18 23:49:43 Tower kernel: br0: port 1(bond0) entered disabled state
Sep 18 23:49:51 Tower kernel: igb 0000:05:00.1 eth1: igb: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Sep 18 23:49:51 Tower kernel: igb 0000:05:00.1 eth1: Link Speed was downgraded by SmartSpeed
Sep 18 23:49:51 Tower kernel: bond0: link status definitely up for interface eth1, 100 Mbps full duplex
Sep 18 23:49:51 Tower kernel: bond0: making interface eth1 the new active one
Sep 18 23:49:51 Tower kernel: device eth1 entered promiscuous mode
Sep 18 23:49:51 Tower kernel: bond0: first active interface up!
Sep 18 23:49:51 Tower kernel: br0: port 1(bond0) entered blocking state
Sep 18 23:49:51 Tower kernel: br0: port 1(bond0) entered forwarding state
Sep 18 23:49:52 Tower kernel: igb 0000:05:00.1 eth1: igb: eth1 NIC Link is Down
Sep 18 23:49:52 Tower kernel: bond0: link status definitely down for interface eth1, disabling it
Sep 18 23:49:52 Tower kernel: device eth1 left promiscuous mode
Sep 18 23:49:52 Tower kernel: bond0: now running without any active interface!
Sep 18 23:49:52 Tower kernel: br0: port 1(bond0) entered disabled state

 

 

Edited September 18, 20178 yr by struisje

Hi,

 

Small update:

• I connected a USB ethernet adapter to the server and plugged the ethernet cable into that. No success
• I updated the network config from static to dynamic IP
• I rebooted into safe mode with GUI and was able to edit the settings for eth2.
• It now receives an IP address from the DHCP
• I was now again able to connect to the unraid GUI from another PC.

So far so good.

 

Now I have eth0, eth1 and eth2.

Should I disable eth0 and eth1 somewhere so it will default to eth2?

 

 

You should probably post your MB and CPU information.  I can not help you (as I have always had a simple Network setup with a single port and no sharing of the link) but I suspect you have a problem with the Network Settings.

I'm running a HP Proliant DL160 G6

 

I believe the motherboard is a HP 637970-001 With LGA 1366/Socket B and 24 Gb DDR3 SDRAM

 

I'm running dual Intel Xeon L5520 CPU's at 2,27 GHz

 

Network is a HP NC362i integrated dual port gigabit server adapter

6.3.x is not good to run on proliants. You should downgrade to 6.2.4 and wait for 6.4 to go stable.