Application Center Ignores User-Defined Default Installation Path, Forcing Data Storage on Volume1

[CursaYang]

In the Application Center, only the installation location for applications can be set; the storage location for application data cannot be specified. Regarding the previously mentioned issue where Docker can only select folders under Volume 1, the output from the `ls` command shows that there are no shared folders created in Volume 3, so it cannot be selected.

[rigveda]

I updated to the latest TNAS version as of 21st of January 2026: TOS version: 7.0.0392

And reinstalled Plex again to see if correct volume has been selected on installation:

It continues to incorrectly write/ create folders in /Volume1 and NOT /Volume3:

Code: Select all

rigvedauser@TNAS:/Volume1# ls
@apps  @cache  @collect  @desktop  @system  @usb  @videoframe  @zlog  Photos  Plex  homes  plexmedia  public

However the hidden folder @apps in /Volume3 is correctly writing a plex folder here:

Code: Select all

rigvedauser@TNAS:/Volume3/@apps# ls
plex

I have tested with 2 other "1st party TNAS applications as well:
TFM Backup
Multimedia Server

Both installed on the @apps folder in /Volume3:

Code: Select all

rigvedauser@TNAS:/Volume3/@apps# ls
MultimediaServer  TFM_Backup  plex

and no other folders in /Volume1

[CursaYang]

Based on the `ls` output information you provided, the current behavior is normal.

In the application center settings, you changed the default installation location to Volume 3, so the corresponding app files are generated under @apps in Volume 3. The Plex in Volume 1 is the shared folder created with the same name during the first installation of the application on the main volume, used for data storage. Changing the application installation location will not change the data storage location. You can confirm this by using the `ll` command to check the creation and modification times of the folder.

[rigveda]

Below is the thread I currently have open with Plex support teams:
https://forums.plex.tv/t/use-the-provid ... me1/934855

The challenge is that in my setup, and the setup of many others with Terramaster is that one defines multiple storage volumes having different attributes and therefore uses. In my case:
/Volume1 - Is my 4x HDD disk TRAID array to store my library of media
/ Voume3 - Is a single SSD disk to store the TOS, app binaries and frankly any data that I can recreate (for example Plex album art, and other meta data about the media I host).

On TOS, I can specify the target Volume where I want Plex to be installed to, which is /Volume3. And I expect all related application binaries and its application data to reside there (in separate folders/ paths thats fine), but all residing in that Storage Pool.

Plex will then be provided the paths in /Volume1 where my media library is and can index and create all the metadata it needs and store in the /Volume3 (which is an SSD backed disk).

Right now, the Plex installation designed for Terramaster seems to install its binaries in /Volume3 (Storage Pool) and other parts in /Volume1 (RAID pool). To me, this strikes me as there is legacy code that is not actually checking for the target Storage pool and ALWAYS defaults to /Volume1 (i.e.: Even if I had 10 Storage volumes, it would ALWAYS default to /Volume1. This is a bug in the installation logic of Plex, not a feature.

So either, Plex need to modify or update their installation logic to ensure that it is using the passed Storage volume to install against consistently across its installation script that it built/ customised for Terramaster customers, and/or Terramaster needs to provide better documentation and guidance to 3rd party App providers (like Plex) on how to work with TOS’ Application Configuration - Default Installation Location.