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.

johnnie.black & mr-hexen, you guys are on it...thank you both for the rapid response!!! All is good to go now & I've started the parity check...which I'm expecting to complete in about half the time (give or take) compared to the avg of 151/2hrs from before. The MAIN tab & system devices are now both displaying the HDD's serial#. I assume this is how most unRAIDers have their's displayed but I knew nothing different since that was my first setup. A question still lingers for me though, was there a setting that I could have altered with the 3ware card's config that would have displayed my drives differently/properly?

Hello all, you've got a Noob here. I've been enjoying unRAID for the past 7months & have been using the 15bay Rosewill setup with a 3ware 9650SE-16ML RAID card (15 HDDs for storage/parity & 1 SSD for cache). All has been good2go, aside from the 3Gbps limit of course. However, in my attempts to somewhat future proof the setup, I've recently acquired a 36bay Supermicro system from eBay with a LSI SAS 9211-8i HBA card (IT mode) & two SAS2 expanders already installed. I ran a few tests before attempting to migrate & felt confident after reading a few posts as to how to proceed with the migration. I took screenshots of the MAIN tab beforehand & the transition went pretty smooth up until it was time to reassign the SSD/HDDs. I didn't pay much attention before beginning the process/past 7months but it seems that the 3ware RAID card assigns an alphanumeric "identifier" which doesn't match up with any of the drive's serial#s. This became apparent after noticing that the LSI card displays the actual serial# to reassign the original drives. The alphanumeric identifier won't match up. I even tried to assign every drive in the drop-down to a few of the slots but no love...always indicates that it's a "Wrong" match. I've searched for a solution before posting & have yet to come across anything related. I'm thinking that I'd first have to switch everything back over to the 3ware RAID card and alter an unknown setting in the card's config utility. I've attached 2screenshots; #1 is the 3ware card & #2 is the LSI card with the drop-down. I do have all the data already backed up but has anyone come across this issue? Is there a known solution without having 2blow out all my data & start over? Thank you in advance for any advice! Sent from my Galaxy S5 using Tapatalk