crittersfritters

I've been having this issue myself for at least as long as the 7.2.x full release version. I've identified the issue happens exactly when my router performs its weekly reboot, and then my ISP serves a new IP address. I can manually update the IP address that Connect uses by toggling access off and on.

I updated the curve optimizer to be +6 and fully disabled C-States about a week ago, so it's now lasted longer than the last lock-up. I'm gonna mark it resolved, and hopefully not invoke fate here.

Well unfortunately the issue happened again today, roughly 12:17PM MST. This time I made sure to have a monitor up to view the headless console, and it was unresponsive with the monitor not detecting input when I looked at it. The changes I made were to set a +4 curve optimizer setting on all cores and set the "Power Supply Idle Control" to "typical current idle." I suppose I should try completely disabling C-State control entirely as it does mention that as a potential step, but I didn't want to add too many variables to the mix. I've attached a new diag zip. tower-diagnostics-20251210-1350.zip

Alright so my memory is compatible per that link, and it looks like I'll need to set up both the C-state bios adjustment and the curve optimizer for a positive adjustment according the the ArchWiki link buried in there.

unRAID OS v7.2.2 I woke up this morning to a complete unresponsive server, to the point that even attempting to connect my extra monitor to see anything on the headless console didn't work. I checked my router, and it reported the network port going down shortly before I got a ton of service outages from my cloud vm monitoring the services I expose. Syslog is set to write to the share I have, and after an unclean shutdown there is no log entries for the period it was down. tower-diagnostics-20251205-0928.zip

Is the plugin update out yet? I'm still having the issue

Also experiencing this issue.

I'm also having an issue with this, and I think I've added the two modprobes correctly, but I don't even get a GUI anymore when I choose unRAID GUI mode on boot up. I'm beginning to think that there may be something wrong with my upgrade but I genuinely have no idea what to do anymore. I realize that Plex won't work until they sort out their end of things, but at the very least it should work on unRAID from what I'm reading. Even this guy managed to get it working, but I wish he'd have actually documented his configuration even a little. tower-diagnostics-20250412-1950.zip

hey man I just wanted to thank you for this awesome submission! My friends have been playing nonstop but they had to wait for one person to get on until now!

I re-applied thermal paste and the issue wasn't reoccuring any more afterwards. Any chance there will be OS native temp monitoring? The fact that a plugin is required but troubleshooting steps involve disabling plugins seems very counterintuitive for temp-related issues like mine was.

So this is the first instance of this error I've even seen, and the immediate entry in the syslog is pasted below, but the Fix Common Problems plugin specifically recommended that I make a support post. "Jun 26 20:40:50 Tower root: Fix Common Problems: Error: Machine Check Events detected on your server Jun 26 20:40:50 Tower root: mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead." I've attached the diagnostic as well, but as far as I'm reading it seems as though mcelog can't even parse the error that's happening? Should a reboot suffice or do I have a deeper issue developing? tower-diagnostics-20240626-2305.zip

If find it hard to believe the issue could be my hardware, as it's not nearly old enough to be failing. The one part in my system that could have been old enough would have been my memory, but now I have replaced it with tested good memory modules. The CPU is running at stock, the PSU is rated well and I'm using it with an UPS as well. Assuming faulty hardware is not the root cause, what else could be causing complete shutdowns with no logging? From the research I've been doing, I'm leaning towards either my system is having temp spikes and shutting itself down, or the possibility that my flash drive is dying. Would I be able to test the flash drive in any capacity for failure?

I've been having a reoccurring issue with my system for about 2 weeks now, and I had originally diagnosed it to be faulty memory but I have a new unbuffered ECC set that's passed 10 runs of memtest86+ and I'm at my wits end. Aside from the memory, the rest of the hardware is less than 2 years old. I have tried rolling the OS version back to an older one and it does not resolve the issue, but I can't find anything in the syslog that could point me in the right direction and have no idea where to start digging past that. There's nothing I can find that indicates a pattern, either. I've attached the diagnostic report made after the last crash. tower-diagnostics-20240426-2050.zip

I started having this same issue on my system recently only after upgrading from 6.12.8 to 6.12.9. Hopefully my diag dump will help with pinpointing the root cause. I chose to downgrade back to 6.12.8 as a troubleshooting step just to save headache. tower-diagnostics-20240408-0439.zip