From: Tejun Heo <htejun@gmail.com>
To: Andrew Paprocki <andrew@ishiboo.com>
Cc: linux-ide@vger.kernel.org, Bruce Allen <ballen@gravity.phys.uwm.edu>
Subject: Re: smartd causing SATA timeouts on sleeping drives
Date: Sun, 07 Oct 2007 05:15:44 +0900 [thread overview]
Message-ID: <4707ECF0.9030800@gmail.com> (raw)
In-Reply-To: <76366b180710051838h11c63c38o9a4248309ff9ee7d@mail.gmail.com>
Andrew Paprocki wrote:
> Tejun/Bruce,
>
> I tracked down the source of timeouts I have been frequently getting.
> It appears smartd is not properly handling drives that are spun down
> by the BIOS ACPI settings. I have SATA timeouts which occur every half
> hour (the default -i 1800 in smartd) that do not occur when smartd is
> not running. The drives smartd is configured to look at have a sleep
> time configured in the BIOS. When the drives are asleep, I get a soft
> reset every half hour as smartd attempts to access the drives. While
> in this state, smartd also reports bad state to syslog (e.g.
> temperature changes to 200C). Just for comparison, hddtemp knows the
> drives are sleeping:
>
> # hddtemp /dev/sda
> /dev/sda: Hitachi HDS721010KLA330 : drive is sleeping
> # ls /storage
> ... wakes up the drives ...
> # hddtemp /dev/sda
> /dev/sda: Hitachi HDS721010KLA330 : 29 C or F
>
> I'm pasting the example cmd / timeout error / soft reset below. Also,
> I'm pasting the invalid settings which smartd detects when in this
> state. What needs to change for smartd to recognize drives are
> sleeping and either not perform its checks, or forcefully wake them up
> to perform them? (Should that be a configuration parameter in smartd?)
smartd should probably issue CHECK POWER MODE (0xe5) before issuing
other commands. Bruce?
Thanks.
--
tejun
next prev parent reply other threads:[~2007-10-06 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 1:38 smartd causing SATA timeouts on sleeping drives Andrew Paprocki
2007-10-06 20:15 ` Tejun Heo [this message]
2007-10-08 5:51 ` Andrew Paprocki
2007-10-08 6:06 ` Tejun Heo
2007-10-08 6:32 ` Andrew Paprocki
2007-10-10 19:39 ` Bruce Allen
2007-10-11 2:02 ` Tejun Heo
2007-10-11 2:46 ` Andrew Paprocki
2007-10-11 3:06 ` Tejun Heo
2007-10-11 4:00 ` Andrew Paprocki
2007-10-12 9:15 ` [smartmontools-devel] " Bruce Allen
2007-10-10 19:42 ` Bruce Allen
2007-10-10 19:46 ` Bruce Allen
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=4707ECF0.9030800@gmail.com \
--to=htejun@gmail.com \
--cc=andrew@ishiboo.com \
--cc=ballen@gravity.phys.uwm.edu \
--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).