nationapn

Thank you for all the info...I’ll be keeping a better eye on attributes 1 and 200 meow. Think I’m ok to just replace and repair from parity, then? Merry Christmas!

Thank you for the time and help! So I presume you mean I should add “1,200” to the custom attributes field? As suggested, it then says “failed” for that drive on the dashboard. Reading between the lines, it sounds like I do, in fact, have a bad drive, then. Out of curiosity, though, from those errors are you able to explain what is failing in the disk? Any reason for me to worry about what has been written to the parity drive? Also, I take it that I should start monitoring attributes 1 and 200 on my other 4 WD reds? Again, I really appreciate your help

All of the disks say “healthy” on the dashboard page. When I run a quick SMART test on the drive in question, it passes. However, it failed the extended SMART test (with the previously attached log).

Happy Holidays fellow UnRAIDers, Does anyone happen to know if there’s a quick reference or secret decoder ring for understanding various disk errors on parity checks and/or SMART tests? I run a parity check every month and have had read errors on one of my drives the past two months. I am ready to replace it with a new drive, but before tossing out what could be a good drive (but with a bad cable), I thought I’d check with the collective knowledge of folks who know a whole lot more than me. Attached are the results of an extended SMART test and a screenshot of the errors I get with the parity check. Thanks for the help, and Merry Christmas! Andy WDC_WD60EFRX-68L0BN1_WD-WX21DC5J2Y6J-20201224-1855.txt

Perhaps someone can help me with a weird issue I am having with Ombi. I have it set up with a reverse proxy using LetsEncrypt (now Swag), and it works perfectly via the web or organizrr. The issue I am having has to do with the Ombi iPhone app. On a fresh start of the Ombi docker, the app works as advertised. However, after some period of time (maybe a few hours), the app has an issue with requesting content (takes a while, then gives a “The request timed out” message. The only way I can get it to work again is to restart the Ombi docker. Of course, my workaround is to run a user script that restarts the Ombi docker periodically, but this is a band-aid until I can actually solve the issue. Here is my Swag config: # first go into ombi settings, under the menu "Ombi" set the base url to /ombi and restart the ombi container location /ombi { return 301 $scheme://$host/ombi/; } location ^~ /ombi/ { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth, also customize and enable ldap.conf in the default conf #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_ombi ombi; proxy_pass http://$upstream_ombi:3579; } # This allows access to the actual api location ^~ /ombi/api { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_ombi ombi; proxy_pass http://$upstream_ombi:3579; } if ($http_referer ~* /ombi) { rewrite ^/api/(.*) /ombi/api/$1? redirect; } # This allows access to the documentation for the api location ^~ /ombi/swagger { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_ombi ombi; proxy_pass http://$upstream_ombi:3579; } if ($http_referer ~* /ombi) { rewrite ^/swagger/(.*) /ombi/swagger/$1? redirect; } Appreciate any help/insight! Having to restart the docker really defeats the purpose of having the iPhone app for convenience...and hopefully this can help solve the problem for anyone else with this experience.

Sooo, I was able to fix my own problem, but it wasn’t particularly easy...I’ll post the solution here in case anyone else experiences the same issue in the future. After lots of troubleshooting, I was convinced my server config was ok. Though I had rebooted the router, I had not yet reset it to factory settings. That did the trick. Of course, then I had to completely re-do port forwarding. Also, I had a new LAN IP for the unRAID server, so I had to reconfigure many of my docker apps that used APIs to communicate with one another (Lidarr, Radarr, Sonarr, Deluge, Sab, Organizr, etc). All good now, but it would have been nice to have that Friday evening back!

Help me unRAID gurus; you're my only hope! I am running unRAID 6.8.3 as a relative novice (lots of SpaceInvaderOne videos). It's been working reliably until we had a thunderstorm last night that knocked out power. Fortunately, my computer/array seem fine...I am running a UPS that shut down the system gracefully. However, I now have an "Unable to Communicate with Github error, my dockers won't update, and particular services (like Plex) are only accessible from the LAN. I have reset my router (and noticed my IP address changed...I manually changed it to match on duckdns.org (even though the client is supposed to do that automatically). I have tried multiple solutions recommended on various threads (double-checking DHCP set to yes in network cfg file, changing DNS to 8.8.8.8 and 8.8.4.4, etc., but I am out of ideas. I very much appreciate any help those more unRAID savvy than I can provide. NOTE: I run a reverse proxy with custom: proxynet and point ports 443 and 80 to 446 and 81, respectively, for letsencrypt.