kleyden

@johnnie.black I just noticed that my cache drive is not mounting after the 6.4 upgrade...which makes sense as to why my VMs are not available. Any advice or questions would be appreciated.

@johnnie.black I have the same issue as @Meloccobut on top of that my VMs are no longer available after upgrading to 6.4 roughly 2hrs ago. I noticed that my vdisk folder is no longer present & there has been no change after a reboot or power down & up. unleyden-diagnostics-20180116-0251.zip

shares => appdata Use cache disk: Only Enable Copy-on-write: Auto

@CHBMB Essentially that's the same appdata folder with a different path; but that did it brother man...plex seems to be functioning as expected again!!! So, does that mean their is still some residual data linked to the initial path, even after I deleted it through MC, that was causing this to not function?

@CHBMB I should have known that's what you were looking for...I had recently deleted it from appdata. I've re-installed the docker & it seems to have the proper permissions... root@unLeyden:~# ls -la /mnt/user/appdata/ total 16 drwxrwxrwx 1 nobody users 26 Mar 5 19:27 ./ drwxrwxrwx 1 nobody users 68 Mar 4 00:21 ../ drwxrwxrwx 1 nobody users 14 Mar 5 19:26 PleXa-SauRus2/ BTW, the docker is still not working

here you go @CHBMB, root@unLeyden:~# ls -la /mnt/user/appdata/ total 16 drwxrwxrwx 1 nobody users 0 Mar 5 17:40 ./ drwxrwxrwx 1 nobody users 68 Mar 4 00:21 ../

I had the linuxserver.io version of plex running very smooth for a little over 2wks. I can truly appreciate the snappy navigation of plex in a docker & ease of linuxserver.io's update process...it worked wonderfully!!! However, the docker is no longer launching; my streaming devices cannot find the server & I keep getting "This site can't be reached" (chrome & IE) when attempting to access the plex WebUI. I've tried an un&re-install of the docker, but no change. The plex docker log is continuously displaying "Starting Plex Media Server."...partial log attached. I even tried the binhex & limetech docker versions as well...still no love. I can only think of one thing that I've recently done that could be affecting the docker from launching. Which was my "attempt" to setup a rsync session with another local storage server; without having to input a ssh password each time & also binding transfers over a 10GbE direct connection. I digress, I'm not at all good with linux so I followed along with a youtube tutorial. One of the commands was **chmod600/root/.ssh/authorized_keys**. I didn't know at the time but as you linux vets may very well know, the chmod command pertains to the access permissions (read/write in this case). A member from another forum mentioned having to modify his chmod to get his linuxserver.io plex version working. It got me thinking that the key generation/transfer or chmod settings in the youtube tutorial had something to do with derailing my unRAID plex experience :-( I could very well be off base with this theory & nothing during the process is the culprit but any feedback/assistance would be GREATLY appreciated as I would love to be pleXing again through unRAID. In the meantime, I've been using plex through the other local server, but the unRAID hardware/docker makes the experience a lot snappier. Another thing, the rsync setup didn't fully work as anticipated :-( I was able to ssh in the other server (putty) & make some transfers but haven't been able to effectively bind the transfers to the 10GbE direct connection. This the least of my concerns at the moment though.