start a new full backup of everything on the array that included that drive while you go check that your existing full system backup exists and is viable.make immediate backups of any critical data not likely to already be backed up.Just buy it and move on.Īnother reason to “ok” a drive is that, until you have the hardware on hand to replace the Bad drive it costs basically nothing to rebuild the array onto the bad drive, and if another drive fails before you can replace the bad one you have a chance of living on. Why go through the pain? Chances are, the drive you need is pretty cheap. I've never been in a situation where it was worth letting a drive fail. Double this value to account (naively) for opportunity cost.How much of your time would be lost if this server died?.How much time would be lost for its users if this server died?.So you could run a full suite of SMART scans, find none, and know no more than you do now.īut, assuming this was an out-of-the-blue failure and not an I-did-something-funny-and-it-failed failure, you already have an indication of problems with the disk. Fully 36% of the failed drives had no SMART errors, fatal or not. Google's infamous paper found that SMART was only useful in that if it alerted, the drives were more likely to fail than if it didn't. The thing is, it's really hard to predict hard drive failures. Some of these are reparable failures, some aren't. Maybe their firmware has a bug that breaks under.
Maybe cosmic rays hit your drive at the right angle and time to fail a scan.
Drives can be marked as failed in an array for many reasons.
0 kommentar(er)
