October 6, 201312 yr No go. When I delete a file and hit refresh, it doesn't acknowledge that it has been deleted. There is no yellow exclamation mark like the guide says. How about a "Deep scan" and then emptying the trash? Did you delete the file from your user share? I've had issues where I delete a file for a disk share and it's on another disk... Was back on one of the early 5 betas, but I always use user shares now. I also have the "empty trash after scan" option checked... That keeps my library clean automatically.
October 7, 201312 yr confirmed, not showing any update available Just open the plex updater plugin setting page and update the plugin and it should work again.
October 7, 201312 yr Just Upgrade the PLG again and then the new plexpass version will be there Benni-Chan upgraded the Plg yesterday evening
October 7, 201312 yr Is there a way to have the PLEX/Library and PLEX/Temp files on another flash in the unraid environment? Reason is, I have those directories pointing to disk11 currently, and it seems like that disk does not spin down even when no users are accessing the disk or PMS, anything, period. I was thinking about getting an SSD, but I have a few flash drives here that would serve the purpose provided it can work that way. Perhaps some suggestions would help, Thank you
October 7, 201312 yr You can use anything you can get to mount. I see no reason you can't get another flashdrive to mount and then point PMS at that. However I do see a reason not to use a flashdrive for this purpose because of their limited endurance. My solution was to use an old SSD I had and mount it outside the array. I didn't just use it as my cache drive because I already have a cache drive (640GB WD black) and the SSD would have been too small for my needs anyway. To make mounting drives outside the array easier, there is SNAP which has been recently updated for Unraid v5 though I do not personally use it because I worked out my GO script to mount my drive before SNAP was updated.
October 7, 201312 yr Hm, yes I was considering flash drive, because looking at my case I don't even know if I can mount a SSD properly even with the bracket. I don't like my disk11 being spun up for what I assume is 24/7. I will have some thinking to do to try to remedy this problem.
October 7, 201312 yr heck, if not a bracket in a drive slot in the case (and you can always buy the right adaptor if needed) then just Velcro is to the floor / side panel. It is not like it will create noise from vibration and SSDs are darn light.
October 7, 201312 yr I was just going to use a 16 or 32gb flash drive, but now I don't know. Might just have to go SSD :-/ Don't like my data drive just running all the time
October 8, 201312 yr That's the spirit!!! The nice thing is, it isn't like you need a huge SSD so it doesn't have to cost you much. Heck you don't even have to go for a speed demon either since really even the slowest SSD will read/write much faster than you'd need for Plex and you'd see zero benefits from worrying about how fast it is.
October 8, 201312 yr That's the spirit!!! The nice thing is, it isn't like you need a huge SSD so it doesn't have to cost you much. Heck you don't even have to go for a speed demon either since really even the slowest SSD will read/write much faster than you'd need for Plex and you'd see zero benefits from worrying about how fast it is. In normal usage you will not see a difference, however when performing a full library re-build or similar, PMS writes a lot of small meta data files and a SSD is significantly faster than a spinning drive. I noticed this when I upgraded my Win8 PMS to SDD. And to repeat it: cache disk (cache-only share) is the recommended install location for Plex Media Server. You should never install anything doing continuous writing onto a flash usb drive.
October 8, 201312 yr [shrug] I'm sure there might be some benefits. I even started to write to that effect but changed my mind because I considered the bottleneck to be scanning the media files, requesting/receiving metadata, and (now) creating the transcoded index images. The final bit of writing that data to the app-drive seems to me not a real limiting step. Doing all that on a Win8 machine, if the SSD is also the OS drive, might make a bigger difference as the drive has other duties to perform beyond ingesting PMS data [shrug again]. In any case, using an SSD is sure not going to slow things down and there is the added benefit of no spinning platters 24/7 which to me is the REAL benefit of an SSD for an app drive with PMS.
October 16, 201312 yr You can use anything you can get to mount. I see no reason you can't get another flashdrive to mount and then point PMS at that. However I do see a reason not to use a flashdrive for this purpose because of their limited endurance. My solution was to use an old SSD I had and mount it outside the array. I didn't just use it as my cache drive because I already have a cache drive (640GB WD black) and the SSD would have been too small for my needs anyway. To make mounting drives outside the array easier, there is SNAP which has been recently updated for Unraid v5 though I do not personally use it because I worked out my GO script to mount my drive before SNAP was updated. Hello.. I tried mounting an SSD outside my array using SNAP for this very same cache drive issue with PMS. However, I'm having a bit of trouble so hopefully someone could lend some assistance. SO, I added my 64gb SSD, mounted it using snap, and pointed plex library files to: /mnt/disk/myshare name/plex /mnt/disk/mysharename/plex/tmp I added my user files to plex without issue then plex scanner began to run. Then BAAM, errors in Log stating: "Out of memory: Kill process" PMS web GUI then becomes unresponsive so I restart unRAID and open PMS library share on SSD and all library files have disappeared. I tried again a few more times with the same exact results. I then quit and pointed PMS library back to cache, all is normal again except that cache still won't spin down. ...any ideas on what or where I may be doing wrong? ..by the way, I'm running a 24TB 11drive array with cache and 2GB memory stick. unRAID memory cache seems to be taking up about 65% of my memory at all times even during idle. I will attach my log shortly
October 16, 201312 yr This is what I think is happening: The share is not being pointed to the SSD and is instead being created in RAM. Then Plex scanner starts to run and fills up the "drive" with the data files until it fills your memory and you start getting the errors. Restarting fixes the issue by clearing out ram which is what your seeing when the "library files have disappeared." One way to test this is to run this command on the share that is suppose to be on your SSD. stat -f -c '%T' /path/to/share It should output the filesystem, if it outputs "ramfs" then its being created in memory. What is most likely happening (if I remember correctly from when others had these types of issues), plex is being installed and trying to write to the share before SNAP can actually mount the drive. If that happens the path plex writes to will be created in memory and SNAP will not be able to mount the drive.
October 16, 201312 yr and if that ends up being the issue, and there is no SNAP/Plex workaround, I can give you the two (iirc) lines of code I added to my GO file to create mnt on the SSD. Mind you my SSD was already formatted with RSF since at one time I made it a cache drive, and I can't help with manual formatting though I bet Influencer can. Mounting in GO is easy and has worked great for me for the last 6 months. You do lose the export of the drive but I have no need to browse my plex folder from my PC. I think there is a way to manually modify your smb.conf to export the share but I never searched hard enough for that info. Oh yeah and either way, I see no reason to create a user share and add that extra layer. Everything is going to be limited to the single SSD so you might as well just create the folder on the disk and not worry about having user shares. Anyway those are my knee-jerk thoughts, the first step is to see if there is a known solution using SNAP.
October 16, 201312 yr Jumper Alex... Thanks for the reply! I kinda figured that plex library was being created on Memory when after restart the library was gone, but I wasnt 100% sure. While plex library was being built, I periodically checked the plex folder on the SSD share and saw that it was steadily increasing in size. To your point; prior to even starting plex, I made sure SNAP had mounted drive and I saw the 3 Green indicators saying the drive was mounted and shared. I did some file transfer tests through SMB from my windows PC to plex using the plex share UPN and the file transfer went well. I actually saw the files in the plex folder on the SSD share.
October 16, 201312 yr hmmm are you sure your path is correct? I'm assuming first of course that it is a type that your two paths roots are different. But beyond that, are you sure they are right? /mnt/disk/myshare name/plex /mnt/disk/mysharename/plex/tmp And did you confirm that the actual disk was seeing an increase in size? and not just the exported SMB share. I can't say for sure that you aren't still looking at a share created in ram [shrug].
October 17, 201312 yr hmmm are you sure your path is correct? I'm assuming first of course that it is a type that your two paths roots are different. But beyond that, are you sure they are right? And did you confirm that the actual disk was seeing an increase in size? and not just the exported SMB share. I can't say for sure that you aren't still looking at a share created in ram [shrug]. Im pretty sure.. I checked it by: 1.) Creating sharename for my SSD in SNAP, I called it "PlexShare" then I mounted and shared it. I had already formatted the SSD to reiserfs(not sure if that matters, NTFS should work too I believe) 2.) Opened PMS plugin and entered these path names: /mnt/disk/PlexShare/plex /mnt/disk/PlexShare/plex/tmp 3.) Started Plex 4.) Opened Explorer in Windows and pointed to share using the UPN: "\\tower\PlexShare" and saw that the plugin had added the "plex" folder in the share 5. Opened PMS web GUI and began to add my media shares to my library and plex began to scan, while scanning, I went back to Windows Explorer and kept right clicking the "plex" folder/properties, and saw the size of the folder steadily increase. So I thought I was golden! BUT, five minutes later I got that Memory Issue and missing library after unRAID reboot!
October 17, 201312 yr well hell, you've got me stumped. not sure a syslog will show anything. Might be worth looking at TOP in a console while the scanner is running to see what is happening with memory.
October 17, 201312 yr Well... You're a saint for working with me on this one.. I sincerely appreciate your time and responses! I had run a TOP inquery during the second and thrid attempts at this.. Plex scanner had my CPU percentage at between 65-75%, the subsequent processes amounted to my CPU% all the way to 100%. Memory on Plex is hard for me to guage since unRAID memory cach always takes up at least 1GB+ of memory all the time even during idle times with all drives spundown and zero file activity. During my search here in the forums, members have reported this problem also with other plugins(SABnzbd, SickBeard, CP) etc...when plugin share is mounted outside of the array. My first thought when this happened was just to add more memory, but the responses here in the forums seem to advise against this saying it would do little to fix the issue. So, my next plan is to do a MemTest just to give me piece of mind. Then add a larger SSD(128gb) as my cache drive to address the Plex Cache drive spindown issue. Thanks againd for your assistance brother!
October 17, 201312 yr Well before you go spending money, you should at least try mounting the drive manually via the GO script. Here is mine: #Mount SSD as appdisk mkdir /mnt/appdisk mount -rw -o noatime,nodiratime -t reiserfs /dev/disk/by-id/[found in /dev/disk/by-id/]/mnt/appdisk And by "found in /dev/disk/by-id/" I mean open a console and go look at the contents of /dev/disk/by-id/, find your SSD and copy the entire string. For example, mine is (slightly munged) "ata-OCZ-VERTEX2_OCZ-0E6807YCXXXXXXWD-part1" You choose "part1" because you want to mount the partition. So once "appdisk" is mounted, i made two directories within appdisk, "app" and "tmp" and i then told PMS to point to: /mnt/appdisk/app/plex/Library /mnt/appdisk/tmp
October 17, 201312 yr Oh yeah and either remove SNAP for the time being, or at least tell it to stop trying to mount that drive to avoid any chance of conflicts.
October 17, 201312 yr Okay.... I'll give it a shot! Not too familiar with Linux scripting, but I have to start somewhere!! Ill report back with my results
October 17, 201312 yr Just to be sure, in the code I posted above, you should NOT include and of the quotation marks or square brackets.
October 17, 201312 yr Okay.... I'll give it a shot! Not too familiar with Linux scripting, but I have to start somewhere!! Ill report back with my results Out of curiosity, did you run the command I posted to see if the share created by SNAP was in fact being created on the SSD or in ram? Unless it was a typo or wrong path on your part it could be a possible bug in SNAP.
October 17, 201312 yr Okay.... I'll give it a shot! Not too familiar with Linux scripting, but I have to start somewhere!! Ill report back with my results Out of curiosity, did you run the command I posted to see if the share created by SNAP was in fact being created on the SSD or in ram? Unless it was a typo or wrong path on your part it could be a possible bug in SNAP. [scratching head] yeah Ditto this because as I reread your post above (#1366) I'm still not sure you've confirmed you aren't hitting a ramdisk. When I first replied to it I remember my thought was that you were for sure hitting the SSD, but rereading it nothing there says for sure you really are. Just that you are hitting a mnt point called "disk" that has a folder called "Plexapp" Mind you, you might be "doing it right" in SNAP and as Influencer says, it could be a bug. Realize that all the checking you did via windows explorer just shows that files are being put into the share. That is no indication where that share really resides. I think I was possibly fooled by this line, "I periodically checked the plex folder on the SSD share and saw that it was steadily increasing in size" which I took to mean you were looking at the share via UnRaid gui (that is how I used to check for transcoding since my SSD is not exported to SMB) which in theory should only show shares on physically drives and not ramdisks. But now I suspect you meant you were checking it via win explorer. Is that correct?
Archived
This topic is now archived and is closed to further replies.