I'm having issues using a new motherboard in unraid, for some reason the system keeps rebooting itself after 8 hours...

 

I'm using a new motherboard from Aliexpress, since I'm from Brazil I don't have many mini itx options here and this motherboard seems to be a good option for us brazilians

 

https://pt.aliexpress.com/item/1005004230983454.html?spm=a2g0o.order_list.0.0.46a8caa4AMJrVa&gatewayAdapt=glo2bra

 

This motherboard have 3 SATA controllers... 1 from the chipset/CPU, and 2 JMB58x probably an modified version of those 5x Sata M.2 PCIe boards

The diagnostic is on the zip attached, do you guys already experienced something like this?

 

PS: I didn't tried any other OS in this machine yet because I already moved everything to this new "server"

 

unraid-diagnostics-20220621-2107.zip

5 hours ago, viniblopes said:

for some reason the system keeps rebooting itself after 8 hours...

The OS should not order a reboot. It might crash or shutdown. The 'reboot' part is probably a setting from your motherboard.

 

The log (like all the OS) is stored in RAM and lost on a reboot. Your diagnostics cannot show what happen. You should set up a syslog server and post this file after the next crash/reboot.

@ChatNoir the server rebooted today and I been running the log to the file a few days and trying to sort it out...

 

See the syslog below:

syslog

 

Since I've seen ERRORs in Sata I changed HDD when I saw this error:

Jun 17 07:55:32 unraid kernel: ata2.00: irq_stat 0x08000000, interface fatal error

Jun 17 07:55:32 unraid kernel: ata2: SError: { RecovData UnrecovData Handshk }

 

But I think sunday I reseted the BIOS settings and plug every HDs back in the mobo and right now I'm seeing this errors: 
 

Jun 22 04:13:49 unraid kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

Jun 22 04:13:49 unraid kernel: ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)

Jun 22 04:13:49 unraid kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

Jun 22 04:13:49 unraid kernel: ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)

Jun 22 04:13:49 unraid kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

Jun 22 04:13:49 unraid kernel: ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)

1 hour ago, viniblopes said:

See the syslog below

 

Near the end of that syslog

Jun 22 04:14:24 unraid kernel: mdcmd (37): check correct
Jun 22 04:14:24 unraid kernel: md: recovery thread: check P ...

Why were you running a CORRECTING parity check?

 

1 hour ago, viniblopes said:

Since I've seen ERRORs in Sata I changed HDD when I saw this error:

Jun 17 07:55:32 unraid kernel: ata2.00: irq_stat 0x08000000, interface fatal error

Jun 17 07:55:32 unraid kernel: ata2: SError: { RecovData UnrecovData Handshk }

How did you decide which drive to change? Probably connection not a drive problem.

@trurl 

2 hours ago, trurl said:

How did you decide which drive to change? Probably connection not a drive problem.

Already tried changing cables and didn't solve anything... already both new ones and also didn't solve the issue

 

 

2 hours ago, trurl said:

Near the end of that syslog

Jun 22 04:14:24 unraid kernel: mdcmd (37): check correct
Jun 22 04:14:24 unraid kernel: md: recovery thread: check P ...

Why were you running a CORRECTING parity check?

Everytime the system reboots it's keep doing parity check

1 hour ago, viniblopes said:

Already tried changing cables and didn't solve anything... already both new ones and also didn't solve the issue

 

That isn't really an answer to this question:

4 hours ago, trurl said:

How did you decide which drive to change?

Do you mean you changed all cables and drives? Regardless, those log entries suggest a problem communicating with a disk, not an actual disk problem.

 

1 hour ago, viniblopes said:

Everytime the system reboots it's keep doing parity check

Unclean shutdown parity check is NONCORRECTING. The log entries I was asking about was a CORRECTING parity check. But it does begin immediately after start. Maybe it is restarting an unfinished CORRECTING parity check you had started before.

 

Go to Main - Array Operation, click the History button, and post a screenshot.