Server Version#: 1.20.0.3181
Player Version#: NA
The latest Plex Server beta update causes the following error. The PlexData share already existed so I’m assuming it’s not checking to see if exists first.
Message: WARNING: Could not create PlexData share. Further assistance is available in our Support Forums. Continuing without.
It sounds like you have the main download from the site and not from my updated version in the introductory thread.
To resolve that,
a. Delete the share
b. Create a new “PlexData” share on your Default System Volume (DataVol1)
c. While there, assign any appropriate privileges.
OR *
d. Delete the share
e. Install the QPKG files (which are unsigned) I have linked directly above)
As I’ve stated above,
I do not pre-assign any permissions when it is created
This means even the admin group users, including admin can’t see the share in File Station until permission is granted.
This is by design to protect each system’s integrity. It would be improper to make such access wide open to all possible users by default.
Surprisingly what worked in my case was deleting the share and just reinstalling PMS using the signed version. For the 2nd time it installed correctly.
BTW - I’ve actually followed your advice with creating a new folder, but I realized I had made a typo in its name. Yet while installing Plex created its folder with no issues.
I may need to withdraw this feature because of all the problems it has.
QNAP’s interface for package developers is NOT very good.
When it comes to creating the PlexData share, it only gives me a “yes” or a “no” answer. It doesn’t let me look to see if PlexData already exists ( like Synology does ) nor does it let me manage Shared Folders in any way from within the package / command line shell of my scripts unless I have your username/password (BAD BAD BAD security practice)
Due to the number of issues being encountered, which to me are totally unacceptable given my zero-tolerance for such things, I will be discussing withdrawing the PlexData share for the time being in tonight’s team meeting.
I am working with QNAP to see if they can provide me a better mechanism to achieve managing shares:
What I need are:
List shares on the system (see if PlexData already exists)
Delete a particular share (an old PlexData) during uninstall.
Add the PlexData share.
Better return codes from their utilities. “Pass/Fail” is unacceptable.
What QNAP currently has implemented is a secondary layer of security AFTER signing in as the admin. There is no justification of a developer, such as myself, to need your password if you’ve already signed in and launched the installation. I “piggyback” on your authorization and either succeed or fail as appropriate.
Please ask the user (maybe when logging in first time after upgrade) on where he wants to store the PlexData share rather than just trying to create it!
It’s interesting. I had this installed from a ways back but even reinstalling the qpkg for the shared library and installing it again, I still get the error when installing the latest PMS.
After going in and deleting PlexData and recreating it as a directory with all permissions, PMS installed fine.
Ok from the perspective of someone who just clicks “install” on the new update and has googled the error message to find this thread, what exactly does “PlexData share” not being created mean to me as a user?
Does that mean Plex stops working?
It appears to work ok on my end.
Does it mean Plex won’t download new metadata?
I haven’t added new anything lately, so can’t test that yet.
Do I have to do anything to “fix” it, or can I just ignore it for the time being?
Running Plex Media Server 1.19.5 on QNAP firmware 4.4.3.1381 on a 431+
Hello, really do not understand any off this, Plex has worked well on my QNAP (TS-251B) until the last server update, then the message listed in this tread. The average guy (Paying for Plex monthly) cannot be expected to understand this sort of information we are not all computer programmers or experts surely Plex and QNAP can resolve this quickly. Yes grumpy and 60 years old lol and just want it to work without 6 hours off pulling out what hair I have left lol.
Sorry for not keeping this thread up to date with what I’ve been doing.
Because of the difficulties with different QNAP models, I’ve made changes which have already been approved and are now pending Engineering releasing another build.
PlexData share is no longer created by the installer. There will be no more errors attempting to create it.
If you create a PlexData share, I will use it to link to the QPKG storage for FileStation to provide the access so you can
a. Backup/Restore your metadata
b. Manually pull the log files should PMS ever not start
c. Add custom options to the Preferences.xml file.
By not creating the share during package installation and allowing you to create it:
a. The Control Panel - Shared Folders mechanism (qcli_sharedfolders) can create it as it should be created with all the proper permissions.
b. If there is no PlexData share, I will assume you don’t want the feature.
In the rare case of conflcts, where you have a “PlexData” named share that you use for other purposes and don’t want PMS poking around in it, I have provided a means to completely disable the feature. Open a SSH or, using FileStation one last time in the “PlexData” share (having followed the symlink).
touch "${QPKG_DIR}/Library/Plex Media Server/.disablePlexDataSymlink"
Did I miss anything?
As for being 60 & grumpy, I thought I owned that patent?
No, I owned that patent but it ran out 60 years ago. But, like @KevinDawson1 before me, I also do not understand any of this. What are these symlinks of which you speak? Where is the PlexData share that I can get to with FileStation? Oddly (to me), I can see but not access it through Windows 10, but can’t see it at all in FilesStation.
And, is any of this likely to be connected with the reason I got here: the fact that my Android app is now crashing on startup (something to do with sycing a Smart Playlist, I suspect)?
The PlexData share , if it exists, will be visible in Control Panel - Shared Folders along with the rest of the shared folders.
How this PlexData share works:
The startup script, fully independent of PMS itself, creates the linkage for FileStation.
The PlexData share must exist and have a directory attached (aka. a real share somewhere)
If the inhibitor (.disablePlexDataSymlink) doesn’t exist, then the linkage is made. This is for those rare name collisions which prevent use of this feature.
It doesn’t make, nor has it ever, made any assumptions about security. There is no way for me to guess a “best permissions” default so I opted to leave everything up to you.
If you want to use this capability, then you only need create the shared folder. Place it anywhere you like and with any permissions you like.
If you want user admin to have access to PlexData , Go to Control Panel - Shared Folders and grant it.
That’s all in the QTS security. I am operating as a service. I let QTS have full control.