NightOps

I'm on 6.12.6 - I don't think it's the Unraid update, but rather the Unraid Connect plugin...

Having same issue, didn't see your thread until after I posted. Any updates?

While in connect.myunraid.net and managing my Unraid server from there, then going to Tools > Update OS, this option now opens a new window AND opens the original window in the Unraid Connect window: Opens this window: (URL: https://account.unraid.net/server) Which then redirects to this window: Meanwhile, the original window just perpetually displays this: This suddenly stopped working after an update to Unraid Connect.

1 & 2: definitely. Cannot confirm #3

Is that starting on 6.11 with Plex Pass/Official?

Typically just sending the full ZIP file is best. Also, for specific docker issues, make sure that you post in the author's forum page. If you are using Linuxserver.io's NZBGet, then you can find it here: I can't be certain, I've not encountered the same issue (using SABNzbD), but I am seeing BTRFS errors/warnings in your syslog: Sep 6 13:58:14 Tower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 92185 off 335380480 csum 0x90b48b64 expected csum 0xed4418db mirror 1 Sep 6 13:58:14 Tower kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 Other forums indicate deleting/recreating your docker.img which is pretty simply: Login to your system from the unRAID webGui (http://tower or http://tower.local from Mac by default). Navigate to the Docker tab. Stop the Docker service if it is not already. Click the checkbox next to the Docker image that says Delete Image File. Click the Delete button after clicking the checkbox to delete the image (this may take some time depending on the size of your image). After the file has been deleted, you can simply re-enable the Docker service and the image will be created in the same storage location with the same name. Once you've done that, you may also want to delete your NZBGet docker and completely wipe the folder in appdata for it to clear all settings, then rebuild it. If you've already done this, you may want to install the "Fix Common Problems" app, see if it identifies any issues, and resolve as appropriate. Again, I'm still a bit of a n00b, but just some steps I've done to resolve issues with my initial setup. If you've tried all these and aren't sure where to go next, post in the forum I linked above.

Might help if you posted Diagnostics Tools > Diagnostics I had a load of issues initially, but now I'm running a dozen docker images, hardware transcoding on Plex (still working on getting QSV on Handbrake to work correctly), but nothing is causing a hard lockup anymore. At one point my RAM was the issue, and then after I got that sorted I had to clear out my docker.img and have it manually re-download/recreate.

Looking good so far. I can confirm that the latest update significantly dropped CPU utilization on my i5-12600k when hardware transcoding streams... I went from running ~40% on a single transcoded 1080p to 360p stream running over 5G on my smartphone, down to under 20%. Tested using the same source, to the same device, on the same signal strength (tested just before updating Plex container, and just after the update). I'm running the official Plex docker.

Is Plex using the latest ICR? Is ICR the holdup?

Sounds good. I forget, is HDR more in unRAID’s side, or Plex’s?

Is ICR packaged in the OS, or is it packaged within the docker (basically making it a Plex issue to include the correct ICR)?

Anyone know about the updates to the official Plex container? INTEL_GMMLIB_VERSION=20.3.2 INTEL_IGC_VERSION=1.0.5699 INTEL_NEO_VERSION=20.48.18558

As long the dedicated graphics was handling the transcoding, then I believe it would work fine.

Hmm, fair question - I've disabled it out of safety until the newer ICR gets thrown into the Plex container, and the 5.18 kernel is implemented by unRAID.

Just make sure to disable HDR tone mapping in Plex, otherwise there will be issues.