May 18, 201610 yr Hi folks - returning to unRAID after being with FlexRAID for 4 years. Like what I see so far! I've installed the official limetech Plex docker but can't reach the webgui (or I get 'File not found'). Looking at the Plex Logs I a see: May 18, 2016 14:39:35 [0x7f3f9de3b700] INFO - Plex Media Server v0.9.16.6.1993-5089475 - ubuntu PC x86_64 - build: linux-ubuntu-x86_64 ubuntu May 18, 2016 14:39:35 [0x7f3f9de3b700] INFO - Linux version: 4.1.18-unRAID (#1 SMP PREEMPT Thu Mar 3 13:08:41 PST 2016) May 18, 2016 14:39:35 [0x7f3f9de3b700] INFO - Processor AMD FX-6100 Six-Core Processor May 18, 2016 14:39:35 [0x7f3faa145840] DEBUG - BPQ: [idle] -> [starting] May 18, 2016 14:39:35 [0x7f3faa145840] DEBUG - Opening 20 database sessions to library, SQLite 3.8.9, threadsafe=1 May 18, 2016 14:39:35 [0x7f3faa145840] INFO - SQLITE3:0x10, 283, recovered 284 frames from WAL file /config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal May 18, 2016 14:39:35 [0x7f3faa145840] DEBUG - Running migrations. May 18, 2016 14:39:35 [0x7f3faa145840] DEBUG - ChangestampAllocator: initialized to 0 May 18, 2016 14:39:35 [0x7f3faa145840] ERROR - Error: Unable to set up server: bind: Address already in use Not sure why it would run into this? Any ideas? Also, every time I install another Docker image, e.g. SickRage or SickBeard I end up with an orphan image in docker? Thanks! Alex
May 18, 201610 yr Author Nope - I wanted the appdata (i.e. Plex library) protected....? The example showed it setup under a user share so assume that should work? If I set it to cache only does it actively run off that but the mover still replicates it to the array overnight?
May 18, 201610 yr Community Expert Nope - I wanted the appdata (i.e. Plex library) protected....? The example showed it setup under a user share so assume that should work? If I set it to cache only does it actively run off that but the mover still replicates it to the array overnight? this is likely to cause problems when the files get moved off the cache disk. If you want protection of files on the cache then you should look at using a cache pool instead.
May 18, 201610 yr Author Thanks - not worried about the cache per se, I just don't want the Plex library permanently on the cache. Cheers.
May 18, 201610 yr Community Expert Thanks - not worried about the cache per se, I just don't want the Plex library permanently on the cache. Cheers. in which case I would suggest creating a share outside appdata for holding the library, and pointing Plex to that for the library. In the past most users have seemed to WANT to keep the Plex library on the cache for performance reasons.
May 18, 201610 yr It's not recommended to use the appdata on your array and indeed some containers will not work with this. (Also I'd recommend mapping the appdata to /mnt/cache/appdata rather than /mnt/user/appdata/ (the appdata share still needs to be set to cache only) Have a read of these topics. And install this Also there are dedicated support threads for the containers so try to use those rather than posting new topics. The authors are more likely to see your post in the appropriate thread.
May 18, 201610 yr Author Thanks appreciate the help - will post on the docker thread, didn't know that was there. Can't say I like having the Plex Library on one unprotected drive and it seems a bit daft to me really - I would think i/o perf off the array would be fine for a relatively small db like plex but hey ho and purchasing another drive just to pool the cache seems like overkill to me personally. I tried setting the share to cache only, no impact sadly....
May 18, 201610 yr Why do you care about protecting the plex library when it is only metadata that can easily be rebuilt. The real items of interest are the media files on your array which is already protected.
May 18, 201610 yr Author Always been a pain when I've re-built a library from scratch and then had to set what we've watched / haven't which usually causes confusion in the household!! That's why I'd prefer to have it protected, that and the cache is my oldest drive so odds are, the next most likely to fail so its a consideration, hence I'd prefer to keep permanent data off it. Fine with it as a transitory drive as any failure of it would be an incremental loss. Truth be told, very little data on my system is that important. The important data is backed up, the media can always be downloaded again if any were to be lost one day.
May 18, 201610 yr If you want the appdata on the array, in share settings, set it up so that its confined to a single disk, and refer to the /config folder as /mnt/diskX/appdata/plex Symlinks that Plex uses are not compatible with /mnt/user
May 18, 201610 yr Community Expert But don't be surprised if plex spins up your parity drive. It often like to write to its library.
Archived
This topic is now archived and is closed to further replies.