Netbug

Thank you for the replies. I still don't understand quite how to interpret those results. I'll have to dig in to what Current_Pending_Sector and Offline_Uncorrectable mean and what thresholds are acceptable. Any recommendations for a Windows utility to test drives (I know it's slightly off-topic)?

UnRaid Version 6.9.2 I noticed that the system was responding very sluggishly for some reason so I had a quick look, and disk 8 was showing offline. I stopped the array, removed the drive from the array, started array, stopped array, re-assigned, started, and waited for rebuild. Everything seemed fine. Then the next day, the same thing happened. This is where I screwed up. I completely removed the drive and attempted to pre-clear it (data wasn't super important). Left it for about 30 hours, and came back to a message of "Error encountered, please verify the log". I now have a replacement drive, which I will be installing now, but I've got a few of these drives that seem to fail and i'm not knowledgeable enough to understand if they are actually dead. I've tried reading through the "Understanding SMART Reports" article but I'm just not smart enough to get it. I'm attaching logs here. My questions are: 1. Is there any way to know, from the logs and information, what happened? 2. Is there a way that I can purchase something (like an external SATA connector) for my Windows PC and use the windows machine to check these supposedly failed drives? Thanks. tower-diagnostics-20211118-0549.zip tower-syslog-20211118-1048.zip

Wonderful. Thank you folks. I will play around with it and see how it goes.

This looks like exactly what I'm trying to do. So just to be clear, I could set the "Extra Parameters" of the binhex-sabnzbd in the "Advanced" view to "--cpu-shares=2" and that would limit that docker to only use 2 cores when other cores are in use. Is that correct?

I thought of that, but there are a lot of times when we're not streaming and there can be quite a backlog of stuff, so I think it would work, but much less efficient.

So I've noticed that when my SABnzbd is doing post-download work (decompression), my CPU usage spikes to pretty much 100% on all cores. This is causing freezing on any stream I'm watching. Is there any way to set the docker running SABnzbd to wait until there is no/little activity on the other dockers? Or, if that's not possible to automatically limit it to run at certain times (say 2300-1100) unless manually triggered to limit the impact? Dockers: binhex-sabnzbd, PlexMediaServer, binhex-radarr, binhex-sonarr, EmbyServer

That's got it. Thank you, sir. If I can get this configured and working with Sonarr and Radarr, I'll send you some beer money.

Why am I unable to access the webui then? I just keep getting "ERR_CONNECTION_TIMED_OUT" and this is on both DelugeVPN and rtorrentVPN. Your other containers (sonarr, radarr) work fine. Attaching the new log. supervisord.log

I'm getting the following over and over again in the log. But i don't see any error. 2017-08-11 22:14:26,869 DEBG 'rtorrent-script' stdout output: [debug] External IP address from tunnel is '212.92.116.6' 2017-08-11 22:14:26,870 DEBG 'rtorrent-script' stdout output: [debug] Incoming port for tunnel is '27739' 2017-08-11 22:14:27,003 DEBG 'rtorrent-script' stdout output: [debug] VPN incoming port is 27739 [debug] VPN IP is 10.37.10.6 [debug] rTorrent incoming port is 27739 [debug] rTorrent IP is 10.37.10.6 2017-08-11 22:14:57,004 DEBG 'rtorrent-script' stdout output: [debug] Waiting for valid IP address from tunnel... 2017-08-11 22:14:57,134 DEBG 'rtorrent-script' stdout output: [debug] Valid IP address from tunnel acquired '10.37.10.6' 2017-08-11 22:14:57,141 DEBG 'rtorrent-script' stdout output: [debug] External IP address from tunnel is '212.92.116.6' 2017-08-11 22:14:57,141 DEBG 'rtorrent-script' stdout output: [debug] Incoming port for tunnel is '27739' 2017-08-11 22:14:57,275 DEBG 'rtorrent-script' stdout output: [debug] VPN incoming port is 27739 [debug] VPN IP is 10.37.10.6 [debug] rTorrent incoming port is 27739 [debug] rTorrent IP is 10.37.10.6

Thanks. I had actually followed that, but realized I had missed the part about deleting the extra ones. I have now done so, but I'm still unable to connect (" ERR_CONNECTION_TIMED_OUT "). Attaching new supervisord.log file. supervisord.log

I'm starting to pull my hair out here. For the past 2 weeks, I haven't been able to get binhex-delugevpn nor binhex-rtorrentvpn to work. From reading this thread, I determined (guessed) that I was missing the openvpn config files for PIA. So I downloaded them and dumped them all in the "openvpn" directory. The container has now started, but I am unable to access the webui. Could you point me in the right direction for troubleshooting this further? supervisord.log

I'm not a very educated Linux user and all of a sudden I'm getting a "Permission Denied" error for any files in Deluge. Would someone be able to point me in the right direction for where to troubleshoot this? Deluge Preferences Docker Setup Thanks. EDIT: Apparently I am using the delugeVPN docker. I'm going to leave this hear unless the creator wants me to move it as I would hope the problem isn't directly related to the VPN component. If it is requested that I repost in that container forum, I will do so.

Apologies. I will try to locate the correct one.

I'm not a very educated Linux user and all of a sudden I'm getting a "Permission Denied" error for any files in Deluge. Would someone be able to point me in the right direction for where to troubleshoot this? Deluge Preferences Docker Setup Thanks.

Okie dokie. So I went through and did this. I only had the 4 containers (binhex-delugevpn, binhex-radarr, binhex-sabnzbd, and binhex-sonarr). Everything seemed to go smoothly. However, when I attempt to access binhex-sonarr, it is now completely blank (fresh setup) (that's ok, I can reconfigure it when I get home), but binhex-radarr is now doing what binhex-sonarr was doing before; it's not running and when I try to run it, I'm getting the "Execution error". EDIT: So likely that the radarr database is corrupt and I'll need to delete that as well? EDIT 2: Attempted to delete a few times and install. No luck. Still getting "Execution error". EDIT 3: Success. I had the same port set for both Radarr and Sonarr somehow. I still need to do full configuration, which sucks, but at least I'm making progress.

Ok. Got it. (Sorry I cannot screenshot when I'm remote) Docker Version: 1.12.6 Docker storage location: /mnt/disk1/docker.img Docker appdata storage location: /mnt/user/appdata Template Authoring Mode: No

I know, I'm an idiot, but I truly don't know. I usually just follow a tutorial for how to do something and tend to forget why or what I've done. I don't recall the unassigned devices plugin being tied to Sonarr though... I'm pretty sure I installed that to see if I could put stuff directly from the unRAID system onto like a USB stick. EDIT: Testing a bit more through remote access, my other two dockers (SAB and Deluge) are both working. It's just binhex-sonarr and binhex-radarr that have stopped working properly.

I agree. I think that due to my lack of true understanding of how the system operates, I may have been missing warning signs. Other dockers (SabNZBD for example) do seem to still be working, but that could just be a coincidence. I'm still trying to get a viable/useful response on the main forums. I've been trying to educate myself on the system all morning, but what I would think would be a simple task like "check the health of the drives" seems to be problematic. Just so I'm 100% clear here, the docker is running on the array, not on the USB stick, correct? So a disk error could cause the corruption? Thanks again for pointing me in the right direction; I know we've kind of eliminated your docker as the problem, and that's great. Baby steps.

I'm trying to catch up on knowledge here, so just so I'm clear, you pointed to that post about the csrf errors. On my system, I'm getting the "Execution error" that I mentioned. Is that representative of the csrf error that is shown in the log (wrong csrf_token)? The post you linked to states: wrong csrf_token - CSRF tokens are randomly generated at every boot of unRaid. You will see this error if you have one browser tab pointed at a page in unRaid and on another tab you initiate a restart of unRaid. Note that the browser in question can also be on any device on your network. This includes other computers, tablets, phones, etc. This error can also be caused by mobile apps such as ControlR checking the status of unRaid but the server has been rebooted after the app was started. Restart the application to fix. This states to restart the application to fix. I've done this multiple times to no avail. So I'm assuming that's where the second part of your statement comes in to play; that it is something to do with the I/O error likely caused by potential disk failure. So I guess what I'm asking now is, should my next step be some sort of health check on the drives to determine which is failing? EDIT: Attempted another full clean install of binhex-sonarr after removing what I thought were all traces. Still getting the "Execution error."

Thank you very much for the reply. I'm in way over my head here. I posted this last night, but haven't had any replies yet. Hopefully someone will be able to help when I get back from work. If you have any further suggestions, I'd be very appreciative.

Sonarr has started failing on me and I'm not sure why. It started a couple of weeks ago where the web interface would become unresponsive. I would reboot the server, it would work for a bit, and then stop. I've been having trouble with Sonarr for the last couple of weeks where the web interface will just stall out. I'm running it as a docker through unRAID. Here are the logs from a recent Sonarr session. Here's a small snippet: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/supervisor/loggers.py", line 84, in emit self.flush() File "/usr/lib/python2.7/site-packages/supervisor/loggers.py", line 64, in flush self.stream.flush() IOError: [Errno 5] Input/output error 2017-07-27 16:46:47,335 DEBG 'sonarr' stdout output: [Error] TaskExtensions: Task Error Anybody have any idea as to what is going on here? EDIT: Attempted to do a clean install with the intention of restoring from backup. The docker will not start now and I'm getting a bunch of errors in the log. https://i.imgur.com/T1krupo.png EDIT 2: And now Radarr is failing in the same way. What the hell is going on?

I'm attempting to follow the instructions outlined in the video tutorial here. I'm running into problems at about the 5 minute mark. After I fill out all the information in the "Update Container" section of unRAID, I click on "Create" at the bottom. Everything seems to complete successfully, however, when I go to the "Docker" section of unRAID, I do not see the binhex-delugeVPN as an option as should be. I'm fairly new to this and a little over my head. Would anyone be able to assist? Below is the command result from the docker installation (UN/PW removed obviously). Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="binhex-delugevpn" --net="bridge" --privileged="true" -e VPN_ENABLED="yes" -e VPN_USER="xxxxxxxxx" -e VPN_PASS="xxxxxxxxx" -e VPN_REMOTE="ca-toronto.privateinternetaccess.com" -e VPN_PORT="1198" -e VPN_PROTOCOL="udp" -e VPN_DEVICE_TYPE="tun" -e VPN_PROV="pia" -e VPN_OPTIONS="000" -e STRONG_CERTS="no|yes" -e ENABLE_PRIVOXY="no|yes" -e LAN_NETWORK="192.168.1.0/24" -e NAME_SERVERS="8.8.8.8,37.235.1.174,8.8.4.4,37.235.1.177" -e DEBUG="false|true" -e UMASK="000" -e PUID="99" -e PGID="100" -e TZ="America/New_York" -p 8112:8112/tcp -p 58846:58846/tcp -p 58946:58946/tcp -p 58946:58946/udp -p 8118:8118/tcp -v "/mnt/cache/appdata/config":"/config":rw -v "/mnt/user/Downloads/":"/data":rw binhex/arch-delugevpn yes: invalid option -- 'e' Try 'yes --help' for more information. yes: invalid option -- 'e' Try 'yes --help' for more information. docker: "run" requires a minimum of 1 argument. See '/usr/bin/docker run --help'. Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...] Run a command in a new container The command finished successfully!