New user, installed unraid a week or so ago have been getting what I assume to be random crashes.

Is there any easy way to diagnose?

Upgraded to 6.7.0-rc8 to allow for persistent syslog but nothing interesting reported (that I can see).

 

Looks like the crash / reboot happened sometime between 2am and 2:27am. 

I get emails to say 'parity check started' after these crashes and there seems to be no correlation with anything

 

May 5, 7:31 PM

May 6, 1:24 AM

May 6, 2:16 AM

May 6, 7:18 AM

May 6, 12:08 PM

May 8 1:02pm

May 10 3:30 am

May 10 7:49 am

May 11 2:29 am

....
May 10 21:00:01 hulk crond[1855]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null
May 10 22:00:01 hulk crond[1855]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null
May 10 23:00:01 hulk crond[1855]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null
May 11 00:00:01 hulk crond[1855]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null
May 11 01:00:01 hulk crond[1855]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null
May 11 02:00:01 hulk crond[1855]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null
May 11 02:27:21 hulk kernel: Linux version 4.19.37-Unraid (root@Develop67) (gcc version 8.3.0 (GCC)) #1 SMP Tue Apr 
30 12:20:22 PDT 2019
May 11 02:27:21 hulk kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot
May 11 02:27:21 hulk kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
May 11 02:27:21 hulk kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
May 11 02:27:21 hulk kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
May 11 02:27:21 hulk kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
May 11 02:27:21 hulk kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' form
at.
....

 

hulk-diagnostics-20190511-0139.zip

Edited May 11, 20197 yr by brucealdridge
uploading diagnostics, since i can't post twice in one day

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

There are known issues with Linux and Ryzen, most workarounds are discussed here.

20 minutes ago, johnnie.black said:

There are known issues with Linux and Ryzen, most workarounds are discussed here.

That's disappointing, having just found unraid really impressed. I guess I just have to put up with these random lockups then... assuming it is the ryzen issue. 

That thread seems to indicate that it's worse on 6.7 RC, having just upgraded a yesterday its clearly an issue on all versions for me.

1 hour ago, brucealdridge said:

I guess I just have to put up with these random lockups then

If you read the thread there are several workarounds that work for most people.

Just some forum advice. You can post as often as you want now that your first post has been approved.

9 hours ago, trurl said:

attach the complete diagnostics zip file to your next post

If you edit an old post, for example, to attach your diagnostics, then it might not be noticed, because many of us that read a lot of threads to help people only look at threads that have new posts in them.

Thanks team, 
Server has been up 3days 15hrs since those changes. clearly made a difference!