Zer0Nin3r

Data loss in early 7.x versions? Hard pass. I installed 7.0.x and my custom Docker networks went completely sideways. All the info I found to fix it was as clear as mud, with no quick and easy guides in sight—exactly what I needed on an already chaotic day. The upgrade was supposed to simplify my life, not hand me another problem to juggle. Hence, the retreat back to trusty 6.x. Honestly, I can’t even recall the last time an Unraid upgrade gave me this much grief. On another note, while the new features in v.7 do look promising, migrating my cache pool to ZFS suddenly feels questionable. Can someone reassure me that wasn’t a colossal mistake? How has your experience been on Unraid 7?

Upgraded from the latest version of 6.12.x directly to 7.0.1 last week. Today I observed that the Plex server was offline. Tried different network settings without success. Moved from Host to Cutom Network/Bridge mode. Assigned IP address in bridge mode. Issue persists. Plex server still shows up offline at app.plex.tv. Tried regular Bridge mode. Issue persists. Can boot into the local instance of Plex, but the media library doesn’t show up. In fact, the Plex server doesn’t even show up in the Plex GUI as if there is not a server running whatsoever. Upon further investigation, been experiencing slow Docker dashboard load times. I haven’t been observing excessive or continuous writes to the USB flash drive that Unraid is installed to. Furthermore, Unraid GUI would freeze when trying to load the NVIDIA settings panel. Discovered after a reboot of the server that an RTX GPU was not being seen by the system. I uninstalled the NVIDIA plugin and reinstalled the plugin. RTX GPU is now recognized. Server is not freezing when loading into the Nvidia settings panel. GUI takes forever to load the Docker panel. Out of all of my updates and upgrades, I’ve never had any major issues until now. Frustrated, I’m seriously considering downgrading. tower-diagnostics-20250309-2108.zip

I was able to experience this issue and have posted my logs here. **Update** I think I know what the issue was. I was messing with ZFS and wanted to create a snapshot of a VM (snapshot it's directory + .img file) and in doing so I ran the following: zfs create cache/htb zfs set mountpoint=/mnt/user/domains/htb cache/domains/htb Moral of the story — don't do this. To set the mount point you will want to leave it as: /mnt/cache/domains/htb

Having the Unraid terminal in a web browser window was throwing this error for me. Thank. you for this insight!

Is it me or was the /upscale folder's symlink forgotten for 07 - StableSwarm?

Is this still necessary? It looks like the Linuxserver version has since updated Playwright.

This is clutch! To think that this was all I had to do for all these years. This method resolves any GPU initialization issues with Docker containers utilizing an NVIDIA GPU (GTX 1060) after waking from sleep. What this script command does is free up the GPU before the system goes to sleep. Lastly, I’ve found that you don’t need to include the shebang in the S3 command fields. @testdasi Thank you for your help. **Edit** I forgot to mention, you can enable power savings wherein the GPU will go into a low power state. For the longest time I didn't know that you could do such a thing. You can add the following command to your S3 Sleep plugin under the Wake-up Command field. This way when the GPU isn't being used, it will go into a low power state. nvidia-smi -pm 1

Issue seemed to have resolved itself over time. Thank you for the insights. Have a great week!

I've noticed that in the 6.12.2 & 6.12.3 update — Terminal and Log no longer launch from the GUI while using Safari. Content blockers is off for the GUI I don't have any extensions that would interfere. Or at least they haven't in the past. Testing in private browser mode — you are immediately logged out when you try to launch Terminal. **Update** Issue is not present when logging in via IP address, but is present when logging in via local domain name. Using the local domain name wasn't an issue before.

Yeah, the new notification makeover is taking some getting used to. For instance, you can't check the notification or see the notification after upgrading to 16.12.3 because the "Update Unraid OS" window's button doesn't change from "Done" to "Finished" and it doesn't allow the notifications to shine through. If you don't think to open a new tab and check the GUI, you'd be waiting until the cows came home. 🐄

Been experiencing this issue more and more lately. Server has been up for three days. You can login with the GUI, it then slows down and then you can’t even log out and log back in while on local network or while connecting to WireGuard. All the docker services are still up and running so, you can still access those respective services. issue is even persistent in incognito mode. I have been finding that a reboot of the server resolves the issue.

What you can do is stop the Unmanic container prior to launching your VM and vice versa — stopping your VM prior to launching Unmanic. This way you don't crash anything. If you pause Unmanic during an encoding process and then launch your VM, the GPU may not be released to the VM resulting in issues. Like @Josh.5 said, you don't have to passthrough your GPU to Unmanic; Unmanic can still encode using CPU. @Eddie Seelke It is possible to run a single GPU in Unraid and also pass it through to your VM. You would have to pull the firmware from the GPU card and then load it into your VM. I had very limited success with it a few year ago with a GTX 1060. In the end, I spung for a cheap GT 710 to make Unraid happy even as a headless server.

For clarity, may I ask what you are trying to accomplish? If you are booting Unraid into GUI — the answer would be yes.

Looking to modify the MTU size so the excruciatingly slow download speeds will be fixed due to ISP constraints. (5G Internet) Adjusting the MTU within Unraid's settings to 1350 has resolved the VPN issues on my other clients with regards to this particular ISP. I am able to set the MTU at the Unraid system level by: Settings > Network Settings > Desired MTU > 1350 I tried the following without any luck: Key 5 - Container Variable: VPN_OPTIONS --fragment 1350 --mssfix --fragment 1350 --mssfix 1350 Setting the 'mssfix 1350' parameter in the OpenVPN configuration file. I can see in the logs that @binhex sets the MTU in the script and I tried to find the script to adjust, but am unable to; it's not in the Appdata share...that's for sure. OPTIONS IMPORT: adjusting link_mtu to 1624 DEBG 'start-script' stdout output: TUN/TAP device tun0 opened net_iface_mtu_set: mtu 1500 for tun0 net_iface_up: set tun0 up Any ideas on how I can resolve this issue? Thanks in advance!

I recommend that you don't uninstall @dee31797's Handbrake docker until we can get an answer from @Djoss whether it will be supported in the future. I'm with you though. Handbrake with NVENC support is my secondary docker application. If you are automating your encodes, you may want to check out Unmanic as that will support hevc-nvenc.