November 30, 20232 yr Hi Folks, I had a drive fail on my array recently. When I replaced it with another drive, I mistakenly set the FS to ZFS (the rest of the drives are XFS). I was not able to complete parity sync after that. I did eventually formatted the drive and set it to XFS but even doing that does not work anymore. Basically parity sync would run for hours but then eventually the array would be unresponsive and I'd be forced to reboot the server. Not sure what else to at this point. Diagnostics logs attached. nas-diagnostics-20231130-1010.zip
November 30, 20232 yr Author Not sure if these logs capture why the server crashed. It seems to have only captured the events post reboot. Am I doing something wrong? dreamnas-syslog-20231130-1457.zip dreamnas-syslog-20231130-2253.zip
November 30, 20232 yr You need to get the persistent log, if you can't find it enable the mirror to flash drive option, since it's the easiest, syslog will be in the flash drive /logs folder.
November 30, 20232 yr Solution Nov 30 16:20:52 DreamNAS kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Nov 30 16:20:52 DreamNAS 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.
December 2, 20232 yr Author Thanks @JorgeB my unRaid server has been stable for over 24 hours now after changing from Macvlan to IPvlan.
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.