lovingHDTV

Ok I enabled it. I used the local syslog folder and set it to a cache folder. Do I need to restart or anything? It typically takes several days before I have an issue, sometimes weeks. thanks,

I've been getting seemingly random crashes after upgrading to 6.11. I'm currently at 6.11.1 and will update after my parity check completes from this AMs crash. Is there a way to save the previous syslog so I can keep the crash information for the next time? I've attached my syslogs after the reboot. I did see an out of date plg that I removed, and fixed my SMTP settings. Ideas? tower-diagnostics-20221128-0810.zip

I've been able to use the automatic docker conversion in the past successfully. But recently I've tried several dockers and the conversion seems to work, but the docker never starts. I get no log file, nothing. It just doesn't start. The latest one is: https://hub.docker.com/layers/kosdk/powershellcore/latest/images/sha256-0bd0c264854a6e83e063c3bd943fb68d590ca0cdd192c5dd6ea797ae8a956465?context=explore I'm trying to get a docker that I can connect to and run power shell to test some things. How do I go about trying to debug why none of my conversions actually work? thanks

I changed over to the official docker and everything works again

the latest update doesn't start for me either. I get "Failed to create CoreCLR, HRESULT: 0x8070008

Interesting. Originally it as Arlington, then that quit working and it became Ashburn. With the latest Ashburn quit working, but it is now back to Arlington. Oddly after connecting to "Arlington", the log file reports the public IP as being United States, Virginia, Ashburn). . . Either way, it is working again.

After the latest update I can no longer get onto Privado VPN. I have been using Regon: Virginia, Country: United States, City: Ashburn. That is still listed as a valid setup on the wiki. However, I now get a message that Ashburn is no longer a valid city. I tried to change to washington, DC as the region as it is listed as a valid choice by the docker, but it won't take that either. For now I've switched to Dallas, TX. Any ideas?

The drive I store my downloads on filled up. /dev/sdh1 1.9T 1.9T 56M 100% /mnt/disks/LocalBackup The server still serves files, I can access all dockers but qBittorrent. So it does work, but with the drive I need to resolve the filled up drive issue. How do I recover from this? I cannot: cd /mnt/disks/LocalBackup; ls , it hangs I was hoping to remove some files to get through it, like I do on other linux systems. access the web page, as it times out docker stop qbittorrent, it hangs /etc/rc.d/rc.docker stop, it hangs shutdown ,it hangs reboot, it hangs reboot -n, it hangs This is a reoccurring theme that I've found with unRaid. When it works, its amazing, when something goes wrong, power cycle and pray. Is there any way to recover unRaid when a drive fills up and a docker is still trying to write to it? I really don't want to power cycle it. thanks david

Typically, this works well for me. However, if the routing container disappears then the web interfaces gets stuck in a loop of trying to rebuild all the dependent containers. It never returns so that I can fix the underlying problem. The underlying issue is that when I updated glueTUN it disappeared and became an abandoned image. So I need to re-install it. I had to edit every dependent docker to no longer route through glueTUN, then apply and stop the docker. I could then add glueTUN back and redo all the other dockers. Is this how it is expected to work?

Thanks, kicked of a correcting check.

Yesterday my server lost power and it had an unclean shutdown. I the past I have always run pairty check with auto correct turned on. Recenlty I disabled that as I figured I wasn't able to see if I ever had errors. I never saw a report that says xxx errors corrected. The parity run that automatically kicked off when I restarted the server has reported a ton of errors. Current operation started on Sat 01 Jan 2022 02:03:48 PM EST (yesterday) Finding 68180805 errors Elapsed time: 21 hours, 48 minutes Estimated finish: 5 hours, 31 minutes I had successfully ran a parity check a week or so ago without error, so something happened when the server lost power. Ideas on where I can start looking to try and figure out what is happening? My disk smart data is fairly clean I only have a single drive with 8 allocated sectors. I do see messaging in syslog: Jan 2 08:42:13 tower kernel: eth0: renamed from veth756310a Jan 2 08:50:09 tower kernel: veth756310a: renamed from eth0 Jan 2 08:50:23 tower kernel: eth0: renamed from veth71571d0 Jan 2 09:35:12 tower emhttpd: spinning down /dev/sdj Jan 2 09:51:27 tower kernel: md: recovery thread: P incorrect, sector=19532874280 Jan 2 09:51:27 tower kernel: md: recovery thread: P incorrect, sector=19532874288 Jan 2 09:51:27 tower kernel: md: recovery thread: P incorrect, sector=19532874296 Jan 2 09:51:27 tower kernel: md: recovery thread: P incorrect, sector=19532874304 Jan 2 09:51:27 tower kernel: md: recovery thread: P incorrect, sector=19532874312 Jan 2 09:51:27 tower kernel: md: recovery thread: P incorrect, sector=19532874320 .... Jan 2 09:51:27 tower kernel: md: recovery thread: P incorrect, sector=19532876584 Jan 2 09:51:27 tower kernel: md: recovery thread: P incorrect, sector=19532877352 Jan 2 09:51:27 tower kernel: md: recovery thread: stopped logging Jan 2 10:18:48 tower emhttpd: spinning down /dev/sdi Jan 2 10:18:58 tower emhttpd: spinning down /dev/sdh Jan 2 10:18:58 tower emhttpd: spinning down /dev/sdf Jan 2 10:19:01 tower emhttpd: read SMART /dev/sdh J thanks, david tower-diagnostics-20220102-1144.zip

Tha That worked fine. thanks

Things are running fine now. Sonarr can successfully send requests to qbittorrent and nzbget and import the resulting downloads. In order to get nzbget to work I had to disable DOT. When I enable DOT, nslookup in GluetunVPN, nzbget and the other dockers it fails to work. I get the following: sh-5.1# nslookup secure.usenetserver.com Server: 127.0.0.1 Address: 127.0.0.1#53 ** server can't find secure.usenetserver.com: NXDOMAIN sh-5.1# nslookup www.google.com Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: Name: www.google.com Address: 142.250.191.196 Name: www.google.com Address: 2607:f8b0:4009:81a::2004 This is true for the two docker I have that have nslookup installed. My DOT settings are fairly default. I just changed to quad9. Is there something I need to change in each docker to get this to work? If I run it on the unraid machine I get: root@tower:/mnt/cache/appdata/gluetun# nslookup secure.usenetserver.com Server: 192.168.1.1 Address: 192.168.1.1#53 Non-authoritative answer: secure.usenetserver.com canonical name = news.usenetserver.com. news.usenetserver.com canonical name = us.na.news.geo.usenetserver.com. us.na.news.geo.usenetserver.com canonical name = news.iad.usenetserver.com. Name: news.iad.usenetserver.com Address: 85.12.62.221 Name: news.iad.usenetserver.com Address: 85.12.62.240 thanks

Why do I find the answer 5 minutes after posting? I looked for an hour . . . Anyway for someone else that may have the same issue. You need to add the FIREWALL_OUTBOUND_SUBNETS

I have the docker up and running. I've added ports for sonarr, jacket, nzbget, qbittornet. Each docker can access the internet and I have verified it has the VPN IP address. Each docker works with its interface to the internet. Sonarr can find TV series, qbittorren is downloading torrents, etc. However, Sonarr cannot access the downloaders, nor jacket any longer. they just timeout. So I'm missing the piece that integrates them together. I must have messed something up. Suggestions? thanks david

OK I'll start from the beginning. When I load the opvn setup file from my VPN provider (Privado) I get: + exec sg vpn -c 'openvpn --cd /vpn --config /vpn/jfk-032.ovpn --script-security 2 --redirect-gateway def1 --auth-user-pass /vpn/vpn.auth ' Options error: Unrecognized option or missing or extra parameter(s) in /vpn/jfk-032.ovpn:24: data-ciphers (2.4.9). Here is the header part of the opvn file. I added the vpn.auth portion only. client dev tun #dev-node "PrivadoVPN (OpenVPN)" proto udp remote jfk-032.vpn.privado.io 1194 resolv-retry infinite nobind persist-key persist-tun persist-remote-ip verify-x509-name jfk-032.vpn.privado.io name tls-client #block-outside-dns route-ipv6 ::/0 route 0.0.0.0 0.0.0.0 vpn_gateway tls-cipher TLS-DHE-RSA-WITH-AES-256-CBC-SHA:TLS-DHE-DSS-WITH-AES-256-CBC-SHA:TLS-RSA-WITH-AES-256-CBC-SHA remote-cert-tls server auth-user-pass vpn.auth verb 3 auth SHA256 data-ciphers AES-256-CBC data-ciphers-fallback AES-256-CBC route-delay 3 From what I've read (not an expert at all), it means I have to run version 2.5 client.

I do have piHole, but already have the extra paramenters. I think it is because data-ciphers are now required. I commented those lines out, but think that is probably the issue. thanks

Looks like this is a known issue. Privado requires v2.5 Upgrade openvpn to 2.5.x to manage data-ciphers options · Issue #392 · dperson/openvpn-client (github.com) david

I've recently been getting the following error when I try to connect to Privado VPN. Prior to this everything has been running fine. I don't recall any changes I've made. Ideas? thanks david

Good to know. I continued as described in the write up as that seemed the least risky. Should be done with the rebuild in a few hours. thanks

The copy just finished. It is now at the prompt for me to start the array, expand and rebuild the data drive. Can I shutdown the system and move it to its closet before rebuilding? I'd like to get it back onto its UPS and off my work bench. thanks david

I was able to complete the parity swap flow. I unassigned the original parity, assigned the 14TB drive as the new parity. I then assigned the old parity as the new data drive. I then got the "copy parity over" button and it is currently copying the old parity drive to the new drive. Then it is supposed to rebuild the data drive.

What happens when you mislabel two drives because their serial numbers are off by one letter? You get really confused!!!! Anyway, my isssue is that the drive that didn't get plugged in all the way had the wrong serial number label on it. So, I was "debugging" a perfectly good working drive. When I left it unplugged, because I gave up on it, I then saw TWO drives missing. Panic ensued. . . Hint: When you print serial number labels for you drives so you can easily match the drive in the case to the drive in UnRaid. Make sure you do it correctly

I do have a couple 1TB and 2TB drives, but they are smaller than the missing 5TB. Does that matter?

I'm at a complete loss now. After rebooting several times trying to get he 5TB drive to come up. I gave up and hooked in the 4tB drive again. When I boot I now see the 4TB drive, but another 5TB drive is gone. I've attached diagnostics in case someone can spot something. tower-diagnostics-20211212-1428.zip