I'm having problems with Unraid rebooting, its unclean because I get parity checks right after

 

I attached a log file, any ideas?

 

Thanks!

 

syslog-previous

Edited April 18, 20242 yr by flowermoron

The log you mention is missing!

 

Having said that the syslog in the diagnostics is the RAM version that starts afresh every time the system is booted.  You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash.  The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field. 

 

When you say 'rebooting' to you mean it actually reboots by itself or do you mean it 'freezes' and you have to manually force a reboot?   Asking because if it spontaneously reboots this suggests a hardware issue.

 

4 minutes ago, itimpi said:

The log you mention is missing!

 

Having said that the syslog in the diagnostics is the RAM version that starts afresh every time the system is booted.  You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash.  The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field. 

 

When you say 'rebooting' to you mean it actually reboots by itself or do you mean it 'freezes' and you have to manually force a reboot?   Asking because if it spontaneously reboots this suggests a hardware issue.

 

 

Sorry about that I had to edit that log because the server is in my real name lol , but its there now!

 

& the server doesn't freeze, its an instant reboot, it goes 'click' and it quickly boots up, but i always get a parity check.

1 minute ago, flowermoron said:

t goes 'click' and it quickly boots up, but i always get a parity check.

 

That will almost certainly be hardware related (in which case there is nothing in the log).   I looked and could not spot anything.

 

The most likely culprits would be PSU not coping with the load or something thermal like the CPU overheating.

 

Just now, itimpi said:

 

That will almost certainly be hardware related (in which case there is nothing in the log).   I looked and could not spot anything.

 

The most likely culprits would be PSU not coping with the load or something thermal like the CPU overheating.

 

 

CPU is barely doing anything, but one thing I noticed was that yesterday it crashed at the same time of day, right when I booted up my PC.

I have GoodSync installed on my PC (synchronization app), and the moment it started working the server crashed.

 

Maybe it's just a coincidence?

5 minutes ago, flowermoron said:

 

CPU is barely doing anything, but one thing I noticed was that yesterday it crashed at the same time of day, right when I booted up my PC.

I have GoodSync installed on my PC (synchronization app), and the moment it started working the server crashed.

 

Maybe it's just a coincidence?

 

That might suggest a PSU overload issue when the server tries to spin up all drives simultaneously?  What PSU do you have? 

 

Since you have not provided the diagnostics for us to look there perhaps more information about your configuration would help.

5 minutes ago, itimpi said:

 

That might suggest a PSU overload issue when the server tries to spin up all drives simultaneously?  What PSU do you have? 

 

Since you have not provided the diagnostics for us to look there perhaps more information about your configuration would help.

 

You probably right, before booting up my PC I was using a couple of apps/dockers and it was fine, the moment those drives spun up and I got a crash.

I'll try another PSU and see if it does happen again...