I upgraded my whitebox unraid server today. I swapped out the RAM, CPU and Motherboard and left everything else the same. Before the swap, the server had been working fine for 3 years up until today a couple hours ago before i started swapping hardware.

The new parts are:

Motherboard: Aorus Z690 Elite AX DDR4

RAM: Corsair Vengance 2x32GB 4000Mhz

CPU: Intel Core i5 12600K

 

Unfortunately after that i couldn't access the server over the network anymore. When i booted it up with a monitor attached it said: 
"error: failed to connect to the hypervisor"

And the IP address it said was unresponsive.

 

Booting in safe mode did not output the same error but the IP address was still unresponsive.

Because i had set the IP Address as static in my router, i have deleted that assignment in my router and i deleted network.cfg from the USB stick to reset the network settings to default and get a DHCP assigned IP address, but in both normal and safe mode it now says:

 

"IPv4 address: not set"

 

I have attached a diagnostics file that i have just ran from the server itself by attaching a monitor and keyboard.

 

tower-diagnostics-20180101-1803.zip

 

Thank you very much in advance for any replies.

 

Edit: also when i try to boot the server with the GUI option, both normal GUI and safe mode GUI results in a black screen. No GUI appears.

 

Edited January 26, 20224 yr by YourNightmar3

I just realized i attached the wrong diagnostics file because the date on the file is wrong. I have just edited my original post to actually have the right diagnostics file that i created yesterday.

 

Edit: I may have found the problem? Some googling told me more people are having issues with onboard NIC's for 12th gen intel. I checked the old diagnostics before the hardware swap and in ifconfig.txt i can see eth0 and eth1 because that board had two onboard ethernet ports.

In the new diagnostics however i don't see any eth listed in the same file. I guess i'll need to get a PCI-e NIC. Can someone who knows how to read the diagnostics file better than me confirm this?

 

However this does not explain the "error: failed to connect to the hypervisor" error.

I did some googling on that as well and people are saying the VM Backup plugin can cause this error. I do have that plugin installed, and that would explain why it doesn't occur in safe mode, but i've always had this plugin also before the hardware swap, so that is kind of strange.

Edited January 26, 20224 yr by YourNightmar3

You probably need a later Unraid release (e.g. 6.10.0 rc2) to have a driver for the NIC in that board.

Thanks for the asnwer. I'll gladly update to try that solution. I did some googling but i could not find how to update unRAID from the command line. How can i do this?

Edited January 26, 20224 yr by YourNightmar3

Download the ZIP for the release and then extract all the bz* type files for the release overwriting the ones on the flash drive.

My previous reply was silly, of course i can't update from commandline without active internet connection

 

Anyway i didn't like the risk of updating an otherwise perfectly stable system so i went out and bought a USB Ethernet adapter that boasted Linux kernel 2.6/3.x compatability and it's now working great. For anyone else reading this, i got the UGREEN USB 3.0 Ethernet Adapter Gigabit. In the Amazon description it states "Wide compatability: Windows 10 / 8.1 / 8/7 / Vista / XP, Mac OS 10.6 amd up , Linux kernel 3, x / 2.6"

 

It only had to plug it in and it works. I may look for a better solution like a network card, i might want to play around with 10gig networking, but for now this was a great cheap solution.

 

My server is booting fine now. I still got this "error: failed to connect to the hypervisor" message but the webui and everything works great!

Edited January 27, 20224 yr by YourNightmar3

Okay, do NOT use the same USB ethernet adapter that i used. It was causing problems for me and occasionally would just stop working completely. I thought my server was crashing but it was just the usb ethernet adapter. I got a PCI-E 1Gbe NIC that is listed as compatible on the unRAID wiki and it works fine now. All problems solved.

 

https://wiki.unraid.net/Hardware_Compatibility#Network_Controllers