From: "Mark Weber" <crash@treysoft.com>
To: "Bart Samwel" <bart@samwel.tk>
Cc: "Mark Lord" <lkml@rtr.ca>, linux-kernel@vger.kernel.org
Subject: Re: hdparm standby timeout not working for WD raptors?
Date: Sun, 14 Oct 2007 15:30:57 -0500 [thread overview]
Message-ID: <71b295590710141330g7a4779e5q2d6b8f50387ee971@mail.gmail.com> (raw)
In-Reply-To: <47120D65.3080008@samwel.tk>
On 10/14/07, Bart Samwel <bart@samwel.tk> wrote:
>
> Some things to check:
>
> * Run "hdparm -I" on your drive. In the "Capabilities" section there is
> a line "Standby timer values", for some drives this mentions a device
> specific minimum. I know some drives that ignore any setting below 60
> seconds.
>
> * I also know of quite a number of drives where hdparm -B settings
> override the -S settings, even if you set the -S settings after the
> hdparm -B settings. You could try combinations with various values of
> hdparm -B, especially 1 and 255.
Thanks for the suggestions.
The -I command prints out a bunch of stuff including:
Standby timer values: spec'd by Standard, with device specific minimum
I tried setting -B to 1 and and then set -S to 5 minutes.
Also, -B 255 and then set -S to 5 minutes.
No luck with either. These drives want to keep running.
One thing of possible interest: The -B command printed
the following message:
/dev/sda:
setting Advanced Power Management level to 0x01 (1)
HDIO_DRIVE_CMD failed: Input/output error
I would guess that the first line came out just before
hdparm tried to do the set, and the second line indicates
that the set failed.
Perhaps -S is failing too, just without the diagnostic?
All of the above using 2.6.22-gentoo-r5
I have not yet tried 2.6.23 as suggested by Mark Lord.
---
"And he puzzled three hours, `till his puzzler was sore."
from "How the Grinch Stole Christmas"
next prev parent reply other threads:[~2007-10-14 20:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 17:11 Mark Weber
2007-10-11 19:37 ` Mark Lord
2007-10-12 5:07 ` Mark Weber
2007-10-12 13:30 ` Mark Lord
2007-10-12 22:19 ` Mark Weber
2007-10-13 12:46 ` Mark Lord
2007-10-14 12:36 ` Bart Samwel
2007-10-14 20:30 ` Mark Weber [this message]
2007-10-14 21:05 ` Bart Samwel
2007-10-14 22:05 ` Mark Weber
2007-10-14 23:40 ` Mark Lord
2007-10-15 0:02 ` Mark Weber
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=71b295590710141330g7a4779e5q2d6b8f50387ee971@mail.gmail.com \
--to=crash@treysoft.com \
--cc=bart@samwel.tk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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
all inboxes | Powered by JetHome®