From: Jim Paris <jim@jtan.com>
To: Tejun Heo <htejun@gmail.com>
Cc: "Tvrtko A. Ursulin" <tvrtko@ursulin.net>,
"Erik Inge Bolsø" <knan-ide@anduin.net>,
linux-ide@vger.kernel.org
Subject: Re: [RESOLVED] Re: libata errors with smartctl on 2.6.24, WD3200AAKS and nVidia AHCI
Date: Wed, 14 May 2008 15:36:48 -0400 [thread overview]
Message-ID: <20080514193648.GA10651@jim.sh> (raw)
In-Reply-To: <482AA37C.1020604@gmail.com>
Tejun Heo wrote:
> Tvrtko A. Ursulin wrote:
>> On Wednesday 14 May 2008 08:58:56 Erik Inge Bolsø wrote:
>>> The drive does say
>>>
>>> Enabled Supported:
>>> SMART feature set
>>> Security Mode feature set
>>> * Power Management feature set
>>> * Write cache
>>> * Look-ahead
>>>
>>> ... so doesn't look like SMART is enabled on the drive.
>>>
>>> Does the problem go away if you do a
>>>
>>> smartctl -s on /dev/sda
>>>
>>> first? :)
>> Indeed it does, shame on me for overseeing that small detail. :)
>
> Oh... shame on me too. :-)
Why didn't smartctl notice that? In my experience it usually does
report when SMART is disabled. Is the error not being properly
reported back to userspace maybe? Tvrtko's original problem report
has lots of uninitialized (or leaked?) data, and a lot of it looks
like ASCII (for example his bogus RAW_VALUEs contain pieces of the
model number).
-jim
next prev parent reply other threads:[~2008-05-14 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 7:58 libata errors with smartctl on 2.6.24, WD3200AAKS and nVidia AHCI Erik Inge Bolsø
2008-05-14 8:05 ` [RESOLVED] " Tvrtko A. Ursulin
2008-05-14 8:31 ` Tejun Heo
2008-05-14 19:36 ` Jim Paris [this message]
2008-05-15 3:44 ` Tejun Heo
2008-05-15 5:28 ` Bruce Allen
2008-05-15 7:21 ` Tvrtko A. Ursulin
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=20080514193648.GA10651@jim.sh \
--to=jim@jtan.com \
--cc=htejun@gmail.com \
--cc=knan-ide@anduin.net \
--cc=linux-ide@vger.kernel.org \
--cc=tvrtko@ursulin.net \
/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.