linux-kernel - Re: hdparm standby timeout not working for WD raptors?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 14 Oct 2007 23:05:43 +0200
From:	Bart Samwel <bart@...wel.tk>
To:	crash@...ysoft.com
CC:	Mark Lord <lkml@....ca>, linux-kernel@...r.kernel.org
Subject: Re: hdparm standby timeout not working for WD raptors?

Mark Weber wrote:
> On 10/14/07, Bart Samwel <bart@...wel.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

Ahhh. Spec'd by standard means that each -S unit is worth 5 seconds (for 
values up to 240 = 20 minutes), and the second part means that there is 
a minimum (which is not specified in this report, unfortunately). 
Perhaps you can get a hold of the full drive manual, the exact minimum 
value is probably specified there.

> 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.

Just to be sure: you did use -S 60 to get 5 minutes, right?

> 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.

Yes, that seems correct. Nothing too weird there: it simply seems that 
the drive doesn't support the power management knob. (AFAIK you should 
be able to confirm this using the feature sets listed in the output of 
hdparm -I.)

> Perhaps -S is failing too, just without the diagnostic?

Perhaps, but I'd expect it to print a diagnostic if it fails. I do seem 
to remember that (at least for some drives that I've seen) there isn't a 
diagnostic if you go below the device specific minimum, the value is 
simply ignored.

Cheers,
Bart
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/