Hi, new here and currently on my first week of the trial. Everything was going well until last night when I got this error. Can someone tell me if this is something to worry about, and also perhaps tell me where to look as to what might be causing this.

 

I don't know if this is related but last night I made the mistake of setting my array to use the cache disk which I thought it would use for writes only but it seems it was also pulling down data from the array for reads and when I got up this morning the cache was full with a bunch of out of space errors on the cache. I have since moved everything back to the array and turned off use cache but the above error "call traces" still persists. Again I dont know if this is even related.

 

Thanks

 

arrush-db-diagnostics-20171029-1508.zip

The actual trace is from the docker.img being corrupted.  Easiest action is Settings - docker - stop the service - Advanced view - delete the image - restart the service - apps tab - previous apps section - reinstall

 

15 minutes ago, arrush said:

I made the mistake of setting my array to use the cache disk

You probably set the shares on the array to Use Cache:Prefer which results in that action.  Use Cache:Yes puts new files on the cache and then mover moves it to the array.

 

21 minutes ago, Squid said:

The actual trace is from the docker.img being corrupted.  Easiest action is Settings - docker - stop the service - Advanced view - delete the image - restart the service - apps tab - previous apps section - reinstall

 

You probably set the shares on the array to Use Cache:Prefer which results in that action.  Use Cache:Yes puts new files on the cache and then mover moves it to the array.

 

 

So what I'm trying to figure out is why those files ended up on the cache drive as I didn't access them, is it possible plex ran a library update overnight so it moved them from the array to the cache? So if I set it to "yes" it will only be a one way from the cache to the array in the evening while mover is running?

 

I'll do the above to fix the docker.img, could this have been caused by the maxed cache drive? Also which file in the .zip did you look at to come to that conclusion, hoping to do my own analysis next time