which resulted in shield reporting running low on storage message. So, I thought there could be some issue with Plex and cleared the data fully once and re-setup my whole plex server from scratch. I made it a mandate only after setting the storage to external HDD I added my media libraries -
You might want to take a look at this support article that explains how you can expand the Shield’s storage and move Plex’ server data to that storage for it to grow happily ever after
Hi @tom80H, The storage location is already in external HDD, It’s not using internal storage, Even with that Plex Server is consuming around 8GB of Internal Storage
Do you have Detect Intro turned on for your TV library? There’s a known issue with where Plex stores this. It seems that regardless of where you store your PMS data, the detect intro data gets stored on the Shield.
It’s seems related to the Skip Intro feature. It’s a known issue among users, but I haven’t seen anyone from Plex comment on it. It’s a serious bug though, and needs to be sorted ASAP.
This really isn’t the issue though. There’s a bug with the Skip Into feature that’s causing Plex to fill up all the available internal (not adopted) storage on the Shield itself.
“Skip Intro” temporarily uses some disk space on the internal drive during it’s detection. This is a known issue and something that will be addressed in the next release (I’ve already written the fix).
8GB is a little suspect though, we only store data for one file at a time. How big are the source files?
Great to hear! Will the fix “restore” the previous lost space, or just fix the issue going forward? It cost me around 5gb. People in the Reddit sub are reporting similar high numbers.
This is good news. I’ve been active in another thread here about this problem as well as one I created on reddit. I seem to have worked around it for now over this last week after rebuilding my library with intro detection turned off. My cache folder keeps growing and growing though and since I never paid attention to it before I’m not sure what is normal in that regard.
Semi unrelated but I think the temporary transcode folder, especially on shield, should have a directory browser though (and on shield it should only allow you to choose folders PMS has write permission on). It’s very cumbersome for most people to figure out, for example, what folder is appropriate to put there especially for removable storage as the only way is to use a third party file manager to find out the ID of the drive and you need to “just know” that only the NVIDIA_SHIELD folder is writable to Plex on removable storage.
Honestly, I think when you choose the storage location on PMS on Shield, that the temporary transcode folder should automatically use that storage location without having to set it manually - this was the behavior that I automatically assumed would take place but it does not. No large files, or large groups of files, should use shield internal storage when you have set the plex storage location outside of internal.
This will be in beta momentarily, public by End-of-Day
(Re: storage picker. That would be nice, but is a fair amount of development effort for a one time perference change. I might look to add a quick pref that makes it easier on SHIELD
EDIT: It’s now in BETA and rolling out to everyone.