indianazoidberg

Thanks. Thats interesting. I had no idea. It looks like its meilisearch which is a dependency for another docker container. Even though its constantly restarting, its working fine. I'll keep a eye on it.

A new log with it now running fine. If its still running without issue in a few days, then I guess the issue was the GPU? Its a shame because that GPU was very helpful for encoding videos syslog

Done and its now running again, and running another parity check. And I uninstalled the Nvidia driver as well. Could this be a example of a issue with the Nvidia driver plugin, or the driver its self? Or a physical GPU issue? I got this GPU because its not externally powered, just via PCIe. And thoughts or advice on the NIC issues? What are the issues? Do you think its serious?

My server has been crashing a lot recently. It will run fine for a day or two, then crash, but it is still reporting to the syslog watcher and my router still sees it, but I cant ping it on my LAN or via my VPN (tailscale) I have attached the syslog file. And it seemingly did it again around 3am Jan 8th 2025 (today). But I honestly don't really know what to do with this infomation and would love some help. And the only way to get it back online it to do a hard reboot. The only major change I have done to it is I added a RTX 3050 (specifically this one. Used. https://www.amazon.com/GIGABYTE-GeForce-Graphics-WINDFORCE-GV-N3050OC-6GL/dp/B0CVHD8PLP) to my server a few weeks ago, and everything seemed to work fine until a few days ago when I started having these issues. I don't know if they are related, but I am pulling my GPU for now to see if it becomes more stable without it. Any help would be greatly appreciated! Edit: System info Motherboard: PRO Z790-P WIFI Ram: 32gb CPU: i5-14500 (mobo updated to hopefully fix microcode) Case: supermicro 4u server with backplane Power: Dual 1500w PSUs with UPS backup syslog

So I seem to have had a hardware failure. Probably the CPU from my testing. But I am using this as a opportunity to upgrade my system. I have ordered new parts and they will be here in a few days. What is the best procedure for such a upgrade? I'll run through some info. Motherboard: Asus Z170 Pro Gaming to MSI PRO Z790-P CPU: i7-6700 (i think) to i5-14500 RAM: 32GB DDR4 to 32GB DDR5 And all of my drives go through a HBA card. Plus a 2TB NVME drive as a cache drive (which I think still has data on it that needs to be transferred) I believe my USB drive is still working from my testing testing. Any tips or guidance would be greatly appreciated. I have 28ish HDD's.

Just tried this a few times. Still won't boot. I guess I will use this as an opportunity for an upgrade. Just sooner than I thought. I'm just going to get a new motherboard, CPU, and RAM. I'm going with the assumption that my PSUs, HBA, and backplane are all still working (the HBA shows drives connected to it on boot, and its showing everything I believe)

Okay. And that won't fuck anything up in that long term?

I have a update that is probably not good, but I would like to hear what others think. I have been running memtest for 48 hours. Zero errors were found. I then tried to boot into unraid, but now I unraid wont even load. Normal, or safemode. And it seems to do it in a different place when it tries to boot. I tried this around 10 times today. So I cant turn on syslog like @JorgeB recommended. I have also noticed that on the monitor I've attached to my server for troubleshooting, when it stops booting, the text at the end seems to get slightly corrupted. I've attached photos showing that, and some of the other screens that its shown when its died. I've also tried removing ram sticks, and swapping them in case there is a faulty stick, but that hasn't seemed to change anything. Questions: 1. Could my CPU be going bad/failed? Or is ram still the most likely issue. 2. Is there anyway check the integrity of my usb drive? I could do this on windows, or linux (if someone could walk me through that process). I managed to pull a usb backup before this went REALLY down hill. But I would also guess if that was the case, it would probably fail to boot in a more reputable way and not seemingly randomly? 3. If this is a hardware failure, I'm probably just going to upgrade my system with a new motherboard, cpu, and ram. Unraid and the dockers it runs have become a thing that I am now using so often that its extremely inconvenient to loose access to it. Should I look into a system that supports ECC ram? Is that worth it? Any other ideas before I start shooting the parts cannon at the problem?

A hardware problem is also what I'm leaning towards. It's hardware is just old PC gaming parts from a last build, so they all have 6+ years of use on them. I'll do the syslog in a few days. I want to let memtest run a long time first. I also wont have time with my work schedule to really mess with it for a few days anyway

Hi. My Unraid server seems to be crashing. Its crashed 4 times in the last 16 hours. I've had it running flawlessly for 8 months until yesterday. Each time I have needed to reboot the server manually (long press the power button, or press the reset button on the front) to get it to boot up again. First time it crashed, I restarted the server, then started the array. A hour or so later it crashed in the middle of the parity check. Restarted again, started the array, it seemed to crash almost immediately. Restart. Ran memtest for a single pass, and passed. Started the array and dumped the log, turned off all my dockers except for 4 that I use all the time (they run together) and copied over my config and USB backup to my desktop. This time it seemed to crash as soon as that copy was finished. I didn’t catch the moment to see if it was exactly the same time, but it seems close to me. I’ve been running a continuous ping test to see when it crashes. It completely drops off my network, and all drive activity stops. I asked the Discord for help. My docker is running ipvlan for my dockers (was asked to check this from the discord), then Unraid crashed while sitting idle. I had not started the array. I'm now running a longer memtest. So far, 12 hours in and its still passing. But I'm going to let it run for 24-72 hours. Any thoughts? newborg-diagnostics-20240728_1223.zip