Cessquill

Apologies if I've missed the start of this conversation, but the "Split Level" setting when creating a share is exactly for this purpose. If you haven't done already, set it up now on your shares to solve it going forward. I don't know how much data you've got, or how patient you are, but I'd be tempted to set up your shares with the correct split level, manually move each show in turn onto your cache (via Midnight Commander, Krusader, command line, other file manager, etc.), and then have Mover put it back on your drives properly. Or tidy them manually by looking at the TV share and identifying where a show spans disks and manually moving it. I haven't fully thought this through, and it could be beyond how much time you want to spend (I tend to chip away at these sorts of jobs sending a copy/move operation off every now and then), but set the split level up correctly so that everything going forward is right. Hope this helps, apologies if not.

Yep. I haven't done it, but you can use the "Unassigned Devices" plugin to add a remote share to Unraid (it'll walk you through a wizard to make the connection). You can then edit your Plex docker to add this share so that Plex can see it. Finally, in Plex, just add it to an existing library, or create a new library as normal.

Did you restart your server after making changes to the disk? The issue this thread covers is where disks are disabled on spinup. If you're saying yours don't spin down, something else is going on. Cables OK? Big enough power supply? Hopefully somebody can point you in the right direction.

In addition to the other suggestion - I kept forgetting how to do this, so I installed the "OCC Web" add-on in Nextcloud. Then, when the system tells me I need to run a command, I can do it straight into a command prompt within the Nextcloud interface.

Or have the Docker Patch plugin installed. I know it's standard practice for some, but I'm reluctant to delete empty paths, just in case I need them in the future. My update went OK too, although for a while yesterday my libraries were showing as unavailable. Came back after about 15 minutes though.

The forums are a place for people with issues to seek help - you're going to find similar incidents. If you could compare that with the amount of people where it runs just fine, you'd likely get a much better outlook. You really ought to use the help available on these forums to sort your server out as there's no way it's that unreliable. I've leaned on them several times where I've come unstuck and they've helped enormously.

Read the first post in the Docker Patch support thread - should get you back up and running.

Ahh, is that why I got a notification this morning saying an updated driver was available (and then when I checked, there wasn't)? Currently on 550.54.14. Hadn't noticed any issues, but rolling back to 550.40.07 for now.

Many thanks for this, and apologies for the delay getting back to you. Wanted to leave it for a while to make sure the error had gone, and then forgot about it(!). I suspect Plex has also fixed the memory leak error at their end too now.

Whilst this won't directly affect me (pro user), I'm a little concerned about what we jokingly call the "coming soon™" roadmap of Unraid might be sacrificed so that a release is launched to pacify those paying for a year and receiving little or nothing. Stability is paramount to me from Lime, and the bells and whistles I get from and give to the community. I don't want to risk stable updates in order to hit a schedule. I get that in recent times updates have been faster, so I might be talking out of my hat. From where I see it, it's not practical to split the system into functionality and security updates - nice idea, but I don't think it's built like that. Likewise, it won't be practical, but I'd rather be charged if I want to opt for a + .1 release rather than tied to a schedule. Steinberg have a policy of charging for major releases, with incremental ones free. If you want to leave it, you can. But you pay some more later on if you want to play catchup. Trivial for me, since I've had a pro licence for a long time, but since I've had cache drives & pools, dockers, plugins and VMs, I've often figured I ought to have paid something extra. But then what if I wanted just a NAS with the latest security patches (can of worms...!).

Working from here with the same tuner (in the browser). Live TV isn't the most polished parts of Plex though, and I've had this before. Can't recall whether I restarted, rescanned for channels in the DVR section, deleted the codecs, refreshed the browser or just waited (sorry).

Fix Common Problems is reporting that I've got out of memory errors and to post my diagnostics on here (attached). This also happened last week, and I rebooted and left it to first check whether it was a one-off. Any help appreciated.

Refer to the pinned post at the top of this page (for me, it's the last of 3)

Many thanks for this. Just to be clear, is this an uninstall / install new plugin situation, or do I wait for an update?

This may need some tweaking depending on your setup, but the Codecs folder is in \\tower\appdata\plexmediaserver\Library\Application Support\Plex Media Server With Plex stopped, just delete the folder (or rename it to something like codecs_old) and restart Plex. It'll automatically redownload the latest. As I understand it, this folder may get corrupt over time and/or updates. With Tdarr, I run analyse across my libraries on Plex afterwards, since when Plex initially scans a file it grabs its info. When you play it, it starts it based on that info. If it's re-encoded using Tdarr and the filename isn't changed, Plex doesn't know that the file is different and tries to play it according to the original specs (at least I think that's what's happening). Analyse forces it to actually look at the file again. Also, I think that @alturismo was saying that turning transcode off for local files is correct.