Unraid 6.11 has been crashing immediately after parity

[clay_statue]

So this is a repeatable error.  Within five minutes of parity completing (or being cancelled) unraid crashes itself.  Total shutdown.

I started mirroring syslog to flash and attached the file below.

Please help!  I cannot see what is causing the problem.  Should I downgrade back to 6.10?

fractaltower-diagnostics-20221114-1020.zip

[JorgeB]

4 minutes ago, clay_statue said:

I started mirroring syslog to flash and attached the file below.

It's not, just the regular diags.

[clay_statue]

Here's the syslog file and the last entries.  I deliberately cancelled the parity to see if it would crash, which it did a few minutes later.
 

Nov 14 10:26:12 FractalTower kernel: docker0: port 1(veth440e05a) entered disabled state
Nov 14 10:38:40 FractalTower kernel: docker0: port 1(vethb74e54b) entered blocking state
Nov 14 10:38:40 FractalTower kernel: docker0: port 1(vethb74e54b) entered disabled state
Nov 14 10:38:40 FractalTower kernel: device vethb74e54b entered promiscuous mode
Nov 14 10:38:40 FractalTower kernel: eth0: renamed from veth6b04af4
Nov 14 10:38:40 FractalTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb74e54b: link becomes ready
Nov 14 10:38:40 FractalTower kernel: docker0: port 1(vethb74e54b) entered blocking state
Nov 14 10:38:40 FractalTower kernel: docker0: port 1(vethb74e54b) entered forwarding state
Nov 14 10:40:38 FractalTower kernel: mdcmd (37): nocheck cancel
Nov 14 10:40:38 FractalTower kernel: md: recovery thread: exit status: -4
 

syslog.txt

[JorgeB]

Nothing relevant logged, and it looks more like a hardware problem, but go back to v6.10 to see if it still doesn't happen there.

[clay_statue]

5 hours ago, JorgeB said:

Nothing relevant logged, and it looks more like a hardware problem, but go back to v6.10 to see if it still doesn't happen there.

Was digging around and found this warning in the syslog from when it was booting...

ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block:

 

 

[JorgeB]

That looks harmless. 

[clay_statue]

I've restored previous version 6.9.x since that was what I upgraded from.  I'm going to hold steady here at this version for a minute and make sure everything is copacetic before venturing into 6.10.x.

Maybe 6.12.x will be released in the meanwhile and the bug will be contained to the previous version so i can leapfrog right over it.