Hi,

i am trying to disagnose what is causing my unraid to keep restarting after a parity check. i have got the syslog. Attached.

Not sure how to read it.

Thanks

syslog

Edited June 16, 20233 yr by fernandes999

This is usually hardware related and there's nothing relevant logged, but also don't even see a parity check starting in the posted log.

36 minutes ago, fernandes999 said:

i am trying to disagnose what is causing my unraid to keep restarting after a parity check

Not sure if you are talking about  crash followed by it restarting or if it seems to do a tidy shutdown followed by a reboot?   Are you getting an unclean shutdown message after restarting?  If a crash I would think the most likely culprit is power as that would be when the system is normally driving the PSU the hardest.

 

You could try setting up the syslog server a get a log that survives a reboot to see if that gives any clue.  Also the full diagnostics zip file rather than just the syslog file you posted is better.

 

On 6/16/2023 at 10:35 AM, itimpi said:

Not sure if you are talking about  crash followed by it restarting or if it seems to do a tidy shutdown followed by a reboot?   Are you getting an unclean shutdown message after restarting?  If a crash I would think the most likely culprit is power as that would be when the system is normally driving the PSU the hardest.

 

You could try setting up the syslog server a get a log that survives a reboot to see if that gives any clue.  Also the full diagnostics zip file rather than just the syslog file you posted is better.

 

this is what happenes -

• server restarts 
• I start parity 
• it crashes or restarts (this is where the problem is and try to get bottom why its happening)
• cycle starts again withe me in parity start screen.

I dont get unclean shutdown message after it restarts

 

I can't seem to get the syslog server (Kiwi Syslog server) working on a pc i use. Instead i have got unraid to mirror log to unraid flash usb.

i have added a few diagnostics. (All were found in the Unraid flash usb)

syslog tower-diagnostics-20230617-0931.zip tower-diagnostics-20230617-1720.zip

I'm still not seeing a single parity check starting in the log, I do see a different issue though, please try updating to v6.12.0 and post new diags after array start, then try to start a parity check.

48 minutes ago, JorgeB said:

I'm still not seeing a single parity check starting in the log, I do see a different issue though, please try updating to v6.12.0 and post new diags after array start, then try to start a parity check.

i have updated v6.12.0

attached is the diagnostics after i have started the array

tower-diagnostics-20230617-2127.zip

if i got in the IPMI in my motherboard.

i see the following.

Everything looks normal in the syslog so far, did you try starting a parity check?

11 hours ago, JorgeB said:

Everything looks normal in the syslog so far, did you try starting a parity check?

i have started a parity check.

Will keep you posted - est time - 1day 3hours for parity check.

tower-diagnostics-20230618-2208.zip

The server had a crash - but the log didnt capture  anthing in the logs not sure why.

This is my IPMI showing a run-time critical stop

 

I was looking at other forums and thought it was realated to this - and i updated to IPVLAN but same crash

 

tower-diagnostics-20230620-0043.zip syslog

Edited June 20, 20233 yr by fernandes999

I found a log that was kept in the shares. Maybe this will help on identifying the issue.

is there a way i can learn to decipher the log? @JorgeB

syslog-192.168.99.XX.log

Jun 19 15:35:23 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Jun 19 15:35:23 Tower kernel: ? _raw_spin_unlock+0x14/0x29
Jun 19 15:35:23 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

Change to ipvlan.