[macOS] How do I handle directory linking?

Previously ran Plex with Windows 8.1 then onto 10. After the recent snafu with the update process and in general issues with Windows, I’ve moved to macOS (hackintosh). I commend Plex for making easy to migrate server data from one OS to the other. Not a single hiccup. All I had to do was point the libraries to a /Volume instead of D:\.

In Windows I used a junction mklink /j to point PMS from AppData to a folder on the Storage drive. This worked well. It seems that macOS doesn’t support that ability. It has symlinks which is essentially an alias. This doesn’t work. I setup Plex with PMS in the correct location. All 32gb of it. Once I move PMS from ~/Library/Application Support/Plex Media Server to the Storage drive and create a symlink, Plex will not launch. It always says Server is starting… and on top of that the macOS version of PMS doesn’t have to ability to change the data location as it does in Windows.

The issue with this is I don’t want PMS data on the boot drive. It’s an SSD with only 250GB. I have a 4TB storage drive for everything else. iTunes handles the symlink just fine as well as some applications and games. I’ve looked into a hardlink brew using hln but that didn’t work. Has anyone managed to get it working using symlinks? Or is there something I am missing?

I just tried, and mine seemed to work. (This is on an iMac not a Hackintosh though)

I have an external drive connected via thunderbolt.

As a test. I shutdown Plex on my Mac

Copied my Plex Media Server folder from my Library to the external drive

Then re-named my original Plex Media Server folder (as I am just testing)

Then created a symlink like so

ln -s /Volumes/extdrive/plexdata/Plex\ Media\ Server/ /Volumes/Macintosh\ HD/Users/user1/Library/Application\ Support/Plex\ Media\ Server

Started up Plex on the iMac and it all seems to work.

I left that detail out. It works initially, but after a restart it no longer works. I don’t understand that.

Borrowed a MacBook. I created a test server and it’s the exact same problem. So I’ve narrowed it down to an alias problem.

ah ok, I have not tried a restart, will see what happens next time I restart this machine.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.