February 17, 20179 yr I am trying to figure out why this happens, but whenever Plex does a scan it will max out the read capabilities of my cache drive and the entire system will become unresponsive. I have a SSD setup as my cache drive, and all my dockers get installed to /mnt/user/appdata. The appdata share is set to cache only, which is the SSD. So because Plex is maxing out the Read of that drive, none of my other dockers will respond, including Plex itself. See screenshots. - How do I stop this from happening?
February 17, 20179 yr all my dockers get installed to /mnt/user/cache/appdata. The appdata share is set to cache only Are you sure about that path? I suspect it's a typo but do you mean /mnt/cache/appdata (which is actually equivalent to /mnt/user/appdata since appdata is a cache-only share)? Your diagnostics (Tools -> Diagnostics) would shed more light on your question.
February 17, 20179 yr Community Expert all my dockers get installed to /mnt/user/cache/appdata. The appdata share is set to cache only Are you sure about that path? I suspect it's a typo but do you mean /mnt/cache/appdata (which is actually equivalent to /mnt/user/appdata since appdata is a cache-only share)? Your diagnostics (Tools -> Diagnostics) would shed more light on your question. If instead you have it set to /mnt/user/cache/appdata like you said, then you have accidentally created a user share named "cache" with a folder named appdata in it. That share will have the default setting of cache-no, so it is on your array.
February 17, 20179 yr Author all my dockers get installed to /mnt/user/cache/appdata. The appdata share is set to cache only Are you sure about that path? I suspect it's a typo but do you mean /mnt/cache/appdata (which is actually equivalent to /mnt/user/appdata since appdata is a cache-only share)? Your diagnostics (Tools -> Diagnostics) would shed more light on your question. If instead you have it set to /mnt/user/cache/appdata like you said, then you have accidentally created a user share named "cache" with a folder named appdata in it. That share will have the default setting of cache-no, so it is on your array. Ah sorry, I had a typo. It is /mnt/user/appdata. I try to do everything to the user share and let the share control which disk gets used.
February 18, 20179 yr Community Expert Is it only after you add media to your library? My system does the same thing due to creating video preview thumbnails. Here is description from Plex server settings: Video preview thumbnails provide live updates in Now Playing and while seeking on supported apps. Thumbnail generation may take a long time, cause high CPU usage, and consume additional disk space. You can turn off thumbnail generation for individual libraries in the library's advanced settings.
February 18, 20179 yr Author Is it only after you add media to your library? My system does the same thing due to creating video preview thumbnails. Here is description from Plex server settings: Video preview thumbnails provide live updates in Now Playing and while seeking on supported apps. Thumbnail generation may take a long time, cause high CPU usage, and consume additional disk space. You can turn off thumbnail generation for individual libraries in the library's advanced settings. I disabled those when I setup the server, and they are still disabled. I even have it set to run scanner tasks at a lower priority. Is there a way to see what files exactly are being accessed during this time of high activity? If you look at the screenshot, it is doing a read... and with it being over 256MB/sec, it has to be the cache SSD drive and not my slower drives where the media is stored. Even after adding music this happens.
Archived
This topic is now archived and is closed to further replies.