From: Nicolas STRANSKY <Nico@stransky.cx>
To: linux-ide@vger.kernel.org
Subject: Re: libata-tj and SMART
Date: Tue, 16 May 2006 10:36:59 +0200 [thread overview]
Message-ID: <e4c2vb$6rj$1@sea.gmane.org> (raw)
In-Reply-To: <4469893A.10901@gmail.com>
Le 05/16/2006 10:11 AM, Tejun Heo a écrit :
> Hmmm.. That measn SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE command fails.
> But weirdly it fails with DRQ (ready for data) bit set, thus triggering
> HSM violation. My guess is the drive doesn't support that command and
> when it aborts, it sends funky status. I think you can safely ignore
> the error or remove -S on from smartd configuration.
Automatic Offline is also failing (-o on):
Error SMART Enable Automatic Offline failed: I/O error
Smartctl: SMART Enable Automatic Offline Failed.
Maybe it's not supported but there was no problem leaving these options
in the past. Anyway removing -o on -S on makes smartd happy.
> If you've got some time though, I'd like to see what's really going on.
> Can you modify #undef ATA_DEBUT to #define ATA_DEBUG in
> include/linux/libata.h and post the kernel messages after issuing above
> command? Be warned that it will produce a LOT of messages while booting
> if you're using SATA disks for your system, and it can considerably slow
> down booting.
OK.
--
Nico
Quand le doigt montre la lune, l'imbécile regarde le doigt.
-+- Confucius -+-
next prev parent reply other threads:[~2006-05-16 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 22:41 libata-tj and SMART Nicolas STRANSKY
2006-05-15 23:13 ` Tejun Heo
2006-05-16 7:44 ` Nicolas STRANSKY
2006-05-16 8:11 ` Tejun Heo
2006-05-16 8:36 ` Nicolas STRANSKY [this message]
2006-05-17 21:15 ` Nicolas STRANSKY
2006-05-18 4:00 ` Tejun Heo
2006-05-18 15:54 ` Jeff Garzik
2006-05-19 3:43 ` [PATCH 1/1] libata: Fix the HSM error_mask mapping (was: Re: libata-tj and SMART) Albert Lee
2006-05-19 5:22 ` [PATCH 1/1] libata: Fix the HSM error_mask mapping Albert Lee
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='e4c2vb$6rj$1@sea.gmane.org' \
--to=nico@stransky.cx \
--cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).