ttttubby

Parity check passed. Everything looks ok. Sooo relieved.

Update Time: I took a chance that the motherboard had a dying capacitor or something causing it to fail due to the extra voltage and I ordered a replacement motherboard from eBay and crossed my fingers that nothing else (including the CPU) was damaged. The new board was an Asus h77. It had 6 sata ports rather than 8 but fortunately I had a second pcie sata controller. Once I confirmed that the new board was working I plugged in my hard drives and my unRAID USB and viola... My server is back up as if nothing happened! Parity check is running now but so far so good. Fingers crossed that this thing will limp along until the chip shortage ends and I build a new gaming rig and donate my old one for building a replacement unRAID server.

So a couple of nights ago lightning struck just outside of my house. I didn't realize until the next morning but there were several casualties. I lost my cable modem (which Spectrum replaced for free) two monoprice 8 port switches, a 4x hdmi switch and my relatively old but previously bulletproof unraid server which would no longer turn on. I ordered a replacement power supply to see if I could get it going again but alas, no dice. I had upgraded the CPU a little while back (from a Pentium G630t to a Core i5 3475S) so I tried popping the old CPU back in but again, no power at all. My motherboard was an ASROCK H77 Pro4/MVP and I had 8-9 drives of various capacities (4tb parity, 2x4tb, 3x2tb, and 2x1tb) with a 500gb cache drive. I used it primarily for Plex and sabnzb and it served my purposes just fine. At this stage I'm inclined to start from scratch maybe re-using at least the 4tb drives though after the lightning strike I don't know how trustworthy they'd be (if they still work at all). I hadn't planned on starting over and don't have much of a budget, but at this stage I don't think I can afford to get all of the modern bells and whistles. My gaming rig, which is long overdue for an upgrade itself is an i74490k but it too was exposed to the lightning (though it seems to be operating normally at the moment). I'd love some recommendations for moving forward. Any and all advice would be appreciated.

So I was able to get Sonarr to work properly by following the instructions on Q26 of the recommended post and adding my local server to the ignored addresses field in Sonarr. So far so good. Unfortunately I've been procrastinating in my move from couchpotato to Radarr. In the settings for couchpotato, there doesn't seem to be an "ignored addresses" field. Am I overlooking something in the couchpotato UI? Or is there some other way to make couchpotato work properly. Thanks

Thank you. Figured it out right before you posted. I guess I should bookmark this to see when it gets fixed.

How did you revert?!

Still not working for me. Are you using RSA4096? Or are you using RSA2048?

Is there any way that I can just go back to the previous (working) docker?

So I'm in the same spot. I had a working SABVPN docker before I updated, and now it is broken. I have tried everything suggested here and on github. (Switching to RSA4096, adding cipher AES-128-GCM to my ovpn file, adding cipher AES-256-GCM to my ovpn file) and nothing seems to be working. I keep getting a looping warning in the logs saying:

Secondary question, What kind of performance differences would I see if I bumped my Pentium dual core (basically a celeron replacement) to a 3rd gen Core i5 quad core? Thinking about buying one used on ebay and I'm wondering if its worth it for improved docker performance (for things like Plex in particular).

Ok, It looks like I found the bad stick. How much of a performance impact would I get if I dropped down to 4gb from 8gb on my server? Does it matter that I'm dropping from dual channel to single? It just so happens that I have another couple of sticks of 4gb ddr3. Should I replace the one still in there? Add them for a total of 12GB?

Does this mean I failed the memory test?

Ok, I'll try that. I get that 24 hours would be ideal, but you think a few hours would be long enough? Also, what settings should I use for memtest?

When I tried to recreate my docker image I tinkered with the settings a bit, moving the image into a /cache/system/docker/ folder and bumping the image size from 30gb to 50gb. Just now I deleted that image again, set it back to 30gb and placed it back in /cache/ and I was able to pull my dockers for sabnzb, couchpotato, sickbeard, dropbox, and krusader again without any errors. So that stuff is working again thankfully. I'm not going to bother with Plex for now though, and I'd still very much like to get to the bottom of this.

So you think it could be my memory? It would just... go bad?

So I deleted my docker image and started to repull my docker apps (using my user templates). Couchpotato pulled fine. So far so good. SabNZB on the other hand was a disaster. I started getting the following error: Error: failed to register layer: ApplyLayer exit status 1 stdout: stderr: unexpected EOF I looked this up and the consensus was to try again. This time it seemed to get a little bit further, but then it spat out Error: failed to register layer: ApplyLayer exit status 1 stdout: stderr: archive/tar: invalid tar header It was then that I looked at my system log and I was getting a ton of CPU errors like the following: Tower kernel: CPU: 1 PID: 13982 Comm: udevadm Tainted: G B 4.18.15-unRAID #1 Followed by a stream of: Tower kernel: swap_info_get: Bad swap file entry 3ffffbdffffff and Tower kernel: swap_info_get: Bad swap file entry 3fffffdffffff I've attached my diagnostics file and syslog file from today, which includes these new errors. Right now my data on the array seems safe, but I'm worried that my cache drive might be done (despite the fact that my main page says no errors). I'm also worried that something might be bad with my CPU and/or motherboard. Maybe its my SATA cables? Please help. tower-diagnostics-20181026-1048.zip tower-syslog-20181026-1049.zip

Ok, let me start at the beginning. 7-8 years ago I built an unraid server using an ASRock - H77 Pro4/MVP motherboard and an Intel Pentium G630T CPU with 8GB of ram. I currently have 8 drives in my array (9 with the Parity drive) and a 500GB cache drive that is at least 9 years old (maybe 10). I've never had a drive failure, though I did remove a 1TB drive about 6 months back because I was running out of SATA connectors between the ones on the motherboard and the two extras that I have from a SYBA Sil3132 PCI-E to SATA II controller card that I installed. Around mid-September, Unraid became unresponsive and I narrowed it down to the SYBA expansion card which had always been a bit wonky, requiring me to physically reseat the SATA connectors any time the server was powered down in order for its drives to be recognized. I replaced the expansion card with another of the same model and everything seemed to be working again + the SATA connectors no longer needed to be reseated. At this time I was running Unraid 6.5.1. Fast forward to a couple of weeks ago (early October) and I started noticing that my plex docker wasn't working properly. One of my libraries seems to have become corrupt, and I couldn't delete it or refresh it from within the plex webgui. Not a big deal, because I didn't use plex that often, so I put it in the back of my mind and didn't let it bother me. Then, about a week later I noticed that the mover didn't seem to be moving my downloads from the cache drive to the array on schedule. It was supposed to do so nightly, but I started to notice downloads hanging out on the cache drive a week after they downloaded. As one of the uses for my server is to archive photos for my wife's photography business this worried me since stuff that stayed on the cache was unprotected. I could invoke the mover manually, and everything seemed to work, but this was a more immediate problem than the one facing plex. Yesterday (10/25) I decided to see if I could figure out the problems. I started by rebooting the server (which may or may not have fixed the mover issue) and then proceeded to update to Unraid 6.6.3. It was at this time that I started checking the logs and started noticing some pretty significant errors (which I can't really make heads or tails of). I wanted to reboot again last night, but I downloaded the diagnostics file and the syslog before doing so. See attachments to this post. After I rebooted, I noticed brtf errors which, through google, I was lead to believe that the problem was with my docker image. So I though maybe, if I deleted my docker image and repulled my docker apps, I might be able to fix my problem. Not so. I think I may have made my problem worse. I'll respond to this post to explain why and to upload today's diagnostics/syslog. tower-diagnostics-20181025-2343.zip tower-syslog-20181025-2358.zip

Just discovered one new problem. For some reason sickbeard isn't notifying plex to update its library anymore and I can't figure out what settings (in sickbeard or plex) will fix it. Updates stopped when I upgraded the other day. Any ideas?

Huzzah! That did the trick! Thanks again!

Looks like my issues with Sab, CP and SB have all been worked out, but nothing I do seems to help with Plex. I'll delete my perms.txt and then walk away for half an hour and when I try to check the web ui, I get the same "server unreachable" error.

Ok seems to be working again.

Ok deleted the couch potato perm file seems to have fixed this. Still waiting to see if post processing works correctly but for now things seem to be back to normal.

Hate to be a bother but I'm getting the same issue with sickbeard. Since updating last night I can't even open the web ui. Have tried deleting the perm files for both sickbeard and sab

Deleting the perm file made it so that I could download files through my watch folder it now I'm not communicating at all with couch potato. Could be a couch potato issue?

Here is a link to the requested pics I will try to delete the perms file again but as I noted earlier this was the first thing I tried.