Gorby

It turned out to be an issue with IPV6. After disabling the IPV6 stack the server has been rock solid and has been up for almost 3 days without any issues. So tonight I re-enabled the IPV6 stack and put back in my static IPV6 address and the server rebooted after 7 hours and 46 minutes. Now I just need to figure out if it's the NIC driver or a bug with the network stack.

I actually found out it's IPV6 that is causing my server to crash. If I disable IPV6 and only run an IPV4 address the system is stable as a rock and it has been up for almost 3 days without any issues. As soon as I re-enabled IPV6 and added my IPV6 address back in and rebooted the system crashed after 7 hours and 46 minutes. So I went back in and disabled IPV6 and the server is back up and running fine. Normally this wouldn't be an issue for me but considering I just switched my whole house over to IPV6 and was getting ready to turn off IPV4 I am going to have to rethink my plans. Now I need to find out if this is a driver issue or something with the IPV6 stack or just give up on my unRAID experiment and switch back to Windows Server 2025.

My unRAID server keeps randomly freezing or rebooting after several hours and I am having trouble isolating the issue. In the syslog file I am seeing a few minor issues like some power saving issues, the Bluetooth driver stopping and an issue with binding port 22 to my IPV6 address, but I am not seeing anything that would explain the reboots. I have attached my diagnostic file, and I am hoping someone will be able to help me atlantis-diagnostics-20250302-1300.zip

I am having the same issue. Everything was working great on 6.12.11 and decided to upgrade to version 7.01 and now for some reason my server is rebooting every 8 to 24 hours. I can't find anything in the syslog file but decided to wipe my array and do a fresh clean install to just see if something in my configuration was messing things up and I decided at the same time to move to zfs. Now I am seein consistent reboots after about 14 to 16 hours but again there isn't anything in the syslog except some minor issues like the bluetooth driver stopping and an issue with binding port 22 on my server's IPV6 address. I am really at a complete loss as to why the reboots are happening but I am going to try disabling IPV6 just to see if it has any impact on stability.

This just happen to me on my ML350 G6 and I was able to work around the issue by installing an HP / Intel 82571EB/82571GB Dual Port NIC I had laying around. I was just wondering if anyone knows if the corruption issue has been fixed or how to tell if your system has this corruption issue and it's safe to re-enable the TG3 driver? ripley-diagnostics-20220528-2218.zip