Dealing with a very similar issue with our system. Here's where we're at as we troubleshoot with Apple and Lumaforge.
Loading a timeline in FCPX 10.4.8, on Mac OS 10.15.3, forces the server connection to our Lumaforge Jellyfish Rack SMB and NFS shares to suddenly disconnect. FCPX then prompts with a "Storage disconnected" error, forcing the library to close. SMB and NFS shares then need to be remounted in the JellyConnect app.
Any computer running 10.15.3.
Any computer running 10.14.6 or earlier.
We have had no issues with the exact same assets or libraries on any system running 10.14.6 or earlier, on FCPX 10.4.8 or earlier, connected to internal or external assets. We also have no issues with the exact same assets and libraries running off the internal drive of a 10.15.3 system. Issue is only present when using external SMB or NFS based assets and libraries.
We have troubleshooted ethernet adaptors, CAT 6/7 cables, different server ports, different assets, different 2 year old libraries, updated JellyFish etc etc.
Currently this is sitting with Lumaforge and Apple, but effectively we are unable to use any newly released Apple computer that can't be downgraded to 10.14.6. Which means no new Mac Pro or MacBook Pro 16".
If anyone has any ideas, we're running out of ideas here!
There is a confirmed issue between Catalina and FCP X when using SMB or NFS protocols. The weird thing is that it does not happen on every system that is running this combination, which makes it very difficult to troubleshoot. As I said, we have quite a few clients running Catalina and FCP X on a Jellyfish without any issues. But recently we also have received reports as the one from Stefan.
This is an incompatibility issue between Catalina and FCP X over a network, running very specific hardware combinations. We have reported this directly to Apple (as Stefan has seen on our support portal) and are waiting for a fix. We have been trying to work around the issue. But as far as I see now, the fix needs to come from Apple.
In the meantime, we advise NOT to use Catalina with FCP X on a network storage. In fact, you never should upgrade an OS without first checking if there are any reported issues with the applications and the hardware you use. The big bummer, however, is that all new MBPs andMPs come with Catalina installed and it's not really easy to downgrade to Mojave. But there are hundreds of pages on the internet that explain how to downgrade from Catalina, so a lot of people must be doing it.
Thanks for all the info. This is great to know as we place orders for MP’s. On Catalina. I was under the impression you couldn’t dial them back to Mojave.
Oddly my behavior started in High Sierra and into Mojave. Perhaps there still is a patch needed. I have several days in a particular library where everything works as it should then can have 3-4 can’t save messages within 15minutes. Then totally fine again.
In working with SNS they said we've found a way to consistently reproduce stalled communication with SMB targets when working with FCP X. I’ll check in with them and see where we are at.
As discouraging as it is, I’m glad to know that it can be reproduced elsewhere. I hope a fix can come swiftly as it’s really troublesome not being able to use new hardware.
oldsoul, we have similar setups and experiences but Mojave is by far more stable as the connection can be recovered in an instant, while on Catalina, the connection recovers very slowly. New Catalina based machines are unusable at this point and it’s extremely frustrating.
Thanks everyone. Lumaforge is working with Apple on this. Fortunately we can still read/write to the SMB share in the Finder just fine, so we'll be copying all assets to an external SSD to work off until this is resolved.
Thanks Jeremy G. Thats great news. I've been working with SNS since the beginning and have been diligent about trying to solve this. They are working on a Mojave patch now and will let me know. Fingers crossed.
Wow, thanks to everyone for troubleshooting this! I thought we were all going crazy. Every once in a while we would have a disconnection, or the library refused to save. Our storage is connected through SMB. I THINK we mitigated the problem somewhat by pointing to the cache to a different subfolder whenever we switched machines.
It's crazy because Apple has broken SMB several times over the years, and they often don't communicate how they're changing the implementation. Whoever's in charge of this needs to be fired.
I am not an IT engineer, I repeat what our techies are saying. But it has something to do with port usage and netbios. Just like SNS, our support team has released a patch for our clients. I am sure that Qnap will do the same soon.
It would be greatly appreciated if someone who is working on solutions could actually publish specific technical details on both the issues introduced in macOS Catalina and the current work arounds being implemented by teams such as yours and other teams like SNS. I keep seeing this issue posted everywhere online, but no one is posting anything helpful for people like myself that have to try and DIY fix this kind of an issue. If you have any ability to get a more technical explanation on potential fixes, it would be so incredibly appreciated. Thanks.
After contacting Qnap they've confirmed they haven't heard this, but a ticket has been filed. Looking at the available information it appears that this has nothing to do with Qnap, Lumaforge, or SNS. They just happened to have figured it out and made changes to MacOS itself rather than updating the firmware on the NAS. While this is nice for those customers it leaves everyone else out in the cold until Apple acknowledges and fixes the problem. If this is the case there has to be a way to get this working without having to be an SNS or Lumaforge customer. They have so far not published any info on how the fixes work.