Abstract7227

Ah damn you're right, I apologize. I probably missed it because I went from 2 rank, 2/4 3200Mhz, which was fine, to 2 rank, 4/4 3200Mhz. I configured it to 2666Mhz now. Thx for the feedback

My current diagnostics (after reboot, as I cannot get my diagnostics during the crash) trantor-diagnostics-20230309-1712.zip

cause I think this is the 3rd time that the whole server crashes while only spitting out a btrfs error. Anything else I can investigate?

and that can crash the entire server?

This might be a noob question, but why is it that a btrfs error result in my server not being accessible anymore via the webgui (500 error)?

so I have to replace that one? cause that drive is pretty new

I tried that, rebooted my server, got another crash today (logs attached) with btrfs corruption warning. At this point I: replaced my RAM (twice) replaced my motherboard replaced my CPU (twice) replaced my PSU replaced my cache drives The only original parts now are the boot flash drive, the spinning drives (which are xfs formated) and the case. Assuming I can rule a hardware issue out at this point, I am not sure how I should proceed now. I only run a nextcloud instance with a swag reverse proxy and a home assistant instance on there, so it's not like I am doing a lot of crazy things with this. Any recommendations? issue.txt

So I did everything. Replaced RAM, CPU, motherboard, PSU, even installed new power cables to make sure they are not the cause. Even used a different power outlet. The system is still crashing, found one warning in the logs (attached), after googling I found this issue so if I understand this correctly, using the Custom : br0 with a static IP address causes issues? Currently, all of my docker containers have a custom static IP address assigned to them via br0. Am I to understand I have to bridge them all? I don't quite understand why though, is this a bug in unraid? T issue.txt

swapped my motherboard for a ASRock X570M Pro4 a few days back, already got a crash however. CPU is next, PSU after that I was wondering if a faulty OS flash drive could also throw an error like that?

So I tested my RAM for 48-ish hours with no error got another crash today though, relevant logs in attachment. can't reach the server or even ping it at the moment. I googled the error, found some guy that fixed this issue by replacing his motherboard, CPU and RAM. issue.txt

So theres little chance this can solve the problem? Is there a rule of thumb to how many memtest passes I need to be pretty confident about the RAM?

For the record, I am talking about that multiplier setting

Reread your post and something I also did not do is check my RAM speeds, it is set to auto in the BIOS, do I have to be conserned about this or is this only a problem if I made a manual effort in the past to overclock it?

The memtest passed. I am unsure how to proceed next though. To summarize: Given that I already replaced my RAM and ran memtests on both module kits, can I rule out that it is a memory issue? Or is there maybe a BIOS setting for memory that I still need to look at? I also set the "Global C-State Control" setting of the BIOS to "disabled", double checked today that it is indeed off. Something I noticed today that might have an impact however, there is a settings called "Power Supply Idle Control" that was on auto, I now put it on "Typical" (thought I already changed that setting from your first suggestion, but it seems I didn't hit save maybe)

I'll try that, but given that I already replaced the RAM and the previous RAM already passed 3 memtests, I doubt the actual RAM is the issue. Can it be something else?