LVLAaron

Gotcha. Just wanted to double check. My pre-clear on these drives was mainly for a burn in process. Going to stop the pre-clear and figure out this drive. Thanks guys!

Yep. I gotcha. With the replace procedure, do I have to wait for the drive to be cleared/zeroed or is the array "online" and just rebuilding from parity? If that's the case, I don't need to let the new drives finish their pre-clear and I can just power off and see what's up with this failed drive and save half of a nervous day.

I was in a bind. Out of ports, had to remove a drive so I had room to install my 2 new 4TB disks. FWIW: The 2 new drives are running pre-clear on the marvell controller. Maybe it's just swamped and that little 2.5 inch drive showing as failed isn't good at recovering itself or surviving a crappy controller?

The zeroing phase on my 2 new 4TB drives is about 80 percent complete and will be done in a few hours. I have an identical 1TB drive going through pre-clear on another box just to inspect it just in case.

Is that the "enable virtualization" piece in the bios? EDIT: I did just install that controller yesterday so I could add a drive and start removing old small drives from the array.

tower-diagnostics-20170126-1035.zip

I read through the swap-disable procedure and am comfortable with that. (I have backups) I have another 1tb drive that I could use to just swap the bad one at this point. It is old and is a 2.5inch drive, It's probably close to death anyway. Does the pre-clear help me at all with the swap disable? Ie, will I still be waiting for unraid to clear the drive in that process?

My parity drive is 1.5TB today. One of those new 4TB drives was going to be used to replace that. Parity today is 1.5TB If I replace the "failed" 1TB drive with a 4TB drive... I know the parity drive needs to be the biggest drive. * Can I replace the 1TB drive with a new 4TB drive? - will unraid throw an errors about adding that in there? How will it handle the extra 3TB? Will that become available once I upgrade the parity drive? - I"ll start a new thread for this in a relevant area. * My question remains, can I kill the pre-clear during the post-read? it's almost done and I dont want to wait another 12 hours to replace this drive.

I'm in a bit of a bind. Installed 2x new 4TB drives in my system and am preclearing them. Which will take ages. Overnight I ran into an issue where a 1TB drive in the system has died :o :o :'( Can I kill the preclear process and proceed as normal after step "5. verifies the signature" when it starts the post read? Put another way, can I kill the preclear process DURING the post-read and add the drive to my array?

Yep. I put that variable in, used the same address as in my .ovpn file and she works.

I added that and have the same issue 2016-08-04 14:56:29,214 DEBG 'start-script' stdout output: [info] VPN provider defined as airvpn [info] VPN config file (ovpn extension) is located at /config/openvpn/AirVPN_United-Kingdom_UDP-443.ovpn 2016-08-04 14:56:29,225 DEBG 'start-script' stdout output: [crit] VPN provider remote gateway not defined (via -e VPN_REMOTE), exiting... 2016-08-04 14:56:29,225 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 46960181956048 for <Subprocess at 46960181886056 with name start-script in state RUNNING> (stderr)> 2016-08-04 14:56:29,226 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 46960181955328 for <Subprocess at 46960181886056 with name start-script in state RUNNING> (stdout)> 2016-08-04 14:56:29,226 INFO exited: start-script (exit status 1; not expected) 2016-08-04 14:56:29,227 DEBG received SIGCLD indicating a child quit

I updated my docker and now it will not start... [info] deluge config file already exists, skipping copy 2016-08-04 14:44:20,912 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-08-04 14:44:20,912 INFO success: webui-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-08-04 14:44:20,912 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-08-04 14:44:20,912 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-08-04 14:44:20,914 DEBG 'deluge-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2016-08-04 14:44:20,919 DEBG 'privoxy-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2016-08-04 14:44:20,929 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2016-08-04 14:44:20,947 DEBG 'start-script' stdout output: [info] VPN provider defined as airvpn [info] VPN config file (ovpn extension) is located at /config/openvpn/AirVPN_United-Kingdom_UDP-443.ovpn 2016-08-04 14:44:20,949 DEBG 'start-script' stdout output: [crit] VPN provider remote gateway not defined (via -e VPN_REMOTE), exiting... 2016-08-04 14:44:20,950 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47065995242960 for <Subprocess at 47065995241952 with name start-script in state RUNNING> (stderr)> 2016-08-04 14:44:20,950 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47065995242168 for <Subprocess at 47065995241952 with name start-script in state RUNNING> (stdout)> 2016-08-04 14:44:20,950 INFO exited: start-script (exit status 1; not expected) 2016-08-04 14:44:20,950 DEBG received SIGCLD indicating a child quit Any help is appreciated.

Got it! Thanks dude!

Will wee see an update to version 1.0.3 any time soon?

Enable SMB Security = No

I'm having a hard time with this plugin lately. unRAID 6.1.9 and the latest version of the plugin. If I set to share my external device, the share shows up but on a windows client I am asked for username/password and cannot log in. From the mac it says "cannot be found" and finder closes out. Any help would be appreciated as this is a helpful feature.

I think this is what most of us are using to integrate sickbeard and sabnzbd sabToSickBeard.py #!/usr/bin/env python # Author: Nic Wolfe <[email protected]> # URL: http://code.google.com/p/sickbeard/ # # This file is part of Sick Beard. # # Sick Beard is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Sick Beard is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Sick Beard. If not, see <http://www.gnu.org/licenses/>. import sys try: import autoProcessTV except: print ("Can't import autoProcessTV.py, make sure it's in the same folder as " + sys.argv[0]) sys.exit(1) # SABnzbd user script parameters - see: http://wiki.sabnzbd.org/user-scripts # 0 sys.argv[0] is the name of this script # 1 The final directory of the job (full path) if len(sys.argv) < 2: print ("No folder supplied - is this being called from SABnzbd?") sys.exit(1) else: download_final_dir = sys.argv[1] # 2 The original name of the NZB file org_NZB_name = sys.argv[2] if len(sys.argv) > 3 else None # 3 Clean version of the job name (no path info and ".nzb" removed) clean_NZB_file = sys.argv[3] if len(sys.argv) > 4 else None # 4 Indexer's report number (if supported) indexer_report = sys.argv[4] if len(sys.argv) > 5 else None # 5 User-defined category sab_user_category = sys.argv[5] if len(sys.argv) > 6 else None # 6 Group that the NZB was posted in e.g. alt.binaries.x group_NZB = sys.argv[6] if len(sys.argv) > 7 else None # 7 Status of post processing. 0 = OK, 1=failed verification, 2=failed unpack, 3=1+2 sab_post_processing_status = sys.argv[7] if len(sys.argv) > 8 else None # Only final_dir and org_NZB_name are being used to process episodes autoProcessTV.processEpisode(download_final_dir, org_NZB_name)

It works... not like that. You'd have to attach yourself to the actual docker instance. do a "docker ps" and find your container ID. Then "docker exec -i -t 665b4a1e17b6 bash" (replace with the proper ID) and you'll be inside your container.

I recently updated SABnzbd (2/25/2016) and am now having trouble with post processing. I use SABnzbd and SickBeard along with the sabToSickBeard.py script to do post processing. SAB is failing on the post processing step stating that python cannot be found. The error in the WebUI is: /usr/bin/env: ‘python’: No such file or directory and the first line of the script it is trying to run is #!/usr/bin/env python Has something changed in the docker plugin? I don't know enough about docker to troubleshoot this.

I figured out that you can get the same hardware as the tiny hardware firewall I linked to earlier; http://www.amazon.com/GL-AR150-router-150Mbps-OpenWrt-Pre-installed/dp/B015CYDVG8/ref=sr_1_1?ie=UTF8&qid=1454177424&sr=8-1&keywords=gl+ar150 So if you already have a VPN account somewhere this would work. it's not free, but I like hardware... less risk of non-proxy'd connections.

Well, if I just get two new 4tb drives and migrate to those, XFS will be easy.

Are you using reiserfs with almost full disks? First thing that comes to mind with your symptoms. ReiserFS yes. One disk is 99 percent full so it never gets any writes; it's just movies. The rest are 70-80 percent.

I'm going to replace the parity drive. It's an old 1.5TB drive from back when that was the biggest drive you could get. If the parity drive is falling apart that would explain crappy writes. Most of the drives are 3+ years powered on and have been in the array for 5 or more. This is a good time and excuse to replace everything with 2x4TB drives and remove the existing 7 disks that are spinning in there . I've only got about 3.2TB of data.

I have several 500 and 750gb drives in an array that have been running for... many years. I do not know how to properly interpret the the smart report data so some assistance would be appreciated. # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value Parity 5 Reallocated sector count 0x0033 100 100 036 Pre-fail Always Never 6 188 Command timeout 0x0032 100 099 000 Old age Always Never 2 Disk2 188 Command timeout 0x0032 100 099 000 Old age Always Never 12885098502 Disk3 188 Command timeout 0x0032 100 099 000 Old age Always Never 17180131332 I looked into this because at times browsing around the SMB shares is sometimes clunky. Right clicking on folders can be slow to open the context menu, sometimes copying files is is slow, almost zero. Thoughts?

I have added 15 00 * * * /usr/bin/rsnapshot -c /etc/rsnapshot.conf hourly 15 02 * * * /usr/bin/rsnapshot -c /etc/rsnapshot.conf daily 15 03 * * Sun /usr/bin/rsnapshot -c /etc/rsnapshot.conf weekly 30 03 1 * * /usr/bin/rsnapshot -c /etc/rsnapshot.conf monthly /boot/config/plugins/rsnapshot.cron and nothing gets added to /etc/cron.d/root Thoughts?