Hi,

 

I upgraded from 6.12.13 to 6.12.14 and now cannot connect to my unraid server ui. I used the plugin to check that everything was up to date before upgrading.

Things I've tried/notes:

The machine starts and I can login via the CLI.

Starting in safe mode with the GUI hangs before the GUI is reached.

Restored my flash back up to a new USB drive (on version 6.12.13). The gui still does not load, but in safe mode with the GUI I at least reach the browser.

 

Not sure if this complicates thing but I have moved since running the update and now rather than the IP being 10.0.0.2 fixed, it is set by DHCP to 192.168.1.113.

 

Any help appreaciated.

 

Thanks

 

tower-diagnostics-20241215-0617.zip

Edited December 15, 20241 yr by ollysharp
Added diagnostics

Please post the diagnostics.
 

I've attached them to the original post.

 

Thanks.

Flash drive is missing some files, including the go file, suggest recreating the flash drive and restore the files you have from the config folder, but likely will still need to reconfigure some things.

Thanks I'll give that a shot. Out of interest where could you see that in the diagnostics file?

52 minutes ago, ollysharp said:

Out of interest where could you see that in the diagnostics file?

By looking to see what files are in the ‘config’ folder in the diagnostics.

This diagnostic file is from a fresh restore from my flash backup from Unraid Connect. How can files be missing? Doesn't this make the back up system useless?

 

I've attached the diagnostics file from original drive which fails to load the UI after the update. Does this show any issues?

tower-diagnostics-20241220-0807.zip

Edited December 20, 20241 yr by ollysharp

Those have the go file.

I've been trying a few things and some more info:

 

 - If I create a fresh flash drive with 6.12.13 or 6.12.14 it appears to work fine

 - If I create a fresh flash drive with 6.12.14 and copy my old config folder over I cannot access the GUI in any way. When I log in to the cli I see the following error:

r8168 0000:2:00.0 eth0: NETDEV WATCHDOG CPU: 6: transmit queue timed out 6272ms

 - If I create a fresh flash drive with 6.12.13 and copy my old config folder over it seems to work like normal. I have done this probably three times, the first two it did not work but third time it did... very confusing.

9 hours ago, ollysharp said:

 - If I create a fresh flash drive with 6.12.14 and copy my old config folder over I cannot access the GUI in any way. When I log in to the cli I see the following error:

r8168 0000:2:00.0 eth0: NETDEV WATCHDOG CPU: 6: transmit queue timed out 6272ms

Remove the Realtek driver, it's a known issue, see the release notes.

I don't have any realtek driver plugins installed, is that what you mean? The release notes only mention the plugin for the driver, nothing else that I can see: https://docs.unraid.net/unraid-os/release-notes/6.12.14/

 

EDIT: Also, not sure if this is known, but it seems like if your licence is tied to a USB drive which is not being used as the boot drive, the licence check will pass as long as the drive with the licence is plugged into the machine as well.

Edited December 21, 20241 yr by ollysharp

2 hours ago, ollysharp said:

I don't have any realtek driver plugins installed

I'm afraid that you do, it's visible in the diags, and it's blacklisting the stock driver, if it's not appearing under plugins, you can install the driver using the GUI mode, and then uninstalled, that will revert to the stock one.

2 hours ago, ollysharp said:

EDIT: Also, not sure if this is known, but it seems like if your licence is tied to a USB drive which is not being used as the boot drive, the licence check will pass as long as the drive with the licence is plugged into the machine as well.

That statement is strictly speaking true, but if the drive that contains the licence key does not have the same release of the Unraid system files on it the boot will probably fail as some OS files are loaded from the licenced drive in the later stages of the boot process.  Also all user configuration settings are written to and loaded from the licenced drive.  As such little point in having two separate drives involved in booting.

On 12/21/2024 at 3:54 AM, JorgeB said:

Remove the Realtek driver, it's a known issue, see the release notes.

How do you do this from the CLI??

Edited January 5, 20251 yr by mwf369

You can boot into GUI mode and uninstall the plugin, then reboot.

2 hours ago, JorgeB said:

You can boot into GUI mode and uninstall the plugin, then reboot.

Well, that's the issue. The GUI won't load.

Using the GUI boot mode? That is done locally: