\V/ Posted September 12, 2022 Share Posted September 12, 2022 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 Quote Link to comment
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.