Is there a setting to stop Plex from spinning up the drives in my SAN or my individual drives when all I am doing is viewing the title’s page or it’s corresponding metadata info? I do NOT want to spin up the drives until play is hit.
No, there is no way to do that.
When you enter an video’s preplay page or inspect its properties, Plex is looking for external subtitles and other local assets. That certainly causes a drive to spin up.
Your only alternative would be to put all of the metadata on SSD leaving the storage for the actual media. Be advised, should you choose to do this, the SSD will be written to a lot. It will not have the typical lifespan. 150TB of write endurance won’t last forever.
Anyone know if Emby does this as well? Because I’m getting sick and tired of Plex here. Privacy policy non-sense, Required log-ins, etc. This program becomes more unusable by the day.
@ChuckPA said:
Your only alternative would be to put all of the metadata on SSD leaving the storage for the actual media. Be advised, should you choose to do this, the SSD will be written to a lot. It will not have the typical lifespan. 150TB of write endurance won’t last forever.
I was under the impression my metadata was already on an SSD. I’m using the setting “The path where local application data is stored” to point to an SSD location under Settings > General.
I presume you’re speaking of Windows. IIRC, wherever you had Plex put its data directory is what I am speaking of.
Did you direct PMS to put its metadata on a SSD in that SAN ?
@ChuckPA said:
I presume you’re speaking of Windows. IIRC, wherever you had Plex put its data directory is what I am speaking of.Did you direct PMS to put its metadata on a SSD in that SAN ?
No. This is a separate drive for Application data only. My media exists on a variety of other drives/locations.
If that’s a SSD, and it contains the entire PMS Library directory structure, there is no reason for your drives to spin up UNLESS your OS is what’s spinning them up. Most NAS vendors will spin up all drives when any of them are needed.
I will say this for the record.
Putting PMS’s metadata and database on a network device isn’t supportable because not all network file systems support file locking (needed to protect the database during normal operation by the various asynchronous processes running )
The most desirable configuration would be
A. SSD in the local machine holding the database and all metadata
B. Media on the NAS/SAN
@ChuckPA said:
If that’s a SSD, and it contains the entire PMSLibrarydirectory structure, there is no reason for your drives to spin up UNLESS your OS is what’s spinning them up. Most NAS vendors will spin up all drives when any of them are needed.I will say this for the record.
Putting PMS’s metadata and database on a network device isn’t supportable because not all network file systems support file locking (needed to protect the database during normal operation by the various asynchronous processes running )
The most desirable configuration would be
A. SSD in the local machine holding the database and all metadata
B. Media on the NAS/SAN
That is the configuration I am currently using. Windows 10, Plex Server 1.9.1.4272. This has been happening for quite some time/versions.
There is a direct correlation to going to a title or info page for a piece of media, and that particular device/drive spinning up.
Can you comment on the below statement? It seems your info and his conflict.
@OttoKerner said:
No, there is no way to do that.
When you enter an video’s preplay page or inspect its properties, Plex is looking for external subtitles and other local assets. That certainly causes a drive to spin up.
Otto and I have discussed this in private.
We conclude the discerning point is Windows versus Linux. If there is an error, it is mine for assuming Windows was more like Linux in this regard. In Linux, particularly NFS, the server sees the date created, modified, and last accessed information. The change notification mechanism is different between Linux and Windows.
I have shared with you how I know it to work in Linux and when using NFS ( both Synology and QNAP NAS units).
Ok. To summarize then, Windows with Plex Server running will always spin up the drive where the media is located to determine changes to the media, rather than using the stored metadata.
Linux will not. I presume this includes PMS running in Docker on say UnRaid?
Docker is a container. Its host OS makes all decisions.
Linux does it to. Every time you are browsing metadata Plex is accessing the underlying file. Its a pain in the a**!!!
All my content is on a NAS and get’s automounted whenever needed. With Plex theres permanent mounting activity.
@mbrown9nu said:
Anyone know if Emby does this as well? Because I’m getting sick and tired of Plex here. Privacy policy non-sense, Required log-ins, etc. This program becomes more unusable by the day.
Same here! Developers seem to be busy implementing those nice and shiny new data harvesting features so that there is no time any more to build a stable core. Sad.
@marcelhehle said:
Linux does it to. Every time you are browsing metadata Plex is accessing the underlying file. Its a pain in the a**!!!All my content is on a NAS and get’s automounted whenever needed. With Plex theres permanent mounting activity.
Automounting / dynamic mounts will. I have all the shared mounted in /etc/fstab and the drives will spin down until I hit play
I’ve links on my local disk that point into an automount location.
Like this:
./Media/Movies/a/Avatar.mkv => /misc/disk05/Avatar.mkv
Plex only sees the symlink. Still my drives spin up, every time I’m accessing the metadata. My conclusion out of that is that Plex reads/scans the file once you browse to a movie in an app.
