Chukwuka13

The share is configured to use the zpool as the primary storage and the Unraid Array as the secondary storage. I did actually notice that even though the Zpool was configured to have a minimum free space of 5%, the share itself was somehow configured to have a minimum free space of 50%. I don't know if that setting was recently changed since my server has been well over 50% capacity for a while now. Reducing the value on the share setting did address this issue.

I turned logging on during a mover scan, and I see a lot of errors about files not being able to be moved due to the No space left on device error. This is probably why nothing was moved after 2 days of leaving that task to run. My array is also not at full capacity.

It looks like IPv6 was never enabled. My network protocol is currently set to IPv4:

@JorgeB My scrub finished with a few permanent errors on some files, which I've gone ahead and deleted. After I paused the parity sync and rebooted my system, then attempted to write to my share, but I still got the insufficient storage error. Here is the diagnostic after the write attempt: diagnostics-20230705-0840.zip Keep in mind the ZFS pool is now at 86.4% capacity: and the minimum free space is set to 4%:

While I wait for the parity sync, can you recommend anything to prevent the nchan errors? I've been seeing these for a while and don't understand the cause. My server has 256 GBs of memory, so it should have more than enough to prevent any out-of-memory issues.

I'm not able to reboot at the moment. I'm currently running a parity check on the array and a scrub on the zpool to see if that helps anything. The parity check probably won't be done until about 48 more hours.

@JorgeB here you go: diagnostics-20230704-0825.zip

When my ZFS pool got to around 90% capacity, I started receiving the "[Errno 28] No space left on device" error when writing to my ZFS pool. I tried moving files off the pool, reducing the storage capacity to 88.5 %, yet this error persists. I later noticed the Minimum free space setting was set to 10%, which could explain the original error. However, I have since tried updating that setting to values less than 5%, but the No space left error persists. I'm not sure what could be the cause at this point. This pool is configured to my Array so that mover moves files from the ZFS pool into the Array. Here is a screenshot providing more info on my share configuration. I'm wondering if this error may have been a result of my moving content from my pool into the Array outside of the mover task. I don't know if that is supported. I did this because the mover task seems to either be broken since the 6.12 upgrade or is very slow when running against the ZFS pool. I had the task running for almost 2 days and saw no sign of anything actually being moved. Any suggestion on how to resolve this would be greatly appreciated.

I was able to resolve this issue by providing the pkg_resources module in the shared libraries folder

After moving my windows plex server to docker in UnRAID my custom plex agents(plugins) seem to be broken. I am getting the following error: File "/usr/lib/plexmediaserver/Resources/Plug-ins-724c56e62/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/code/sandbox.py", line 345, in __import__ raise e ImportError: No module named pkg_resources Seems like I need to install python for the plugin to have access to that module. I went ahead and installed the NerdPack app to install python into UnRAID. However, this issue persists. Seems like the docker container does not have visibility of the python install which probably makes sense. Does anyone know how I could get around this? I am using the official plex docker container.

Okay that makes sense. In my case, past the initial migration to UnRAID I don't foresee myself attaching any temporary drives to my server. I guess it wouldn't hurt to keep the plugin around just in case.

That's a good point. With the multi pool feature in UnRAID 6.9 is there any benefit to keeping the unassigned drive plugin around?

Thanks for the info itimpi. If that's the case I'll just leave the spare NVMe unassigned for plex.

I am currently on UnRAID 6.9.1. My server is currently using 1 of my 2 2TB NVMe drives as in the cache pool. Up until this point, the second NVMe drive had been sitting around as an unsigned drive. My initial intention for the second drive was to have it be a dedicated Plex meta drive. However, once I learned that the Plex docker container stores the Plex metadata folder on the cache drive by default I figured I may as well merge the second NVMe SSD into my cache pool. But for whatever reason when I try to add the spare drive to my cache pool the total size of the pool does not increase to 4TB. It continues to show 2TB. I’m not sure why this is. I have tried removing and re-adding the drive to the cache pool only for the issue to persist. Any ideas?