Hi all,

 

I recently migrated to new hardware. I had a dell r720xd with a md1200 expansion bay and moved over to a Dell t640.

 

About a month after the migration, I began experiencing random crashes about every 20 hours or so. I am on Unraid version 6.12.4. I have updated my plugins and switched the Docker network type from macvlan and ipvlan. Neither change has worked.

 

Running dell lifecycle hardware diagnostics did not indicate any hardware issues.

 

I have a couple syslog dumps and a diagnostic zip attached below. If anyone has any recommendations on where I should look next, I appreciate any help I can get.

 

Thanks!

diagnostics.zip 11_11_syslog.txt 11_14_syslog 11_19_syslog

Nov 18 08:12:32 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Nov 18 08:12:32 Tower kernel: ? _raw_spin_unlock+0x14/0x29
Nov 18 08:12:32 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

Thank you for the response. I had changed the settings from macvlan to ipvlan after the most recent log posted, but had two crashes after that as well (with no syslogs saved). I have renabled writing logs to the flash drive and will post a update if the crashing continues.

Attached is a syslog of the system after a crash that occurred today. Docker network type has remained as ipvlan for this period.

syslog

Dec  3 03:30:01 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Dec  3 03:30:01 Tower kernel: ? _raw_spin_unlock+0x14/0x29
Dec  3 03:30:01 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

 

You are still getting macvlan call traces, did you reboot after changing to ipvlan? If yes post the output of

 

docker network ls

 

Thankful I saw this message thread. I have been dealing with macvlan traces for 2 weeks now and finally had some time to get logs situated and written to a share. Found this, this morning:

Dec  4 09:05:32 stratus kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]
Dec  4 09:05:32 stratus kernel: process_one_work+0x1ab/0x295
Dec  4 09:05:32 stratus kernel: worker_thread+0x18b/0x244

 

Crashed right after.

 

I just switched to ipvlan moments ago, but I did NOT reboot until I just saw this thread. Hope this works now!

17 hours ago, JorgeB said:

 

You are still getting macvlan call traces, did you reboot after changing to ipvlan? If yes post the output of

 

I did switch to ipvlan on the docker page, but it looks like br0 is set to macvlan. I only have my pihole docker instance running on that network. Can I change br0 from macvlan to ipvlan directly?

 

 

NETWORK ID     NAME           DRIVER    SCOPE
655545584bd0   arrs           bridge    local
ff632669d8c0   br0            macvlan   local
7481b7a4d678   bridge         bridge    local
a6f3acc276be   host           host      local
ee864e579b17   mgmt_stuff     bridge    local
239340eb6ecc   none           null      local
96810df6f3c2   odoo-network   bridge    local

 

3 hours ago, birdsofprey02 said:

Thankful I saw this message thread. I have been dealing with macvlan traces for 2 weeks now and finally had some time to get logs situated and written to a share. Found this, this morning:

Dec  4 09:05:32 stratus kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]
Dec  4 09:05:32 stratus kernel: process_one_work+0x1ab/0x295
Dec  4 09:05:32 stratus kernel: worker_thread+0x18b/0x244

 

Crashed right after.

 

I just switched to ipvlan moments ago, but I did NOT reboot until I just saw this thread. Hope this works now!

 

Glad my mistake helped you out!

4 hours ago, Til20 said:

I did switch to ipvlan on the docker page, but it looks like br0 is set to macvlan. 

Did you reboot after the change?

I did not. I had assumed the system crashing and the rebooting would include that change, as it showed as ipvlan in the docker settings on the webui. I did a planned restart this morning and the br0 network has changed from macvlan to ipvlan successfully. 

 

Thanks for correcting me on this. I will continue to keep an eye on the system. I am hoping that this is the fix.