So, I posted here a week ago asking for help on my Plex issue. Basically, my appdata was ending up as a User share. I think Squib indicated that the 20GB container was running over (possibly due to corruption or a bad path settings) and then it would then be converted to a User share. I tried reloading Plex and I think I got all the Paths correct but, I am still having the problem. Then, I noticed my Dashboard seems to indicate that I have a bad SSD for Cache2. If my Cache2 is acting as the mirror for Cache and Cache2 has an issue, is the Cache container converted to a User share? Does anybody else have problems with their SSDs? Also, is it better to go ahead and run the Plex /config on a User share instead of Cache?

First of all - your appdata IS a user share. That is not a problem.

 

What could be a problem on the other hand is that you have configured the Plex container to look for its configuration on the cache drive, without having set the appdata share to "cache only". Setting "Use cache disk" to "yes" will cause the files to be moved away from the cache disk to the array whenever Mover runs.

 

Still, you should absolutely investigate those SMART warnings...

So, you're saying that appdata should always be listed as a User share as part of a normal running Plex? I guess I didn't notice it before. What is the reason for the preference of running the appdata on Cache (SSD) instead of Disk?

So, you're saying that appdata should always be listed as a User share as part of a normal running Plex? I guess I didn't notice it before. What is the reason for the preference of running the appdata on Cache (SSD) instead of Disk?

Performance!  If on a data disk then the performance will not be as good as if run from the cache drive.

So, you're saying that appdata should always be listed as a User share as part of a normal running Plex? I guess I didn't notice it before. What is the reason for the preference of running the appdata on Cache (SSD) instead of Disk?

Performance!  If on a data disk then the performance will not be as good as if run from the cache drive.

And writing to an array data disk will also write to parity, actually reading both and writing both so even more slow.

So, you're saying that appdata should always be listed as a User share as part of a normal running Plex? I guess I didn't notice it before. What is the reason for the preference of running the appdata on Cache (SSD) instead of Disk?

 

If you create a share it will be a share. If you use a folder that is not a share, well, it won't be a share.

 

I have set up my appdata as a cache only share, with the plex configuration stored there. The main reason for me is that basic operations and browsing in a plex client won't require any of the array disks to be spun up.

If you create a share it will be a share. If you use a folder that is not a share, well, it won't be a share.

Not exactly.

 

If you create a share, it will be a top level folder on cache and/or one or more of the array data disks depending on the share settings.

 

Conversely, if you create a top level folder on cache and/or one or more of the array data disks, it will be a share whether you explicitly create it as a share or not. If you don't configure a share it will have default settings.

If you create a share it will be a share. If you use a folder that is not a share, well, it won't be a share.

Not exactly.

 

If you create a share, it will be a top level folder on cache and/or one or more of the array data disks depending on the share settings.

 

Conversely, if you create a top level folder on cache and/or one or more of the array data disks, it will be a share whether you explicitly create it as a share or not. If you don't configure a share it will have default settings.

 

Rather meant that it is not necessary to use a top level folder, and leaving unassigned devices as an option.

 

In any case, there seem to be at least two potential problems here. One is that Plex is expecting its configuration to be located under /mint/cache/appdata when the share is not cache only, and then we have smart.