Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About ksman75

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm using the linuxserver.io container. You're using the Limetech container. Not a big difference. Limetech has less options to screw up, LOL. At the bottom of your screen you have the "Add another Path, Port, Variable, Label or Device" option. Click on that and you can add the path(s) you need, pointing to your actual media. It'll look like the next screenshot. The "Config Type" defaults to "Path", so leave it. "Name" can be anything you want. "Container Path" is what you'll see in Plex. Be sure to have the leading slash. "Host Path" is a drop down you can use to drill down to the path on your array path. If it helps, it's very similar to mapping a network drive in windows. You want to map your host path (/mnt/user/whatever) to a local path (/mymedia in this example) that Plex will see.
  2. You don't want to use /mnt. When you install Plex you have the following screen... Notice the three in red? These are the paths you want to use in Plex. You want /Movies for your movies, /TV for your TV shows, /Music for your music, etc. I add a path "/user1" that points to /mnt/user/media where all my media folders are. On my system, Plex looks like... On my system, it looks like this... I hope this helps
  3. Above you show 'split level' set to 'auto split any directory' - do you think it was like that before, when you had appdata existing only on array? Also, do you know if appdata/plex directory specifically existed on multiple array disks? Yes, that's how all my shares are configured. Yes, appdata was spread across all 14 of my array drives. What I'd like to ask you to do is leave all config exactly the way it is, except, change the Plex appdata mapping from: /mnt/cache/appdata/plex to /mnt/user/appdata/plex Sorry . It's not that I don't want to, but I've finally got it working, and don't want to invest any more downtime, in the event it starts failing again. I hope you can understand this from my perspective.
  4. My original configuration didn't use or have cache at all. Plex Config was set to /mnt/user/appdata/plex. Appdata (and all other shares) was configured to not use cache. After updating unRaid to 6.7.0, the database corruption started. While trying to find a fix, I found this link: https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md. Q/A 7 seemed to describe the problem...see below. I rolled unRaid back to 6.6.7, added a single 240GB SSD cache drive, set appdata to "Cache Only", deleted the Plex folder in appdata, and reinstalled Plex. I ran this configuration for two weeks to make sure it was stable, then updated unRaid to 6.7.0 on June 13th. It has been one week today, running under 6.7.0, and I haven't has a single problem. I'm running several of the "Community Applications" plug-ins, and several more of the "Dynamix" plug-ins. I haven't made any changes to the plug-ins. I use "CA Backup / Restore" to backup my appdata daily, and haven't made any changes to it either. Hope this helps... Q7. I am seeing corruption with the applications database or issues when attempting to run Lidarr/Radarr/Sonarr/Plex/PlexPass, what could be the cause? A7. Certain applications are not compatible with FUSE, which is part of unRAID, FUSE is used to join or fuse (thus the name) multiple disks together to create a logical view of your media. The FUSE system is seen when you browse any share with /mnt/user/ in the path, such as /mnt/user/appdata. Due to this limitation certain apps need to have their configuration files defined on a non FUSE share, to do this follow the procedure below:- Stop the docker container that has the issues Left click the icon in the unRAID Web UI and select 'edit' Click on the toggle to switch to 'Advanced View' (top right) Scroll down to the path defined for /config and change it:- from /mnt/user/appdata/<container name> to (if you have a cache drive):- /mnt/cache/appdata/<container name> or (if you do NOT have a cache drive):- /mnt/disk<number>/appdata/<container name> Click on 'apply' to save the change Check the application is running. Note:- If you do NOT have a cache drive and you switch to a specific disk then you may need to reconfigure the application from scratch.
  5. The original Plex config was /mnt/user/appdata/Plex. The new config is /mnt/cache/appdata/Plex. I also changed appdata to be cache only. I won't say this is the solution for everyone, but it is working for me. It's been a week, and I haven't had a single problem. Before making these changes, it would corrupt within hours, if not minutes.
  6. So, it's been one full week since my last post, and everything is still running smoothly.It seems that moving appdata to cache/a single dedicated drive may be the fix for Plex corruption.
  7. I rolled back to 6.6.7 on May 31st, and haven't had any problems since then, which should come as no surprise, since the problem seems to follow 6.7.0. I had read that spreading Plex over the array could cause the corruption problem, so I installed a 240gb ssd when I rolled back and set appdata to cache only plus I edited all my docker containers to use /mnt/cache/appdata. To get appdata on to the cache drive, I used MC (midnight commander) to move appdata from all my shares to cache. I scoff at Triskaidekaphobia so on the 13th, I upgraded to 6.7.0 to see if forcing appdata onto the cache drive would eliminate the corruption problems. So far, I've been lucky, and haven't had any problems. I just hope it lasts, lol. I'll post an update when it crashes again, or in a couple weeks to update my success
  8. Just a suggestion, and I'm no expert by any stretch of the imagination... Assuming you're using Docker (you didn't say), and your plex folder is named 'Plex'. Stop plex. Rename or move the 'plex' folder in appdata. Uninstall plex. Reinstall plex. See if everything is working. If it is then you have two choices... Sit back and let plex do it's thing. Yeah, I know, a PITA, but this would be my suggestion, or... Stop plex. Delete (no need keeping it at this point) the 'plex' folder. Rename or move your new 'plex' folder, the one you created in step 4 above, to its original name. Restart plex. You should be back to where you were in step 5 above. Good Luck
  9. Cool! That's all I really needed to know, Safety over Speed any day
  10. My real question is... If I replace one drive (5TB to 6TB) at a time, will the new parity drive(s) be limited to 5TB, or will I get the full 6TB after I install the second drive. I'm not sure how that works, and that's my main concern. I don't want to be stuck with 6TB drives only having access to 5TB.
  11. I'm running two 5TB 7200 RPM parity drives and want to swap them with two 6TB 5400 RPM drives due to heat issues. What's the recommended route I should take? Is it recommended to replace them both at the same time, or one at a time, if that's even possible? Seems to me that both together would be the best route to take, but I would like some feedback before I do it. TIA
  12. iilied posted his logs from plex. Haven't seen anyone post the syslog or Docker logs. I haven't checked my syslog, but my Docker log wasn't very helpful. Plex either starts normally, or it goes into an infinite loop, something like "Starting Plex Media Server", but Plex never starts.
  13. Downshot is after 3 days error free, then crashing, I'm bats%#t crazy, and afraid to update unRaid in fear that the next update will have the same problems. As a side note, last night, I went back to unRaid 6.6.7, but...I deleted the share, appdata, installed a SSD (cache) drive, and configured appdata to use cache only. I restored appdata from a backup, and rebuilt PLEX from scratch. Now I have the conundrum of staying with 6.6.7 or updating to 6.7.0.