\V/

Backstory: I have experienced multiple instances of two-disks failures over the summer due to the combo of heat wave and old drives. In one of those rebuilds, the recreated disks were totally corrupt due to bad parity. As some of the data were not backed up, this resulted in permanent data loss. How did this happen: Mover ran itself to schedule in emulated mode, even though there were two drives with errors. Feature request: Don't let mover run when array is in emulated mode OR when there are disk errors

Hi all, I am wondering if it is safe to put this in my go file so that Unraid will auto reboot when suffering from a kernel panic: echo 20 >/proc/sys/kernel/panic My server has been experiencing some occasional kernel panics since 6.9.2 (I suspect it's related to: 1, 2). I work long hours and hate coming home to a furnace when it does. Will the above quick fix work? Thanks