Hey, I've been experiencing random shutdowns, potentially after upgrading to version 7.0.0, but i'm unsure how to troubleshoot it.

my system consists of the following:
R7 7900x
Gigabyte B650I v1.0
RTX 3070 TI

x2 48GB (96GB) Micron 5600Mhz DDR5

x1 Sata SSD

x2 seagate x18 16 tb

x3 nvme SSD's from Intel, Kingston and Samsung

Corsair SF850L PSU

 

I've been running unraid pretty stably on 6.12.11 and upgraded to 7.0.0 about 2 weeks ago, and ever since it hasn't been stabil for more than a few hours.
it doesn't seem like it's caused by the PSU, and I've pulled out my GPU to ease the load on on it, but no clicks occurs when the system restarts, so i'm suspecting it's a software issue, rather than a hardware problem.
Yesterday i also ran memtest86 for 10 hours and it passed with 0 errors (also with no shutdowns).
It has now been running in maintenance mode for a little over 16 hours now and there has been no restarting.

I also made sure to check for system temperatures, and all components was running at pretty stabil temps - Cpu stayed at around 40c at idle and gpu at about the same.
Even during high load operations the cpu stayed below 70, and the drives never really exceeded 40c.

I've read in a previous post, that some people have experienced shutdowns after deploying a new docker container or downloading plugins, which i have done in the meantime.
Since the system shuts down and I therefore don't have any useful logs, I'd try and see if there was a known issue regarding this, before i start testing out all 20 of my containers

Happy sunday!

The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot.   It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.
 

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

Okau 

1 hour ago, itimpi said:

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

Thanks I wasn't exactly sure how the syslog server worked, but this makes a lot of sense! I thought I had to use another system as a syslog server haha.
I'll try and wait for a system restart again and attach the logs and system diagnostics  

Looks like I was victim of the nchan memory leakage bug in 7.0.0, since that's what the last call in syslog_previous reported on before it crashed. I've updated to 7.0.1 now and will report back if things stabilise or continues to misbehave!

Edited March 2, 20251 yr by jztreso

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.

For me it worked to upgrade to 7.0.1.
It has been running for 17 hours now, which it never did on 7.0.0 so i think i'll be closing the ticket.

 

12 hours ago, Gorby said:

I am having the same issue.

I unfortunately doubt this is the threat for your issue, and imo it sound like a bit like a hardware issue so maybe run a memtest86, replace components if possible, run in maintenence mode and see if it still happens

Happy this solved it for me and good monday!

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.