September 30, 20232 yr Hello everyone, I've got a bit of a situation here. My unraid server's been acting up lately — freezes, crashes, you name it. I have to keep restarting it just to get things running smoothly again. I noticed my cache drive got set to read-only for some reason, and no matter what I do, I can't change it back to read-write. I backed up all the data and formatted the cache, thinking it might solve the crash problem, but the problem's still there. I've turned on syslog to gather some logs, and I'm also attaching the diagnostics output from my server. Anyone have any idea what's going on? syslog_unraid.zip unraid-diagnostics-20231001-0148.zip Edited October 1, 20232 yr by mmjaberi
October 1, 20232 yr Community Expert Solution Sep 30 05:09:29 unraid kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Sep 30 05:09:29 unraid kernel: ? _raw_spin_unlock+0x14/0x29 Sep 30 05:09:29 unraid 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)).
October 4, 20232 yr Author On 10/1/2023 at 1:18 PM, JorgeB said: 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)). I followed the steps you mentioned and it fixed the issue. Thanx 🤙
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.