Hi,

I recently got some hp servers for free, and thought I'd use them for an unraid server. I used the unraid flasher to put it on a usb and plugged it into the internal usb port on my server. After it's done starting up, it says "IPv4 Address: Not Set IPv6 Address: Not Set". I'm unable to access the unraid server by any means, I've tried using http://proliant-2 (i set the name in the flash utility) and it won't connect. I'm using an emulex 10GB network card to connect to a tp link switch, which connects to another switch, and then to my modem/router combo. My other devices don't have issues with dhcp when connected in this system. I've attached a diagnostics file to help.

 

Thanks.proliant-2-diagnostics-20220913-1524.zip

ethtool says no link detected, but driver is loaded. Check cable, port, plug on server, switches, router, try other ports

 

RAID controllers are NOT recommended. Have you flashed it to IT mode (HBA)?

Ill try some different configs. The only thing I changed when flashing the boot media was the name. The RAID controller in my server acts as a PCIE sata card when the raid isn't set up (as far as i know).

I switched the ethernet connection from the emulex card to the onboard ethernet, and it gives me an ip that I can connect to. I'd really prefer if I could get the emulex card to work because the ports integrated on my server are only 1gbps.

23 minutes ago, trurl said:

driver is loaded

0d:00.0 Ethernet controller [0200]: Emulex Corporation OneConnect 10Gb NIC (be3) [19a2:0710] (rev 02)
	Subsystem: IBM PCIe2 2-port 10GbE SR Adapter for POWER [1014:03d0]
	Kernel driver in use: be2net
	Kernel modules: be2net

 

Is there something I'm missing? Because I don't understand.

i've tried every possible combination of ports with the 10gb card, and none of them give me an ip address. 

I think i've changed every variable I can, I've changed pci slots, changed network cards, turned of bond, set the ip manually, used a different usb port etc. Nothing has worked.

Sep 13 15:24:39 Proliant-2 kernel: be2net 0000:0d:00.0 eth4: Link is Down
Sep 13 15:24:39 Proliant-2 kernel: be2net 0000:0d:00.1 eth5: Link is Up

 

Log does show link up on one of the ports, note that you should set it as eth0 (Settings -> Network Settings -> Interface Rules then reboot) if you want to use that NIC as the main one to manage Unraid.

4 minutes ago, JorgeB said:

Settings -> Network Settings -> Interface Rules then reboot

Should i start it up with the ethernet connected to the on board ports, access the web ui, change the NIC port to eth0, power off, switch the ethernet cable to the NIC, and power it back on?

Yes, try that, post new diags if it doesn't work after changing eth5 to eth0

No dice. Still says not set.

tower-diagnostics-20220914-0245.zip

Sep 14 02:42:58 Tower kernel: be2net 0000:0d:00.0 eth0: Link is Down

 

No link now.

Everything works now. Thank you.