[HELP] Plex running in Nvidia Shield 2017 (Running out of storage)

Hi,
Last Week Plex occupy almost 8GB of my Shield Internal Storage -

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 -

But after a week, Again my Shield Internal Storage is full -

and It doesn’t allow me to update/ install any app. I don’t know if anyone else has been facing the same issue. I don’t find a fix for this issue.

PS: I have also disabled Preview thumbnails based on community feedback -

Server Version#: (Beta): 1.19.4.2902 Updated Jun 2,2020
Player Version#: (Beta): 8.2.0.18280 Updated Jun 4,2020

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 :wink:

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.

1 Like

Yes I have turned on Detect Into for TV library. Thanks for helping me figure out the issue. Hopefully they fix it soon.

is this issue reported? is there any tracker which I can follow to get updates?

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.

Hey,

“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?

1 Like

There could be approx 800-1000 episodes of the TV shows in total, Each file could vary from ~500mb to ~15GB per individual file.

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.

Yes, it will :slight_smile:

Is there an ETA for the next release? This issue is taking up 11gb on my Shield so I’m encountering all sorts of issues with Plex and other apps.

:+1: Cheers for that. Though it just occurred to me I asked you two question. Hopefully you said yes to the first one. :wink:

ETA: Tomorrow. I’m planning a hotfix release.

And yes, the fix will clean up existing storage as well as fix it going forward.

To explain the fix a little:

  • I’ve fixed a bug that would leave residual files around (when things fail)
  • Temporary files will now be about 50% smaller
  • We will start using the application cache space. Which will allow you to ‘clear cache’ at any point to clean up.
  • You will be able to change the ‘transcoder temp directory’ to your external storage (if you choose). Intro detection will now honour that preference.
5 Likes

Brilliant, that all sounds good.

Quick update:

I’m still trying for today, but it’s quite likely to slip into tomorrow.

2 Likes

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.

1 Like

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.

1 Like

That update worked perfectly and did just what it should. Thank you!

PS. An easy way to back up and restore our libraries on the Shield would be brilliant. Just saying. :wink: