September 30, 201312 yr Cache drive won't spindown when running PLEX. I know this has been addressed, but I can't seem to resolve my issue. I'm running 5.0 w/ PLEX as my only add-on. I run PLEX via the cache drive per the instructions posted in this forum. I believe PLEX sporadically accesses my cache drive and therefore prevents it from spinning down according to my UNRAID settings (1 hr delay). I disabled all logging/debugging via the PLEX/Web portal. PLEX is set to update my library every 24hrs. I have tested with and without PLEX installed. All UNRAID drives spindown according to their UNRAID settings without PLEX installed. With PLEX installed, the data/parity drives spindown and I can manually spindown all drives (including cache)...but shortly thereafter the cache drive (only) spins back up and I note both new 'reads' and 'writes' to the disk statistics. I've scoured the UNRAID and PLEX forums but cannot find the setting(s) for either UNRAID or PLEX I'm missing that would fix this issue. I'm running the latest updates for UNRAID and PLEX. Any help or direction towards help would be greatly appreciated. Syslog attached. Thanks. vader2k_Syslog_30sep13.txt
October 23, 201312 yr You and I both my friend. I've got the same issue as well. I'm thinking of buying a SSD drive for cache instead of using the 2TB 7200 RPM drive I am currently using.
October 23, 201312 yr Keep the 2TB cache and install the SSD as an independent app drive outside the array. That lets you save a few bucks by buying a much smaller SSD for the app drive than you could probably get away with as a cache drive. Just a thought.
October 24, 201312 yr Keep the 2TB cache and install the SSD as an independent app drive outside the array. That lets you save a few bucks by buying a much smaller SSD for the app drive than you could probably get away with as a cache drive. Just a thought. I only use the cache drive for Plex and nothing else. So, I don't really see any reason to keep the 2TB as cache. I think it would be more useful as storage.
October 24, 201312 yr Yes, If you aren't caching array writes, then your plan makes sense. As you might guess, many people are indeed still caching array writes so then the question is how best to bring an SSD into the picture for plex. Hence my initial advice.
October 24, 201312 yr You and I both my friend. I've got the same issue as well. I'm thinking of buying a SSD drive for cache instead of using the 2TB 7200 RPM drive I am currently using. That is what i did. pickup a 64gb from ebay $50 works great.
October 24, 201312 yr Another thing to consider is that once you start creating index files, which take a LONG TIME, it really becomes a smart idea to rsync your plex DB back onto the array in case your SSD takes a dump. *I* haven't done that yet, but it is on my list of things to do.
October 24, 201312 yr Another thing to consider is that once you start creating index files, which take a LONG TIME, it really becomes a smart idea to rsync your plex DB back onto the array in case your SSD takes a dump. *I* haven't done that yet, but it is on my list of things to do. I'm backing up my whole apps share just because of Plex db: #!/bin/bash date >> /mnt/disk1/backup/rsync/unraid/apps.date rsync -av --delete /mnt/cache/apps/ /mnt/disk1/backup/rsync/unraid/apps --exclude "Cache" --exclude "incomplete" --exclude "torrents" I copy this script to cron using /boot/config/go: cp /boot/plugins/custom/rsync-apps /etc/cron.weekly
Archived
This topic is now archived and is closed to further replies.