EDIT: After several restarts of the unRAID OS, setting OS X interoperability to yes and some other stuff, I am able to open FCP X libraries one, two and three folders deep. Libraries, that contain everything. I still have a slight problem with FCP X libraries, where media, cache and backups are outside the library, but that can be fixed.

 

 

ORIGINAL:

 

Hi.

 

I want to use unRAID to store FCP X projects and all the associated data and I am using macOS Sierra and I use SMB to let unRAID and Sierra talk to each other. It works okay.

 

Since I cannot create sparse images Carbon Copy Cloner copies to (CCC always aborts after some GBs have been copied - sparse bundles work), I tried just copying the actual folders and libraries inside to the Share I created.

 

FCP X can open a library with all the data if it is one library with all data consolidated inside it and if the library is in the root. Once it goes one folder deep, FCP X has a lovely problem ("Unsupported volume type. Choose a local, SAN, or supported SMB location.").

 

Apple has an article about that here and proposes to edit the "smb.conf.file" (I suppose only "smb.conf").

 

Now I found the SMB Extras settings and added the line of code* they wanted to have added, but I suppose, since I edit the "smb-extra.conf" file on the flash drive, it might not help as editing the "smb.conf" file, which I cannot find on the flash drive.

 

*

vfs objects = catia fruit streams_xattr

 

See attached screenshot of the files and folders on the flash drive.

 

Is there such "smb.conf" file I can edit or is there not? I used Googlefuh, but it didn't get me very far.** I don't mind using the Terminal for that, if I can give it a try that way.

 

Thanks for any pointers.

 

 

** I searched for the code and found this unRAID thread, which seems to indicate, that adding that code to the SMB Extras would suffice. If that is correct, well, then expletive, as I just created an ordering system for every project with the library three folders deep.

Edited June 28, 20179 yr by rainer

It's in /etc/samba/

This is a file in ram that is rewritten at each boot. If you want to verify that your changes have been written you can use ConfigFileEditor to view/edit the file. It'll be in tools if you have it installed or you can install it from Community Applications.

The smb-extra.conf file is what you want to work with. It is added to the default smb.conf when the server starts.

Mine has a hook to include smb extra configs. I'm guessing yours does too. Did you click "Apply" after adding settings?