Hi all,

thanks to all who are going to read this and have helpful comments. But a disclaimer first: I am a total amateur with regards to servers and homelabs and are slowly starting to get my feet wet. 

After a few months of Unraid running fairly okay, we had a power outage and Unraid was not shutdown gracefully as far as I can tell. Upon reboot, I could not reach the server in my network. In order to figure out what was going on, I did the following:

 

1. I hooked up a screen, keyboard and mouse, rebooted and started the GUI via the slim command. Firefox did not show the usual GUI but an error that localhost could not be loaded.

2. Rebooted into safe mode with GUI, which booted up. I saved a syslog which is attached. 

3. I rebooted again, no safe mode, into the terminal, started the GUI via slim and saved a diagnostics file (syslog from that is also attached).

 

From what I can tell, there might be an issue with SSH, but I am not sure. I disabled the use of SSH in access management using the safe mode GUI, rebooted but no success.

 

Has anybody seen this issue, or can tell what is going on based on the description of sys logs?

 

Thank you so much for your help!

 

PS: I have the following plugins installed (not sure how to update them in the terminal in case those are issues)

 

community.applications.plg - 2025.01.28  (Up to date)
fix.common.problems.plg - 2025.03.12  (Up to date)
gpustat.plg - 2025.03.28  (Update available: 2025.04.27)
radeontop.plg - 2023.02.22  (Up to date)
tailscale.plg - 2025.04.17  (Update available: 2025.05.08)
unraid.patch.plg - 2025.01.31a  (Up to date)
unRAIDServer.plg - 7.0.1
user.scripts.plg - 2024.12.19  (Up to date)

syslog-20250510-2134-safe-mode-GUI.zip logs-20250510-1818-normal-boot-no-localhost.zip

Can you try again and get us diagnostics instead of only syslog?

Hi trurl,

 

Thanks for your quick reply. The diagnostics are attached for both cases.

 

I hope this helps.

blipa-diagnostics-20250510-1818-normal-boot-no-localhost.zip blipa-diagnostics-20250511-1116-safe-mode-GUI.zip

07:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
	DeviceName: Realtek RTL8125BG LAN
	Subsystem: ASUSTeK Computer Inc. Device [1043:87d7]
	Kernel driver in use: r8169
	Kernel modules: r8169

You might try installing this plugin:

 

Also

Model name:                           AMD Ryzen 5 8600G w/ Radeon 760M Graphics

 

Hello,

thanks for your help. I installed the RTL8125 driver app, updated the BIOS and disabled c-state in the BIOS. 

I now lost network connection completely. I could see the Unraid server in my network before, but cannot anymore.

I attached a new diagnostics file.

 

In the syslog, I can see that in the sshd line the server listing is now 0.0.0.0 port 22, while it was 192.168.1.79 port 22.

 

Thanks for your help.

blipa-diagnostics-20250511-1533.zip

Edited May 11, 20251 yr by MCheiron13

Maybe the plugin made things worse.

ethtool says

	Link detected: no

lspci says its still using 8169 driver

 

Boot in SAFE mode and see if you get an IP address

Using ifconfig eth0, I am receiving an error: fetching interface information: Device not found

In system drivers under Type net/ethernet/realtek, r8169 is now disabled (on the right it says blacklist r8169). Not sure if I can enable that again. Should I try and enable that and if so, how?

In system drivers there is another disabled driver: cdc_ether

Delete /config/modprobe.d/r8169.conf from the flash drive and reboot, then post new diags.

Here you go (one for safemode GUI, the other one normal booting into GUI). Thanks for your help. 

 

When booting into safe mode with GUI, I have access to localhost on the server screen and can install apps. I can see the server in my local network and access the flash drive (which I made visible for faster troubleshooting purposes).

When booting normally into the GUI, I cannot see localhost on the server screen. Surprisingly, I can see the server in my local network and get access to the flash drive.

 

I appreciate all your help.

blipa-diagnostics-20250512-2026-normalGUI.zip blipa-diagnostics-20250512-2019-safemodeGUI.zip

6 hours ago, MCheiron13 said:

When booting normally into the GUI, I cannot see localhost on the server screen.

Uninstall the Realtek plugin, if you see it in the list, install, then uninstall, because it's still installing its driver in normal boot, and that's the problem.

16 hours ago, JorgeB said:

Uninstall the Realtek plugin, if you see it in the list, install, then uninstall, because it's still installing its driver in normal boot, and that's the problem.

I did that following the steps in parentheses, there might be an easier way but this is what I did.

 

(for anyone who doesn't know how to without internet access: 1. boot to safemode with GUI, 2. open Plugins tab; 3. open Install Plugins tab, 4. browse to config/plugins, 5. find plugin, 6. install, 7. in my case, then uninstall).

 

I now started the server and tried to connect. I collected diagnostic data ending in the time stamps listed below for each reboot and after what I did described below:

 

1314: after safe mode GUI after Realtek plugin uninstall, then reboot

1324: after safe mode GUI: access via local network confirmed, then reboot

1332: after normal reboot: able to connect to server locally and login in remotely from another networked PC, waited, started array, lost connection. On screen connected to server I saw several messages from syslog: nginx....[emerg]...... bind() to ..(some IP that is not local).. failed (98: already in use).

1931: after reboot normal: short time able to login remotely, but after around 20 sec connection lost and nginx error appears locally again..

 

 

blipa-diagnostics-20250513-1931.zip blipa-diagnostics-20250513-1314.zip blipa-diagnostics-20250513-1324.zip blipa-diagnostics-20250513-1332.zip

The driver is no longer installed, but there are other issues:

 

May 13 19:29:27 BlipA nginx: 2025/05/13 19:29:25 [emerg] 6898#6898: bind() to 100.118.195.70:443 failed (98: Address already in use)
May 13 19:29:27 BlipA nginx: 2025/05/13 19:29:25 [emerg] 6898#6898: bind() to [fd7a:115c:a1e0::2901:c346]:443 failed (98: Address already in use)
May 13 19:29:28 BlipA nginx: 2025/05/13 19:29:25 [emerg] 6898#6898: still could not bind()

 

IS this a new or old install?

4 hours ago, JorgeB said:

The driver is no longer installed, but there are other issues:

 

May 13 19:29:27 BlipA nginx: 2025/05/13 19:29:25 [emerg] 6898#6898: bind() to 100.118.195.70:443 failed (98: Address already in use)
May 13 19:29:27 BlipA nginx: 2025/05/13 19:29:25 [emerg] 6898#6898: bind() to [fd7a:115c:a1e0::2901:c346]:443 failed (98: Address already in use)
May 13 19:29:28 BlipA nginx: 2025/05/13 19:29:25 [emerg] 6898#6898: still could not bind()

 

IS this a new or old install?

This is an old install that worked well until an unexpected crash due to a power outage and the UPS apparently not communicating correctly with the server. Version is 7.0.1. I haven’t updated yet. 

You can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.