May 15, 20242 yr I own an unraid server with a w680 board and an intel 13900 in it. It works good but I recently got a new to me dell R7525 and wanted to migrate to that. I set up a new thumb drive to test unraid out on the dell but can not get the gui to load. If I use it headless it will load up to the log in and let me log in but that is it. I can not get to the webgui. I feel like I set the bios properly but there may be something in bios I am overlooking. Any help would be appreciated!
May 15, 20242 yr Community Expert https://i.dell.com/sites/csdocuments/Product_Docs/en/PowerEdge-R7525-Spec-Sheet.pdf make sure you are pluged into a USB 2.0 port. Also make sure your bios boot settings are correct to boot to the USB drive only. Sometimes you have to enable boot support on these rack devices.
May 15, 20242 yr Author I went through and tried it on all 3 usb ports on the machine. It is doing the samething on all of them. I believe I got a necessary stuff in BIOS set as well but I could be wrong. It boots to the drive. I can select to boot with gui. It loads like normal but when it goes to bring up the gui the screen just goes black. No cursor in the top left corner or nothing. Just a black screen. If I load without gui it seems to fully load. I can log into root with no password and that it. I can not see it on my network. I can not ping it nothing.
May 15, 20242 yr Community Expert is htis a modified usb or cary over. per first post i thought you had a trail verion. So you are getting the grub screen. why gui mode? boot headless and get terminal you should get to a black screen with white text. You should get a ip address to use the web UI. login with root user in machine and type diagnostic then post the diagnostic here. If getting to grub run mem test.
May 15, 20242 yr Author I apologize, let me explain again. I currently have a pro license on a machine working great. Before I try to migrate to the dell server I wanted to try the unraid experience on it. I did set up a new drive with a trial version to test it out. Hope that makes sense now. I was trying to load the os with a gui to see if that would work better than headless is all. I don't care either way. I access my current server through the webgui. When I set up the new drive and loaded the os headless, it loads completely and lets me log in. It does not assign it an ip address to reach it on a webgui. I tried setting it up with a static ip and when it loads, the console shows the ipv4 address I set, but it is unreachable. Here is a diagnostics log! Thanks for the help! r7525-diagnostics-20240514-1239.zip
May 15, 20242 yr Community Expert Thank you For that information and clarification. Since you are able to boot headless mode. This tells me that the unraid kernel is missing linux drivers for your nic card. Please login to unraid and in the terminal run lspci netstat -i you should still have a LO loop back driver. note that you are missing a eth0 interface is is due to dell pripertary hardware. A plugin may be available to fix this. Thank you for your diagnostic file this helps us help you with what it reports: Per you diagnostic file you have multiple nics registered but they are all down: lo UNKNOWN 127.0.0.1/8 ::1/128 tunl0@NONE DOWN eth0 DOWN eth1 DOWN eth2 DOWN eth3 DOWN eth4 DOWN eth5 DOWN bond0 DOWN br0 DOWN Run command ifconfig eth0 up You appear to have Broadcom network nics: 63:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f] DeviceName: Integrated NIC 1 Port 1 Subsystem: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:2018] Kernel driver in use: tg3 Kernel modules: tg3 63:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f] DeviceName: Integrated NIC 1 Port 2 Subsystem: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:2018] Kernel driver in use: tg3 Kernel modules: tg3 64:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f] DeviceName: Integrated NIC 1 Port 3 Subsystem: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:2018] Kernel driver in use: tg3 Kernel modules: tg3 64:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f] DeviceName: Integrated NIC 1 Port 4 Subsystem: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:2018] Kernel driver in use: tg3 Kernel modules: tg3 and per syslog it appears that the drivers are loading form kernel: May 14 12:38:34 R7525 kernel: tg3 0000:63:00.0 eth0: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address b0:26:28:e8:ae:3c May 14 12:38:34 R7525 kernel: tg3 0000:63:00.0 eth0: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) May 14 12:38:34 R7525 kernel: tg3 0000:63:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1] May 14 12:38:34 R7525 kernel: tg3 0000:63:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit] May 14 12:38:34 R7525 kernel: tg3 0000:63:00.1 eth1: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address b0:26:28:e8:ae:3d May 14 12:38:34 R7525 kernel: tg3 0000:63:00.1 eth1: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) Please check you cable and confirm its pluged in and that you see lights. Per syslog dhcp was asked but non received: rc.inet1: ip link add name bond0 type bond mode 1 miimon 100 May 14 12:38:35 R7525 rc.inet1: ip link set eth0 up May 14 12:38:35 R7525 rc.inet1: ip link set eth0 master bond0 down type bond_slave May 14 12:38:35 R7525 kernel: bond0: (slave eth0): Enslaving as a backup interface with a down link May 14 12:38:35 R7525 rc.inet1: ip link set eth1 up May 14 12:38:35 R7525 rc.inet1: ip link set eth1 master bond0 down type bond_slave May 14 12:38:36 R7525 kernel: bond0: (slave eth1): Enslaving as a backup interface with a down link May 14 12:38:36 R7525 rc.inet1: ip link set eth2 up May 14 12:38:36 R7525 rc.inet1: ip link set eth2 master bond0 down type bond_slave May 14 12:38:36 R7525 kernel: bond0: (slave eth2): Enslaving as a backup interface with a down link May 14 12:38:36 R7525 rc.inet1: ip link set eth3 up May 14 12:38:36 R7525 rc.inet1: ip link set eth3 master bond0 down type bond_slave May 14 12:38:36 R7525 kernel: bond0: (slave eth3): Enslaving as a backup interface with a down link May 14 12:38:36 R7525 rc.inet1: ip link set name bond0 type bond primary eth0 May 14 12:38:36 R7525 rc.inet1: ip link add name br0 type bridge stp_state 0 forward_delay 0 May 14 12:38:36 R7525 kernel: bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. May 14 12:38:37 R7525 rc.inet1: ip link set bond0 down May 14 12:38:37 R7525 rc.inet1: ip -4 addr flush dev bond0 May 14 12:38:37 R7525 rc.inet1: ip link set bond0 master br0 up May 14 12:38:37 R7525 kernel: br0: port 1(bond0) entered blocking state May 14 12:38:37 R7525 kernel: br0: port 1(bond0) entered disabled state May 14 12:38:37 R7525 kernel: device bond0 entered promiscuous mode May 14 12:38:37 R7525 rc.inet1: ip link set br0 up May 14 12:38:48 R7525 rc.inet1: interface br0 is DOWN, polling DHCP ipv4 server in background May 14 12:38:48 R7525 rc.inet1: dhcpcd -b -q -n -p -t 10 -h R7525 -4 br0 May 14 12:38:48 R7525 dhcpcd[2356]: dhcpcd-9.4.1 starting May 14 12:38:48 R7525 dhcpcd[2359]: DUID 00:04:4c:4c:45:44:00:4e:42:10:80:38:c6:c0:4f:4b:44:33 May 14 12:38:48 R7525 kernel: 8021q: 802.1Q VLAN Support v1.8 May 14 12:38:48 R7525 kernel: 8021q: adding VLAN 0 to HW filter on device bond0 May 14 12:38:48 R7525 dhcpcd[2359]: br0: waiting for carrier you may need to delete the netwrok config file in the config folder on the flash driver to move you previous usb over to redo netwrok configurations. bond0 apears to be breaking per ethtool: Settings for bond0: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: off Port: Other PHYAD: 0 Transceiver: internal Link detected: no driver: bonding version: 6.1.79-Unraid firmware-version: 2 expansion-rom-version: bus-info: supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no -------------------------------- Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: on Port: Twisted Pair PHYAD: 1 Transceiver: internal MDI-X: Unknown Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) drv probe link timer ifdown ifup rx_err tx_err Link detected: no driver: tg3 version: 6.1.79-Unraid firmware-version: FFV22.71.3 bc 5720-v1.39 expansion-rom-version: bus-info: 0000:63:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no -------------------------------- Settings for eth1: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: on Port: Twisted Pair PHYAD: 2 Transceiver: internal MDI-X: Unknown Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) drv probe link timer ifdown ifup rx_err tx_err Link detected: no driver: tg3 version: 6.1.79-Unraid firmware-version: FFV22.71.3 bc 5720-v1.39 expansion-rom-version: bus-info: 0000:63:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no -------------------------------- Settings for eth2: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: on Port: Twisted Pair PHYAD: 1 Transceiver: internal MDI-X: Unknown Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) drv probe link timer ifdown ifup rx_err tx_err Link detected: no driver: tg3 version: 6.1.79-Unraid firmware-version: FFV22.71.3 bc 5720-v1.39 expansion-rom-version: bus-info: 0000:64:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no -------------------------------- Settings for eth3: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: on Port: Twisted Pair PHYAD: 2 Transceiver: internal MDI-X: Unknown Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) drv probe link timer ifdown ifup rx_err tx_err Link detected: no driver: tg3 version: 6.1.79-Unraid firmware-version: FFV22.71.3 bc 5720-v1.39 expansion-rom-version: bus-info: 0000:64:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no -------------------------------- Settings for eth4: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: on Port: Twisted Pair PHYAD: 1 Transceiver: internal MDI-X: Unknown Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) drv probe link timer ifdown ifup rx_err tx_err Link detected: no driver: tg3 version: 6.1.79-Unraid firmware-version: FFV22.71.3 bc 5720-v1.39 expansion-rom-version: bus-info: 0000:e1:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no -------------------------------- Settings for eth5: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: on Port: Twisted Pair PHYAD: 2 Transceiver: internal MDI-X: Unknown Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) drv probe link timer ifdown ifup rx_err tx_err Link detected: no driver: tg3 version: 6.1.79-Unraid firmware-version: FFV22.71.3 bc 5720-v1.39 expansion-rom-version: bus-info: 0000:e1:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no -------------------------------- and the defualt network config done't have bond0 enabled by default: Per diag network config: # Generated network settings USE_DHCP="yes" IPADDR= NETMASK= GATEWAY= BONDING="yes" BRIDGING="yes" To potentia lget it up and wokring as it appears that eth0 is down you will need to bring the interfaces up and or delete the network config to have unraid regenerate it.
May 16, 20242 yr Author I figured that was the case! I did try to delete the config file and give it a go but it still is not assigning an ip address. I am unsure on how I can try to get eth0 up? Can you point me to some info on that please?
May 16, 20242 yr Community Expert Solution Terminal commands: ip a netstat -i ifconfig ifconfig bond0 down any errors? ifconfig br0 down any errors? ifconfig eth0 down any errors? and then ifconfig eth0 up ifconfig br0 up
May 16, 20242 yr Author It worked! It finally assigned an ip and I am currently in the webgui! Thank you for you time and help I really appreciate it!
May 16, 20242 yr Community Expert Glad that command worked for you. you may need to use user script plugin to run these commands. Hopefully unraid settings will get applied and a reboot won't kill networking. that line of nics has a known linux driver support issues. Thx dell https://askubuntu.com/questions/1273413/broadcom-bcm5720-not-working-in-ubuntu-20-04-server sudo modprobe tg3 && dmesg | grep tg3 modprobe -r broadcom modprobe -r tg3 modprobe broadcom modprobe tg3 what ever commands you used above may need to be in a cron script custom cron set to @reboot Edited May 16, 20242 yr by bmartino1
May 16, 20242 yr Author I will be messing with it for sure to see if it retains or not through reboot. I do plan on getting a 10gb ocp 3.0 card for this thing. I have a choice of broadcom or mellanox. Any suggestions?
May 16, 20242 yr Community Expert melnox 100% you may need to install the melonx firmware tool to use Broadcom are ok.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.