Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

brezen25

Members
  • Joined

  • Last visited

  1. I have solved the issue. It was the IPMI generating that weird MAC address (it's not the IPMI LAN port, as I can see that MAC and it does not match what Unraid was showing). I disabled IPMI, flashed Unraid onto my USB drive one last time, and it came right up with the 2.5G NIC as eth0. It is interestingly still coming up with a bond by default, but it works fine with it disabled. Also the trial key activated right away without issue.
  2. Of course I decended directly into another issue. I'm trying to activate my trial key and I get an 'Error. Something went wrong'. The syslog is full of these: Dec 13 19:30:21 JJUNRAID emhttpd: error: get_key_info, 600: Invalid argument (22): stat: /boot/config/Trial.key I've confirmed that file is in the correct place.
  3. I've made significant headway and have a connection now, but I'm still wondering why and if this config is going to not cause any problems down the line. It turns out that the eth0 interface is some unknown interface. The MAC address of it does not correspond to either 2.5G port or the IPMI port. This is what lshw -C network outputs: resources: irq:17 memory:8ca00000-8cafffff memory:8cb00000-8cb03fff *-network DISABLED description: Ethernet interface physical id: 2 bus info: usb@1:10.3 logical name: eth0 serial: 2e:bd:23:3d:85:8b capabilities: ethernet physical configuration: autonegotiation=off broadcast=yes driver=cdc_ether driverversion=6.1.118-Unraid duplex=half firmware=CDC Ethernet Device link=no multicast=yes port=twisted pair (no I do not have any USB NICs) So what I have done is put eth0 into a down state, and brought up eth2, which is one of the 2.5G interfaces (the other is eth1). I set the correct IP figures on that interface and enabled bridging (whose interface is now br2). I can ping out and connect in. My router shows the device. ifconfig now: br2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.10 netmask 255.255.255.0 broadcast 0.0.0.0 ether 10:7c:61:b4:8e:41 txqueuelen 1000 (Ethernet) RX packets 150 bytes 27098 (26.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 55 bytes 32328 (31.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 10:7c:61:b4:8e:41 txqueuelen 1000 (Ethernet) RX packets 320 bytes 58368 (57.0 KiB) RX errors 0 dropped 2 overruns 0 frame 0 TX packets 175 bytes 83483 (81.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0x8ca00000-8cafffff lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 3048 bytes 3632559 (3.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3048 bytes 3632559 (3.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vhost0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 02:03:e2:a2:85:9b txqueuelen 500 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ip a now: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 6: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq state DOWN group default qlen 1000 link/ether 2e:bd:23:3d:85:8b brd ff:ff:ff:ff:ff:ff 7: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 10:7c:61:b4:8e:40 brd ff:ff:ff:ff:ff:ff 8: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br2 state UP group default qlen 1000 link/ether 10:7c:61:b4:8e:41 brd ff:ff:ff:ff:ff:ff 12: vhost0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc fq state UP group default qlen 500 link/ether 02:03:e2:a2:85:9b brd ff:ff:ff:ff:ff:ff 13: br2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 10:7c:61:b4:8e:41 brd ff:ff:ff:ff:ff:ff inet 192.168.1.10/24 metric 1 scope global br2 valid_lft forever preferred_lft forever ip link show eth2: 8: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br2 state UP mode DEFAULT group default qlen 1000 link/ether 10:7c:61:b4:8e:41 brd ff:ff:ff:ff:ff:ff I'm not totally sure what vhost0 is; something to do with a VM network?
  4. I first disabled bridging. I confirmed via ifconfig the br0 interface was gone and the correct IP was listed under eth0. I still was unable to get any sort of connection. I reenabled bridging and ran the commands you posted. They all completed successfully but still no connection and eth0 is still in an unknown state. I've reflashed the USB drive multiple times before originally posting here, so I'm not sure what another try would accomplish. I am quite disappointed this is occuring. I believed it to be a simple flash USB, and boot up and everything would be good to go. I do appreciate you taking time to assist me, as no one else has.
  5. I have checked with 4 different cables with the same results. I have link lights. Something interesting I noticed was Unraid created a bond interface, bond0, even though I did not specify that. I assume it saw 2 NICs and just turned it on. I've since disabled one of the NICs for good and logged into the webgui via boot to gui and turned off bonding, only leaving eth0, br0, and lo as active interfaces. Output of the commands you suggested are below. ifconfig: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.10 netmask 255.255.255.0 broadcast 0.0.0.0 ether 2e:bd:23:3d:85:8b txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 152 bytes 10634 (10.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 2e:bd:23:3d:85:8b txqueuelen 1000 (Ethernet) RX packets 17 bytes 2924 (2.8 KiB) RX errors 0 dropped 13 overruns 0 frame 0 TX packets 256 bytes 21226 (20.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 2781 bytes 3634413 (3.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2781 bytes 3634413 (3.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ip a: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq master br0 state UNKNOWN group default qlen 1000 link/ether 2e:bd:23:3d:85:8b brd ff:ff:ff:ff:ff:ff 6: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 10:7c:61:b4:8e:40 brd ff:ff:ff:ff:ff:ff 9: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 2e:bd:23:3d:85:8b brd ff:ff:ff:ff:ff:ff inet 192.168.1.10/24 metric 1 scope global br0 valid_lft forever preferred_lft forever ip link show eth0: 5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq master br0 state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 2e:bd:23:3d:85:8b brd ff:ff:ff:ff:ff:ff cat /sys/class/net/eth0/carrier came back with 1.
  6. brezen25 joined the community
  7. Hello, This is my first time running Unraid. I finished building my system today and prepped my USB drive for Unraid, giving it a static IP. Unraid boots up fine; I get a login prompt locally. However, I cannot connect to the WebGUI or SSH, nor can I ping the server or see the client device on my router (Ubiquiti Dream Machine SE). I'm not super great with Linux, but I know enough to at least run ifconfig and see my interfaces. I show the br0 interface holding the static IP I set at USB setup. There is also an eth0 and eth1, neither of which have any address assigned to them. It is interesting that the MAC address for all these interfaces is the same. Note that this motherboard (ASUS WS PRO W680M-ACE SE) has dual NICs. I have tried booting with one or the other populated. I even tried populating both at once. I have also tried disabling one or the other in the BIOS to no effect. I have made sure UEFI network stack is on (it doesn't work whether this is on or off), the NICs are enabled in the BIOS. I also booted Unraid into GUI mode locally, and it is not able to ping out nor access anything external. Any help would be greatly appreciated. jjunraid-diagnostics-20241212-2216.zip

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.