I have just installed a new Realtek RTL8125B 2.5gb network card in my system and i can see it under ifconfig

 

Quote

eth118: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether 3a:e0:4c:68:34:51  txqueuelen 1000  (Ethernet)
        RX packets 4696782640  bytes 5809434302172 (5.2 TiB)
        RX errors 0  dropped 5935  overruns 0  frame 0
        TX packets 2062238774  bytes 2767111769712 (2.5 TiB)
        TX errors 55  dropped 71 overruns 0  carrier 0  collisions 0
        device interrupt 75

 

However I'm struggling to make this the default eth0 because I'm Interface rules the mac address displayed above (3a:e0:4c:68:34:51) doesn't show up I'm the list.

 

 

This above is all that shows up, so I am at a loss about what to do from here. Any help is appreciated.

Edited November 24, 20241 yr by thatja

install the plugin driver and ask in the support topic there are know issues with realtek nics.

 

What exactly is the issues you are having? the nic dispaly under ip a / net link
lscpi -v make sure the driver is loading...

 

Edited November 24, 20241 yr by bmartino1

6 minutes ago, bmartino1 said:

install the plugin driver and ask in the support topic there are know issues with realtek nics.

 

What exactly is the issues you are having? the nic dispaly under ip a / net link make sure the driver is loading...

 

 

root@SubZero:~# lspci -nnk | grep -A 3 8125
44:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
        Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
        Kernel driver in use: r8125
        Kernel modules: r8169, r8125
7f:08.0 System peripheral [0880]: Intel Corporation Xeon E5/Core i7 QPI Link 0 [8086:3c80] (rev 07)
        Subsystem: Intel Corporation Device [8086:0000]
7f:09.0 System peripheral [0880]: Intel Corporation Xeon E5/Core i7 QPI Link 1 [8086:3c90] (rev 07)

 

AND

 

44:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
        Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
        Flags: bus master, fast devsel, latency 0, IRQ 75, NUMA node 1, IOMMU group 10
        I/O ports at cc00 [size=256]
        Memory at d3fe0000 (64-bit, non-prefetchable) [size=64K]
        Memory at d3ffc000 (64-bit, non-prefetchable) [size=16K]
        Expansion ROM at d3000000 [virtual] [disabled] [size=64K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
        Capabilities: [70] Express Endpoint, IntMsgNum 1
        Capabilities: [b0] MSI-X: Enable+ Count=32 Masked-
        Capabilities: [d0] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [148] Virtual Channel
        Capabilities: [168] Device Serial Number 01-00-00-00-68-4c-e0-00
        Capabilities: [178] Transaction Processing Hints
        Capabilities: [204] Latency Tolerance Reporting
        Capabilities: [20c] L1 PM Substates
        Capabilities: [21c] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?>
        Kernel driver in use: r8125
        Kernel modules: r8169, r8125

 

Its definitely loading the driver, it just doesn't show the MAC address under interface rules so I cannot make it eth0, it shows up under eth118 in the network settings. I am wanting to make this eth0 by default.

as said earlier use the plugin ther is a known issues with the kerneal driver that ships with unraid... 

13 minutes ago, bmartino1 said:

as said earlier use the plugin ther is a known issues with the kerneal driver that ships with unraid... 

 

I already had the plugin installed, this is the first thing i did when I installed the card.

Thank you for the clarifications.. Please post diag file...

What unraid version are you runing beta. Have you read through:

as you may need to restart emhttp or run other modprobe / eth commands...

if the thermal is showing the mac(which it appears) its a graphical bug in unraid try clear borowser cookie data.

would need diag to further torubleshooot

2 minutes ago, bmartino1 said:

Thank you for the clarifications.. Please post diag file...

What unraid version are you runing beta. Have you read through:

as you may need to restart emhttp or run other modprobe / eth commands...

if the thermal is showing the mac(which it appears) its a graphical bug in unraid try clear borowser cookie data.

would need diag to further torubleshooot

 

Thanks for the help I appreciate it. I am indeed running unraid 7 BETA, the latest version (4)

 

Here are diagnostics

subzero-diagnostics-20241124-2030.zip

Thank you reviewing the diag file now seeing if there is anything I can suggest / find:

I do see a weird go file:
#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp 
loadkeys /usr/share/kbd/keymaps/i386/qwerty/uk.map.gz

*most likely dealing with encryption...

and we need to add info here to use the 2.5
per the forum post add:
 

ethtool -s eth0 autoneg on advertise 0x80000000002f

Change and using the correct eth# for your interface.

 

Some weirdness in name change:

 

The logs provide useful insights into the issue:

The r8125 Realtek driver is loading correctly, and the device is recognized with its MAC address (3a:e0:4c:68:34:51).

The interface was initially named eth0 but was later renamed to eth118.

The MAC address (3a:e0:4c:68:34:51) is present and being initialized properly in the kernel log.

Potential Cause:

The renaming of the network interface (eth0 to eth118) is likely caused by a udev rule or a configuration issue in the Unraid beta that determines how interfaces are named. This is why it doesn't appear as eth0 on the web UI.

we can try a user script at first array start to fix with a udev rule and some /dev flush stuff.

 

Recommended Steps to Resolve:

Check Network Rules File:

Navigate to /etc/udev/rules.d/ and check for any 70-persistent-net.rules or similar file.

Look for rules corresponding to eth118 and the MAC address 3a:e0:4c:68:34:51.

Force Rename Interface:

You can manually edit or create a udev rule to rename eth118 back to eth0. Example

sudo nano /etc/udev/rules.d/70-persistent-net.rules

*Udev is hard to keep and use in unraid.

Example udev rule to stop name chaingin:
 

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="3a:e0:4c:68:34:51", NAME="eth0"

Apply Changes:

Run the following to reload the udev rules and restart the network:

sudo udevadm control --reload
sudo udevadm trigger
sudo /etc/rc.d/rc.inet1 restart

Validate:

Check if eth0 is now visible in the web UI. Use ifconfig or ip a to confirm the interface name.

user script at first boot:

#!/bin/bash
# Script to rename network interface to eth0 and apply changes

# Define variables
RULES_FILE="/etc/udev/rules.d/70-persistent-net.rules"
MAC_ADDRESS="3a:e0:4c:68:34:51"

# Create the udev rule
echo "Creating udev rule to rename eth118 to eth0..."
echo "SUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"$MAC_ADDRESS\", NAME=\"eth0\"" > "$RULES_FILE"

# Flush old network settings
echo "Flushing network settings..."
ip link set eth118 down
ip addr flush dev eth118
ip route flush dev eth118

# Reload udev rules
echo "Reloading udev rules..."
udevadm control --reload
udevadm trigger

# Bring eth0 up
echo "Bringing eth0 up..."
ip link set eth0 up

# Confirmation message
echo "Interface renaming and setup complete. Check the configuration with 'ip a' or the web UI."

review:

 

Edited November 24, 20241 yr by bmartino1
fix script order of operations to remove a bad interface...

Thanks for this, I will give this ago in a little while and report back! I really appreciate the help.

The post above did the trick and now eth0 is correctly showing and using the realtek pcie card

 

However, during my troubleshooting I've uncovered a somewhat alarming issue, I lot access to the server over LAN so went to use the built in GUI mode on the actual server it's self however, when doing this it just shown a blank screen with a _ in the top left, this also made the entire unraid server inaccessible on all devices over LAN (tested when I restored networking) the only way I could fix the networking was safe mode with gui (normal non gui mode functions normal).

 

I'm wondering from the diags i posted previously, can you see why this would be happening? I've rebooted into GUI mode 5 times and all 5 times the GUI wouldn't boot and it just shows the blank screen with an underscore symbol on the top left and the server isn't accessible at all over LAN.

 

I would really like to get this fixed

 

Thanks!

Edited November 25, 20241 yr by thatja

would need new diags. How are you running the script? did you add that to the go file, if so that can be what is causing the break. I don't like to add things to the go file as i use the user script plugin and start at first array option for a corn to run the script.

What your describing, this can be any number of issues from misconfiguration to plugin issues to other hardware problems. the fact that safe mode works tell me that this may be a plugin issue.

Became your go file had loadkeys /usr/share/kbd/keymaps/i386/qwerty/uk.map.gz

My bet is a issue with encryption at mount of disk. 

Here are the diagnostics, i cannot get into normal UNRAID GUI mode, only safe mode works. 

 

subzero-diagnostics-20241126-0857.zip

uninstall the driver plugin and try again if safe mode works and others do not this its the plugin.

Curiosity
why boot to unraid gui mode? did you try standard terminal mode no gui?

if using the script eth0 may already be in use yo may need to use a different eth# 
as you have a picture with alot of nics... and 0,1,2,3,4,5 are in use in the web ui....

Edited November 27, 20241 yr by bmartino1

32 minutes ago, bmartino1 said:

uninstall the driver plugin and try again if safe mode works and others do not this its the plugin.

Curiosity
why boot to unraid gui mode? did you try standard terminal mode no gui?

if using the script eth0 may already be in use yo may need to use a different eth# 
as you have a picture with alot of nics... and 0,1,2,3,4,5 are in use in the web ui....

 

Which driver plugin?

since we were workign on the realtek i would start there its honestly trial and error remove until you find the culprit.