Export triggers drive eject? or network fail?

THIS MAY WORK

This is from Will - "da Man" @ SpaceRex who is all things NAS.

https://www.youtube.com/watch?v=0ujPx0KFO5E 

Also… it’s not always a mistake. Over the weekend I wanted to create lower rez versions of videos files on our server and since I was gone for three days I set it up to do about 300, only to find when I returned it only got 75% of the way  through before the drives ejected and AME just failed the rest of the operations. But there was really no easy way to batch convert those files (each in  their own folder). I just rolled the dice. So frustrating.

Yeah it is/was (hopefully) soooo annoying. I was the same... had a 'renders' folder on my desktop that i would render to and then copy to the correct project folder on my NAS. But then sometimes id forget, poor admin, and then have a monster renders folder and not remember which ones i had already transfered etc etc... nightmare.

Is it not worth trying the nsmb.config trick again... i had no idea how to do it, but it was actualy really quite simple in the end.

I tried it. I found things were working “better”. But I was having other problems, I ended up totally wiping my hard drive clean and installing all the apps clean and I got rid of a ton of bugginess. However, I did not redo the config (which technically I had someone else do) and yes, the NAS problems are back. I have given up and now just render and export internally and copy things over. So sad. So Stupid.

After struggling with this intermittently for years... i tried the nsmb.config just now, as i had a render from Premier that was crashing everytime when reading the source footage from my NAS and rendering to the NAS (but it was fine when source footage/rendered destination were on my desktop). And after NAS/Mac restarts and the nsmb.config patch it rendered from Premier/Media Encoder from/to the NAS first time. Fingers crossed this will continue.

My most common problem was that the files would render... but then right at the end would eject the NAS and then not quite finalising the h264 package and leaving the extra 'filename.mp4 00' or simialr name. the eactual rendered file worked but would just eject the NAS which was really annoying.

I’m posting an update here: I ended up completely wiping my internal drive and manually reinstalling all my apps with fresh settings/preferences. This greatly speeded up my Premiere performance. the NAS issue has returned, but now that I know not to export to the NAS but instead to so to my internal drive, I can deal with it. Annoying as it is,

It appears to be on Apple's side. According to Synology experts, Apple frequently 'breaks' the SMB protocol.

Is this a Synology specific setting? Cause I'm running a homebuilt TrueNAS with SMB with a Windows editing computer. And occasionally when Premiere Pro is loading something, either during a render, while editing or opening projects, it takes out the whole network and I have to restart the network adapter.

https://www.reddit.com/r/MacOS/comments/1fnug2a/comment/lor4kv1/ 

[default]

 

streams=yes

 

soft=yes

 

signing_required=yes

 

dir_cache_off=no

 

protocol_vers_map=6

 

port445=no_netbios

 

notify_off=yes

 

mc_prefer_wired=yes

Yes. This is what happens to my exports as well