Unraid-arr

Old plugin still works just fine for me... https://forums.unraid.net/topic/51961-plugin-ca-cleanup-appdata/

Thanks for the fix, the row for that error is gone now.

Thanks, after today's update the columns are fixed now. I am still using your CSS for incognito button. Have a good day!

@binhex - After update today to version 5.0.0 - WARNING 01 May 2026 3:20pm 7za binary... NOT found! Thanks

I had the same issue with my P2000. Plugin has a bug where on upgrading the UnRaid from 7.2.4 to 7.2.5 it installed the latest driver that is incompatible with my GPU even though I had manually selected the 580 driver branch. Had to reboot the server 2 times after fixing this. Now it is okay though. Cheers!

IIRC, it was missed in the last update, before that it was good. Thanks for fixing it.

Hi @chodeus - Can you help me with the custom CSS to claim the space from last empty column "uptime"? My folders are always closed like this, and the uptime column is wasted space I would rather use to show extra containers in the folder. When the folder is opened I do see a use for the Uptime column and if there is a way to do that, I would appreciate it. I did use your CSS above to make things nicer today as I do not use incognito as well, but it did come in handy for the screenshot in this post. (https://forums.unraid.net/topic/197223-plugin-folderview3/page/7/#findComment-1618192) Thanks for the work on the plugin!

All the containers with Extra Parameters: --net=container:<container-name> failed to start, and I had to remove those Extra Parameters and manually set the container networks from none in dropdown to the container name. Just curious, why remove the parameter option?

Thanks, this helped me with my issue. Can you please let me know if this will persist across reboots? You saved my brain from a kernel panic at 2AM after updating UnRaid.

Unraid 7.2.4 with Docker compose plugin - Immich fails to start with error - Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #0: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' nvidia-container-cli: ldcache error: process /sbin/ldconfig failed with error code: 1

I have moved on to Glance. - https://github.com/glanceapp/glance/ Cheers!

Agree, 100%. I reached here because Fix Common Problems showed me the deprecated warning today. I see no reason to remove the old and install the new plugin. This plugin is trying to solve a problem that did not exist in the 1st place. People need to realize that sometimes the software does what it needs to, and no feature updates are needed except security fixes. I will keep the old version. TYVM Thanks!

Plex SupportRepair a Corrupted DatabaseNote: This article is for Plex Media Server version 1.23.2 and newer. If using an earlier version, see . Though...

If anyone comes across this issue, in the meanwhile if you turn off all processing you can use the server. I changed from version - docker to public and no change in version (1.42.2.10156). That is the public version. Thanks

Thanks for acknowledging the issue and helping to resolve it. I cannot say for others but what I do is what has been preached by all YouTubers who make UnRaid content (not naming anyone specific). This is my config that is relevant and is how it's been told to do it for ages now. I transcode to RAM and put temp data to a folder in config directory. Ideally, I expect all this data to be deleted by Plex as it is done processing and especially on container restart if it crashed and restarted. But regardless the ram disk will be cleared if the machine is restarted. Whenever Plex fixes their end of the issues and tmp folder works as intended, I would switch that to RAM disk as well. There is no reason for me to have it on persistent storage. It is literally called temp folder. <Config Name="Transcode" Target="/transcode" Default="" Mode="rw" Description="Path for transcoding folder (Optional)" Type="Path" Display="always" Required="false" Mask="false">/tmp/plex-ramdisk</Config> <Config Name="Temp directory" Target="/tmp" Default="/mnt/plex_appdata/plex/tmp" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/plex_appdata/plex/tmp</Config> <Config Name="Appdata" Target="/config" Default="" Mode="rw" Description="Appdata" Type="Path" Display="advanced" Required="false" Mask="false">/mnt/plex_appdata/plex/</Config> 👇🏻This below is absolutely on Plex, who know if they will even listen to me. They have been ignoring customer feedback for a while now. I did create the issue on their forum as you suggested. If you would like to add your investigation to it, please be my guest. Plex Forum Link 👇🏻I used to do it this way before, but to investigate I replaced with the above config and stuck with it. I have 128GB RAM so that is not an issue for me. <ExtraParams>--runtime=nvidia --mount type=tmpfs,destination=/tmp,tmpfs-size=17179869184 --no-healthcheck</ExtraParams>Thanks 🙂

So, @j0nnymoe it turns out it is not a Plex issue rather a LSIO issue. 'TMPDIR=/run/plex-temp' is specified by your build process. Look at what I found on your build - https://hub.docker.com/layers/linuxserver/plex/latest/images/sha256-9170109a442498630befe62f8236c68ddd7da21cf66c606f9a390dacf931a6e2 TMPDIR=/run/plex-tempENV DEBIAN_FRONTEND=noninteractive PLEX_DOWNLOAD=https://downloads.plex.tv/plex-media-server-new PLEX_ARCH=amd64 PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR=/config/Library/Application Support PLEX_MEDIA_SERVER_HOME=/usr/lib/plexmediaserver PLEX_MEDIA_SERVER_MAX_PLUGIN_PROCS=6 PLEX_MEDIA_SERVER_USER=abc PLEX_MEDIA_SERVER_INFO_VENDOR=Docker PLEX_MEDIA_SERVER_INFO_DEVICE=Docker Container (LinuxServer.io) TMPDIR=/run/plex-temp This was first added to 1.41.0 - https://hub.docker.com/layers/linuxserver/plex/1.41.0/images/sha256-dff1f3af12fc385eb3a13901480ce62cd6b2e64f74897cc7d6a13a2922bf5f5a Before that the last image without this TMPDIR variable is 1.40.5 - https://hub.docker.com/layers/linuxserver/plex/1.40.5/images/sha256-55ca5b9bb96ded7a0ea54f6579ad8285cec7822869f86c88a1bfedd3cf4febcd I am assuming this makes it so that the docker variable for temp folder gets ignored as well. Please fix thanks.

Done. Thanks https://forums.plex.tv/t/plex-server-dumping-temp-files-for-credit-detections-sonic-analysis-inside-container/931758

Made comment here. Follow there for solution if it ever happens. Thanks

Hi @linuxserver.io - This is an urgent matter that needs to be fixed. Thanks in advance. I have been plagued with this issue for over 2/3 weeks now (havent nailed it when it started but I have been having crashes since then). Something has changed which annoys me way more than it should. I had to destroy my docker.img file twice as it was crashing all containers and server eventually. I could not go into the container to check what was taking so much space, so then I switched to docker folders to investigate this. Today I have the receipts. This is the bloated folder - Over 67G (67G --> ./c411fe64e3325eae2da44368f02627ba7b12c197d2f15010db4e178140640e47) /mnt/cache/system/docker/overlay2/c411fe64e3325eae2da44368f02627ba7b12c197d2f15010db4e178140640e47/ ├── diff (33G) │ ├── ... │ ├── run (33G) │ │ └── plex-tmp (33G) │ │ └── PlexCreditsDetection-de8cedc6-e9c0-448d-bd02-ffc962f4181e (33G) │ ├── ... ├── ... ├── merged (34G) │ ├── ... │ ├── run (34G) │ │ └── plex-tmp (34G) │ │ └── PlexCreditsDetection-de8cedc6-e9c0-448d-bd02-ffc962f4181e (34G) │ ├── ... │ ├── ... └── ...I have got these sizes from du -sh ./* command for all folders. Here is my Plex template. I am mapping the Transcoder temporary directory - /transcode to RAMDISK and Downloads temporary directory - /tmp to TEMP folder on the Plex config drive. root@Tower:/boot/config/plugins/dockerMan/templates-user# cat my-plex.xml <?xml version="1.0"?> <Container version="2"> <Name>plex</Name> <Repository>linuxserver/plex</Repository> <Registry>https://hub.docker.com/r/linuxserver/plex/</Registry> <Network>host</Network> <MyIP/> <Shell>bash</Shell> <Privileged>false</Privileged> <Support>https://forums.unraid.net/topic/40463-support-linuxserverio-plex-media-server/</Support> <Project>https://www.plex.tv/</Project> <Overview>Plex organizes video, music and photos from personal media libraries and streams them to smart TVs, streaming boxes and mobile devices.&#xD; &#xD; Nvidia GPU Use&#xD; Using the Unraid Nvidia Plugin to install a version of Unraid with the Nvidia Drivers installed and&#xD; add --runtime=nvidia to "extra parameters" (switch on advanced view) and&#xD; copy your GPU UUID to NVIDIA_VISIBLE_DEVICES.&#xD; &#xD; Intel GPU Use&#xD; Edit your go file to include:&#xD; modprobe i915&#xD; , save and reboot, then &#xD; add --device=/dev/dri to "extra parameters" (switch on advanced view)</Overview> <Category>MediaServer:Video MediaServer:Music MediaServer:Photos</Category> <WebUI>http://[IP]:[PORT:32400]/web</WebUI> <TemplateURL>https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/plex.xml</TemplateURL> <Icon>https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/plex-icon.png</Icon> <ExtraParams>--runtime=nvidia --no-healthcheck</ExtraParams> <PostArgs/> <CPUset>12,13,14,15,36,37,38,39,16,17,18,19,20,21,22,23,40,41,42,43,44,45,46,47</CPUset> <DateInstalled>1758649637</DateInstalled> <DonateText/> <DonateLink/> <Requires/> <Config Name="VERSION" Target="VERSION" Default="" Mode="" Description="VERSION" Type="Variable" Display="always" Required="false" Mask="false">docker</Config> <Config Name="Nvidia Visible Devices" Target="NVIDIA_VISIBLE_DEVICES" Default="" Mode="" Description="Nvidia Visible Devices (Optional - Requires Nvidia GPU and Unraid Nvidia build)" Type="Variable" Display="always" Required="false" Mask="false">GPU-xxxxxxx-MASKED-xxxxxxx</Config> <Config Name="Media" Target="/media/" Default="/mnt/user/media/" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/media/</Config> <Config Name="Transcode" Target="/transcode" Default="" Mode="rw" Description="Path for transcoding folder (Optional)" Type="Path" Display="always" Required="false" Mask="false">/tmp/plex-ramdisk</Config> <Config Name="Webtools" Target="33400" Default="33400" Mode="tcp" Description="" Type="Port" Display="always" Required="false" Mask="false">33400</Config> <Config Name="Temp directory" Target="/tmp" Default="/mnt/plex_appdata/plex/tmp" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/plex_appdata/plex/tmp</Config> <Config Name="Appdata" Target="/config" Default="" Mode="rw" Description="Appdata" Type="Path" Display="advanced" Required="false" Mask="false">/mnt/plex_appdata/plex/</Config> <Config Name="Webui" Target="32400" Default="32400" Mode="tcp" Description="For access to the Plex Media Server Webui (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">32400</Config> <Config Name="Plex Companion" Target="3005" Default="3005" Mode="tcp" Description="For controlling Plex Home Theater via Plex Companion (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">3005</Config> <Config Name="Roku via Plex Companion" Target="8324" Default="8324" Mode="tcp" Description="For controlling Plex for Roku via Plex Companion (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">8324</Config> <Config Name="Plex DLNA Server" Target="32469" Default="32469" Mode="tcp" Description="For access to the Plex DLNA Server (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">32469</Config> <Config Name="Plex DLNA Server" Target="1900" Default="1900" Mode="udp" Description="For access to the Plex DLNA Server (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">1900</Config> <Config Name="GDM network discovery" Target="32410" Default="32410" Mode="udp" Description="For current GDM network discovery (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">32410</Config> <Config Name="GDM network discovery" Target="32412" Default="32412" Mode="udp" Description="For current GDM network discovery (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">32412</Config> <Config Name="GDM network discovery" Target="32413" Default="32413" Mode="udp" Description="For current GDM network discovery (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">32413</Config> <Config Name="GDM network discovery" Target="32414" Default="32414" Mode="udp" Description="For current GDM network discovery (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">32414</Config> <Config Name="PUID" Target="PUID" Default="" Mode="" Description="PUID" Type="Variable" Display="advanced" Required="false" Mask="false">99</Config> <Config Name="PGID" Target="PGID" Default="" Mode="" Description="PGID" Type="Variable" Display="advanced" Required="false" Mask="false">100</Config> <TailscaleStateDir/> </Container> Also, to add the actual mapped /tmp and /transcode folders are completely empty. root@Tower:/mnt/plex_appdata/plex# du -sh ./* 230G ./Library 0 ./tmproot@Tower:/tmp# du -sh ./* ... more folders 0 ./plex-ramdisk ... more folders

I deleted my docker.img and have moved to docker folder and I will monitor to see what folder grows in coming days. Thats the best way I could find to get to the bottom of this issue. I am recreating all the containers as I write this. I hope there is no significant difference between docker.img vs docker folder. Fingers crossed. Thanks.

Thanks @JorgeB - I understand, yes the problem came back today morning. At this point I am not sure if it is plex. I removed Plex and the size didn't shrink. Then I force recreated all the containers again. (Force Update button). Removed all orphan images. Reinstalled plex. Size dropped to 88GB. Nowhere close to previous stable 40-ish GB. Here is the container size from the button on docker page. I have masked the container names except plex. Name Container Writable Log plex 20.7 GB 20.3 GB 18.7 kB container#1 4.71 GB 55.6 kB 8.04 kB container#2 3.30 GB 28.6 MB 223 kB container#3 2.21 GB 127 MB 127 kB container#4 2.04 GB 3.77 MB 948 kB container#5 1.87 GB 643 MB 34.0 MB container#6 1.79 GB 1.14 MB 81.0 kB container#7 1.77 GB 104 MB 18.5 kB container#8 1.71 GB 53.1 kB 34.8 MB container#9 1.54 GB 0 B 148 MB container#10 1.40 GB 167 MB 3.62 MB container#11 1.37 GB 151 MB 7.18 MB container#12 1.35 GB 0 B 148 MB container#13 820 MB 0 B 148 MB container#14 820 MB 0 B 148 MB container#15 754 MB 533 B 7.49 kB container#16 743 MB 3.88 MB 33.9 kB container#17 722 MB 2.35 MB 234 kB container#18 696 MB 21.0 MB 34.6 kB container#19 674 MB 105 MB 39.1 kB container#20 606 MB 135 kB 744 kB container#21 490 MB 0 B 148 MB container#22 483 MB 322 kB 74.2 kB container#23 454 MB 63 B 21.1 kB container#24 443 MB 885 kB 3.58 kB container#25 420 MB 18.5 kB 29.3 kB container#26 416 MB 59.1 kB 52.3 kB container#27 348 MB 4.71 kB 15.1 kB container#28 337 MB 12.7 kB 709 kB container#29 328 MB 18.6 kB 23.5 kB container#30 327 MB 6.19 kB 29.2 MB container#31 306 MB 0 B 3 kB container#32 267 MB 1.92 MB 6.83 MB container#33 235 MB 0 B 148 MB container#34 222 MB 0 B 282 kB container#35 219 MB 0 B 148 MB container#36 214 MB 0 B 2.27 kB container#37 193 MB 0 B 148 MB container#38 189 MB 0 B 148 MB container#39 189 MB 9.85 kB 179 kB container#40 188 MB 2.41 MB 8.11 kB container#41 186 MB 0 B 15.3 kB container#42 182 MB 4.81 kB 5.80 kB container#43 164 MB 0 B 148 MB container#44 149 MB 0 B 148 MB container#45 146 MB 19.9 kB 1.84 MB container#46 140 MB 22.1 kB 15.2 kB container#47 135 MB 0 B 148 MB container#48 133 MB 0 B 148 MB container#49 131 MB 28.4 kB 2.95 kB container#50 128 MB 0 B 148 MB container#51 126 MB 31.9 MB 64.6 kB container#52 113 MB 0 B 567 kB container#53 112 MB 111 kB 15.6 kB container#54 105 MB 0 B 148 MB container#55 84.6 MB 4.46 MB 66.5 kB container#56 84.6 MB 4.46 MB 12.6 MB container#57 78.7 MB 278 kB 129 kB container#58 74.3 MB 190 B 505 kB container#59 65.9 MB 0 B 148 MB container#60 61.4 MB 0 B 18.1 kB container#61 36.3 MB 5.50 kB 514 kB container#62 34.8 MB 0 B 148 MB container#63 34.8 MB 0 B 148 MB container#64 34.8 MB 0 B 148 MB container#65 34.8 MB 0 B 148 MB container#66 34.8 MB 0 B 148 MB container#67 34.8 MB 0 B 148 MB container#68 34.8 MB 0 B 812 B container#69 31.5 MB 18.1 kB 34.6 kB container#70 31.5 MB 0 B 148 MB container#71 31.5 MB 0 B 148 MB container#72 31.5 MB 0 B 148 MB container#73 31.5 MB 0 B 148 MB container#74 31.5 MB 0 B 148 MB container#75 31.5 MB 0 B 148 MB container#76 31.5 MB 18.1 kB 34.7 kB container#77 22.7 MB 0 B 148 MB container#78 21.9 MB 0 B 136 kB container#79 16.6 MB 0 B 90.8 kB Total size 60.9 GB 21.7 GB 4.44 GBIf anyone can help me here. I would appreciate that. Thanks

As the Read-Check scheduler is coming back in UnRaid 7.2.x - https://forums.unraid.net/topic/193500-unraid-read-check/#findComment-1578307 I would like to see this implemented soon in the API as well. Thanks

Thanks for this, it gives me hope. I am not sure why it was removed in the 1st place. But glad to see it is returning. Thanks

UnRaid API was exposing correct information for Parity/Read-Checks before. Lately for the past few weeks, some code has been changed, and now it doesn't show the info for Read-Checks and only shows for Parity checks. For people who don't have parity disk and don't do them, the API would automatically show the read-check info in its place which I do on schedule. That is how it should be. If Parity Check is not available because there is no parity disk, check for Read-Check data and send that. I would like to know when this will be fixed. Thanks

Hello Dynamix team, @bonienl and @Squid - I have been waiting patiently for a while for the Parity/Read-Check issue to be fixed. Premise - If someone doesn't have a parity disk the Parity schedule settings don't show up in the schedule section in the settings menu. Read-Check can still be done. Issue - The old versions of UnRaid used to have Read-Check schedule in case someone doesn't have Parity. I did that all the time. Still do that. Someone like me who had a Schedule setup for Read-Check can still use the same schedule as the config exists '/boot/config/plugins/dynamix/dynamix.cfg ' and has the relevant section for that. However, I cannot change those settings without editing the config manually. [parity] mode="0" dotm="1" hour="0 13" day="2" month="2" write="NOCORRECT" frequency="1" duration="1"I do not have the documentation to know what possible values I can set them to if I need to change the settings. So, I have just let things run as is. Unless, there is a reason that has not been explained why this section was removed from UI for people without parity, when can I expect it to come back. It is still possible to do those Read-Checks, why take away the scheduling part. Thanks and looking forward to the response.