moved unraid to new hardware network unavailable

[Ghostearror]

Hello all, 

 

 This is probably my first time posting here, but i'm stumped and I need assistance.  I have moved unraid from an old HP DL350 G3, to a not as old desktop i wasn't using. The problem is when i booted up the new hardware its not pulling a 192.x.x.x address, its now getting an 164.x.x.x address.  No network link on nic.  The console said something about bond0, so I pulled the usb drive popped it into another pc and found that bonding was set to "yes" in the config.  I changed it to no, however upon boot, it still doesn't pull an address.  I have tried getting the syslog, but I must be doing something wrong because i can't get the syslog.zip.  At the console I tried "diagnostics", which said it wrote a file, but i couldn't find it in the root of the usb, then i tried another command "cp /var/log/syslog /boot", but that did nothing as well, no file on the root of usb...  I suspect the board in my new hardware setup may be the issue as the nic is not intel, its made by killer, its a gigabyte board and i'm using the onboard.  I'd really love to give you all the syslog, as i'm sure someone could quickly identify my problem, but i'm at a loss for how to get it.

[trurl]

9 minutes ago, Ghostearror said:

getting an 164.x.x.x address

Are you sure it isn't a 169.x.x.x address?

 

Try renaming or deleting config/network.cfg on flash so it will use the default network settings, which will use DHCP to get an IP from your router.

[Ghostearror]

It is 169.x.x.x, the 164 was a typo.  I'll delete the network.cfg, and see if that works.  I did however check it before it was already set to DHCP. 

[trurl]

169 is what happens when it can't get ip from router. Check cables plugs ports 

[Ghostearror]

Its plugged into the same cable the old server was on, and i rebooted the switch it was plugged into.  I deleted the network.cfg and still no go.  I will try a different port and cable and see if that makes a difference. 

[Frank1940]

If that does not work, go to the console (Monitor/keyboard or terminal in GUI) and type diagnostics    Upload the file in a new post.

[Ghostearror]

So as a test, I plugged a drive with windows on it, and it pulls an address. When I throw unraid back in, it does not. I have tried to get the diag log, but I must being doing something wrong because it doesn't write the file. I've ordered a network card, with the hope that the new mac will pull a dhcp address... Because I'm running out of ideas.

[remotevisitor]

Are you sure the flash drive is being successfully mounted on /boot?

 

If you run the following command what files/folders do you see?

ls /boot

 

[Ghostearror]

I'll check, but if it wasn't, would I even be able to get into unraid?  I've logged in, ran command diagnostics, it says it writes the file but when i move the flash drive to my pc there is no folder for logs or any file that is written.  I also noticed that its not creating the network.cfg, which I removed that as part of troubleshooting earlier, expecting it to recreate itself upon boot.  I was able to get into the gui, I checked the network settings and its showing: 

Jun 20 19:23:36 Tower: kernel: alx 0000:04:00.0 eth0: fatal interrupt 0x200, resetting

 

Does this mean there is an irq conflict?  I've checked in bios and I don't see any way to change irq assignments... 

 

This whole move has really frustrated me, I'm half tempted to put all the drives back in the old box, just to get it working again.  I have a feeling this is an issue with the Killer onboard nic my Gigabyte board has.  I've ordered a pcix network card that should be coming today, I'm gonna pop that in and see if it will at least pull an address.

[JorgeB]

5 minutes ago, Ghostearror said:

I also noticed that its not creating the network.cfg

That suggests a flash drive problem, try recreating it or using a different one.

[Frank1940]

Make sure the boot drive is plugged into a UBS2 port...

 

[Ghostearror]

The flash drive is plugged into a usb 2.0 port.  I can get into the GUI, so unraid does load, and I can see all the drives, i just get no network. 

[Frank1940]

4 minutes ago, Ghostearror said:

I can get into the GUI,

A bit of clarification.  You are referring to the GUI on the console that you can activate by selecting it during the boot process. 

[Ghostearror]

Yes the console gui.

[Ghostearror]

I was finally able to get the syslog.  I put the new NIC in and still no address.  My thinking is there is something in my bios that needs adjusting, because this board has a mix of 3.1, 3.0, 2.0 ports.  I have the flash plugged into a 2.0 port, and when anything else is plugged into the 3.1 or 3.0 ports the system won't boot.  I'm hoping one of you gurus can read the log and tell me what the heck is going on.  Thanks for everyones assistance on this. 

syslog.txt

[trurl]

12 minutes ago, Ghostearror said:

My thinking is there is something in my bios that needs adjusting, because this board has a mix of 3.1, 3.0, 2.0 ports.  I have the flash plugged into a 2.0 port, and when anything else is plugged into the 3.1 or 3.0 ports the system won't boot.

Probably because your BIOS is trying to boot from those other ports. Make sure only the flash drive is allowed as a boot device in the BIOS.

 

On 6/19/2020 at 6:50 PM, Ghostearror said:

I suspect the board in my new hardware setup may be the issue as the nic is not intel, its made by killer,

Here is another link I found about that, but I'm not sure if that is the final word on whether your NIC is supported.

 

https://forums.unraid.net/topic/73697-cache-drive-not-working/?do=findComment&comment=678161

 

There is this in your syslog which suggests it may be communicating with the router:

Jun 21 13:40:33 Tower avahi-daemon[4808]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Jun 21 13:40:33 Tower avahi-daemon[4808]: New relevant interface virbr0.IPv4 for mDNS.
Jun 21 13:40:33 Tower avahi-daemon[4808]: Registering new address record for 192.168.122.1 on virbr0.IPv4.

 

 

[Ghostearror]

My frustration level is at its breaking point. I've tried everything I can think of and I just can't figure out why unraid won't get an ip address. My only recourse at this point is to put all the old hardware back together and restore the flash drive. At least then I can get the server back up while I troubleshoot the new hardware.