Yes, all media is accessed using a network mount.
BTW, when the 9.0.1+ Hotfix becomes available to your Shield, I recall seeing an alert that the “9.0.2” firmware was available to install. It was actually just the 9.0.1+ Hotfix .
1 Like
Your experience sounds like the known NTFS/exFAT issues Nvidia previously described.
Nvidia relies on Paragon, which develops software to allow operating systems access to files systems that the operating system does not support by default, i.e., Apple files systems, HFS+ and APFS file system support for Windows or NTFS support for the MacOS.
Paragon provides the NTFS/exFAT support the Nvidia Shield relies upon. Supposedly the new hotfix for 9.0.1 (First HotFix (33.1.0.291 deployed 2/16/2022) ) adds a new version of the Paragon NTFS/exFAT filesystem support. https://www.paragon-software.com/free/exfat-ntfs-fat32-hfs-android/
Inotherwords, sign up for the new hotfix and if the new filesystem driver works correctly you, in theory, should have PMS back.
2 Likes
See that Thread :
and use : click on first item and "“hold the Shift key down and click the last item”
and vote for that thread :
1 Like
Dolby Atmos not working after the update. Movie files with Atmos worked fine before the update.
On the new hotfix, PMS can’t seem to stay up for 24 hours, and have had several shield crashes while it’s just sitting there on standby 
NTFS external storage.
I installed the hotfix yesterday (Paragon fix); I did not Power Off the shield overnight. Today my PMS is still available.
I’m feeling dangerously optimistic!
Installed new Hotfix yesterday and all seems stable, including adding content. In order to keep my previous version going I stopped all overnight scheduled tasks. I’ve just turned those tasks back on and will report back on how that goes in a couple of days. So far so good for me. Hopefully it stays that way. Media is on an external NTFS USB drive attached directly to the shield. 
Plex app on iPhone just hangs/freezes when accessing PMS on Shield with USB 8tb storage. I don’t even get past the first screen.
Is this an extension of all the other issues that still persist?
My Shield has auto-updated even though I have auto-update turned off, the Shield is not used/touched and the remote in the cabinet… I have no choice but to install 9.0.1 now and hope for the best.
The nightmare begins.
Since Plex confirmed that hardware transcoding is broken on Android 11 in all flavors (i.e. for both the Shield TV (Pro) and even for clients), I am staying on Shield Experience 8.x (Android 9) for now since I am on PMS 1.23.x which does not have the HW transcoding issues.
Not sure how much hardware transcoding is transpiring in my case now (let me check Plex dashboard or logs to see if I can find any data on that - have not had to do that before, but I believe HW transcoding activity is logged), but I will wait till that is fixed (no ETA from Plex on that).
did you check audio settings on the Shield?
Can you be more specific as to what is broken? Does it transcode the audio, you get no sound, file won’t play at all, etc. Is passthrough enabled?
I dont have very much technical knowledge but I’ll explain the best I can. Before the update, when i would play an Atmos video file, it would work fine. When i change the volume on my receiver, a small window appears on the screen and it tells me what the volume is and what sound profile is being used. For example, it would say “32, Dolby Atmos”. After the update I resumed playing an Atmos video file and it said something like “32- TrueHD 3/4”. I checked another video file that I know has Atmos and the exact same thing happened. I checked the Plex settings and the Shield settings and couldn’t find anything that appeared wrong. I made some temporary changes to some of the audio settings and that didn’t fix it either. I have a 7.2.4 system so having the Atmos track is very important to me. No changes were made to my receiver so I don’t think that is the culprit. I watched a movie on Disney+ on the Roku that has Atmos and it worked fine. So I’m confident the issue is with the Shield and/or Plex.
I had a similar issue, though several PMS versions back. For me, changing the audio “passthrough” setting back and forth resolved it.
I haven’t revisited it since to see if that’s still a thing as there are too many other bigger issues I deal with in the times I sit down to do TV stuff.
Just got a PMS update to 1.25.3.5575
Anything new?
FWIW, after doing the uninstall/restart/reinstall/restart shuffle, I did get PMS to allow me to move my data location to my external 8TB WD, this morning. I downloaded PMS from the Google Store, this time. Not in the same location as the shield to check the actual PMS version number (so whatever is currently on the Google store), but I can add some libraries and get a scan running from here.
One more report.
Preface - My PMS is installed on an external NTFS formatted HDD. I have 2 identical Seagate Expansion 4TB connected to both USBs (both are set to be always on, even when the Shield sleeps). I don’t have Plex Pass, so I don’t know about HW transcoding.
On 9.0.1. No hotfixes, only officially pushed stuff. My server has been running for 52 hours straight after I disabled scheduled tasks. Doing manual scanning from my phone without any issues so far. If I didn’t know there was a problem I wouldn’t guess there was one.
1 Like
I got the same update and haven’t noticed anything new, I also cant find that update listed in the Plex Media Server change-log, I wouldn’t be surprised if it’s just a minor update to accommodate Android TV 11 permissions for those that had problems/issues.
Lemme know if you find anything new
Hotfix #1 for 9.0.2 seems to have resolved the issue with external drive issues.
Disabling SMB signing has resolved the issue with PMS crashing while scanning media.
12 hours and still up.
3 Likes
