ljm42

It is very difficult to do back and forth support in a release thread, please start a new thread under General Support and provide diagnostics.zip from both versions. Thanks!

This is a bug fix release, resolving a nice collection of problems reported by the community, details below. All users are encouraged to read the release notes and upgrade. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.6, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully If you have Unraid 6.12.8 or Unraid Connect installed: Open the dropdown in the top-right of the Unraid webgui and click Check for Update. More details in this blog post If you are on an earlier version: Go to Tools -> Update OS and switch to the "Stable" branch if needed. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip.

Excellent. I'd suggest turning that other piece of hardware off and then see if Unraid can boot and get an IP. If so, you'll want to dig into the config of that other system and figure out why it is claiming 10.1.10.81 when you have it set to use 10.1.10.82

This line: Mar 22 09:25:44 [1394]: br0: 7a:8c:b5:08:ef:51(7a:8c:b5:08:ef:51) claims 10.1.10.81 means the NIC with MAC address 7a:8c:b5:08:ef:51 is already using 10.1.10.81 so it can't be assigned to the server. These log messages are the only time it is mentioned in the diagnostics, so there is no clue where to look. It might possibly be a different computer on the network, or it might be a virtual nic on the server maybe somehow left over from tailscale? Or maybe an issue with a custom Docker network? Does your router give any hints as to where 7a:8c:b5:08:ef:51 is? If you turn off your server does that nic also go offline in your router? While you are working on this I'd recommend editing config/disk.ini on the flash drive and setting startArray to "no". This will prevent the array from starting so there is no risk of an unclean shutdown if you need to reboot. My only other suggestion at the moment is to try booting in safe mode to rule out plugins.

What version of Unraid is this?

Unraid 6.12.8 has further improvements in this area. Oh I see in your other comment that you updated to 6.12.8, so in theory this particular cause of Docker preventing the array from stopping should not be an issue for you going forward.

Thanks, I see an issue with Docker notifications. Should be fixed in the next release

Thanks, we're looking into it

Can you provide me with a sample tunnel config from mullvad? You should change the keys and anything personal, I just want to see the format (particularly the colon) that seems to be causing an issue.

Navigate to Settings -> Identification and remove any single or double quote marks from the description and model fields. This will be resolved in the next release.

Here's what I would expect... The first group of 5 areas (OS Update/Plugins update/Docker update/Language update/Array status) are specifically defined areas that can be enabled/disabled completely. I believe this happens without regard to whether the notification is a notice, warning, or alert. However, plugins and other areas of the OS can also send notifications. For those, you can enable/disable notifications based on the severity (notice/warning/alert) If you are seeing something different please provide your diagnostics.zip (from Tools -> Diagnostics)

Most likely, you disabled bridging in order to enable macvlan. If you want to switch to ipvlan you need to re-enable bridging first. For more info see: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces Being able to enable macvlan without getting call traces/crashes was a big enhancement of 6.12.4. A side effect of the network changes is that your router may complain about duplicate IPs on different interfaces. Aside from the complaint from your router it should not cause any actual problems.

Ah thanks, that clears things up. These warnings are unrelated to the blank server-state.php page and have been fixed in 6.12.8. Unfortunately that means we have no clues as to why server-state.php is blank. For now I'd suggest uninstalling the Connect plugin and upgrading back to 6.12.8

Your earlier diagnostics showed you were on 6.12.8, is that the version you are running when you get those PHP warnings?

Please upload your diagnostics.zip file (from Tools -> Diagnostics)

Interesting. Please go to Tools -> PHP Settings and press Clear Log if it is not disabled. Then set the "Error reporting level" to All categories and apply. Then use a different tab to visit http://Homeserver.local/plugins/dynamix.my.servers/data/server-state.php Wait a bit then switch back to the original tab and click the View Log button. That should show some warnings or errors that you can paste back here.

We found the issue... please navigate to Settings -> Identification and remove the single quote / tick mark from your server's description. You will be able to add it back in the next release Would you mind reinstalling the Connect plugin? If the issue returns, please visit this URL: http://Homeserver.local/plugins/dynamix.my.servers/data/server-state.php Then send the results to me in a DM or create a support ticket https://unraid.net/contact . Be sure to include the link back to this conversation for context. Thanks!

When in the broken state, please SSH in and type the word "diagnostics". This will put the diagnostics.zip file in the logs directory on the flash drive. We really need to see these diagnostics so we can see what is going on with the system. After doing that, please reboot into safe mode (which disables all plugins) and see if the same problem occurs.

Excellent sleuthing! We'll fix that but at least there is an easy work around.

Would you please visit this url: http://RaidOS.local/plugins/dynamix.my.servers/data/server-state.php If it throws an error please post it here (or if it looks personal you can DM me). If it shows data then that probably isn't the source of the error, but it might be helpful if you DM it to me

Thank you for the phplog. Are you able to capture diagnostics when in that state? (by typing "diagnostics" and then grabbing the file out of the logs directory on the flash drive) I'm still unclear, once the problem happens is it specific pages that go all white or is it all pages?

So the webgui initially works after a reboot and then after some time it goes blank? The next time this happens, please SSH to the server (or use a local keyboard/monitor) and and type "diagnostics". This will create a new diagnostics zip file on the flash drive (in the logs directory) which will capture logs after the problem starts, hopefully giving us some clues. Also once the problem starts, please type: cat /var/log/phplog You may be able to copy/paste the response back here, if not you can run: cp /var/log/phplog /boot/logs and then the phplog file will be available on your flash drive along with the new diagnostics zip file (look for the latest one created today). Get both files off the flash and upload here.

Is it an intermittent problem? I see you are running 6.12.8 which has only been available for a few days, how did you upgrade if the webgui wasn't working? Or is it just some pages with issues? Is the entire page white or does it show a header and navigation? Just trying to get a clear understanding of the problem, thanks!

Hey everyone, this thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic in https://forums.unraid.net/forum/55-general-support/ . Be sure to include your diagnostics.zip (from Tools -> Diagnostics)

Hmm please start a new thread in https://forums.unraid.net/forum/55-general-support/ Be sure to include your diagnostics and any testing you can think of. Having a dedicated thread allows for better back and forth than we can do in a release thread.