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