Your assumption that unpacking to local drive and then moving to NAS is faster than unpacking to NAS is plain wrong. NZBGet unpacks directly to DestDir for the reason of making the whole process faster and more performant. And in a case you didn't know - SAB works the same way.
You will need to do that even if files will be moved after local unpack because moving to NAS requires more than a millisecond and will take roughly the same time as unpack.
When you unpack to NAS the only thing NAS has to do is to write the data it gets from PC. When you unpack locally and when move to NAS the only thing NAS has to do is to write the data it gets from PC. As you see for your NAS there is no difference whether you unpack locally or directly to NAS.
Can you please provide a log for one such case in order for me to see at what stage the error occurs? Click on item in history, then on button "Log", when button "Save to file" or send me the global log-file (that's even better as this file may contain more info) - email@example.com.
So you tried NZBGet on your NAS already or have your tried SAB only?
With NZBGet or SAB? If you didn't try NZBGet there it would be interesting to know how it performs, even if you are not gonna use it there after the test. 300Mbps (approx. 32-36 MB/s) should be possible with two cores Intel CPUs. If you can use a separate physical drive (HDD or SSD) for InterDir, that would decrease load on RAID.
At the end you probably want Plex to scan new files. You can achieve this by using pp-script VideoSort
They all are supported. Take a look at Notifications section of Catalog of extension scripts. In particular, as a nerd, you should fall in love with pp-script Notify - notifications (All In One) which supports just any notification service in the world. And if you manage to find a service it doesn't support - let the author know and he adds support for it, probably the same day you ask.
Thanks so much for looking. Like I said before, once I got past this hiccup it was smooth sailing. I've successfully downloaded over 225 nzbs since the file locking issue with zero problems other than deleted articles. I love how logging events have a relationship with specific downloads. I also love how logging failures clear from the web console if the failure is corrected. Thanks again, sending some beer money your way.
instantaneous you say. That got me thinking. It makes a lot of sense to have the _unpack on the destination and then Videosort will do a simple move. So I changed the Movie destination in categories to a tmp dir on my NAS. Movie downloaded and unpacked successfully into the tmp dir. Then Videosort kicked off. Found the new NAS tmp dir and proceeded to copy, not move the file.
Users browsing this forum: No registered users and 5 guests