Abe87

I had seen these warnings. It won't impact this machine since it's a purpose built machine. Once it's working reliably it won't be updated. I'll just stick with @alturismo suggestion to suppress the cnr = messages in the syslog.

Thanks for the suggestion. I was able to get it working to block those messages. I can always revert the change if @ich777 has info to stop that message from being created in the syslog.

I'm having an issue that I'm hoping I could get some help with. I'm using a TBS 6704 and it works great. But I keep getting these kind of messages in my unRAID system log when my Tvheadend docker is running and accessing the card kernel: cnr = 3430 It looks like cnr is the snr of each tuner. So the log gets spammed with those messages but the number is constantly changing. I'm not sure if the issue is Tvheadend or the TBS kernel. Is there a way to disable this logging?

Hopefully hardware security keys like the Yubikey will be considered.

I was having 429 Rate Limit Exceeded errors in my log. It was taking 20-30 seconds to access files. I found this thread on the RClone with other users having the same problem. The fix is to add the user-agent option to your mount script. I added this --user-agent "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36" which is the Chrome user-agent. This has fixed the problem for me. There are reports that you can choose any user agent you want and it will work.

I have a couple of curiosity questions. Why are you encrypting your drives? Also, why are you moving your files to the array after they are unpacked?

Fixed my issue. It turns out it was that the port had changed. I searched the thread and saw where you had posted this info. Can I suggest that you put this important info in the first post or one of your reserved posts? Thanks for the great docker!

I have gone back to 6.1.9 still having issues with this docker. I have deleted the rtorrent folder from appdata and re-entered all the information from scratch when installing the docker. Nothing has fixed the issue. Same errors as the last picture.

I'm having an issue where rtorrent is not starting after upgrading to unRAID 6.2 Here is what is displayed in the log file. I have tried reinstalling but that didn't fix the issue. Any help would be appreciated. Thanks

I updated and it seems to be working correctly now. Thanks for the quick fix.

Thanks for the info. When switching to the Joe L. script(actually bjp999) I have the option for fast post read. But, I have a different issue now. I just ran 2 simultaneous 5 cycle preclears in 15 minutes. The reason it was so fast is that it is only looking at 1gb of the 2tb. The only thing I did is choose the script and activate the fast post read. Tried it without the fast post read and it did the same thing. Normally I would think it was the drive but to have 2 drives with the exact same problem. Any help anyone can provide would be greatly appreciated. Here is a screenshot of the log on a freshly started preclear.

I am having the slow performance as well. I'm on unRAID version 6.1.9 The option for fast post read is missing on my options. I have options to skip the pre read and post read. Is there a way to rollback to a previous plugin version?

Make sure that you are passing the correct path to the docker. Make sure that you specify that in the settings. And try restarting the docker after it has been setup.

You can't go wrong with linuxserver.io lonix is very helpful.