jcouch93

I do the same thing, but I have SAB download into a folder that FileFlows monitors, FF does the conversion, and then FF moves the file(s) into the folder that Sonarr/Radarr is monitoring.

That worked perfectly! Thank you!

To get that to work, do I need all the stuff in the folder.view directories? I have your plugin, but on the Github page the folders have things in them (but my scripts and styles folders are empty). I tried just putting a docker-custom.css file in scripts but that didn't seem to do anything. Thank you for your help!

In Icon Only mode, is there way to have the icon show the status of the Docker (i.e. started, stopped)? Or is there a way to have Icon and Text to show multiple rows (I don't think so based on an earlier conversation in this topic)?

Running that one now. Seems to be running fine using my GPU as far as I can tell.

Been searching through the thread but I can't find an update on the support for nVidia HW transcoding? Is it still a no-go?

I'm seeing the same thing as well. Found this when searching around: https://forums.sabnzbd.org/viewtopic.php?t=23364 Started up normally after doing the following: 1. Connected to the docker (my container name was "sabnzbd") How to connect to a running Docker container? There is a docker exec command that can be used to connect to a container that is already running. Use docker ps to get the name of the existing container. Use the command docker exec -it <container name> /bin/bash to get a bash shell in the container. 2. cd /config/admin 3. mv server.cert server.cert.old (or delete it, but I was trying to play it safe) 4. mv server.key server.key.old (or delete it, but again playing it safe) I did an ls-al then and saw that the server.cert was immediately recreated but not the server.key I checked SAB and it was then running normally

Seeing this error in the System Log (Tools -> System Log): Oct 11 16:53:30 COUCHSERV kernel: CIFS VFS: Free previous auth_key.response = ffff88080fa7e780 Oct 11 16:53:30 COUCHSERV kernel: Status code returned 0xc000006d STATUS_LOGON_FAILURE Oct 11 16:53:30 COUCHSERV kernel: CIFS VFS: Send error in SessSetup = -13 Weird part is I see it every two seconds even when the array is offline and there are no mounted Unassigned Devices. Can anyone help me identify what is causing it? Thanks! couchserv-diagnostics-20181012-1400.zip

I hate that you're having this issue too as at least it means I'm not crazy! Hopefully someone else can help track it down too. If you roll back to 6.4.0 get a diagnostic for the developers (I forgot to do it).

For the VM settings, I set VNC-Keyboard to English-United States (en-us) In the VM itself, using Linux Mint 18.3 as the Guest, I go to Menu -> Preferences -> Keyboard -> Layouts and make sure only "English (US)" is there and hit "Reset to Defaults". I also changed the Keyboard model to Generic 101-key PC.

No. I thought that might be the issue so I reset everything back to "US English" just to make sure but still had the issue. Thanks!

Upgraded from 6.4.0 to 6.5.1 and noticed that in the terminal and desktop in my VM (and also a test VM) that I couldn't type a pipe symbol (all I would get was a < symbol) while at the same time I couldn't type a > symbol using the keys for it (was just a < symbol for both keys but the comma and period worked fine). I tried changing the keyboard in the Preferences, also did a re set-up on the keyboard via GUI and CLI, but nothing worked. Using an Ubuntu forum post, I ran: xmodmap -e 'keycode 94 = backslash bar'. That got the pipe back but the < > keys still didn't work (but comma and period still worked fine). I then downgraded back to 6.4.0 and everything works with no issues. Any ideas?

That worked! Thanks saarg!

I tried it and it still says ANSI in the config. Here's from the Docker log on startup: 2017-03-14 13:12:10,523::INFO::[sabnzbdplus:1173] sabnzbdplus-1.2.1 (rev=d32cf57c7573ed43bcab40eb9b23a0853f1f7015) 2017-03-14 13:12:10,523::INFO::[sabnzbdplus:1174] Full executable path = /usr/bin/sabnzbdplus 2017-03-14 13:12:10,523::INFO::[sabnzbdplus:1186] Platform = posix 2017-03-14 13:12:10,524::INFO::[sabnzbdplus:1187] Python-version = 2.7.12 (default, Nov 19 2016, 06:48:10) [GCC 5.4.0 20160609] 2017-03-14 13:12:10,524::INFO::[sabnzbdplus:1188] Arguments = /usr/bin/sabnzbdplus --config-file /config --server 0.0.0.0:8080 2017-03-14 13:12:10,524::INFO::[sabnzbdplus:1190] Preferred encoding = ANSI_X3.4-1968 2017-03-14 13:12:10,524::INFO::[sabnzbdplus:1238] Read INI file /config/sabnzbd.ini My startup says all commands completed successfully and it showed that the variable were passed.

I have updated but no go. I think it all boils down to I need to get SAB to change it's encoding (as reported on the Config page) to Unicode\UTF and not ANSI and I don't know how to do that. Thanks!

I'm having the exact same issue with dir scanner crashing (as shown in your earlier posts). Thinking of trying NZBget again. Any luck on resolution so far? Unraid uses UTF8. Do the below when connected to unraid to check. echo $LANG I get root@COUCHSERV:~# echo $LANG en_US.UTF-8 but when I run it inside the docker container I get nothing: root@COUCHSERV:~# docker exec -it sabnzbd /bin/bash root@c6de913a870a:/# echo $LANG root@c6de913a870a:/# Python config page: Python Version: 2.7.12 (default, Nov 19 2016, 06:48:10) [GCC 5.4.0 20160609] [ANSI_X3.4-1968] Any other help\ideas would be welcome. Thanks!

I'm having the exact same issue with dir scanner crashing (as shown in your earlier posts). Thinking of trying NZBget again. Any luck on resolution so far?

Swapped the old card back in and speeds are back up to 30-34MBps (which is normal for my array). I guess those cards are getting RMA'd and I'll have to find a card that has 2 Port-Multipliers on it to connect to the 8 Bay enclosure. Anyone have a suggestion for a card?

The one currently connected is only 1 eSATA port to the enclosure: http://www.newegg.com/Product/Product.aspx?Item=N82E16816111148 The new one is an 8 bay that does have 2 (which is why I bought the 2 port cards): http://www.sansdigital.com/tr8m6gnc.html Ok, I will swap the old card back in and see what happens.

Thanks johnnie! What do you need to be able to tell what disks those are? If I had to guess I'd say those are the 4 in the enclosure via eSATA. If so, I'll swap the old eSATA card back in to see if the issue disappears and if it does that tells me that maybe those cards aren't compatible with that MB? Thanks! PS: Here's the diagnostics file from the server (I just pulled it and hopefully it will tell you what disks) couchserv-diagnostics-20170112-1107.zip

First off thanks to all that helped me get the array back online, that was a huge relief. Now for the new problem: I've replaced the MB, CPU, and RAM to upgrade the server. Now that the array is back online, when I run a parity check (with or without write to parity disk checked doesn't matter) the check only starts off at appprox 1MBps and goes down from there (as low as 250kBps). Setup info: MB: Asus H170-Pro with an i7 6700. https://www.asus.com/us/Motherboards/H170-PRO/specifications/ SATA: Only 2 SATA drives are connected to the MB, the cache drive and the Parity drive (Cache = Corsair Force GS 180GB SSD)(Parity = WD Red Pro 7200 RPM 4TB) eSATA: 2 installed eS3-PCIe22-I DATOPTIC http://www.datoptic.com/ec/6gb-dual-sata-port-host-support-pm-mac-windows-linux-490.html in the x16 and the x4 slot on the MB that connects to a Sans Digital TR4MBNC 4 drive enclosure. The enclosure has 4 WD Red 5400 RPM drives that are all running off of the x16 slot card. So far I have swapped out SATA cables and power connectors and also changed MB SATA ports for the Parity drive with no change. I am attaching the syslog data and the Parity Drive SMART extended test results so that perhaps someone can shed some light on what I'm missing or doing wrong so that I can get a good parity check within my lifetime. Thank you! syslog.zip couchserv-smart-20170112-1033_-_Parity_Drive.zip

Great news! After the extended SMART tests finished with no errors\issues, I rebuilt the config per johnny.black and everything came up just like it was. I removed Parity 2 and will start a Parity Check shortly. I'll report back once that's started with a status. Again, thank you to all that helped!

I rebooted before pulling the diagnostics so I don't have them and I apologize. As for the SMART tests, I am currently running Extended tests on both drives. Short tests passed with no errors right before I started the long test. I'm hopeful I can recover the array and I am very appreciative of all the hep that's been provided. PS: When I rebooted, it started a parity check\sync. Would that effect the parity check when I create a new config with the drives now accessible? What I'm asking is that when I rebooted was it recalculating parity or just syncing Parity 1 and Parity 2?

Would that recover the data or is that toast? (Like I said I have backups) Also, when you say "new config with single parity using the trust parity option" I'm not sure how to do that. Is there a tutorial for what you want me to do? Thanks for all the help.