Hi all,

 

I have been struggling with this for quite a few days. My unraid has always been rock solid but then I tried to add a few hard drives. It used to be a two hard drive, one parity one standard set up. I have since added three more hard drives of the same size. Parity rebuilt without any problem. Thinking that now I have 4 data hard drives, I added another parity drive. But I cannot finish the parity sync. Unraid always reboots at a random point during the parity sync process.

 

I have tried:

 

1. switch out the PSU

2. memtest

3. switch out the new parity drive with another harddrive

 

The syslog shows no error whatsoever like the following:

 

Apr 27 10:18:13 Boston kernel: mdcmd (36): check
Apr 27 10:18:13 Boston kernel: md: recovery thread: recon Q ...
Apr 27 10:18:28 Boston  nmbd[7230]: [2023/04/27 10:18:28.459587,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Apr 27 10:18:28 Boston  nmbd[7230]:   *****
Apr 27 10:18:28 Boston  nmbd[7230]:
Apr 27 10:18:28 Boston  nmbd[7230]:   Samba name server BOSTON is now a local master browser for workgroup WORKGROUP on subnet 192.168.68.100
Apr 27 10:18:28 Boston  nmbd[7230]:
Apr 27 10:18:28 Boston  nmbd[7230]:   *****
Apr 27 10:19:55 Boston  ntpd[1599]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Apr 27 10:23:42 Boston  nmbd[7230]: [2023/04/27 10:23:42.054461,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Apr 27 10:23:42 Boston  nmbd[7230]:   *****
Apr 27 10:23:42 Boston  nmbd[7230]:
Apr 27 10:23:42 Boston  nmbd[7230]:   Samba name server BOSTON is now a local master browser for workgroup WORKGROUP on subnet 172.18.0.1
Apr 27 10:23:42 Boston  nmbd[7230]:
Apr 27 10:23:42 Boston  nmbd[7230]:   *****
Apr 27 10:23:42 Boston  nmbd[7230]: [2023/04/27 10:23:42.054605,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Apr 27 10:23:42 Boston  nmbd[7230]:   *****
Apr 27 10:23:42 Boston  nmbd[7230]:
Apr 27 10:23:42 Boston  nmbd[7230]:   Samba name server BOSTON is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
Apr 27 10:23:42 Boston  nmbd[7230]:
Apr 27 10:23:42 Boston  nmbd[7230]:   *****
Apr 27 12:40:15 Boston webGUI: Successful login user root from 192.168.68.75
Apr 27 13:46:33 Boston kernel: Linux version 5.19.17-Unraid (root@Develop) (gcc (GCC) 12.2.0, GNU ld version 2.39-slack151) #2 SMP PREEMPT_DYNAMIC Wed Nov 2 11:54:15 PDT 2022
Apr 27 13:46:33 Boston kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot
Apr 27 13:46:33 Boston kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Apr 27 13:46:33 Boston kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Apr 27 13:46:33 Boston kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Apr 27 13:46:33 Boston kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Apr 27 13:46:33 Boston kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Apr 27 13:46:33 Boston kernel: signal: max sigframe size: 1776
Apr 27 13:46:33 Boston kernel: BIOS-provided physical RAM map:

 

It's stable running parity check and suddenly restarts at 13:46. The same story repeated multiple times.

 

Also attached is the diagnostics. and would really love to hear people's thoughts on what's wrong. Thank you all!

boston-diagnostics-20230427-1555.zip

Edited April 27, 20233 yr by rainrdx

Are you sure your power supply is up to handling the load when a parity check is running?    The other thing to check is that you do not have a thermal issue so that the CPU overheating shuts down the server.

10 minutes ago, itimpi said:

Are you sure your power supply is up to handling the load when a parity check is running?    The other thing to check is that you do not have a thermal issue so that the CPU overheating shuts down the server.

Thank you! The four new drives are in a separate set up with its own PSU and connected through an HBA card. Need to check CPU thermal too but doesn’t seem like there’s an issue given this is a big server with ample air flow. Thank you again for taking a look!