Give W.D. a call, this sounds like a problem I have had in the past. Every now and then the drive manufactures will get there assembly line out of wack and they end up putting in to much lubricant, or not enough on the drive and you will get these same problems. Usually the manufacture can tell you what ser #'s to look for. I went through a time with Dell when they were using W.D.'s and we had to go through and replace over 100 drives from the same lot, and these were just the systems that I got the # range was in the thousands of drives. Not a nice thought to think about, but if you can get the resolution that I did then you get to save your data and replace the drives before the problem shows up at the end user level. Jeff
>>You haven't had the "Full Body Shudder"(tm) until you hear the >>"clank,clank,clank,etc..." a WD drive makes when it goes to find >>the never,never land.... >>(I can recognize a dying WD in the dark) > >Hey, that is exactly the sound it made when my WD died. I've always thought of WD as a quality HD but I'm starting to think otherwise. I've returned a significant number of them over the past six months. Heck in December, I returned 3 in the same week....all of them less than 6 months old at the time of failure. Their service was good and I did get replacements within a few days. The "clank clank clank" sure is unmistakeable though :) -- PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES! http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
