I've been dealing with unclean shutdowns since moving to unpaid 7. I assumed they were coincidental with unraid 7 release timing, so I replaced an older (and notorious) nvme drive this week thinking that might solve the issue. It did not. Wondering if anyone sees any memory issues or any other hardware indications on what might be going on in my diags. They are attached.

 

Thanks in advance

unraid-diagnostics-20250317-0902.zip

5 minutes ago, bmrowe said:

I've been dealing with unclean shutdowns since moving to unpaid 7. I assumed they were coincidental with unraid 7 release timing, so I replaced an older (and notorious) nvme drive this week thinking that might solve the issue. It did not. Wondering if anyone sees any memory issues or any other hardware indications on what might be going on in my diags. They are attached.

 

Thanks in advance

unraid-diagnostics-20250317-0902.zip 171.62 kB · 0 downloads

 

Looks like the diags were captured after reboot, try mirroring the syslog

12 minutes ago, Michael_P said:

 

Looks like the diags were captured after reboot, try mirroring the syslog

Thanks for taking a look. I have been mirroring the syslog. Attached.

syslog-127.0.0.1.log

8 minutes ago, bmrowe said:

Thanks for taking a look. I have been mirroring the syslog. Attached.

syslog-127.0.0.1.log 85.34 kB · 0 downloads

 

Are you commanding the shutdowns, like the one from yesterday?

54 minutes ago, Michael_P said:

 

Are you commanding the shutdowns, like the one from yesterday?

I've triggered two shutdowns (to replace the nvme drive and later go back and add a heatsink), neither were unclean from what I remember. All the shutdowns that are concerning me, like the one this morning around 830am, are not being triggered by me.

Edited March 17, 20251 yr by bmrowe

28 minutes ago, bmrowe said:

I've triggered two shutdowns (to replace the nvme drive and later go back and add a heatsink), neither were unclean from what I remember. All the shutdowns that are concerning me, like the one this morning around 830am, are not being triggered by me.

 

Mar 16 23:11:28 unraid kernel: x86/PAT: frigate.detecto:3408520 map pfn RAM range req uncached-minus for [mem 0x1d6490000-0x1d6493fff], got write-back
Mar 16 23:11:28 unraid kernel: x86/PAT: frigate.detecto:3408522 map pfn RAM range req uncached-minus for [mem 0x3335d0000-0x3335d3fff], got write-back

 

Besides this, I don't see anything crazy - try turning off containers one at a time or run it in safe mode for a bit to see if you can narrow it down - else it's probably a power issue or hardware

7 minutes ago, Michael_P said:

 

Mar 16 23:11:28 unraid kernel: x86/PAT: frigate.detecto:3408520 map pfn RAM range req uncached-minus for [mem 0x1d6490000-0x1d6493fff], got write-back
Mar 16 23:11:28 unraid kernel: x86/PAT: frigate.detecto:3408522 map pfn RAM range req uncached-minus for [mem 0x3335d0000-0x3335d3fff], got write-back

 

Besides this, I don't see anything crazy - try turning off containers one at a time or run it in safe mode for a bit to see if you can narrow it down - else it's probably a power issue or hardware

Those warnings stem from a dual coral tpu pci card I’m using with frigate. Not sure if they are normal. I’ll open a thread there as well. 
 

is there any additional logging I can be doing? I was hoping the logs would be more verbose. Like I remember weird things in the past when my battery backup gets close to

end of life - but I don’t want to go replace RAM, battery backup, power supply, etc without some indication. 

21 minutes ago, bmrowe said:

my battery backup gets close to

end of life

 

definitely a possibility, nothing would be logged if it lost power. As for RAM, you can run memtest on it. flaky hardware can be tricky to troubleshoot