I recently upgraded from version 6.9.2
But all versions I've tried has been crashing after array startup
Some versions (like 6.11.5) the array was able to start (sporadically) but then would crash during Parity Checks

I've had to downgrade to 6.9.2 to get back to an operational state.
 

Here's what i've tried so far:

- Booted into Safe Mode (no plugins), made no difference
- Fixed all Common Issues reported
- Removed old plugins
- Upgraded all plugins to latest version
- Looked at logs to see if anything stood out that might be causing a kernal panic (couldn't find anything meaningful
- Messed around with c-state and acpi settings in bios (no difference)

What might I be missing in order to figure out what's causing the issue?

Thanks
S

Post the syslog after a crash, enable the syslog server if you cannot get the normal one.

Hey @JorgeB

I've captured and attached the latest syslog
It's still crashing upon array startup

syslog

Since you're running a Threadripper, have you tried look at this post

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-819173

 

Thanks for the reply @Squid

 

yes I've double checked those settings. I've even toggled C-State to see if it would make a difference, no luck.

Here's the latest syslog after most recent reboot and crash

 

syslog

Unfortunately there's nothing relevant that I can seen, some data corruption detected by btrfs, but that doesn't explain the symptoms.

So I've downgraded back to 6.9.2 for now
Array did start, however interestingly, I've been doing a ping test to the server every time i start the array to see if it goes down.

It seems even with 6.9.2 the interface goes offline for a moment but comes back up.
I don't know if it's related, but is it possible that my network cards or net config is what's causing the crashes --- and i didn't notice because it recovers with 6.9.2 but not the later versions?

 

Here's a screenshot of the ping test as the array was starting --- and i've included the latest syslog as well (weird)

 

syslog

Is the server still responsive on the local monitor/keyboard during that time?

@JorgeB no, with versions > than 6.9.2 when it crash, if's inaccessible even on the local terminal (frozen).

Then it's not just a network problem, but without anything in the logs difficult to guess what, maybe some incompatibility with the newer kernel.