Good evening fellow Unraid users and future magistrates.

I've been an Unraid user for about a week and I've been absolutely thrilled with it so far.

 

Last night I finally finished setting everything up and noticed there was a software update. I performed the update and after the reboot I wasn't able to connect to Unraid. 

I connected a monitor and keyboard, restarted the server, and I chose to boot without a GUI.

I was presented with a login prompt and was able to log in successfully. however, I still couldn't connect to the server remotely. I had previously assigned a static IP address, so I checked it with ifconfig. Everything looked fine but I wasn't able to connect remotely. 

I rebooted and selected boot with GUI. 

This time everything appears to start normally (all the scrolling text) but when it gets to the point where the GUI should come up, it just hangs at a black screen.

I also tried booting in safe mode and there was no change.

 

I sent an email to Unraid support this morning and they asked me to run the diagnostics program and share the zip file which I've attached. I'd be eternally grateful if someone was able to assist me in resolving this. Unfortunately, I'm too new with Unraid to even know where to start.

 

Thanks!

dayserver-diagnostics-20210304-1457.zip

Have you tried the other ethernet port?

Thanks for your reply. 

 

No, I haven't.

I built the server using a Gigabyte Z490m Gaming X motherboard. 

I couldn't get the onboard network card to work with Unraid (I'm assuming they don't have a driver for it yet?) so I installed

a PCI card that works. 

ethtool is saying no ethernet connection. Maybe the one you are using doesn't work on the update, or maybe you have some other problem such as cable or port somewhere.

Ok, thanks. 

Is there a supported hardware list for network cards I could look at while considering a purchase? 

 

Better yet, is there a way to revert back to v6.8.3? 

Can I reflash the USB stick somehow without losing all the work I've done? 

 

Have you actually tried plugging the Ethernet cable into the onboard NIC?    It would not have worked with 6.8.3 which did not have a driver for it but 6.9.0 release does have the driver so it is likely that is the card that unRaid is currently trying to use.   UnRaid will always use the NIC that is configured as eth0 for accessing the GUI.  It is possible from the GUI to change which card is treated as eth0 if you want to force a specific card to be used as eth0.

Yes, I did try using the onboard NIC. I also removed the PCI NIC and tried again.

I've confirmed its enabled in the BIOS. Still no change. 

Can I force the onboard NIC to be eth0 from the command line? 

Edited March 5, 20215 yr by Daxton

You can boot using GUI mode, then go to settings- network settings- interface rules 

JorgeB, 

I can't boot into GUI mode. 

You can try resetting network config buy deleting network.cfg and network-rules.cfg, then reboot.

Thank's everyone for your help this far.

I've made a little bit of progress but I'm still having some issues.

 

I deleted with network.cfg and network-rules.cfg files and rebooted.

I started the server without GUI and used ifconfig to check the IP address. I was able to log into the server remotely using this IP address. 👍 (However, if I start the server with GUI mode, the GUI still won't run. It's just stuck on a black screen.)

 

I stopped the VM and Docker services and assigned a static IP to eth0:

 

Interface description:

MAC address:                         18:C0:4D:28:EB:8D

Enable bonding:                      No

Enable bridging:                      Yes

Bridging members of br0:       eth0

Network protocol:                   IPv4 only

IPv4 address assignment:       Static

IPv4 address:                         192.168.2.11

IPv4 default gateway:             192.168.2.1

IPv4 DNS server assignment:  Static

IPv4 DNS server:                    8.8.8.8

IPv4 DNS server 2:                 8.8.4.4

Desired MTU:                          1500

Enable VLANs:                        No

 

after applying the settings,  Here's what ifconfig spits out:

( I should mention that i've been playing with some Docker apps and an Ubuntu VM. At the moment all that's installed is Plex in a Docker conatiner )

 

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.11  netmask 255.255.255.0  broadcast 0.0.0.0
        ether 18:c0:4d:28:eb:8d  txqueuelen 1000  (Ethernet)
        RX packets 2570  bytes 791073 (772.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1662  bytes 916720 (895.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:d5:a9:82:6c  txqueuelen 0  (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

eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether 18:c0:4d:28:eb:8d  txqueuelen 1000  (Ethernet)
        RX packets 2648  bytes 846269 (826.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1920  bytes 940674 (918.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0x51200000-51220000  

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 1783  bytes 210837 (205.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1783  bytes 210837 (205.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:94:c9:f3  txqueuelen 1000  (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

wg0: flags=209<UP,POINTOPOINT,RUNNING,NOARP>  mtu 1420
        inet 10.253.0.1  netmask 255.255.255.255  destination 10.253.0.1
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        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 5  dropped 0 overruns 0  carrier 0  collisions 0

 

Is any of this an issue? Why is the assigned static IP address showing under br0 and not eth0?

Any clue why booting with GUI mode doesn't work?

12 hours ago, Daxton said:

Why is the assigned static IP address showing under br0 and not eth0?

Normal when bridging is enable.

 

12 hours ago, Daxton said:

Any clue why booting with GUI mode doesn't work?

Nope sorry, but it happens to other users, possibly hardware related.

If booting UEFI and GUI don't work together for you, try changing one or the other.