From: Wes Janzen <superchkn@sbcglobal.net>
To: linux-kernel@vger.kernel.org
Subject: Re: IDE DMA problem with 2.6.0-test1
Date: Fri, 08 Aug 2003 05:27:32 -0500 [thread overview]
Message-ID: <3F337B14.2000307@sbcglobal.net> (raw)
In-Reply-To: <Pine.SOL.4.30.0308072019250.3600-100000@mion.elka.pw.edu.pl>
I don't know, I've had a few SMART capable Maxtor drives go bad to the
point I knew it without a warning. Eventually, when things got really
bad though, they would report SMART errors. The errors were at first
intermittent, and then got to the point the warning wouldn't go away.
In their defense, two of them (I've had 5) had smart errors and I never
encountered any noticeable defects (still, I replaced them when they
were doing the upgrade program so I could get a new 3 year warranty).
All of those are several generations old though, the newer ones I have
now don't seem to want to die ;-)
--Wes--
Bartlomiej Zolnierkiewicz wrote:
>Can be buggy drive's firmware or bug in smartmontools (unlikely)...
>
>--bartlomiej
>
>On Thu, 7 Aug 2003, Mike Castle wrote:
>
>
>
>>In article <Pine.SOL.4.30.0308061750260.22000-100000@mion.elka.pw.edu.pl>,
>>Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl> wrote:
>>
>>
>>>You can also install smartmontools (http://smartmontools.sf.net/)
>>>and check your drives (if they support SMART of course).
>>>
>>>
>>Point of interest: I just had a Maxtor drive go bad on me recently. Their
>>diag tools caught it, as did my ear (made a nice clunking noise :-). But
>>SMART didn't report a thing, and I looked hard too. :-/
>>
>>mrc
>>
>>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
prev parent reply other threads:[~2003-08-08 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 11:00 IDE DMA problem with 2.6.0-test1 Nick Sanders
2003-08-06 14:07 ` Bartlomiej Zolnierkiewicz
2003-08-06 14:51 ` Nick Sanders
2003-08-06 15:53 ` Bartlomiej Zolnierkiewicz
2003-08-07 17:41 ` Mike Castle
2003-08-07 18:20 ` Bartlomiej Zolnierkiewicz
2003-08-08 10:27 ` Wes Janzen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F337B14.2000307@sbcglobal.net \
--to=superchkn@sbcglobal.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.