TCB13 , 2 months ago (edited 2 months ago)

WD Red Plus drives go to standby (spindown) after 30 minutes of inactivity, without success. I read about WD not respecting hdparm commands, interpreting them differently and tried all suggestions, again without success. I even read about WD support saying they don’t support Linux.

This may appear to be the case, but it isn’t. I’ve tons of WD RED disks and they’re frankly one the best when it comes to power management. However you must be very carefully with the parameters you’re setting as they tend to require more than just setting the APM value.

Here’s an example from one of my drives from hdparm.conf:

<span style="color:#323232;">/dev/disk/by-uuid/xxxxxx {
</span><span style="color:#323232;">	apm = 127
</span><span style="color:#323232;">	spindown_time = 24
</span><span style="color:#323232;">}
</span>

Same thing on the CLI:

<span style="color:#323232;">hdparm -B 127 /dev/disk/by-uuid/xxxxxx
</span><span style="color:#323232;">hdparm -S 24 /dev/disk/by-uuid/xxxxxx
</span>

What one has to be aware to start is that -B on the cli equals apm on the config file and -S = spindown_time.

The interface of hdparm varies from the command line to the hdparm.conf file in multiple ways. Anyways the Arch Wiki has a table that makes your like easy: wiki.archlinux.org/title/hdparm#Power_management_…

Now the two important bits to be aware with WD:

-B/apm > Values from 1 to 127 permit spin-down, whereas values from 128 to 254 do not. A value of 255 completely disables the feature. -S/spindown_time > The value of 0 disables spindown, the values from 1 to 240 specify multiples of 5 seconds and values from 241 to 251 specify multiples of 30 minutes.

What I’ve noticed by querying the drives is that they usually come with apm=127 and spindown_time=0 or something like that. It becomes obvious that the drive will never spin-down and people tend to focus only on the apm value and forget about the other… or vice-versa and ever a drive to spin down.

Note: the apm (-B) value can be queried with hdparm -B /dev/disk/by-uuid/xxxx however the current values of spindown_time (-S) cannot be queried.

Tip: to apply changes made to hdparm.conf you can run udevadm trigger /dev/disk/by-uuid/xxxxxx or /usr/lib/pm-utils/power.d/95hdparm-apm resume.

Give a try to my example above (cli) and you’ll see the drive spinning down in a few minutes.