Please ... I just want to get my server back to its working state, but it currently won't boot.

 

I was trying to upgrade the NIC to 10Gbe (which obviously failed).

 

Now, removing the old card and just inserting the old HP 4-port NIC which had always worked ... Unraid will no longer boot.

 

I've tried deleting /conf/network.cfg ... 

 

And I modified /conf/network-rules.cfg to:

 

# PCI device 0x8086:0x1563 (ixgbe)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="d0::18", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"
--

# PCI device 0x8086:0x1563 (ixgbe)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="d0::19", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth5"
--

# PCI device 0x8086:0x150e (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ac::5c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x8086:0x150e (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ac::5d", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x150e (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ac::5e", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x8086:0x150e (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ac::5f", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

 

The first two are my motherboard NIC(s) ... and they never worked.

 

The remaining 4 are the HP 4-port NIC which always did work ... except they were renamed eth6-9 after attempting to add the 10Gbe NIC.  So, I renamed them back to eth0-3.

 

I've read in other posts that the GUI always starts on eth0, so I was hoping this would clue Unraid in to look at that ::5c MAC address, which is where I had always plugged a single Gigabit ethernet cable into.

 

But, nothing ever appears to boot, my router never registers a new IP (or ... the reserved IP that ::5c MAC should get), and I'm stuck >12 hours now without my server

 

Any help is appreciated getting my beast back up and running.  

Edited March 16, 20233 yr by gizmo000

8 minutes ago, gizmo000 said:

And I modified /conf/network-rules.cfg to:

Try deleting/renaming this one as well, it will get recreated on first boot.

3 minutes ago, JorgeB said:

Try deleting/renaming this one as well, it will get recreated on first boot.

In one of my iterations, I had deleted both `network.cfg` and `network-rules.cfg`, but the system still failed to respond to anything (never showed up on my network).

Link lights show up on the NIC, but IP addresses never register with my router.

 

Ironically, when I had the 10Gbe NIC plugged in, the same behavior occurred ... I would get a good link, but no IP address.

 

I have over 50 devices on the network, so I know DHCP is working properly ... swapping the hardware NIC was the only change(s) I made to the Unraid server.

41 minutes ago, gizmo000 said:

I had deleted both `network.cfg` and `network-rules.cfg`, but the system still failed to respond to anything (never showed up on my network).

Post the diagnostics after doing this again.

Turns out my boot order was mangled in one of the reboots ... no idea why or how that would occur without me changing it.  So the server was just sitting there not knowing what to boot.  My BIOS won't seem to pick the right boot drive (tries to boot UEFI, but I boot Unraid legacy).

 

If I manually boot, it starts just fine.  So, I'll have to dig into the BIOS settings to see if I can't force it to skip the UEFI checks (I didn't see any obvious way to force this at first glance).  It's an ASRockRack ROMED8-2T.

 

So, I tried to re-install the 10Gbe adapter, which is utilizing the `ixgbe` driver that I happened to notice wouldn't get IP addresses in Unraid before.  I already have an identical NIC in a workstation running linux (ixgbe) that picks up the IP address just fine.  Is there a known bug in Unraid that prevents ixgbe from obtaining IP addresses?

 

 

Actually with the 10Gbe NIC installed, and eth0 properly assigned (5c is the HP 4-port Ethernet NIC):

 

# PCI device 0x8086:0x150e (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ac::5c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x8086:0x150e (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ac::5d", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x150e (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ac::5e", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x8086:0x150e (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ac::5f", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

# PCI device 0x8086:0x1563 (ixgbe)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="d0::18", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"

# PCI device 0x8086:0x1563 (ixgbe)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="d0::19", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth5"

# PCI device 0x8086:0x10fb (ixgbe)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="80::08", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth6"

# PCI device 0x8086:0x10fb (ixgbe)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="80::09", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth7"

 

Unraid is still failing to assign an IP on the ::5c MAC (eth0) interface.

 

I wish I could get an IP so I could get you some diagnostics.

Edited March 16, 20233 yr by gizmo000

FWIW, the ASRock BIOS/splash screen seems to hang with "Update FRU System device..." before booting Unraid.  Not finding much on this error either...

11 minutes ago, gizmo000 said:

Unraid is still failing to assign an IP on the ::5c MAC (eth0) interface.

 

I wish I could get an IP so I could get you some diagnostics.

 

I spoke too soon ... after another reboot, the WebUI came up with the appropriate IP address.

 

Diagnostics are attached.

diagnostics-20230316-1649.zip