From: Greg Stark <gsstark@mit.edu>
To: Mark Lord <liml@rtr.ca>
Cc: Greg Stark <gsstark@mit.edu>, Jeff Garzik <jgarzik@pobox.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: [SATA] libata-dev queue updated
Date: 07 Jun 2005 09:51:23 -0400 [thread overview]
Message-ID: <87is0qi8bo.fsf@stark.xeocode.com> (raw)
In-Reply-To: <42A6AE3E.7070401@rtr.ca>
Mark Lord <liml@rtr.ca> writes:
> Greg Stark wrote:
> > Uh, this is 2.6.12-rc4 with the latest libata-dev patch from Garzik's web
> > site:
> > bash-3.00$ smartctl -data -a /dev/sda
> > smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
> > Home page is http://smartmontools.sourceforge.net/
> > Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)
>
> Oh, wait a sec -- Jeff just posted that he's nuked the "read identity" ioctl(),
> so I suppose that has now broken smartmontools compatibility.
I think this libata-dev patch was prior to that announcement.
It's 2.6.11-bk6-libata-dev1.patch which I appear to have downloaded May 15th.
(Sorry I guess "latest" wasn't very precise)
> So Linux either goes without S.M.A.R.T. for SATA (again),
> or Jeff puts it back, or smartmontools gets upgraded Real Soon Now.
:(
What I really want to get working is actually hddtemp which uses SMART just to
get the temperature:
bash-3.00$ hddtemp /dev/hda
/dev/hda: MAXTOR 6L080J4: 50 C
bash-3.00$ hddtemp /dev/sda
/dev/sda: Maxtor 7Y250M0 YAR5: drive is sleeping
bash-3.00$ hddtemp /dev/sdb
/dev/sdb: Maxtor 6Y120M0 YAR5: drive is sleeping
The two M0 drives are SATA drives and they certainly are not sleeping. Come to
think of it that's awfully hot for the PATA drive. I think I'll put it to
sleep for a while.
--
greg
next prev parent reply other threads:[~2005-06-07 13:51 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 6:08 [SATA] libata-dev queue updated Jeff Garzik
2005-06-04 15:17 ` Greg Stark
2005-06-04 17:48 ` Jeff Garzik
2005-06-04 18:50 ` Adrian Bunk
2005-06-04 19:05 ` Jeff Garzik
2005-06-04 19:15 ` Greg Stark
2005-06-04 19:19 ` Jeff Garzik
2005-06-05 2:25 ` Greg Stark
2005-06-05 2:30 ` Jeff Garzik
2005-06-05 5:30 ` Greg Stark
2005-06-22 16:15 ` Mark Lord
2005-06-22 20:23 ` Jeff Garzik
2005-06-23 3:39 ` Mark Lord
2005-06-05 2:40 ` Drew Winstel
2005-06-05 2:58 ` Jim Crilly
2005-06-06 16:01 ` Mark Lord
2005-06-07 1:57 ` Greg Stark
2005-06-07 11:20 ` Brad Campbell
2005-06-08 8:33 ` Mark Lord
2005-06-07 13:15 ` Brad Campbell
2005-06-08 8:37 ` Mark Lord
2005-06-07 13:51 ` Greg Stark [this message]
2005-06-08 10:30 ` Mark Lord
2005-06-08 8:51 ` Mark Lord
2005-06-07 17:53 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 7:00 Bene Martin
2005-03-10 5:40 Jeff Garzik
2005-03-29 9:12 ` kern.petr
2005-03-08 11:20 Jeff Garzik
2005-03-02 2:40 Jeff Garzik
2005-02-19 8:40 Jeff Garzik
2005-02-19 16:58 ` Andre Tomt
2005-02-19 17:09 ` Jeff Garzik
2005-02-13 20:33 Jeff Garzik
2004-10-30 16:15 Jeff Garzik
2004-10-27 6:52 Jeff Garzik
2004-10-27 6:53 ` Jeff Garzik
2004-10-27 22:53 ` Rob van Nieuwkerk
2004-10-27 23:03 ` Jeff Garzik
2004-10-18 23:52 Jeff Garzik
2004-10-16 0:44 Jeff Garzik
2004-10-15 8:04 Jeff Garzik
2004-10-15 17:15 ` Jeff Garzik
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=87is0qi8bo.fsf@stark.xeocode.com \
--to=gsstark@mit.edu \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--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 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).