so for about a year now i have been dealing with the frequent crashing of unraid. I figured I recently purchased a new faster server and installed unraid and started from scratch but the crashes continue and seem to be getting more frequent. 

 

I am running a dell R720 with dual E5-2690 0 @ 2.90GHz CPU's and 129gb of ram. Its running a Mellanox 3 10g card and also have a 1tb nmve cache drive on an adapter in one of the PCI slots and, running version Version 6.11.5 2022-11-20. I look at the log and I'm just lost on what exactly is going on.

 

This crashing was happening on my old server before i moved to a 10g card and before i hade the 1tb cache.

 

I have attached the sys log and any help would be appreciated. this went from a minor inconvenience i could deal with to the point of wanting to move away from Unraid. 

 

I have another unraid server set up at my moms house with the exact same configuration with the exception of the Mellanox card and it has not crashed at all which makes me think this is a card/driver issue.

syslog-.log

diags.zip

Edited December 30, 20223 yr by Keebler
added diagnostics

Dec  9 07:51:36 UnraidMedia kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Dec  9 07:51:36 UnraidMedia kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, upgrading to v6.10 or later and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right))

Thank you! I have made the changes and will let it run a couple days then report back and mark it solved. 

OK. I need further help. It just crashed this morning. Added the diagnostics file. 

 

thanks for the continued help

 

EDIT: After posting this i looked at upgrading the Firmware on my 10g nic. I went from version 2.33 to 2.42 which is the latest firmware since 2017. 

unraidmedia-diagnostics-20230102-0641.zip

Edited January 2, 20233 yr by Keebler

Enable the syslog server and post that after a crash.

syslog-192.168.1.39.log here is the sysy log, thanks for the help

Do you know the time it last crashed? Nothing obvious in the log.

I think it was around the 6am'ish time frame.

 

when it crashed in the past i had a screen connected to it or connected to it through iDRAC and the last line was something about kernal panic. I dont remember the specifics. I will have to hook a monitor up and get a screen shot of it.  this last time it lasted what, 3 and a half days i think from my first post.

1 hour ago, Keebler said:

I will have to hook a monitor up and get a screen shot of it.

Try that because unfortunately there's nothing relevant in the syslog.

Sorry for the late response on this. I have been laid up in the hospital having surgery. As of right now the server is going on 7 days without a crash. As soon as it does ill grab the screen shot.

OK I have been running now for 10 days without issue. I'm going to mark this resolved. If i crash again I will get a screen shot of the crash screen and open a new thread.

 

Thanks for the help