Mac OS Sequoia 15.2 (current latest) and storing images on a NAS

[MissLiz]

Hi,

I guess looking at other posts here that I know roughly what the answer to my question here is going to be.

However, I believe that there is a bug in Mac OS Sequoia that is stopping me from using my current workflow that I have been using fine without issue for many years.

So all my images are stored on a NAS. I open them in Bridge/ACR/Photoshop directly from the NAS, 

edit, and save the results back to the NAS. The images are never saved locally. The files on the NAS also get automatically backed up.

Anyway, I understand this isn't Adobe's recommended workflow and they suggest you work on your files locally for performance reasons. However it seems that Sequoia has introduced a file system issue (bug?)  that makes my current workflow pretty much impossible now.

So.. an example....

Double click a raw file in Bridge (should open Photoshop, then open the file in ACR)

It really couldn't be much simpler. However, this process now randomly fails, about 25% of the time with

"File <xxx> could not be opened because of a disk error"

At this point, if I try and copy the file off the NAS using Finder I get  an error  "Unable to copy file. Error code - 51"

So that's quite scary... has the file been corrupted on the NAS?

The answer is no. If I reboot the NAS, then the  file can be copied with Finder without error. So the "Disk Error" message is clearly not describing the real problem.

(I suspect that when Photoshop says "Disk Error" that it keeps a lock on the file, which is why Finder then can't copy it)

If I'm lucky,  the file will now open if I double click on it in Adobe Bridge after the reboot.

So anyway, it looks like Sequoia is actually responsible for most of this problem. Has anyone else come across this problem with a NAS?

Anyway, I think it's time for a long overdue change to my workflow, and edit files locally, and set up a backup to my NAS from there instead.

I'm very interested to know what's going on with Sequoia though, so if anyone has any thoughts on this, that would be really appreciated.

Thank you for reading

Liz

[D Fosse]

Working directly over a network connection, or any external storage, is one of those things that work until they don't.

It is not supported and officially warned against. Read this:

https://helpx.adobe.com/photoshop/kb/networks-removable-media-photoshop.html 

"Technical Support strongly recommends working in Photoshop directly on the local hard disk. To prevent data loss, save files to your hard disk first. Then transfer them to the network or removable drive in the Finder or in Windows Explorer."

[MissLiz]

Yes, thanks, I am aware of all that 😀

It doesn't, however, stop me wondering what has changed to cause this problem now. I have after all been using a NAS for over 10 years with this workflow and I've had no NAS related issues in that time.

As it happens, in this case, I do not believe this is an Adobe problem... I think it's some kind of SMB related issue that Apple have introduced in Sequoia.  I'm wondering what other (non-Adobe) issues are yet to surface. Ideally Apple would allow you to downgrade the OS, but it looks like I'm stuck with it, unfortunately.

Liz

[D Fosse]

As I said, it works until it doesn't. We get posts like this very often. Suddenly network drives or servers start corrupting files. This is why Adobe warns against it, and will not support it.

[MissLiz]

My problem is not about corruption of files, which is why I posted this, because there is a distinction here compared to other previous posts.. The files are all completely fine, as rebooting the Mac proves.

You said "As I said, it works until it doesn't", well this doesn't apply just to NAS workflows, it applies to everything related to software... Over the years I've had lots of problems with software due to bugs  (Photoshop included), but this is the first time I've had a NAS related issue.

The fact is, in a properly configured NAS/network set up, things can actually be more reliable than a local drive, due to the extra redundancy that a NAS offers. It can even protect you against bit rot, which a non-RAIDed local drive cannot. The only issue I've had is a small decrease in performance, due to slower read/write speeds... but that's always been a compromise I was willing to make.

I understand that it's not the recommended Adobe workflow, but surely that doesn't mean that we're not allowed to discuss this here? Surely it's worth striving to understand what the real problems are, and whether they can be resolved?

Can we get back on-topic please..

If anyone has had any issues since upgrading to Sequoia, I'd appreciate a response.

Thank you

Liz

[Ged_Traynor]

@MissLiz "I believe that there is a bug in Mac OS Sequoia" have you tried contacting Apple support about the issue

[MissLiz]

Not yet, but I plan to.

I'm still trying to accumulate more information with my own analysis, and also seeing if anyone else has similar issues here. 
I've not checked the Apple forums either yet, but I will do,

[MissLiz]

If anyone's still reading, I've fixed my problem by configuring and using an NFS share instead of SMB.

No more incorrect 'disk errors'. Also, NFS is noticably faster than SMB, so all seems good!

I consider this all to be more proof of buggy SMB support in Sequoia.

I can continue with my preferred workflow! 😀

Liz