You are not logged in.
Pages: 1
Hello,
recently i have made a new clean uefi-installation.
Somehow now it is not possible to enable advanced power management features of my hdd's.
I know it for sure, without uefi it worked without issues.
So im asking you pro's out there again.
Output of hdparm -I /dev/sdb
/dev/sdb:
ATA device, with non-removable media
Model Number: WDC WD2500AAJS-00VTA0
Serial Number: WD-WMART0450844
Firmware Revision: 01.01B01
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: 488397168
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 238475 MBytes
device size with M = 1000*1000: 250059 MBytes (250 GB)
cache/buffer size = 8192 KBytes
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
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
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
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
* 64-bit World wide name
* Segmented DOWNLOAD_MICROCODE
* 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
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Read/Write Long (AC1), obsolete
* SCT Write Same (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
52min for SECURITY ERASE UNIT. 52min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50014ee0005c117b
NAA : 5
IEEE OUI : 0014ee
Unique ID : 0005c117b
Checksum: correctOutput of hdparm -B /dev/sdb
/dev/sdb:
APM_level = not supportedOutput of hdparm -B254 /dev/sdb
/dev/sdb:
setting Advanced Power Management level to 0xfe (254)
HDIO_DRIVE_CMD failed: Input/output error
APM_level = not supportedPS: sda = ssd root, sd[b,c] = hdd lvm, sdf = ssd lvm kvm, sd[g,h] = hdd lvm --> only hdd apm is required.
Thanks in advance
Last edited by Schlunze (2016-02-24 15:21:20)
Offline
Are you saying that if you boot in BIOS mode in the exact same computer, then advanced power management works? Are you really sure of this? Have you not upgraded changed anything else? Your claim appear unlikely as I don't think UEFI or BIOS is used for this (but I may be wrong). Could you try to boot your system back in BIOS mode to see (you can easily configure syslinux to boot in BIOS mode from a GPT partition, it is even easy that make a system that boot indifferently on BIOS or UEFI mode).
Last edited by olive (2016-02-23 20:44:10)
Offline
Hello olive,
unfortunately you are right, i have tryed booting a arch usb-key in bios mode and the same problem occurs. APM_level = not supported, i have absolutly no clue why and change the headline.
Maybe someone has a hint..
Thank in advance again.
Last edited by Schlunze (2016-02-24 15:02:42)
Offline
If you own a "green drive" that comes with built-in power saving features, you might also see "APM_level=not supported" here. In that case you can't set the APM_level manually, but you can still change the spin-down time by using e.g. "sudo hdparm -S180 /dev/sda" to spin down sda after 15 minutes.
I also googled your hard drive and it may have some built in power saving features, but can't be sure.
Did you try if hdparm -S works?
Offline
Hi OOO,
hdparm -y works, '-s' also.
TY maybe i messed something up.
Offline
Hey OOO,
i'm too stupid to follow your guide on howtoeverything.net!
Please explain me what needs to be done. hdparm -y standby works, is there a systemd service that reconizes disk i/o.
Output of hdparm -B /dev/sd?
/dev/sda:
APM_level = not supported
/dev/sdb:
APM_level = not supported
/dev/sdc:
APM_level = not supported
/dev/sdd:
APM_level = not supported
/dev/sde:
APM_level = not supported
/dev/sdf:
APM_level = off
/dev/sdg:
APM_level = not supported
/dev/sdh:
SG_IO: bad/missing sense data, sb[]: 70 00 02 00 00 00 00 0a 00 00 00 00 3a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
APM_level = not supportedi have absolutly no clue how to trigger hdparm -y /dev/somedriveinmyveryloudpccasebecauseofhddvibrationin2016.aaaaarrrrrrrrgggghhhh.net !
my 11-hd-parm-spindown.rules:
#/etc/udev/rules.d/11-hd-parm-spindown.rules
ACTION=="add|change", KERNEL=="sd[b-z]", ATTR{queue/rotational}=="1", RUN+="/usr/bin/hdparm -B255 -S241 /dev/$kernel"thanks
Last edited by Schlunze (2016-03-02 19:27:07)
Offline
My point was, that your drive may be one of those with internal power saving features which is why APM is not supported, as suggested by the article.
According to the article you should be able to use 'hdparm -S' to set the spindown timeout even if your disk is one with built-in power saving features.
I never suggested trying 'hdparm -s' which could be dangerous.
Your udev rule looks ok to me, maybe your disks are being accessed and don't spin down for that reason.
If your HDD's noise is the only reason you're looking into enabling APM, I'd rather look into mechanical solution to get rid of the noise, e.g. suspending the drive with bungee cord or placing it on top of a plastic foam block.
Offline
Pages: 1