RobFlix

robflix-diagnostics-20260520-0752.ziprobflix-diagnostics-20260528-0727.zipFortunately I had it enabled. Here are a couple......

robflix-diagnostics-20260528-0727.zip I've poked through the diagnostics but can't see anything obvious but I'm not a Linux guru. I can't seem to go a week without an unplanned shutdown. Thanks for any insights you may have.

Fingers crossed this may just be a minor issue. I ran a memtest and after about 30 minutes one of the two sticks failed testing. I shut it down, popped out stick 0 and ran a memtest on stick 1. It passed. I have 64GB of RAM so I just left stick 1 in and ran a correcting parity check. I think it found 15 errors. I then immediately ran a non correcting parity check and it returned zero errors. Yay! After this I popped out stick 1, installed stick 0, and ran a memtest. It passed. I'm speculating stick 0 may have just needed a re-seat. I'm currently running with 64GB again and will report back if there are any additional hiccups. Thanks for pointing me in the right direction Jorge!!

Thanks Jorge, I will and will report back.

Hi, So I had some parity errors and found some instructions here. I ran a parity check with error correction, had errors, then, without rebooting ran a parity check without error correction but still had errors. The next instruction was to post a diagnostic here and ask for help so that's what I'm doing. Thanks in advance, -RobFlix robflix-diagnostics-20251115-1242.zip

Just wanted to follow up in case anyone else has had similar struggles. I was able to get a refund for my 14900K and replaced it with a 12900K. I installed the new CPU Saturday and have not had a single blip. It appears completely stable and the 12900K is still more than overkill for my usage with room for growth. Thanks for the input JorgeB!

So it looks like I may be getting a refund for my 14900K since I've already replaced it once. My motherboard supports 14th, 13th & 12th Gen Intel® Core™ Processors (LGA1700) CPU's. The 14900K is/was admittedly overkill but I wanted to future proof as much as possible. So, if I get a refund, what CPU should I get to replace this one? I definitely want quicksync and room for future expansion but my primary goal is stability. TIA! -Rob

Ugh, I've already replaced the MoBo and CPU under warranty. 😥 Appreciate the insight. I'll reach back out to Intel.

I can't seem to get more than 5 or 6 days of uptime. Periodically I'll see a core get pinned to 100%. I'm unable to stop the Dockers via web GUI or cli and this seems to keep the array from being able to shut down. I've now removed every container except Plex. This is less than ideal. In addition the current parity check is running so slow it will take +800 days to complete. Really appreciate any assistance you can offer. I've poked around the diag and syslog but I'm a little out of my element. TIA, -Rob robflix-diagnostics-20250130-1615.zip RobFlix Syslog.txt

Not really sure what happened but Plex did not like running on the the bridge network. The web GUI would not load. Still not sure how to troubleshoot the root issue though.

It looks like everything but Plex is set to bridge mode. I assume I need to fix that for Plex?

Really happy to have this system back up and relatively stable after struggling with hardware issues the last few months. The last two days I've ended up with containers that were unresponsive. I have a pretty typical *Arr suite setup. Yesterday I was able to SSH in and stop/kill all but two containers but couldn't get the last two to shut down and had to hard down. Today a sort of similar situation occurred but the Unraid web GUI became unresponsive. I attempted to restart Nginx but (I'm a little out of my comfort zone here) it seemed like there were running containers I couldn't kill keeping that from happening. I really wanted to get the web GUI back online because I was still running a parity check from the day before. I ended up having to hard down again, deleted the docker image, and reinstalled. All of this has been a great learning experience but one common theme that kept coming up was that I probably need to figure out what's causing the containers to become unresponsive in the first place to ultimately resolve this issue. Right now I only have Plex running but am kind of lost as to how to figure out what the root cause of this issue might be. Some seem to suggest I should pin cores to certain containers? Not sure how to distribute them if that's the case. Would really appreciate any insight someone might offer. Syslog & diag attached. robflix-diagnostics-20241228-1821.zip RobFlix_Syslog.txt

Thanks so much! Great suggestion! I appear to have all of my content. Now to look into my docker configs.

OK, I have a replacement CPU. I was not able to get it to boot with any of my backups though. Right now I have a fresh install of 6.12.14. How can I restore my array config so I don't lose all of my content?

RMA process with Intel has started. Cross your fingers.

For 6 months everything was running smoothly. For 6 months after that I've been fighting constant crashes. For 6 months I've been told I have a hardware problem. I've tested the RAM for 24 hours which produced no errors, replaced my network cables, switch, and router. I recently replaced the USB drive. I RMA'd the motherboard and am working on an RMA for the Intel Core i9-14900K CPU. Currently, the only way I can get the server to run is restore an old backup long enough to enable syslogs to the USB and download a diag. Maybe it's 5 minutes before the GUI crashes. If I'm lucky, when the GUI is crashed I can SSH into it, reboot, and get the GUI for another 5 minutes. I want this to work so bad. Thanks in advance for anything you can offer. robflix-diagnostics-20241201-1959.zip syslog

This is going from bad to worse and I just want to enjoy this OS so badly. I've been suffering from random crashes for months but now it's getting worse. Hopefully, with help, I can figure out WTH is going on. My current state is that it crashes, I power cycle, and it comes back online. I log in, navigate to any page, and it goes offline again. I truly don't think there's a hardware issue. I've run 24 hours of memory tests with no issue revealed. What's my next step? I'd post a syslogs and diags but I don't think it will run long enough to collect those.

Well, the mystery deepens. I started a container a day and waited for a crash. I'm now up to almost 8 days of uptime with all containers running. When its crashed in the past I usually do a manual reboot, start the array, then fire up all the containers, usually all or most at once. Could this be causing some sort of hiccup that results in the crashes I've been experiencing?

I'm starting to think this is actually a software issue. I've had 48 hours of straight up time which is a bit of a record. After the last crash I started only the Plex docker. It appears Some other container is causing the crash. I'm running the Arr suite, SAB, Flaresolver, and Cloudflare tunnel. I'm thinking I start one additional docker per day to see what causes the crash. Any thoughts on this process or what order to start them?

Ok, this is intriguing. Are you thinking it might be worthwhile to buy a new USB drive and transfer my license?

Was afraid you'd say that. Not really sure how to troubleshoot those. In addition I've noticed all shutdowns are now unclean even if I stop the array and initiate a reboot.

Was afraid you'd say that. Not really sure how to troubleshoot those.

Ok, over the past few days I've removed one stick of RAM, let it run until it crashes (still appears random, most uptime so far has been 22 hours) swapped the other stick in until it crashes, and done the same procedure with the second slot. It's still crashing. I don't have a cooling issue. Currently I'm running memtest. It's passed the first round of checks. I intend to let it run 24 hours. What are my next steps if both sticks of RAM are good?

JorgeB, Thanks so much for the suggestions. I think I have it so much in my head that I got great parts so hardware couldn't be the problem. I've taken a stick out and will monitor. Time will tell. Thanks for the focus, -Rob

It's rebooting itself. I built it last November and it would typically be stable for about a week. Now it's rare that it stays online for a day. Normally after a crash I can reach it, verify unclean shutdown, reboot, then bring the array back online. Now after a reboot I still have an unclean shutdown message. One item of note, during a parity check it seems to start at regular speed, ~200 Mbs but after an hour or two it will drop to ~100-200 kbps. Once it's dropped to that speed it will eventually crash.