Just with the most recent release I can't write to my NAS from C1, rest of my mac is not effected
C1 16.3.3.6. on a Studio M1 Max/64GB/2T networked directly to an Asustor AS6704T with an ethernet cord (Four M.2. SSDs running as a RAID 0 array, four 8T Seawolf HDDs running in a RAID 6 array.)
Using the C1 import dialog I've been unable to write to my NAS (error is "can't write to location") yet I have no problem writing to my internal SSD and exporting to the NAS.
Weird, huh?
I've talked to sages from C1, Apple, and Asustor. C1 has direct access to everything, and file permissions, hall pass, everything, worked with two different techs from apple and they walked me through everything, had me change some settings through terminal, created test profiles, and verified C1 has correct permissions.
C1 walked me through some details and determined I should remove previous versions and associated files (not settings, etc) and do a clean reinstall. Nope.
Everyone has all of the correct permissions on the NAS.
Apple tech said that sometimes the SMB code (??) on the NAS can present like this, but I've used it for almost a year in this configuration with no issues with C1 playing well with the NAS.
Sooo, I'm posting this here hoping someone has had a similar experience and might have some suggestions. Helpful suggestions. ;)
Happy New Year!!
Brian
-
Hi Brian,
Perhaps not the answer you seek and apologies if you have tried these already... But below I've listed some of the things I'd try if faced with a similar issue.
a) Apple have deprecated AFP (Apple File Protocol) choosing to use SMB as its successor. However, MacOS and NAS units (I can only speak for Synology) still retain AFP support. Whilst I'd recommend sticking with SMB, it would be interesting to try AFP to see if that bypasses the issue. Try enabling AFP sharing on the NAS and mount your NAS share using AFP from your Mac. Do unmount the SMB share first tho....
b) If you have multiple shares on the NAS, can you import, using C1, to any other shares? Again, just an interesting test that may help identify what's causing your issue.
c) From your post I understand you can export from C1 to the NAS. Is that to exactly the same share and folder to which write on import fails? If not, I highly recommend trying it and see what happens - it may just help identify the issue.
d) It does not sound like a permissions/credentials issue unless you have multiple NAS shares mapped with different user accounts/credentials. You don't say how you mount the NAS share. I appreciate there are different ways to do this but I choose to use 'Go | Connect to Server...' from the menu and issue a command like that below. This says mount a share named 'data' using SMB, as NAS1 user 'agp' and prompt for a password. NAS1 and its following domain name is the name of one of my NAS units. I mention this, although I feel it's a long shot, as remounting your share with explicit username, password etc may again help identify what the issue may be.
"smb://nas1\agp:*@nas1.andygawthrope.photography/data"So, the above suggestions are really just attempts to gain further information which will, hopefully, help localise and identify the issue. Let us know how you get on. :-)
Andy
1 -
Thanks for your thoughts! They are much appreciated!
Andy, Yeah. Vexing. My current hypothesis is that this is Santa's retribution for my wicked ways.
a). I've tried it both ways and decided that leaving it ticked might make a difference. The second Apple tech asked if he might look at control panel settings for the NAS (AMD for Asustor) and said to turn off AFP, it hasn't been supported by the OS since 2018 and might be causing a conflict somewhere.
b). Tried creating a second user (guy named, "Test") and experienced no joy.
c) I WAS able to export from C1 to the NAS until December 13th, but not since.
d). I mount the NAS using the "Go" command in Finder as well.
Here are a couple of links the second Apple guy found and suggested I explore (he really went to the mat for this!).
https://forum.openmediavault.org/index.php?thread/44294-omv6-iphone-osstatus-error-100093/
The second one discusses SMB code, which is way above my pay grade, although I could dig into it if that route seems to hold promise.
Thanks again for the suggestions!
Brian
0 -
Brian,
Re your (c): So you can't export to the NAS? In your first post you wrote "...yet I have no problem writing to ... and exporting to the NAS.". Can you write any files to the NAS share that's giving the issue or another share on the same NAS via a C1 export or, importantly, using Finder? If you can write to the NAS share from Finder then there is likely nothing wrong with the NAS and Mac config....
I very much doubt there will be deep technical issue at the root of your issue; Its far more likely to be something simple like a misconfiguration. So, my 'gut' feeling is those links are distractions and not helpful.
Can you post the SMB and AFP mount commands - the commands you are specifying in 'Go | Connect to server'?
Andy
0 -
Andy,
Yes, I can write to the NAS with anything other than C1. Sorry for the confusion.
I tend to agree, there may be one box ticked that shouldn't be.
I'm in the middle of a project right now. I'll post those later this evening. Again, I've disabled AFP. Unless C1 16.3 still uses AFP, I'm not sure there is any value in it.
Thank you again!
Brian
0 -
The latest Capture One installs as a different app name (Capture One vs Capture One 23). You may need to go into Security & Privacy and grant the new app permissions to access folders and files?
0 -
Walter,
I haven't checked for the new name, that's a great idea. I'll do that tomorrow!
Thanks!
Brian
0 -
Walter,
In Privacy and Security, Capture One has permissions for full-disk access, Files and Folders access, and is listed and checked under Accessibility.
Sound idea, but not the issue, apparently. :(
0 -
Having beat my head against the wall for days I'm wondering if there may be an error in my import dialog screen settings? Here is what I currently have.
Do you see any errors I may have committed?
0 -
Hi Brian,
I am having the same issue with my Synology NAS. I used to be able to create a new session to my NAS, but all of the sudden I can't. I can create new sessions everywhere else. I can also open old sessions from the NAS but if I try to create a new one I get "Failed to create session database" and "An error occured and the session must close". Weird thing is that C1 2023 creates a new session folder but there is nothing inside it.
I reached out to support here, but they responded that C1 2023 is not supported on macOS Sonoma 14 but I know I have created new sessions on Sonoma 14. They want me to upgrade to C1 2024.
Have you figured anything out on your end?
0 -
Capture One 23 supports Sonoma but officially only up to Sonoma 14.0. See the release notes here.
https://support.captureone.com/hc/en-us/articles/14219459895837-Capture-One-23-16-2-6-release-notes
Some users may say that it has worked for them on later releases of Sonoma, but that is no guarantee that it will work for everyone since systems vary. (For instance not everyone is trying to make it work with an NAS.)
There is no such product as Capture One 24 - the version after Capture One 23 is just called Capture One Pro.
Ian
0 -
Hello Frank,
No, other than swearing a lot. Currently, my process is to import to my Mac's internal SSD and then, using the C1 file manager, move the folder to my NAS. Not elegant, but it works. :)
Brian
0 -
Thanks Ian,
My apologies, I wasn’t aware that Capture One changed the naming convention. I meant the latest version when I said 2024.
I did download the Capture One Pro trial and experienced the exact same issue so I know upgrading will not solve the problem. I have uploaded a screen recording and submitted that to my ticket.
Thanks for your input as well Brian. It is frustrating and I think your work around is going to be my next step until this can be resolved. It’s weird though because I can save a “New Catalog” to my NAS as usual but not a “New Session”.
I’ll keep you posted.
0 -
Hi Brian,
I seem to have been able to restore normal session behavior again. With some help from Victor at Capture One I did the following:- Confirmed Capture One has Full Disk Access in Settings.- I then restarted the computer and opened Capture One. It created a new session on my NAS as it should. To test it again, I quit Capture One, reopened the program, and created a new session. Unfortunately, I was met with the same error again and a failed new session creation.- To rule out an Apple bug, I updated to the latest OS and then tried again with the same result.- I then shut down my Mac and started in recovery mode, ran the First Aid function in the Disk Utility on my local disks and then shut down.- Booted up normally again, and the issue seems to have been resolved but I will keep testing to make sure and keep you posted.I hope this helps you to resolve your issue.0 -
Hi Frank,
Thank you! Yes, Victor is wonderful and extremely knowledgeable. I did the same things, with the exception of starting in recovery mode and running the First Aid app. I will try that now and report!
Brian
0 -
I am having the same issue with C1 shooting to the NAS. It will create the folder but stops short of building the database. I have had to create the session locally move to the server then re-open from there. It's not very efficient. If anyone has any suggestions I would appreciate it.
0 -
UPDATE: After initially thinking I resolved the issue it has since started again. My workaround now, like Brian mentioned, is to save locally and then move the folder to my NAS.
Steve, you are not alone in having the issue and it seems as if the workaround works. I hope there will be a fix soon though.
0 -
This sounds like a permission problem where the new Capture One doesn't have disk and folder access to the NAS.
0 -
I just appended a support request on this issue and am sharing it here as an act of contrition.
Dear Capture One People:
I owe you a big apology. I have found the defect and it was in the settings for connecting to the external SSD. Although Apple told me in no uncertain terms that I must disable AFP and only use SMB, on a whim (and because I was just throwing shit at the wall at this point) I enabled AFP and connected to the external device with the afp address. It worked. Months of annoyance because Apple told me pointedly that AFP was obsolete as of a few years ago and that attempting to use this protocol would cause me untold problems. It was absolutely shit advice.
I cannot apologise to you enough for the time and resources I have caused you to waste on this non-problem. Please accept my most sincere apology and I hope that perhaps this information may one day enable you to help another stupid user!
Most humbly yours,
Brian (the Idiot) Creek0 -
Wow. That is quite humbling and respectful of you to provide that feedback. Glad you found the issue. I think I will share this in my FB group as some others have had recent issues with connecting to NAS.
0 -
Everyone I have met or had interaction with from Capture One has been top-shelf and has gone the extra mile in helping me and answering my questions. I was frustrated and unfairly took that out on you and your colleagues. I'm not perfect (not quite) but I always try to comport myself with honesty and professionalism, and I genuinely regret not doing my homework on this earlier.
0 -
Thanks Brian,
Could you point me to where you enabled AFP? In my Synology NAS Control Panel both SMB and AFP are enabled and I am still having the issue randomly. I didn't see it in System Settings anywhere. I am having no issues with any other program accessing the NAS including Davinci Resolve, Pro Tools, Affinity Photo, Finder, ect.
0 -
Hi Frank,
When you go to Finder - Go, select the IP address for your NAS and change the first part from SMB to AFP, and click "Connect." That is all that I did and it fixed the issue. My NAS manufacturer put me on the trail of this by telling me;
"Actually, Mas OS cannot directly mount the volume from NAS SSDs, as you install M.2 SSD module in the SSD card (it's not equal to the flash drive).
Please mount the shared folder via SMB/AFP/WebDav protocol. "And then directed me to their support page on connecting to a Mac. I just stumbled on changing the SMB to afp while reading their directions. I also have both enabled and TimeMachine's NAS folder is defined in the SMB dialog.
Good luck!
0 -
Brian Creek .. you change from SMB to AFP, or from AFP to SMB?
0 -
SMB to AFP
The IP address now looks like: afp://123.456.7.8
0 -
Changing from SMB to AFP did it for me... but really... C1 doesnt work through SMB?? Capture One, is this true... are there limitations when connecting to a NAS via SMB?
0
Post is closed for comments.
Comments
25 comments