David Kelly writes: > Whether or not Anthony understood it or not, can't say he was not > warned that something was amiss.
Anthony didn't need a warning, since he knew that something was amiss from the beginning ... else he'd have no reason to ask questions about it. What Anthony didn't and still doesn't know is whether or not it's an OS bug. Normally this sort of thing is likely to be an OS bug; however, if the messages occur only for one of two identical drives (as they appear to be at the moment), this tends to tip the balance in favor of a possible hardware problem on one drive. It's possible that a driver might have an unusual bug that causes it to treat one drive differently from another or creates unusual situations in which only one drive is affected, but such bugs are rare. Anthony is thus thinking of buying another identical drive and installing it to see if the problem goes away. If it doesn't, the balance will tip back strongly in favor of an OS bug. The drive passes all the self-tests, though, so nothing is certain. -- Anthony _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
