Martini_Mcfly

So after a couple of hours this is whats posted: A repeated connection error for Dynamix. The IP is pointing to the IP for a laptop on my network (for some reason). Seems aligned to this: Not sure if that's simply correlation and has nothing to do with this or not. Attached below. syslog-127.0.0.1.log

Wow, I cant believe I overlooked that. Thank you. Added.

Ahhh.. Appreciate your clarification and apologies for my ignorance on a lot of this. These are the current settings.

Thank you for the fast reply! I did that a bit earlier and I believe this is the correct file? Let me know if I need to configure it differently. syslog.txt

I've been lurking for ages, but am at the end of my rope so need some expert insight. The sever has been up for a couple years. To be fair, I've been having some random issues for a while that are most likely due to my own learning curve with Unraid. However, for the last few months parity check has failed due to (what seams to be) an OS crash. This results in me needing to do a hard power down. Not great. I've hunted these forums, tried multiple fixes, but nothing has helped. I even tried upgrading to the latest OS, but a lot of communication issues popped up and I rolled back. I thought it might be a nvme drive that was accidentally added a while back, so I cleared it, removed it, and went to rebuild parity. This was probably a mistake. Now parity wont rebuild and gets "stuck" like it did when checking. Right now its stuck at 10.8% with days ticking up. I ran memory tests a couple weeks ago that seemed to pass, and just went in to the case to re-confirm the cables were tight and reseated. So I'm opening this to the team. My logs are attached. Please help direct me on what I'm missing. I have a massive amount of data and configs I really would hate to lose. walle-diagnostics-20250405-1341.zip