I reworked the logic again for this.
- I query QTS about which volume (path) it is installed on.
- If I cannot pull the information about where QTS is installed (HDA, MD0, CACHEDEV1) then I abort installation. If this fails, then QTS is damaged.
- I then create the PlexData share on that volume, directory name
PlexData. - The linkage to where Plex actually is continues to function as before .
If any errors are encountered, they are raised as INFO.
If, for whatever reason, the PlexData share doesn’t get created, creating it manually will resolve the problem. I have already dispatched an email to QNAP requesting their assistance. They have not yet responded.
To try this, I ask:
- Stop PMS
- Remove the PlexData share and delete the ISO directory (check the box).
- Install PMS
- Go to Control Panel - Shared Folders - Assign the permissions you wish to grant.
It should now continue to function as it I intend.
I apologize for the difficulties here. I wish I had the additional QNAP models I needed during development to flush this all out up front.
Further, I would never have imagined QNAP to be so problematic.
Please let me know how this goes:
I had a problem building the Armv7hf_neon. I will address that with my team on Monday.
