Earlier this week, i upgrade to 6.12.4, i had no issues before running 6.12.0.
twice this week the server has crashed. seems when the server is idle.
enabled sysloging after the 1st crash.  the common error im getting in the syslog file is 
vmalloc bug: 0xffffc9002116c000-0xffffc90021171000 overlaps with 0x1ae-0xffffffff82a11d00
Oct 28 00:37:15 KingUnRaid kernel: WARNING: CPU: 10 PID: 903 at mm/vmalloc.c:903 __purge_vmap_area_lazy+0x167/0x4f8
Oct 28 00:37:15 KingUnRaid kernel: 
 

may not be related but my server does not reliably boot/post either when the USB stick is plugged in. 
attached is syslog file and tshoot file. Running i5-12400 on MSI Z390-A Pro using intergrated graphics and 32GB memory. 
Considering taking the server offline tonight to run memtest. 
Also considering rolling back the update.

 

syslog-192.168.2.250.log kingunraid-diagnostics-20231028-1651.zip

Try disabling C-states on the board BIOS.

looking into this now.
When i posted the above piece, i decided to role back the update to 6.12.0
but i continue to have issues. just less often. Running MemTest now, its gotten a few passes over the last few hours with no issue. 
looking into the C-State piece now

 

Computer continues to crash. lots of issues with docker apps.
finally found where the c-state options was in my bios. just disabled that option. Hopefully this brings reliability back to the server without jacking up my power bill......
ive read alot of people suggesting moving to ipvlan instead of macvlan. tried switching, which made things worse. did some research on how to configure them. no luck. ... switched back to macvlan.
seriously considering abandoning my unraid build. i work in IT all day, Sucks having to work on your own pc repeatedly after supporting a business all day.

 

You can use macvlan but need to update to v6.12.4 and disable bridging, see the release notes.