Disable mover schedule when array is faulted to prevent data corruption

[\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