How can SATA power management feature be controlled?
Peter van Hooft
peter.van.hooft at gmail.com
Sun May 2 08:16:46 UTC 2010
>> Hi,
>>
>> I use both:
>> hdparm -q -S 0 /dev/sda
>> hdparm -q -B 255 /dev/sda
>> which seems to work.
>
> On what make and model of drive? I know that works on my other drives,
> but the WD10EADS doesn't support whatever ATA command "hdparm -B" uses.
> Here:
>
> # hdparm -B 255 /dev/sda
>
> /dev/sda:
> setting Advanced Power Management level to disabled
> HDIO_DRIVE_CMD failed: Input/output error
> HDIO_DRIVE_CMD(identify) failed: Input/output error
> # hdparm -B /dev/sda
>
> /dev/sda:
> APM_level = not supported
>
> The drive does claim to support "Power Management feature set". See
> below:
>
> # hdparm -I /dev/sda
>
> /dev/sda:
>
> ATA device, with non-removable media
> Model Number: WDC WD10EADS-65M2B0
> Serial Number: WD-WCAV53157295
> Firmware Revision: 01.00A01
> Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5,
> SATA Rev 2.6
> Standards:
> Supported: 8 7 6 5
> Likely used: 8
> Configuration:
> Logical max current
> cylinders 16383 16383
> heads 16 16
> sectors/track 63 63
> --
> CHS current addressable sectors: 16514064
> LBA user addressable sectors: 268435455
> LBA48 user addressable sectors: 1953525168
> Logical/Physical Sector size: 512 bytes
> device size with M = 1024*1024: 953869 MBytes
> device size with M = 1000*1000: 1000204 MBytes (1000 GB)
> cache/buffer size = unknown
> Capabilities:
> LBA, IORDY(can be disabled)
> Queue depth: 32
> Standby timer values: spec'd by Standard, with device specific minimum
> R/W multiple sector transfer: Max = 16 Current = 16
> Recommended acoustic management value: 128, current value: 254
> DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
> Cycle time: min=120ns recommended=120ns
> PIO: pio0 pio1 pio2 pio3 pio4
> Cycle time: no flow control=120ns IORDY flow control=120ns
> Commands/features:
> Enabled Supported:
> * SMART feature set
> * Power Management feature set
> * Write cache
> * Look-ahead
> * WRITE_BUFFER command
> * READ_BUFFER command
> * NOP cmd
> * DOWNLOAD_MICROCODE
> Power-Up In Standby feature set
> * SET_FEATURES required to spinup after power up
> * Automatic Acoustic Management feature set
> * 48-bit Address feature set
> * Device Configuration Overlay feature set
> * Mandatory FLUSH_CACHE
> * FLUSH_CACHE_EXT
> * SMART error logging
> * SMART self-test
> * General Purpose Logging feature set
> * 64-bit World wide name
> * WRITE_UNCORRECTABLE_EXT command
> * {READ,WRITE}_DMA_EXT_GPL commands
> * Segmented DOWNLOAD_MICROCODE
> * Gen1 signaling speed (1.5Gb/s)
> * Gen2 signaling speed (3.0Gb/s)
> * Native Command Queueing (NCQ)
> * Phy event counters
> * NCQ priority information
> * DMA Setup Auto-Activate optimization
> Device-initiated interface power management
> * Software settings preservation
> * SMART Command Transport (SCT) feature set
> * SCT Long Sector Access (AC1)
> * SCT LBA Segment Access (AC2)
> * SCT Error Recovery Control (AC3)
> * SCT Features Control (AC4)
> * SCT Data Tables (AC5)
> unknown 206[12] (vendor specific)
> unknown 206[13] (vendor specific)
> Logical Unit WWN Device Identifier: 50014ee203885dba
> NAA : 5
> IEEE OUI : 0014ee
> Unique ID : 203885dba
> Checksum: correct
Well, my disk claims to support 'Advanced Power Management:
/dev/sda:
ATA device, with non-removable media
Model Number: WDC WD3200BJKT-00F4T0
Serial Number: WD-WX30AC9E6538
Firmware Revision: 11.01A11
Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5
Standards:
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 625142448
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 305245 MBytes
device size with M = 1000*1000: 320072 MBytes (320 GB)
cache/buffer size = 16384 KBytes
Nominal Media Rotation Rate: 7200
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 8
Advanced power management level: disabled
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
Advanced Power Management feature set
SET_MAX security extension
* Automatic Acoustic Management feature set
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* IDLE_IMMEDIATE with UNLOAD
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* Free-fall Control feature set
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
* Phy event counters
* DMA Setup Auto-Activate optimization
Device-initiated interface power management
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
unknown 206[12] (vendor specific)
unknown 206[13] (vendor specific)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
supported: enhanced erase
80min for SECURITY ERASE UNIT. 80min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50014ee2ae89294c
NAA : 5
IEEE OUI : 0014ee
Unique ID : 2ae89294c
Checksum: correctLoad_Cycle_Count
What is also interesting is that when I upgraded the BIOS of my Dell
Latitude D630 yesterday, the Load_Cycle_Count
started to grow again. So, it looks like that the BIOS you are
running also affects how much you can
limit Load_Cycle_Count.
peter
More information about the users
mailing list