randommonth

Hi everyone, this issue had popped up recently in that my Plex server appears to refuse to transcode. Many users and clients are reporting getting the 'Not enough CPU' error message or files just aren't working. I've got an Unraid server running an i7 8770 with 16 GB of RAM. PMS is the Binhex docker container. I have had hardware acceleration working perfectly for several years, until now. Server logs attached Thanks in advance. Plex Media Server Logs_2023-12-30_17-28-51.zip

Thanks @JorgeB

Hi guys, my server just logged an out of memory error... diagnostics attached. Thanks bigdaddy-diagnostics-20230924-0839.zip

Thanks again @JorgeB! It's taken me a few days to backup my cache but then when I performed the process this morning, I found the process didn't wipe my cache after all. I'll give it a few weeks to monitor for success before marking this as the solution.

Hi guys, I have had issues with cache drive stability in the past when I was running dual SSDs in a pool. I reduced the cache down to a single drive and have experienced excellent stability for the last 6-9 months. I could not pin point the root cause but I suspect some of the SATA ports on my motherboard are loose or faulty. I upgraded to 6.12.3 about a week ago and have seen consistent re-occurrence of the cache instability. Every morning I'm waking to find the cache has degraded somehow overnight, either completely disappearing or simply being unreadable. I have managed to resolve quickly each time by shutting down and rebooting, sometimes needing to stop the array and reassign the cache to pool. Each time the cache has reappeared and worked fine. Find diagnostics attached. Thanks bigdaddy-diagnostics-20230816-0641.zip

I followed the guide here without any issues. Didn't bother with the mover.

Thanks but I'm a bit confused now. I have two cache drives in a pool. I want to remove one. Is it as simple as stopping the array, removing the drive then restarting the array? Or do I have to go through the process of changing the cache preferences on applicable shares and running the mover?

Thanks. I'm fed up with this and I'm pretty sure the culprit is a dodgy SATA port on the MB. I can't afford to upgrade MB and CPU, so I'm just going to remove this drive from the pool. Can you advise the right way to remove the drive from the pool?

Thanks. Does it specify which drive has the bad link? I don't see any reference to SDB or SDD. All the cables are new too. Are the MB sata ports the only other potential source?

Hi guys, following on from months of errors in my cache pool, I recently nuked the pool and started over with some great help from @JorgeB. This morning my syslog was full and I found many errors coming from one of my cache drives (SDB1). I assume this is the 256 GB ADATA drive in my pool, see below. Before I go and replace this drive I just wanted to make absolutely certain this was the problematic drive in my pool? bigdaddy-diagnostics-20221124-1219.zip

Thanks again man!

Attached. Thanks. bigdaddy-diagnostics-20221114-0841.zip

Thanks again @JorgeB bigdaddy-diagnostics-20221113-2204.zip

Hi everyone, Over the last few months I've had numerous problems with my cache pool, with @JorgeB providing a lot of very helpful advice. A few weeks back I nuked the pool and started afresh, or at least I thought I had started with a clean new cache pool. The pool has performed flawlessly ever since then, however I've noticed that the second drive 'Cache 2' appears to have been on standby the entire time since starting over. The fact that the second drive being on standby coincides with the absence of all the earlier issues may be confirmation that the second drive was the source of all my earlier issues, however I want to know why it's on standby and if it can be fixed? What are the next steps I should take in root causing the problem?

Hi everyone, I was having the same problems with the same setup and found a solution that others may appreciate. With the change of the Organizr app name to organizrv2, the "set $upstream_app" line should have organizrv2 in it. I think the SWAG sample conf files need updating to reflect the change in app name.