dikkiedirk

My first download with NZBGet resulted in a unpack failure. Perhaps a configuration error. I enclose the NZBGet log and the docker settings I used. Is it a beginners error? La_Grande_Vadrouille_1966_Louis_de_Funès_1080p_NL_Subs.zip

Thanks Squid. Gonna try NZBGet again and this time a bit longer, trying to get used to it.

Thanks Quid. Where can I find this appdata folder? Is it hidden somewhere? I already tried NZBGET but I don't like the UI, might be because I am used to SABNZB. I see five NZBGETs in APPS, what is the preferred one BTW?

SABNZB docker wont load any nzb from the watched folder anymore. I added 36 nzbs to SABNZB yesterday evening but the 37th wasn't added. the log shows many dirscanner crashes like pictured beneath. 2017-01-08 14:37:43,288::DEBUG::[__init__:1206] Test IPv6: Cannot reach IPv6 test host. Disabling IPv6 2017-01-08 14:37:43,288::DEBUG::[downloader:382] External IPv6 test result: False 2017-01-08 14:37:43,343::DEBUG::[downloader:398] SSL verification test: True Exception in thread Thread-9: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner self.run() File "/usr/share/sabnzbdplus/sabnzbd/dirscanner.py", line 328, in run self.scan() File "/usr/share/sabnzbdplus/sabnzbd/dirscanner.py", line 414, in scan run_dir(dirscan_dir, None) File "/usr/share/sabnzbdplus/sabnzbd/dirscanner.py", line 343, in run_dir if os.path.isdir(path) or path in self.ignored or filename[0] == '.': File "/usr/lib/python2.7/genericpath.py", line 49, in isdir st = os.stat(s) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe8' in position 51: ordinal not in range(128) 2017-01-08 14:38:16,289::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:38:16,289::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:38:49,324::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:38:49,324::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:39:22,355::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:39:22,356::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:39:55,390::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:39:55,391::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:40:28,424::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:40:28,425::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:41:01,456::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:41:01,457::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:41:34,491::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:41:34,491::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:42:07,525::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:42:07,525::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:42:40,557::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:42:40,558::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:43:13,591::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:43:13,591::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:43:46,624::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:43:46,625::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:44:19,659::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:44:19,659::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:44:19,659::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:44:19,659::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:44:52,693::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:44:52,693::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:45:25,727::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:45:25,728::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab Can the docker.img be full or is something corrupt? Can I somehow check this and clear this image? Or do I need to delete the image and rebuild my dockers? Can I keep my current configs? Off course I am only guessing, I can be on the wrong track.

My watched folder doesn't seem to work like it used to be. I have several subfolders inside for different categories but when I put a nzb there it doesn't get loaded at all, like it used to. When I put a nzb in the root-folder, i.e. nzb, it only gets loaded after restarting sabnzbd. Is this a bug in sabnzbd 1.1.1 that is loaded now or is something else going on? Can I fix it myself or is there a work-around that doesn't involve a restart?

After running the modified for 6.2 script and while a parity check is running I get the following status message: unRAID Status: 21-09-2016 00:20 Notice [TOWER1] - array health report [FAIL] Array has 24 disks (including parity & cache) What can be wrong? Should I be worried? Is it related to 6.2, the utt script, the unthrottled valus I used or something entirely different? Everything seems to be working as normal. tower1-diagnostics-20160921-1043.zip

Where can I get this script vor V6.2?

It is a great controller and so is the Dell Perc H310. Which cable did you buy?

I installed the beta plugin from here: http://lime-technology.com/forum/index.php?topic=39985.msg453938#msg453938 But it doesn't show up under settings---user utilities. Can someone tell me where it is? This is on my test server which was recently updated from 6.1.9 to 6.2.0 RC2

One little quirk: I left the container port at 8080 but changed the hostport to 8090. I get to sabnzb gui at ip-address:8090, but when I need to restart sabnzb it tries to load it at ip-adres:8080 and I need to enter 8090 manually.

You are right on the last part. I used to be more "adventurous" when it comes to trying out new things. I really am a noob when it comes to dockers. I tried something and have it working now. I just get a very funny graph in SABNZB that shows the download speed. Is this a bug in the current SABNZB?

it depends on how you set it up. The container can only access folders which you map, you can add as many folders mapped as you want, the template is a starting point. If you don't add say /watched or /nzb then you'd have to place them in a subfolder of a folder you do have mapped. For the plugin version of SABNZB I created a cache only share named nzb which I set as my watched folder inside SABNZB. I could simply drop nzbs in it and they would get picked up by SABNZB. What mapping would I need to set up to make this work in this docker? I also defined categories for DVD, MKV, Blu-Ray so downloads would be moved to /mnt/user/DVD,MKV or Blu-Ray. Would I need special mappings for this too? Or can I map /data to /map?

Is there no need for separate volume mappings for Watched and NZB backup in either docker? Can you set these up inside SABNZB and is the /mnt---/mnt mapping necessary for that?

Regarding NZBget and SABNZB what are the Pros and Cons between the two. How does portmapping work and how should it be setup? I now use PHAZEs plugin of SABNZB and have several Categories setup. Can I use something similar in NZBget? My guess is that NZBGet also has a watched folder, download folder etc. How do I setup folder mappings to these. Or can I point it to /mnt?

I want to move SABNZB PHAZE's plugin to binhex docker, but don't understand the volume and portmappings. In the current plugin setup I setup the watched folder to a cach only share called nzb. I also have categories defined and Relative folders are based on: /mnt/user/Movies2. I use port 8085 non-SSL at the moment. How do I use these settings in the docker? Which port mappings should I use? Why are port 8080 and 8090 setup by default? Should I use direct folders in Categories like mnt/user/movies/mkv instead of relative folders?

Where does it show you this kind of info? Which unRAID version? Under tools PCI devices it shows: 02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) On a former testserver with unraid 6.0 beta 6.

Thanks. Just flashed 2 H310s on my trusty X8SIL-F following the steps in the Toolset. They now also show up in unraid as LSI/Symbios Falcon something... No drives attached yet though. And without masking any contacts.

I saw reports of servers not booting with the PERC H310. It is needed to mask some contacts in that case. What exactly are the symptoms when this happens, just a back screen? I have one inserted in a system now and after booting I can enter the configuration utility. Should I be ok, without masking those contacts? Also when flashing to IT should I still need to flash the 6GBPSAS.FW and then the 2118it.bin? Or can I also do without the 6GBPSAS.FW? When I follow the steps in the toolset will it be flashed to a plain LSI card and can I still add the ROM so I can see if all connected disks are detected? And what is the story about the que depth? Is it important? Is the LSI version better or worse than the Dell version?

Unraid 5 is EOL I think and will not be updated anymore, again I think. Unraid 6 brings a 64bit environment and the possibility to use dockers. That was enough reason for me to switch to unraid 6. But unraid 6 brings more, for instance VMs and a nicer GUI. I think you can use 6 TB in unraid 5. But please, all others, correct me if I am wrong.

Some questions arise: I ran the script a while back in fullauto mode and updated the settings accordingly. I want to re-run the script. Does the script use any of the current settings? Should I restore the default settings as after a fresh install of unraid? Should the script be run on an as clean as possible server, without any dockers or plugins?

sorry, but don't fix until it works You are right. Remember Murphy?

I have two M1015s and a Supermicro motherboard with a LSI 2008 integrated on it. I used Supermicros files to flash this one to IT mode, their latest is P16. The M1015 were flashed a while back with files I found here. They are P14s. Are there any known defects in these fws? Or performance differences? Would it be advisable to upgrade to P19 or P20?

What gives the most reliable results for you guys? Running fullauto or manual? Are you all going the the most convenient fullauto way or do you all select manual with normal or even extreme option?

i don't think so, these low power procs will work just fine i think.. mine are second powerful in all range, and uses much power - when idle it uses about 100W without any hdd/controllers. at full load it uses over 200W. Other question: What memory do I need for this board, would the Kingston UDIMMS from my X9SCM work?

The board can be seen working before buying it. It will be pulled from a Supermicro chassis. It has 2 low power Xeon CPUs, L5630. Maybe that is a drawback? But they sell the memory separately.