[SOLVED] Randomly restarting parity check after it passed

[SpankMeLater]

Unraid beginner here , I'm experiencing a weird problem om my nas.
Last week, I started building a new nas, was able to set an array and shares.
Setted a parity check at monthly, it did a parity check (and passed). But after a few hours, it restarts the parity check again?
I also momentarly lose connection; but by refreshing, its works fine again.
Would this be a hardware problem?
Currently using it for storing games and schoolwork. So i'm not really pushing or doing crazy stuff on the system 😛.
I added diagnostics and syslog zips.
Thanks in advance.

vault-syslog-20201221-1500.zip vault-diagnostics-20201221-1524.zip

[itimpi]

BTW:  to save you effort in the future probably worth mentioning that the diagnostics include the current Syslog so no need to supply it separately.

[SpankMeLater]

30 minutes ago, itimpi said:

BTW:  to save you effort in the future probably worth mentioning that the diagnostics include the current Syslog so no need to supply it separately.

Ooh, ok, good to know and sorry for the confusion.😅 Yes, they are the same.

[trurl]

Dec 21 14:20:15 Vault emhttpd: unclean shutdown detected

That will always start a parity check.

 

Did you know your server rebooted?

[SpankMeLater]

10 minutes ago, trurl said:

Dec 21 14:20:15 Vault emhttpd: unclean shutdown detected

That will always start a parity check.

 

Did you know your server rebooted?

No, I did not. I wasn't near it at the time. 
I looked in the logs and saw:
"Dec 21 14:20:27 could not insert 'kvm_amd': Operation not supported"
or
"Dec 21 14:25:52 kernel reports TIME_ERROR: 0x41: Clock Unsynchronized"
But those 2 should not be responsible for a sudden shutdown?

[trurl]

28 minutes ago, SpankMeLater said:

I looked in the logs and saw:
"Dec 21 14:20:27 could not insert 'kvm_amd': Operation not supported"
or
"Dec 21 14:25:52 kernel reports TIME_ERROR: 0x41: Clock Unsynchronized"

But those 2 should not be responsible for a sudden shutdown?

These are after the reboot and start with unclean shutdown as you can see from the timestamps.

 

And in fact, syslog always restarts when you reboot since it is in RAM like the rest of the OS.

[trurl]

Is you BIOS configured to autostart on powerup? Is your server on an UPS? My guess is you are losing power.

[SpankMeLater]

Just now, trurl said:

Is you BIOS configured to autostart on powerup? My guess is you are losing power.

Not that i'm aware of.
I will shutdown the nas, physically check if connectors are loose and check the in the bios for that.
 

[SpankMeLater]

23 minutes ago, trurl said:

Is you BIOS configured to autostart on powerup? Is your server on an UPS? My guess is you are losing power.

More detailes on my motherboard.
Gigabyte B450M DS3H-CF
ac back ("autostart on powerup") is always off,
wake on lan= enabled
All internal connectors are well plugged in 

[trurl]

I was thinking more about the power from the outlet where it is plugged in.

1 hour ago, trurl said:

Is your server on an UPS?

 

 

[SpankMeLater]

9 minutes ago, trurl said:

I was thinking more about the power from the outlet where it is plugged in.

 

 

You mean a unstable net? that is unlikely, it is on a power brick, but on the power brick, there are only a 3D printer and 2 pc's.
That woudn't be the problem I suppose?

[SpankMeLater]

Updated
I bought a APC ups and installed a new motherboard (motherboard failed randomly?).
So far, so good.
Will bring an update within a few days, or sooner when if a error occurs.
 

[SpankMeLater]

Updated 2:
The NAS has been running for more than 5 days without any errors.
The problem was the C-state settings in the bios. After disable it, The problems I had disappeared.