YankeeJohnboy

If anyone finds this, I wish I had more helpful news. Ultimately I took the MB/CPU/Mem and swapped it with my other Unraid server and suddenly they both are running fine. I have no idea what particular thing was the problem or solution, but it all seems to be happy now. Thanks for the pointer @JorgeB!

Can do. I just pulled stick 2 of memory and started up a new parity check, will report back with failures/successes after trying both sticks.

I'm going a little crazy... I've been fighting a loop for the last month or so where Unraid crash/freezes, and eventually forces me to do a hard reboot to bring it around. Because of the hard reboot, it forces a parity check, which then eventually freezes forcing the cycle to repeat. Things to know: 1. I recently replaced the MB/Processor/RAM, moving from an i5-4690k to an i7-13700k. Server had been pretty solid prior to the change. 2. After dealing with some freezes early on, I ran memtest as suggested in other threads, finding bad sticks. I replaced the sticks with a different set and got a solid memtest out of them. 3. ISP has been doing some overnight work in my area several times, causing connectivity issues. 4. My UDM SE seems to be on the fritz as well. It's dropping the WAN port, and requires a reset of the port to bring it around. Based on posts in the Ubiquiti forum, it seems to be a shared issue and likely unrelated to this, but just for full disclosure. Things I've tried: 1. SSH into server when GUI is inaccessible - This will allow me in to do some basic checking, but I can't seem to make any significant changes. powerdown commands are unsuccessful, as well as attempting to run diagnostics, both just hang forever. I was able to check the progress of the parity sync, but over the course of an hour it didn't change position (made it to mdResyncPos="16170318848" of 18TB). 2. Booting into safe mode - Tried this last night, and ended up in the same position 3. Re-seating the RAM - I did a memtest and replace as indicated above, and moved sticks from A1-B1 to A2-B2. The replacement seemed to lengthen my runtime, but not fix things entirely. 4. Setup syslog - finally got this setup yesterday per the forum sticky, and have attached the file from the USB after reboot. There are tons of things going on in the file, but I am not adept enough to decipher them correctly. 5. Upgrading OS - Grasping at straws, thinking maybe I was having some issues with it being a 13th gen CPU, I moved to 6.12.0-rc5. Helped some, but still suffering. Attached: 1. Syslog following most recent crash, pulled from USB 2. Diagnostics from after the crash, haven't been able to get them in a crashing state. Don't know if helpful, but figured it couldn't hurt. If anyone has any ideas, I welcome the input. I'm pulling out my hair trying to figure this out. syslog odin-diagnostics-20230516-1228.zip

Thank you, I've installed the swapfile plugin, as the system is limited to 16G of RAM. Hopefully that will alleviate any future issues!

Getting this error pop up in fix problems, and Squid's post directed me to post the diagnostics here. This error has recurred despite a reboot. Can someone please help me correct this? 😞 odin-diagnostics-20230314-1434.zip