dealing with a failing drive
modulok at gmail.com
Sat Nov 10 21:09:57 PST 2007
>> I'd welcome suggestions on how (or whether) to try to revive a SCSI
drive that's failing.
It depends on how valuable the data on the array is, and more
importantly, how much funding you have at your disposal to fix the
problem. If it were me, I would set aside the bad disk, connect a new
disk to the card and re-synchronize the array. (Assuming one of the
members still retains a good copy of the data.) Afterwards I would
destroy, or toss the existing disk in the trash can (depending on the
sensitivity of the data stored on it.)
>> Is there some other way to:
>> b)monitor the health of disks on a Compaq controller so it doesn't
get to this point to begin with?
There are various tools out there that attempt to 'monitor' the
condition of disk drives to try and predict when failure is eminent.
For valuable data, it is safer to setup a mirror and simply toss out
bad disks as they fail. For extremely valuable data use a 3 disk
array. With a 3 disk setup you will still be covered in the event that
an additional disk craps out during the re-sync.
To quote google's article on disk failure, regarding SMART:
"...we find that failure prediction models based on SMART parameters
alone are likely to be severely limited in the prediction accuracy,
given that a large fraction of our failed drives have shown on SMART
error signals whatsoever. This result suggests that SMART models are
more useful in predicting trends for large aggregate populations that
for individual components."
My 2 cents.
On 11/10/07, David Newman <dnewman at networktest.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> I'd welcome suggestions on how (or whether) to try to revive a SCSI
> drive that's failing.
> This is on FreeBSD 6.2-RELENG on a Compaq Proliant DL320, onboard RAID
> and two SCSI drives in a RAID1 array.
> Today this system rebooted and hung on Compaq's "what do you want the
> RAID controller to do?" message. I told it to fix any errors.
> When I brought the system back up (after running fsck in single-user
> mode), the log had lots of errors like this:
> Nov 10 09:00:40 mail kernel: ida0: hard write error
> Nov 10 09:00:40 mail kernel: ida0: invalid request
> Nov 10 09:01:48 mail last message repeated 35 times
> Nov 10 09:03:49 mail last message repeated 571 times
> Nov 10 09:12:27 mail last message repeated 796 times
> I vaguely remember trying about a year ago to load a SMART utility from
> the ports collection but it wouldn't work on drives in a RAID array.
> Is there some other way to:
> a) diagnose/fix the errant disk here?
> b) monitor the health of disks on a Compaq controller so it doesn't get
> to this point to begin with?
> thanks in advance
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Darwin)
> -----END PGP SIGNATURE-----
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions