IamSpartacus

I have DelugeVPN working great on one of my Ubuntu 16.04 Servers but I've tried to setup a new docker on a different server and no go. I'm getting the following errors in the logs: 2016-09-07 19:26:59,982 DEBG 'start-script' stdout output: Wed Sep 7 19:26:59 2016 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, [email protected] Wed Sep 7 19:26:59 2016 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed Wed Sep 7 19:26:59 2016 TLS_ERROR: BIO read tls_read_plaintext error Wed Sep 7 19:26:59 2016 TLS Error: TLS object -> incoming plaintext read error Wed Sep 7 19:26:59 2016 TLS Error: TLS handshake failed Docker looks like this: docker create \ --cap-add=NET_ADMIN \ -p 8112:8112 \ -p 8118:8118 \ --name=delugevpn \ -v /storage/downloads:/data \ -v /docker/containers/delugevpn/config:/config \ -v /etc/localtime:/etc/localtime:ro \ -e VPN_ENABLED=yes \ -e VPN_USER=<username> \ -e VPN_PASS=<password> \ -e VPN_REMOTE=us-east.privateinternetaccess.com \ -e VPN_PORT=1194 \ -e VPN_PROTOCOL=udp \ -e VPN_PROV=pia \ -e STRONG_CERTS=no \ -e ENABLE_PRIVOXY=no \ -e LAN_NETWORK=10.0.10.0/24 \ -e DEBUG=false \ -e PUID=1000 \ -e PGID=1000 \ binhex/arch-delugevpn Any thoughts? I've even tried rsyncing the config over from my working docker but that's a no go either. It appears the old docker used a ca.crt where as the new docker is using a ca.rsa.2048.crt (same goes for the .pem file).

Just so you know there is both an AHCI and NVMe version of this drive. I had the AHCI version and it worked just fine with version 6.0 and 6.1. Have you confirmed that your motherboard is in fact detecting the drive first off?

Through UnRAID no, but since my server is joined to AD I lose access to those files via other AD joined Windows PC's when they permissions get changed.

My dockers are running on my UnRAID server they are running on a separate Ubuntu 16.04 Server. I have fixed the permissions many times but I'm looking for a solution that will keep things automated without me having to constantly fix permissions each time a new folder is moved/created by one of my Dockers. No matter what the base system you're running them on, the concept is still the same 0777 gives rwx access to the files / folders for the owner, the group members, and other members. And as you can see from my SS#2, I have the permissions set to 0777 so how is that permissions are getting set to SS#1 when CP moves my newly DL'd movie from /mnt/user/Downloads to /mnt/user/Movies?

My dockers are running on my UnRAID server they are running on a separate Ubuntu 16.04 Server. I have fixed the permissions many times but I'm looking for a solution that will keep things automated without me having to constantly fix permissions each time a new folder is moved/created by one of my Dockers.

Anytime my CouchPotato or Sonarr dockers add a new folder such as a new movie or a new TV show (not a new episode to an already created TV show folder), the permissions seem to get screwed up for those folders. I've tried setting the CP permissions to 777 instead of 0777 but the permissions get even more screwed up that way. I know I'm doing something wrong because I'm a Windows guy a know very little about Linux permissions.

This very slow disk scanning has caused my parity checks to slow to a crawl since I have my Plex server set to scan libraries each hour. Typically these scans took about 30 seconds per library but not they are taking more than a half hour which means they are pretty much just perpetually scanning. Because of this, the parity checks slow to a crawl. I think I'm going to have to unjoin from AD since that's the only change I've made recently.

So I joined my UnRAID server to AD and now any kind of disk scanning (Plex library scans or SyncBack backups) is now SUPER slow. Seeing nothing in the logs during the scans at all. Anyone else see slow downs when bound to AD? Running 6.2RC3.

Is there any way (or will there be in the final release of 6.2) to prevent the automatically created shares (ie. appdata, domains) from being recreated after each upgrade once they've been deleted?

Has anyone successfully implement folder redirection through group policy using an UnRAID share (ie. Home Drives)? It seems each time I login to a new computer and the folders redirect to the network share, the permissions get all screwed up and the home drive's owner changes from the user to nobody. My only experience with AD is using Windows file servers so I'm not sure how well this plays with Linux file servers.

I'm trying to change the DNS server #1 of my UnRAID server to my Windows Server 2012r2 box so that I can add it to my domain. However, when I change the DNS settings in the WebUI and hit apply it doesn't change the DNS server IP and I see the following entries in the log: Jul 26 21:45:21 UNRAID avahi-dnsconfd[22244]: New DNS Server 8.8.8.8 (interface: 20.IPv4) Jul 26 21:45:21 UNRAID avahi-dnsconfd[22244]: New DNS Server 71.250.x.x (interface: 20.IPv4) Jul 26 21:45:21 UNRAID avahi-dnsconfd[22244]: New DNS Server 68.237.x.x (interface: 20.IPv4) Jul 26 21:45:21 UNRAID avahi-dnsconfd[22244]: New DNS Server 8.8.4.4 (interface: 20.IPv4) None of those IP's are the ones I changed DNS Server #1 to and I left #2 and #3 blank. Furthermore if I run 'cat /etc/resolv.conf' from the CLI I get the following output: nameserver 8.8.4.4 nameserver 68.237.161.12 nameserver 71.250.0.12 nameserver 8.8.8.8 nameserver 208.67.220.220 nameserver 208.67.222.222 Until I can get my DNS to change I can't add UnRAID to my domain. Not sure where to go from here. EDIT: Updating the nameservers in /etc/resolv.conf seems to have done the trick though the WebUI is none the wiser sand still displays the wrong IPs.

I've been seeing the following log entries from time to time in my logs. I know that since I'm running UnRAID in a VM on ESXi that I'm not running a "supported" version of UnRAID but just looking for any insight as to what may be causing this so I can troubleshoot it myself. Jul 20 13:55:44 SPE-UNRAID kernel: nfsd: non-standard errno: -38 Jul 20 13:55:44 SPE-UNRAID kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net vhost macvtap macvlan tun xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod vmw_vsock_vmci_transport vmw_vmci coretemp mpt3sas raid_class mptsas mptscsih mptbase i2c_piix4 scsi_transport_sas intel_agp intel_gtt ata_piix agpgart acpi_cpufreq Jul 20 13:55:44 SPE-UNRAID kernel: CPU: 0 PID: 8946 Comm: nfsd Tainted: G W 4.4.15-unRAID #1 Jul 20 13:55:44 SPE-UNRAID kernel: Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/21/2015 Jul 20 13:55:44 SPE-UNRAID kernel: 0000000000000000 ffff8802359bbcf8 ffffffff81369dfe ffff8802359bbd40 Jul 20 13:55:44 SPE-UNRAID kernel: 0000000000000324 ffff8802359bbd30 ffffffff8104a31d ffffffff811efdba Jul 20 13:55:44 SPE-UNRAID kernel: ffff880229df0408 ffff880229df0548 ffff88014942b540 ffff88023569c000 Jul 20 13:55:44 SPE-UNRAID kernel: Call Trace: Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff81369dfe>] dump_stack+0x61/0x7e Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff8104a31d>] warn_slowpath_common+0x8f/0xa8 Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff811efdba>] ? nfserrno+0x43/0x4a Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff8104a379>] warn_slowpath_fmt+0x43/0x4b Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff811123a7>] ? vfs_link+0x192/0x219 Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff81229763>] ? create_new_entry.constprop.12+0x15d/0x177 Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff811efdba>] nfserrno+0x43/0x4a Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff811f26a6>] nfsd_link+0x1e5/0x27a Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff811f79c5>] nfsd3_proc_link+0xae/0xba Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff811eeab4>] nfsd_dispatch+0x8d/0x145 Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff8160036a>] svc_process+0x3bb/0x632 Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff811ee65e>] nfsd+0x102/0x154 Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff811ee55c>] ? nfsd_destroy+0x69/0x69 Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff8105f910>] kthread+0xcd/0xd5 Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff8105f843>] ? kthread_worker_fn+0x137/0x137 Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff816232bf>] ret_from_fork+0x3f/0x70 Jul 20 13:55:44 SPE-UNRAID kernel: [<ffffffff8105f843>] ? kthread_worker_fn+0x137/0x137 Jul 20 13:55:44 SPE-UNRAID kernel: ---[ end trace ec6c29089916b320 ]---

Ditto. Updated for 6.2-RC2 As always... You are the man Zeron! Sent from my Nexus 5X using Tapatalk

Ditto.

How can I stop the email notifications I'm getting when one of the plugins I've have configured to auto update is in fact updated? My current Notification Settings are set as such. Is it Notices?

Hi, i just upgraded my test server from 6.1.9 to 6.2RC1 and this issue is back again no changes on test server hardware/host software.. and looks like workaround with second USB/UPS on USB is still working. I upgraded my backup server from 6.2b23 to 6.2RC1 last night and I haven't gotten any USB reset errors. Will probably give it a few more days before I upgrade my main. Running ESXi 6.0 U2.

Ok booted bare metal and data rebuild has commenced. We'll see how it goes.

I am on VMware. I can boot this server bare metal if need be though. Just not sure where to go from here. Stop the data rebuild? Sent from my Nexus 5X using Tapatalk

Here you go. You can ignore all the "refused mount request from 10.0.10.202" messages in the log. That's something on my end and is unrelated. spe-unraid-bckp-diagnostics-20160623-0953.zip

After running 3 preclear cycles on a new 8TB disk, I assigned it as a replacement for one of my disks (a 3TB disk). Parity Check / Data Rebuild commenced. I checked on it during the first few hours and it was going along just fine (over 120MB/s). The last time I checked the status yesterday it was at 20% and still chugging along. Then I login this morning to check and I see the following: P.S. I'm on 6.2b23.

Considering we don't even have a RC out yet I'd say that's highly unlikely.

Under \\<Server>\flash\preclear_reports\ I have no preclear reports in there from the 3 cycles I just ran on my new Seagate 8TB drive. The latest ones I have are from 02-19-2016. EDIT: Don't mind my slowness this morning...I was looking at the wrong server .

Where do the preclear reports output to with the new beta plugin? Can't seem to find them.

Correct, the beta plugin is stand-alone. Thanks Johnnie that clears everything up. Quick question on the preclear script settings. If running multiple cycles on a disk, what's the best/fastest setting with regard the skip pre/post read options?

Running 6.2b23 and I keep getting the device busy error. I've installed the beta plugin as well as edited preclear_disk.sh with the following command: sed -i -e "s/print \$8 /print \$9 /" -e "s/sfdisk -R /blockdev --rereadpt /" preclear_disk.sh What am I missing?