On 16 Sep 2005 07:29:29 -0700, "Random Person"
<nonexistent2032@yahoo.co.uk> wrote:
>Hi Kony. I know it sounds silly but I have a deadline looming next week
>and I have a lot of work to get done...I can certainly do without
>having to reinstall Linux, get all the libraries in again, get
>everything working, etc. If my drive is dying on me, fingers crossed it
>will die after next week. Everything is backed up already though.
That is exactly why you should not "piddle around" with it,
why you should just copy off data and replace it.
There is no need to reinstall Linux if the drive works well
enough to dupe it to another, but if it doesn't work that
well, you had to do it anyway.
The worst thing here could be trying to get more miles out
of a drive already demonstrating failure. Contact Maxtor
and have them do an advanced replacement. There is no
thought on your part about when an ideal time to do it would
be, that changes when the drive is finally failed if it
will. You were actually pretty lucky that it works at all,
still.
>
>Once the deadline passes I'll try to stress the HD to get any failures
>to show themselves.
>
>I was hoping for an independent diagnostic utility because I am getting
>the feeling that the current diagnostic utility is failing to detect
>errors.
it doesn't matter.
Literally, you do not need an independant diagnostic utility
and are just wasting time to look for one. Either the drive
is working fine or you're posting here about it... and need
to check the cables then if they're ok, replace it.
> Perhaps to reduce the number of RMAs? Not to point fingers at
>anyone in particular, but it is *never* good when a company decides to
>self-regulate (as is the case with all the companies in the HDD
>industry AFAIK).
How is it going ot reduce # of RMAs for a drive that's
failed to not show a failure code? Drive is still obviously
dead or malfunctional, and in such cases they still accept
it for warranty replacement if the warranty is still in
effect. Your argument cannot be valid because of this.
Come to think of it, the last one I had replaced, they
didn't even ask about failure code #s.