hansolo77

I think something is wrong with my Radarr. I typically have the docker running in the background so it can grab better quality of movies I have when they're released. I noticed today when I loaded up the webui that I couldn't connect. Instead of connecting, it gives me an error in the webui: Failed to load custom filters from API Version 4.7.5.7809 Also, my log is stuck in a repeating cycle: [Info] Bootstrap: Starting Radarr - /app/radarr/bin/Radarr - Version 4.7.5.7809 [Info] AppFolderInfo: Data directory is being overridden to [/config] [Debug] Bootstrap: Console selected [Info] AppFolderInfo: Data directory is being overridden to [/config] [Info] AppFolderInfo: Data directory is being overridden to [/config] [Info] MigrationController: *** Migrating data source=/config/radarr.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 *** [Info] MigrationController: *** Migrating data source=/config/logs.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 *** [Info] Microsoft.Hosting.Lifetime: Now listening on: http://[::]:7878 [Info] CommandExecutor: Starting 2 threads for tasks. [Info] Microsoft.Hosting.Lifetime: Application started. Press Ctrl+C to shut down. [Info] Microsoft.Hosting.Lifetime: Hosting environment: Production [Info] Microsoft.Hosting.Lifetime: Content root path: /app/radarr/bin Anybody else having this issue? What do I do?

I had the MyServers addon installed and working, but it's not working either. Now it just sits there unable to connect. I have OpenVPN on my router, I'm going to try and see if I export a config for that to my phone. It works great with my tablet.

Ok thanks!

Got a question... I just set up SWAG so I can access my newly installed Nextcloud docker. Working great so far. Earlier today I tried to access my Unraid server while at work on my phone. When I tried to access the url I typically used (subdomain.domain.org) it came up with the SWAG page rather than the Unraid page. I imagine this is typical behavior now for whenever I access my server's address. Trouble is, I don't know how to get around it. To get Nextcloud to work, I had to follow our old pal SpaceInvader's video. I don't know what to do now to access my server. I checked the `/proxy-confs/` folder but it doesn't have a template sample for this particular situation. So.. yeah.. what do I do?

Just wanted to post a quick update (hopefully not jinxing). Firstly, I "had the last straw" and finally decided to move out of my dad's place and get my own. It's been a month or so that I've been doing the move. I'm done now, and decided now's as good a time as any to try and do some spring cleaning and solve the issue once and for good. While I didn't do the ULTIMATE FIX, which would involve a complete rebuild of hardware, I did accomplish a FIX just the same. The solution now is to not use ANY SATA controllers. The motherboard just doesn't seem compatible with any of my new 20tb drives. No matter what I tried, from replacing cables to replacing drives (yes, I even RMA'd a drive hoping it would fix the problem), nothing worked. I even tried that expansion card for a while, but it had the same results after awhile. I just gave up. I pulled the two bottom right drives from my case (drives 23 and 24) and put the parity drives in there. I did it properly though. I used `krusader` and moved all the data off those drives before removing them. Once removed from the array, I crossed my fingers then removed the parity drives from the array. After a "no guts no glory" reboot, I then put the parity drives in and rebuilt the array parity. I didn't have a single issue. And since then I've done 2 forced parity checks and the July 1st auto check all came back perfect. So now I'm relying entirely on the array's HBA controller. So far so good. Here's hoping it stays that way.

Here's Hoping!

Sorry, I don't typically visit the forums unless I have an issue. Just noticed you tagged me. I can honestly say that even though I was finally able to get it to work, I don't remember how. The issues I was having made me rethink the situation. I remember giving up and trying the official version rather than this fork. While I used @SpaceInvaderOne's video as a guide, I pretty much installed everything from the official branches, like MariaDB and Nextcloud. I had to do a lot of googling, and figuring out I needed to manually change a bunch of things like lines in the scripts. When I finally had it up and running, I was able to install the app on my iphone and it connected when I was local. That was all I needed, and I got my backup of my iphone complete. After all that, I unisntalled everything with the intentions of re-installing it with some notes I made to to see if I could get a clean copy (because my brother wants it on his server too). Unfortunately, it was at that time I "had the last straw" at home and decided to finally move out my dad's place and onto my own. I've just finished moving in the last couple of weeks. So maybe, if I can find the time, I'll try and report in a new update with details on the things I changed. I will say though, that I did PM @SpaceInvaderOne asking him to create a new video, or update his existing one, to give us some help with the latest version and any necessary changes we need to do. I have yet to hear back from him (probably doesn't take personal requests and insta-blocked me ^_^). One thing I also should mention.. I didn't get any of that "remote proxy" stuff working. Following his instructions, I was only able to get as far as installing MariaDB and Nextcloud (both official), getting it set up, and backing up all the photos currently on my phone. I never got any further than that.

I have this problem too. Been trying to upgrade to a higher capacity drive. Need to stop array to remove the old drive and again to install the new drive. System gets stuck stopping the array. Only solution I know of is to then do a forced reboot, which causes a dirty bit and a parity check on reboot. I know everything is good so I cancel the check, but this is a crazy thing that's never happened before. Did something change when we all upgraded to 6.12?

Seems like I still have the problem, unfortunately. Future build plan is to not use Ryzen again. I'll just have to live with it. On the plus side, the resets/etc haven't caused Unraid to completely disable the drives like it did in the past. So maybe that's a good sign. I'm still concerned about it though. Oh well. Guess AMD and MSI didn't plan on having 20tb drives when they designed their components.

I appreciate your feedback. Unfortunately there's not anything I can do about the power. The setup of my server uses 2x server grade PSU's that combine into a PDU. That PDU only has so many cables on it. In fact (and you may feel like this is an ah-ha! moment) I had to use a splitter to get 2 SATA power connector's out of one. I've previously connected various drives (2x8tb, then 2x12tb, and now 2x20tb) to this primary cable. Also, although not mentioned, I have tried switching cables (first to a 4-pin MOLEX splitter with 4 in and 4 out, and then to a SATA splitter with 4 in and SATA out) but had no change in behavior. This has definitely been an eye-opening experience for me. I've been building computers since the 90's. I pretty much know everything on the hardware-side to try. I even at one point tried having the drives OUTSIDE the case, just in case the problem was something possibly "magnetic" because they're mounted on the side of the power supply (see the pictures in my build). At this point I don't think it's hardware. I take that back though. It looks more and more like the problem is with Ryzen and Linux. I made a post (mentioned in the OP of this thread) on the motherboard's manufacturing forum about the issue I'm having. The general consensus was to upgrade the BIOS. I did that, then started to rebuild parity again. It made no difference at all. I still ended up getting hard and soft resets (although the drives never disabled). My last ditch effort was to install a separate SATA controller. With it connected, I've not had ANY further reset issues. I started a parity check last night and noticed it having errors so I'm rebuilding a clean parity now using the new controller (the last parity was built on the motherboard controller with drives resetting, so hopefully this will solve everything).

Yeah I definitely have a tendency to leave the tab and/or browser open when I'm not using it. So with the new release I would still have to log out if I'm not using it? Probably easier to just remember to close the browser.

Quick update, got the new controller installed, parity check is running. Just for reference, the controller card is this: https://www.amazon.com/dp/B07M93P18S?psc=1&ref=ppx_yo2ov_dt_b_product_details Also.. started running the parity check last night around 7:30pm. Woke up this morning to check and the drives are all still good. Got home from work about an hour ago and just now checked. Drives are still good, showing no signs of resetting like it had been before. Unfortunately, they do have some Parity errors that occurred after midnight. The errors are from Unraid and not from the Drive logs, so that should indicate a good sign that the controller is working well; I would have seen resets by now. I'm running the check "uncorrecting". I suspect there would be issues from the drive resetting when they were first being built for parity. So I'm going to try and start over with them connected to the new controller (stop array, remove parity, start array, stop array, add parity, start array, parity rebuilds). Unless this isn't a good idea? I don't think correcting parity bits with a "dirty" drive is a bad idea.. would likely corrupt data more than protect it. Thoughts?

I have a Samsung Tablet (yes, android) that I use as a remote client. I do Remote Desktop via an app with it to connect to various VM's and my main PC. I also use the Chrome browser to directly access the server occasionally. Now that you mention it, I do recall reading something about that being a problem... using andoid browser to access unraid. Is there a way to fix that?

What is nchan? If it's not something critical, I'll wait until the official release is available.

I'm still trying to troubleshoot my parity drives becoming disabled. I bought a new controller card, installed it, and started another check last night. When I got up this morning to check on it's progress, none of the drives are showing any issues (yet). However, when I checked the system log, it has a LOT of errors about being out of memory. I'm not sure what could be causing it. I have 128GB of RAM, and it's rarely over 10% used. Is there something else going on I should look at? Current System Log: kyber-diagnostics-20230511-0534.zip

Funny you should mention that. The more I think about it, the more I think that’s when I’ve been having trouble. Here I thought building a system with a Ryzen processor that had 12 cores would be awesome. If I ever build another machine, I think I’ll stick with tried and true Intel. lol So far so good, no issues. Only 33% complete though. **** EDIT Seems I spoke to soon. About an hour after I posted this, I started getting errors again. Grr it's so frustrating.

Thanks for the reply! Yeah swapping drives in and out with the HBA has been something I tried. Whenever a drive is connected to the HBA, it works fine. I've not had any of my drives display this kind of behavior when connected to the HBA controller. It's only been with the motherboard controller. Up until a few months ago, I was having trouble with the drives having all kinds of parity check errors, but I finally figured out it was the motherboard connected parity drives and that it didn't like Seagate drives for whatever reason. After switching to WesternDigital, the problem went away. That's why I'm thinking the problem might be the motherboard and compatibility. I'm still using WD drives, but the 20tb range just has not been cooperating. I've had 6 drives with this issue, so I know it's practically impossible for it to still be a DRIVE problem. I'm about to try updating the BIOS, since there has been numerous updates. Although nothing mentioned in the update notes indicates a fix to this type of problem, it's worth the shot right? If this doesn't fix the problem, I'm very tempted to try and get a different controller card and just not use the motherboard connectors. **** EDIT After an hour of tinkering, I've got the latest BIOS installed. Rebuilding parity now.. We'll see. (fingers crossed)

After figuring out that my motherboard just doesn't like Seagate drives, I finally managed to have a solid/stable server for a couple of months. No more parity check errors, drives disabling, etc. I thought I had it solved. Then I decided to start upgrading my 12tb drives to 20tb drives (slowly). I started with 2 drives for my parity. I precleared them with no issues. I then swapped one in as parity 1 and let it rebuild. That went fine. Then, as luck would have it, while swapping the other into Parity 2, the parity 1 drive started having issues and then disabled. I didn't know because I was at work at the time. I came home, and had to start the whole process over again. Not really knowing what I'm doing, I just started over and precleared both drives again and this time swapped the 2 drives, so the 2nd drive was now parity 1. That seemed to work. I was then able to get parity 2 installed as well, and all was good for about 3 days. Then, Parity 2 disabled again. Maybe Parity 2 is bad? I posted the logs in discord and everybody helping agreed the problem isn't with the drive but with the SATA cables. So, I bought new ones. And actually, that didn't help (2 days pasted then they disabled again) so I bought ANOTHER set of cables. Thought I had it, then after a full week they disabled again. I've since bought 2 more 20tb drives and have swapped them into the parity. They ALSO have been having this disabling issue. So my latest attempt has been to first of all do an extended self-test on the parity 1 drive, which came back perfect. I then did an extended test on my parity 2 drive, which was perfect too. I have another 20tb now, and prior to doing it's preclear I did an extended test on it, and it was perfect as well. I then have started the preclears, this time doing the full gamut of tests, pre-read then clear then post-read. Everything has been going great on the 2nd new drive. But, just as expected, the one connected as Parity 2 has started having issues again. It's not been disabled yet, but I imagine it will soon. My current setup... The motherboard has 4 SATA ports on it. The "array" drives are connected to an HBA. The parity drives are connected to the first 2 motherboard ports, and an SSD is connected to a 3rd used for VM's. The 4th port is not used. I have tried swapping SATA ports as well (when trying to replace the cables) so they were using 3 & 4, and had the SSD disconnected. This just doesn't seem to be working. At this point, I'm out of ideas. I've tried different drives, different cables, different ports. I don't know what else to try. I'm starting to suspect the problem might be with the motherboard. I realize SATA drives are pretty much a standard. But is it possible my BIOS doesn't work well with this capacity? I checked the manufacturer's website and I do see they have newer BIOS's available, but nothing directly indicates they have improved compatibility with drives. I posted a thread in their forums but nobody has replied in a week. Am I just SOL? Should I maybe look at getting a controller card and not use the onboard? If so, any good recommendations? I really appreciate any help anybody can provide. I'm just totally lost now. Here's the recent errors my drive is showing. Diagnostics also attached. kyber-diagnostics-20230507-1110.zip

I think I've got a lot of of this working now, but I can't get a few of the files on my phone to transfer over. Photos and some 3-5 second videos transferred fine. But I can't transfer large files. The app says I'm not authorized and complains it's too big. How do I fix that? For reference, I've already tried reading through https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html with not much luck. I can't find any of the files I'm supposed to edit to add the lines to. Can somebody be super nice and help me out? Also, all that I've done so far is install the "OFFICIAL" mariaDB, and this thread's "OFFICIAL" nextcloud. I created an admin account, and then also created a user (added to admin role) that I use for my phone. I can upload files, and access them on another computer, just not anything large. Thanks guys!

Hey guys! I need some help big time. I was trying to get NextCloud to work with SpaceInvaderOne's video, using the linuxserver version of NextCloud and MariaDB. Seems like the dockers and/or install scripts are out dated and I just couldn't get it to install properly. I tried so many times but just kept running into problems. So I decided to use the "Official" versions of MariaDB and NextCloud, so here I am! I really don't know what I'm doing. The process seems very much over my head. But I think I at least have it installed. I was able to create an admin account, but then couldn't log in. Every time I put in the credentials and hit the button, the screen would just refresh with the login prompt again. However, if I connected to the webui using my tablet (by first logging into unraid, then going to the docker, then webui) I could log straight in. I then read somebody suggesting a fix to that is to clear the cache/cookies in the browser. Sounds kinda pointless, but I tried it and so far I was able to login with my regular machine. Inside the admin settings, I seem to be getting a lot of security errors, so maybe that's why I'm having trouble? They say things like: ``` Accessing site insecurely via HTTP. You are strongly advised to set up your server to require HTTPS instead, as described in the security tips ↗. You have not set or verified your email server configuration, yet. Please head over to the Basic settings in order to set them. Afterwards, use the "Send email" button below the form to verify your settings. Your installation has no default phone region set. This is required to validate phone numbers in the profile settings without a country code. To allow numbers without a country code, please add "default_phone_region" with the respective ISO 3166-1 code ↗ of the region to your config file. ``` I have no idea how to fix the first point, unless that's referring to the OP, about using a reverse proxy. I will do that eventually, but for right now I'm only interested in using this locally when I'm on the same network - no remote access yet. So I can just ignore that warning right? As for the 2nd point, that just means I've not setup the email service yet right? And I can just use my current email provider (yahoo) like I do for unraid correct? As for the 3rd issue.. I have no idea how to fix that. I don't believe there is a setting for that in the admin settings. Once I get these things fixed, I'm pretty much good to go right? Again, I'm really not sure what I'm doing. I'm still very newbish to all this (unraid, dockers, etc). My goal here was to eliminate the need for my iPhone to keep photos stored on the iCloud, as my storage is all used up. My brother uses Amazon Photos but his storage is now full too, and he needs a free alternative, so I thought this might be the solution for both of us. The way I understand it, we just need an ability to connect to our server for the syncing, and then we can go into our share and move the data around (like put uploaded photos into a photos share on unraid, etc). Am I mistaken about this functionality? Any help would be greatly appreciated! Thanks guys!

Old thread, still a good build though. Thought I'd post an update, now that 20tb drives are available. I'm actually having some difficulty now with my 2nd parity drive frequently having to hard or soft reset. When I upgraded it, I actually ran into a problem where Parity 1 became disabled. After I re-enabled it and pre-cleared Parity 2 again and tried to rebuilt it, I was able to get it finished. Then when I upgraded my Disk 1 to 20tb (now with parity 1 and 2 being 20tb) abou 1/3 of the way through rebuilding, Parity 2 became disabled. I stopped rebuilding Disk 1 so I could focus on re-enabling Parity 2 and fixing it's problem. Well, that, in turn, caused Parity 1 to get disabled again. Once I got both parity drives up and running and stable for a week, I started rebuilding Disk 1 again. However, once it completed, Unraid said it was unable to mount the drive because of an invalid file system. I took the drive out, put it in another computer, and repartitioned it. I then put it back into Unraid, ran a sucessful preclear, then started rebuilding it again. But, it was still reporting the file system was invalid. After a long week of troubleshooting, I finally learned with the help of a user on Discord that my Parity had become corrupted. Probably due to each drive becoming disabled in turn. So as I am now, I had to build a new configuration without Parity, restored all the data that was on my old Disk 1 prior to upgrade, and I'm now rebuilding the Parity. Everything has been going good "so far". Then I decided to check my system logs to see if the Parity drives are acting like they should. And so, of course, Parity 2 is showing signs in the logs that it is once again getting hard and soft resets. I think there are 4 factors at play here that I'm coping with: The Parity 2 drive could just be physically bad. The SMART data is not indicating any failures, like unwritable sectors or reallocations, etc. The drive as had a perfect preclear. So I don't really think this is the problem. The drivers on the motherboard and/or version of the software on the Parity 2 drive may need updating. There could be some underlying issue with the communication, etc. I wouldn't consider this a possibility were it not for the fact that this very problem is why I replaced my Parity drives that were originally Seagate NAS drives with Western Digital Red drives. Apparently the Seagates were having issues with my motherboard/cpu/whatever. Every time I would run the monthly parity check, it would come up with errors, even though the data on my array was fine, the parity would always find errors. Swapped to WD, and hadn't had an issue since. So it makes me wonder, even though these new drives are WD too, maybe the software/hardware isn't compatible? Replacing the drives with newer ones maybe be causing extra wear on my SATA connectors. For the longest time, using the Seagate drives, I had no problems until I started running the full case with 24 drives. Once I started having parity errors, I swapped them to WD drives (see #2). I was lucky, in that the physical connectors were good with the swap. But, the way these drives are mounted in the case (vertically against the power supply (see pictures above)) the plugs don't sit exactly straight. They're kinda angled like 20-degrees or so because there isn't enough clearance with the power supply. So I think the frequent pulling and plugging of the cables may have damaged the plugs slightly, at least with Parity 2, in that it doesn't provide a good connection anymore. So, I purchased some new cables. https://www.amazon.com/dp/B00KTLGDZG?psc=1&ref=ppx_yo2ov_dt_b_product_details At first, I thought this would solve all my problems. They give me all the clearance I need. But, as I mentioned earlier, I'm still having issues with the drives getting disabled and/or hard/soft resetting. I recently replaced the fans in my custom fanwall. Originally, my design was to help with the noise factor. The original fans that came with the case were extremely loud. Not ideal for having in your closet in your bedroom. So I was using some 120mm Noctua fans. It was great, the noise wasn't nearly as bad anymore. I've decided it's time to move out on my own, after 43 years (I know, I have mental issues and a fear of breaking from routine). A lot of it came from my Dad's increasing memory loss, and my inability to hold a conversation with him longer than 30 seconds without him forgetting what I just said. I can't take it anymore, so I'm moving out. I found an apartment, waiting for the keys. I decided I could upgrade my fans in the server since I'll have the server in a bedroom on it's own and noise won't be a factor. The new fans I got are still Noctua's, but they're industrial. They're designed to run faster, and work harder when air flow is hard (like sitting behind a wall of hard drives). I don't really know much about it, but I assumed since they're still regular fan connectors, they wouldn't be any different "powerwise". But now that I've replaced them, I've been having these drive problems. So maybe they are drawing more power? I don't even know if that's possible, but that's another theory. These are the new fans: https://www.amazon.com/dp/B00KFCRATC?psc=1&ref=ppx_yo2ov_dt_b_product_details I really think the problem is with the connectors, and MAYBE the fans. With the help of the Discord friend, I've got my data on the array sitting ok, no losses. I'm trying to rebuilt a new parity. I'm getting errors on Parity 2 (hard/soft resets, not ERRORS like bad sectors, etc). My goal is to wait it out and hope I get a good parity built. Once that's done, I'm going to try a new set of connectors for my parity drives. I just bought 2 of these, with the hopes that they'll provide a solid connector with enough clearance for me to close the lid, and I won't have any more connectors sitting on harsh angles. https://www.amazon.com/gp/product/B07JPZMQCL/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 They won't arrive for 3-4 days, so hopefully I can get the parity built by then. At that time, I will use these new connectors and run a parity check to see if the results come back ok, and watch the log to see if I get any more reset errors. IF I DO, my next plan is to replace the fan wall with the old one and re-run the parity check again. If I still get reset errors (especially if it continues to be Parity 2) I'll see about returning the drive. Hopefully that will solve the problem. Any take aways or feedback? I'd really like some help if anybody has any to give. I appreciate you all and look forward to keeping everybody updated.

Added diagnostics. Thanks for any help! kyber-diagnostics-20230330-1903.zip

Hey guys.. I know you want a full diagnostics, and I'll provide if it necessary (I'm posting this on my tablet and I don't know how to "download" and/or "upload" the zip from it, so I'll get it later). Anyway, I recently decided I wanted to go up to 20tb drives on my server. I've had it running swell on 12tb drives but I'd just like to have that extra cushion. So I bought 2 WD drives for my parity, and got them installed/upgraded just fine. I then decided before starting the expensive task of upgrading the next 24 drives, I wanted to upgrade my "fan wall" I built in my case. Rather than use the existing fan wall, with ridiculously loud fans, I replaced the 4x80's with 3x120's from Noctua. They're quite and all, but the drive temps (now that I have it fully loaded) are sitting a little hot. So I wanted get some fans that would move a little more air. I went with 3x120's from Noctua again, but they're those black, industrial fans. Wow what a difference, temps dropped 20c! Now I'm on to replacing the data drives. I've gone through and precleared the first drive. After it was done I swapped it into the array. Then after restarting the array it started rebuilding. Pretty normal. However, after about 20 minutes I noticed the speed was still really slow, like 70kps, just barely above dialup speed. I posted in Discord about it then realized one of my parity drives disabled itself. I don't know what the problem was, the log indicated it just lost connection. So I turned off the server, removed the cover and disconnected/reconnected all the cables and restarted. Of course, now the parity needs to rebuild. So I put the array drive on hold and begun rebuilding the parity. Once it was done I started the new array drive again. Then.. wouldn't you know, the same thing happened only this time with the 2nd parity drive. This is driving me nuts. I've got a sneaky suspicion that the problem is with the SATA cables. See, the way these drives are mounted, they sit vertically with their "butts" in the air, mounted on the side of the power supply. The problem with mounting this way is the plugs stick out higher than the top of the case and you can't close it up. So I bought some right angle connectors hoping I could lower the plugs. It worked, and was working fine for a long time with the 12tb drives. But for some reason, now with the 20tb's, they just don't sit right. They never sat flush anyway, because the power supply was just slightly taller than the right angles, so the plugs still sat kinda at an angle. So, because I thoght that might be the problem (not providing a good SATA connection) I ordered some NEW replacement SATA cables. These guys are nice. Rather than have the wires come out the end of the plug, they come out the side. Finally I have a cable where the connector is low enough for clearance! So after a long, nearly a week long, lengthly process, I've got both parity drives rebuilt with good cables. Time to start rebuilding the new drive in the array...again. First I had to preclear it, again, because Unraid was yelling at me about the filesystem being unmountable. So I precleared it, started the rebuild, and saw it chugging along at like 150-160mbs, where it SHOULD be. I went to bed. Woke up this morning, checked the status before going to work. NOT GOOD! It's only like 3% complete, speed is down around 30mbs. The logs are not promising. They indicate Parity 2 is still on the verge of being disabled, but somehow it recovers. Lots of "soft resets" failing then succeeding, etc. I don't know what thep problem is. Then it dawned on me while at work (thus my inclusion of it in the post).. Could it be the drives are just not getting enough power? Everything was working fine (except for the rebuilding of the parities from them getting disabled) until I replaced the fans with those faster ones. They're still using the power points on the motherboard, and the settings to be "full on" hasn't changed. But could they still be drawing more power and now the drives are starving for juice? If it's not that, what else could it be? As I said, I'll provide full diagnostics zip soon if somebody needs it to help figure out the problem. In the mean while.. here is just the entire "system log" cut/pasted... Mar 30 07:18:18 Kyber kernel: ata2: softreset failed (device not ready) Mar 30 07:18:18 Kyber kernel: ata2: hard resetting link Mar 30 07:18:22 Kyber kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 30 07:18:22 Kyber kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 30 07:18:22 Kyber kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 30 07:18:22 Kyber kernel: ata2.00: configured for UDMA/133 Mar 30 07:18:22 Kyber kernel: ata2: EH complete Mar 30 07:30:10 Kyber kernel: ata2.00: exception Emask 0x10 SAct 0x100 SErr 0x90302 action 0xe frozen Mar 30 07:30:10 Kyber kernel: ata2.00: irq_stat 0x00400000, PHY RDY changed Mar 30 07:30:10 Kyber kernel: ata2: SError: { RecovComm UnrecovData Persist PHYRdyChg 10B8B } Mar 30 07:30:10 Kyber kernel: ata2.00: failed command: READ FPDMA QUEUED Mar 30 07:30:10 Kyber kernel: ata2.00: cmd 60/b8:40:88:49:f5/02:00:1a:03:00/40 tag 8 ncq dma 356352 in Mar 30 07:30:10 Kyber kernel: res 40/00:00:88:49:f5/00:00:1a:03:00/40 Emask 0x10 (ATA bus error) Mar 30 07:30:10 Kyber kernel: ata2.00: status: { DRDY } Mar 30 07:30:10 Kyber kernel: ata2: hard resetting link Mar 30 07:30:12 Kyber kernel: ata2: found unknown device (class 0) Mar 30 07:30:12 Kyber kernel: ata2: SATA link down (SStatus 0 SControl 300) Mar 30 07:30:12 Kyber kernel: ata2: hard resetting link Mar 30 07:30:17 Kyber kernel: ata2: found unknown device (class 0) Mar 30 07:30:22 Kyber kernel: ata2: softreset failed (device not ready) Mar 30 07:30:22 Kyber kernel: ata2: hard resetting link Mar 30 07:30:26 Kyber kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 30 07:30:26 Kyber kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 30 07:30:26 Kyber kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 30 07:30:26 Kyber kernel: ata2.00: configured for UDMA/133 Mar 30 07:30:26 Kyber kernel: ata2: EH complete Mar 30 07:50:54 Kyber kernel: ata2.00: exception Emask 0x10 SAct 0xc00000 SErr 0x90202 action 0xe frozen Mar 30 07:50:54 Kyber kernel: ata2.00: irq_stat 0x00400000, PHY RDY changed Mar 30 07:50:54 Kyber kernel: ata2: SError: { RecovComm Persist PHYRdyChg 10B8B } Mar 30 07:50:54 Kyber kernel: ata2.00: failed command: READ FPDMA QUEUED Mar 30 07:50:54 Kyber kernel: ata2.00: cmd 60/00:b0:68:cb:3d/04:00:2e:03:00/40 tag 22 ncq dma 524288 in Mar 30 07:50:54 Kyber kernel: res 40/00:00:68:cb:3d/00:00:2e:03:00/40 Emask 0x10 (ATA bus error) Mar 30 07:50:54 Kyber kernel: ata2.00: status: { DRDY } Mar 30 07:50:54 Kyber kernel: ata2.00: failed command: READ FPDMA QUEUED Mar 30 07:50:54 Kyber kernel: ata2.00: cmd 60/28:b8:68:cf:3d/01:00:2e:03:00/40 tag 23 ncq dma 151552 in Mar 30 07:50:54 Kyber kernel: res 40/00:00:68:cb:3d/00:00:2e:03:00/40 Emask 0x10 (ATA bus error) Mar 30 07:50:54 Kyber kernel: ata2.00: status: { DRDY } Mar 30 07:50:54 Kyber kernel: ata2: hard resetting link Mar 30 07:50:56 Kyber kernel: ata2: found unknown device (class 0) Mar 30 07:50:56 Kyber kernel: ata2: SATA link down (SStatus 0 SControl 300) Mar 30 07:50:56 Kyber kernel: ata2: hard resetting link Mar 30 07:51:01 Kyber kernel: ata2: found unknown device (class 0) Mar 30 07:51:06 Kyber kernel: ata2: softreset failed (device not ready) Mar 30 07:51:06 Kyber kernel: ata2: hard resetting link Mar 30 07:51:10 Kyber kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 30 07:51:10 Kyber kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 30 07:51:10 Kyber kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 30 07:51:10 Kyber kernel: ata2.00: configured for UDMA/133 Mar 30 07:51:10 Kyber kernel: ata2: EH complete Mar 30 08:20:00 Kyber kernel: ata2.00: exception Emask 0x10 SAct 0x400 SErr 0x90302 action 0xe frozen Mar 30 08:20:00 Kyber kernel: ata2.00: irq_stat 0x00400000, PHY RDY changed Mar 30 08:20:00 Kyber kernel: ata2: SError: { RecovComm UnrecovData Persist PHYRdyChg 10B8B } Mar 30 08:20:00 Kyber kernel: ata2.00: failed command: READ FPDMA QUEUED Mar 30 08:20:00 Kyber kernel: ata2.00: cmd 60/a0:50:28:bb:4a/01:00:49:03:00/40 tag 10 ncq dma 212992 in Mar 30 08:20:00 Kyber kernel: res 40/00:00:28:bb:4a/00:00:49:03:00/40 Emask 0x10 (ATA bus error) Mar 30 08:20:00 Kyber kernel: ata2.00: status: { DRDY } Mar 30 08:20:00 Kyber kernel: ata2: hard resetting link Mar 30 08:20:02 Kyber kernel: ata2: found unknown device (class 0) Mar 30 08:20:02 Kyber kernel: ata2: SATA link down (SStatus 0 SControl 300) Mar 30 08:20:02 Kyber kernel: ata2: hard resetting link Mar 30 08:20:08 Kyber kernel: ata2: found unknown device (class 0) Mar 30 08:20:09 Kyber webGUI: Successful login user root from 10.27.27.1 Mar 30 08:20:12 Kyber kernel: ata2: softreset failed (device not ready) Mar 30 08:20:12 Kyber kernel: ata2: hard resetting link Mar 30 08:20:17 Kyber kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 30 08:20:17 Kyber kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 30 08:20:17 Kyber kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 30 08:20:17 Kyber kernel: ata2.00: configured for UDMA/133 Mar 30 08:20:17 Kyber kernel: ata2: EH complete Mar 30 08:22:51 Kyber kernel: ata2: found unknown device (class 0) Mar 30 08:22:51 Kyber kernel: ata2: SATA link down (SStatus 0 SControl 300) Mar 30 08:22:56 Kyber kernel: ata2: found unknown device (class 0) Mar 30 08:23:01 Kyber kernel: ata2: softreset failed (device not ready) Mar 30 08:23:05 Kyber kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 30 08:23:05 Kyber kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 30 08:23:05 Kyber kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 30 08:23:05 Kyber kernel: ata2.00: configured for UDMA/133 Mar 30 09:14:43 Kyber nginx: 2023/03/30 09:14:43 [crit] 9855#9855: *229325 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 212.102.40.218, server: 0.0.0.0:443 Mar 30 10:39:18 Kyber nginx: 2023/03/30 10:39:18 [crit] 9855#9855: *244850 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 139.59.177.49, server: 0.0.0.0:443 Mar 30 11:01:04 Kyber nginx: 2023/03/30 11:01:04 [crit] 9855#9855: *248883 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 46.101.164.72, server: 0.0.0.0:443 Mar 30 11:04:00 Kyber nginx: 2023/03/30 11:04:00 [crit] 9855#9855: *249431 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 46.101.164.72, server: 0.0.0.0:443 Mar 30 11:08:20 Kyber nginx: 2023/03/30 11:08:20 [crit] 9855#9855: *250237 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 46.101.164.72, server: 0.0.0.0:443 Mar 30 12:02:38 Kyber root: /var/lib/docker: 10.7 GiB (11497426944 bytes) trimmed on /dev/loop2 Mar 30 12:02:38 Kyber root: /mnt/disks/PLEX DATA: 381.6 GiB (409735974912 bytes) trimmed on /dev/nvme1n1p1 Mar 30 12:02:38 Kyber root: /mnt/cache: 1.7 TiB (1899060109312 bytes) trimmed on /dev/nvme0n1p1 Mar 30 15:36:29 Kyber nginx: 2023/03/30 15:36:29 [crit] 9855#9855: *300187 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 87.236.176.63, server: 0.0.0.0:443 Mar 30 15:45:46 Kyber nginx: 2023/03/30 15:45:46 [crit] 9855#9855: *301979 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 46.101.130.16, server: 0.0.0.0:443 Mar 30 17:17:02 Kyber nginx: 2023/03/30 17:17:02 [crit] 9855#9855: *318900 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 162.243.150.11, server: 0.0.0.0:443 Mar 30 17:45:52 Kyber webGUI: Successful login user root from 10.27.27.1 Mar 30 17:48:16 Kyber webGUI: Successful login user root from 10.27.27.1 Thanks again guys! And if you're curious, here's the new SATA cables I'm using: https://www.amazon.com/dp/B00KTLGDZG?psc=1&ref=ppx_yo2ov_dt_b_product_details And here's the new fans: https://www.amazon.com/dp/B00KFCRATC?psc=1&ref=ppx_yo2ov_dt_b_product_details

Ok, now that I'm more awake, I figured out the problem. Zap2It was not providing proper artwork. When I went back to the website and clicked on various shows that were missing artwork in Plex, they were also missing in the Zap2It website. So now I have to rethink the source. Is there a popular recommendation? For my needs, obviously I'm using Unraid and Plex. xTeve is running in a docker. I would prefer a "set up once and forget about it" automated system.

Sorry, it must be because it's 12:30am here.. I'm totally lost lol. This whole thing is new to me.