July 11, 20232 yr Hi ! My unraid server freezes about every two days (randomly), I can't access web interface, shares or dockers. It won't power down then when I press the physical power button, so I have to shut the power down to power it again. I recently changed motherboard/cpu/ram/ssds, memtest runs all night without error. I mirrored syslog to flash, last time it froze, latest entry was an array spin down (2 HDDs). This morning it seems last entry was dynamix cache dirs plugin execution (I disabled it now). Any help appreciated. Thanks !! tower-diagnostics-20230711-0814.zip Edited July 11, 20232 yr by AmokK forgot details
July 11, 20232 yr Community Expert You didn't post the persistent syslog but if there's nothing logged there it usually points to a hardware problem.
July 11, 20232 yr Community Expert Yes, there's nothing just before the crash but there are these: Jul 8 22:00:13 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Jul 8 22:00:13 Tower kernel: ? _raw_spin_unlock+0x14/0x29 Jul 8 22:00:13 Tower 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, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
July 11, 20232 yr Author Ok ! I don't know the difference between macvlan and ipvlan, but I will try this, that's something ! Thanks for your insight
July 11, 20232 yr Author Switched to ipvlan for a few hours, froze again. Last syslog entries : Jul 11 15:25:02 Tower emhttpd: read SMART /dev/sdc Jul 11 15:27:23 Tower kernel: mdcmd (47): set md_write_method 1 Jul 11 15:27:23 Tower kernel: Jul 11 15:40:12 Tower emhttpd: spinning down /dev/sdc Jul 11 15:42:23 Tower kernel: mdcmd (48): set md_write_method 0 Jul 11 15:42:23 Tower kernel:
July 11, 20232 yr Community Expert Having nothing relevant logged before the crash usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
July 11, 20232 yr Author Ok, that's a start, it will be long and painful, but at least I could pinpoint the problem, thanks for your help !
July 25, 20232 yr Author I don't know if it's really the solution, but I switched my cache pool (two NVMe SSDs) from ZFS to btrfs, and it's been rock solid for a week, and going on !
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.