datruedave

Plex docker seems to be working fine. I just had to remember how to make the GUI work. I needed to "pin" the new server libraries/playlists to "home." Duh. I don't want to forget to fix that transcode folder. Where is that normally pointed to? Maybe the appdata user share?

I had time to do this tonight, and reinstalled the Plex docker app. It's working, kinda. My problem seems to be within Plex (Plex sees this as a new Plex server, and I can't get the GUI to work the way I want.) I'll try playing around with this tomorrow. Diagnostics attached. I'm headed for bed. Thanks again! serenity-diagnostics-20220807-2310.zip

Ah, I see. But what is referring to mnt/Books? Why am I getting that error now, when I didn't before? Especially now that the Docker apps are gone? What is it that Fix Common Problems is seeing that refers to that path? I'd rather just fix things than figure out the answer to this, honestly. I think the little lightbulb that you just made go off in my head about user shares will help me a lot. Thank you. I'll have to look up how to do command line stuff again. I think I need to telnet or something? I don't have a spare monitor to hook up to my server. I'll do what you mention in your last post tomorrow and will post here. Thanks again.

Thanks. I don't understand that fix common problems error that refers to the "Books" share, as that existed previously and I made no changes to it. Why would it throw an error now, but not previously? I don't understand why I'm getting the other errors, but at least they refer to things that I've been screwing with...

Yes to both. The unassignd appdisk is not in the machine, but there is room for me to put it back in. The old cache drive is still in the machine, but unmounted. Do I add them as "pool" drives with new names?

I don't have any dockers currently. They all disappeared. I did shut down dockers and set cache:yes and move, and then the reverse after new SSD was installed. At this point, I guess I just start from scratch with new docker apps? Can I delete the docker.img files that are there?

Also, here's my latest diagnostics: serenity-diagnostics-20220807-0824.zip

OK, installed the new SSD as cache. I have a few questions. Dockers are all gone. All my torrents are gone <sad face>. I've got the Transmission plugin running again and have downloaded a bunch of torrents from one of my trackers in hopes of getting off ratio watch, but I figure I'll be starting from scratch with the other trackers once I get the Dockers running. Is it safe to delete the Docker.img files that I have floating around since I'm going to be starting over with the Dockers? Also, I got some errors in "Fix Common Problems" that I don't understand:

It has a Phaze folder, which I presume has plugin stuff that I don't want to lose until I get the Transmission Docker working. And it has an appdata folder, which I assume is the appdata share. It also has a system folder, which has a docker folder, which has a docker.img file inside it (but nothing else in the system folder).

Once I get the new SSD, what's the procedure for replacing my current cache drive? I think the fact that my current cache drive is ReiserFS complicates things. Is it possible to add it as a BTRFS pool drive, copy everything over from the "old" cache drive, then rename it to cache? I found this, but this is the part that confused me earlier. I guess this is going to have mover move the appdata share to the array, I replace the cache drive, and then the mover will move appdata back to the cache drive?

To fix that, I might set the transcoder directory within Plex to /plexmediaserver/transcoder and within the Plex Docker map /mnt/appdisk/plexmediaserver/tmp/plex to /plexmediaserver/transcoder ? I do not use DVR or download features of Plex. Wait, on my phone, I'll sometimes download stuff within the Plex app to watch on the plane, but I don't think that's what you're referring to here.

Heh... Interesting side note, @trurl Way back in 2014, you and others helped me set up this appdisk. (I found this by googling my cache drive's serial number to see if I could easily figure out if it was a hybrid drive without cracking open my server's case to physically look at the drive.)

OK, the plex config being on my Books share is weird and something I must have fat fingered in the last day or two (same with those empty mappings?). It's supposed to be on my appdisk (and a copy still is). After further review, it appears that my Plex library grew too large for that SSD and I did move the Plex library over to the Books share. Perhaps I should take this opportunity to upgrade to a larger SSD. Yes, 1TB SSD gets here tomorrow. So, what do I need to do to move my appdisk to a pool? Copy everything off it, change file system/reformat it, and then look for the tutorial here on pools to set that up, I suppose. After reading a bit, I see that the cache is a pool, and that I can set up this appdisk as a pool. I'm a bit confused about using the mover to move files from the pool to the array (I get why we want this with cache, but don't understand why I'd want it for my appdisk use), but I do most of my file moving from within Windows, so if (from within Windows), I move files from my new appdisk pool drive to a data drive (user share), that should work fine, right? To answer your questions, within Plex, I have the transcode directory set as /mnt/appdisk/plexmediaserver/tmp/plex I do not have any other dockers (just Plex and Transmission). Well, I started to try to set up Deluge, but I just deleted it, as I now hope to get Transmission working. And my appdisk is only used for Plex (well, it used to be), and Transmission. Nothing else.

I don't even know what "go" is. Truthfully, I figure out how to get things running, and then I don't mess with them until/unless they stop working. I know it's probably frustrating to help people like me, but, again, I appreciate it. I set up the Plex docker after the Phaze Plex plugin stopped working, so maybe there's some leftover stuff in there from the plugin? I created that appdisk when I first set up my Unraid server. It's an SSD and, back in the day, it was recommended as a fast disk outside of the array to host config files and other (relatively) small amounts of data that would benefit from fast access. It's worked for me, but I understand it's not the preferred method any longer. I wouldn't mind fixing that. Here's my docker run for plex: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'VERSION'='latest' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'PUID'='99' -e 'PGID'='100' -e 'TCP_PORT_32400'='32400' -e 'TCP_PORT_3005'='3005' -e 'TCP_PORT_8324'='8324' -e 'TCP_PORT_32469'='32469' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_32410'='32410' -e 'UDP_PORT_32412'='32412' -e 'UDP_PORT_32413'='32413' -e 'UDP_PORT_32414'='32414' -v '/mnt/user/Books/Audiobooks/':'/media/Audiobooks':'rw' -v '/mnt/user/Movies/':'/media/Movies':'rw' -v '/mnt/user/Photos/':'/media/Photos':'rw' -v '/mnt/user/Sounds (music)/':'/media/Music':'rw' -v '/mnt/user/TV/':'/media/TV':'rw' -v '/mnt/user/Videos (Music)/':'/media/Videos':'rw' -v '':'/movies':'rw' -v '':'/tv':'rw' -v '':'/music':'rw' -v '':'/transcode':'rw' -v '/mnt/user/Books/plexmediaserver/config/':'/config':'rw' 'linuxserver/plex' e471c5195c971af47b098350770ade64a281e44a8c2ee0996f50ba5cd86b00a6 The command finished successfully!

Thanks for your help with this. I've been using the Plex docker for years now, but was never able to get Transmission working. serenity-diagnostics-20220802-0821.zip

OK, the Phaze Transmission plugin that I've been using for years won't work with the latest version of Unraid, so I'm going to try to get the Docker working. I'm not a linux guy, not a command line guy, and not even really that knowledgeable about torrent tech. I think I've figure out the mapping, and now my problem is that all of my torrents disappear every time I restart the Docker. Here's my run line: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='transmission' --net='host' --privileged=true -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'TCP_PORT_9091'='9091' -e 'TCP_PORT_51413'='51413' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/appdisk/transmission/config/torrents/':'/watch':'rw' -v '/mnt/user/Books/Audiobooks/':'/downloads/Books/Audiobooks':'rw' -v '/mnt/user/Books/Comic books/':'/downloads/Books/Comic books':'rw' -v '/mnt/user/Books/eBooks/':'/downloads/Books/eBooks':'rw' -v '/mnt/user/Movies/':'/downloads/Movies':'rw' -v '/mnt/user/Sounds (music)/':'/downloads/Music':'rw' -v '/mnt/user/TV/':'/downloads/TV':'rw' -v '/mnt/user/Videos (Music)/':'/downloads/Videos':'rw' -v '/mnt/appdisk/transmission/downloads/':'/root/Downloads':'rw' -v '/mnt/appdisk/transmission/config/':'/config':'rw' 'linuxserver/transmission' dc1d35e8167941bc3377c612ba9755b2e8a6de1b46a94f92f806598463819f80 I want to use the Transmission Remote GUI to manage my torrents, and not use a "watch folder," whatever that is... I most recently mapped that "/root/Downloads" path because it's in the Remote GUI, and I thought that might be where it stores all of the torrents for it to remember, but that doesn't seem to be it. Anyone have any hints?

No doubt. I think I might grasp the concept. I'm playing around with it now, and it looks like I've got it working. The problem I had before was that I was mapping things in the remote GUI, and then also in the Docker. I've got that straightened out, and I'm able to seed a torrent, but: When I stop the Docker and start it back up, all the torrents are gone. It looks like I pointed my Docker version of Transmission to the same config that I was using for the plugin version of Transmission, so I'm gonna mess around with changing that. I'm going to post in the Docker thread since that's what I'm working on now.

Hmmm... Last time I tried to get it working, someone said it wouldn't work like that. I'll try again.

More accurately described in my OP: won't work with the way I have my media split up into different user shares.

Yeah, the Docker just won't work with my server. I guess I'll just stick with 6.9.2. That sucks.

I just rolled back to 6.9.2 and it works fine. Is there some new setting that will allow it to work? I've tried getting the Transmission Docker to work, but it doesn't seem to like my Unraid setup (I have a different user share for each type of media).

Finally getting around to formatting my Reiser FS formatted drives to XFS. I'm sure there were more efficient ways to do this, but here's where I'm at now: I've used unBALANCE to move just about everything off one of my RFS drives to my new big XFS drive. But there's still some stuff that it couldn't move. A couple of temp files, and maybe some directories? Here's a screenshot from within the unBALANCE GUI: Is it likely safe to reformat that (nearly) empty drive? If so, what are my next steps? I'm a "set it and forget it" type of guy, so I have to learn how to mess with these disks every time I need to change something. After I stop the array, is it a simple option in the GUI to just reformat the empty disk?

Right. I guess I wish there was a way to make the notifications based on actual space instead of (or in addition to) a percentage. 5% free space on my 18TB drives is a LOT of space. Way more (it seems to me anyway) than needed for overhead. 5% free space on a 500GB drive is a different story. I don't know what kind of overhead Unraid needs to be happy, but 900GB (5% of 18TB) seems excessive. So, I've just been taking the low disk notifications with a grain of salt, but I do wonder what level of free space is actually needed.

Yeah, I just never considered a disk with 400GB of free space to be "full." Everything's still working fine, but UnRaid is giving me low disk space warnings. I've been ignoring them, but now I'm wondering if I should take them more seriously.

How much space does it need? I'm getting low disk space notifications that my 10TB drives only have 300GB or 400GB free, which seems like a lot of overhead space to me. I'm upgrading one of my 4TB drives to an 18TB right now (mostly so I can convert my Reiser drives to XFS). Should I worry about keeping more free space per drive? Does it need a certain amount of space, or a certain percentage of space?