On 10/14/07, Mark Lord <[EMAIL PROTECTED]> wrote:
> 1. How are you forcing the drives into standby?
hdparm -y
> 2. Have you reproduced this with a stock kernel.org kernel yet?
No; maybe later this week.
> One possibility is that these drives may be the kind that
> generate a "spurious" inte
On 10/14/07, Bart Samwel <[EMAIL PROTECTED]> wrote:
>
> Just to be sure: you did use -S 60 to get 5 minutes, right?
Yes. And hdparm is kind enough to print:
/dev/sda:
setting standby to 60 (5 minutes)
Here's a bizarre sequence which I just noticed:
[extraneous blank lines removed for clarity]
On 10/14/07, Bart Samwel <[EMAIL PROTECTED]> 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
>
On 10/12/07, Mark Lord <[EMAIL PROTECTED]> wrote:
>
> That's interesting.
>
> So, either something is regularly accessing/polling the drive,
> or it just doesn't work with the standby timer.
>
> Are there any interesting kernel messages being generated
> during execution of those commands?
No mess
On 10/11/07, Mark Lord <[EMAIL PROTECTED]> wrote:
>
> What do you get when you try this:
> hdparm -S1 -C /dev/sda;sleep 6; hdparm -C /dev/sda
> ??
Thanks for taking an interest.
I ran the commands and got the result shown
below. Anything else you want me to try?
# hdparm -S1 -C /dev/sda; sleep
I can't get "hdparm -S" to work at all.
Using "hdparm -S 1" should set the timeout to
5 seconds, but the drives stay active/idle all the
time. When I set to standby manually, the drives
stay on standby for days, and start up fine when
they are used. I know this because I logged status
every 30 m
6 matches
Mail list logo
