You are not logged in.
Well hi folks, I have a bunch of ata/sata drives.
-M acoustic = not supported
-B APM_level = not supported
-k DIO_GET_KEEPSETTINGS failed: Inappropriate ioctl for device
If i apply -S 60 (5 min) it works out very well.
But any value higher than 120 won't spin down the drives at all.
Apparently i'd like to set 240 (20 min). 60 is too low.
I've tried hdparm -K 1 as well as smartctl -s off --offlineaouto=off --saveauto=on
With mounted partitions or not. With systemd oneshot unit or
the udev rule mentioned in the wiki. Fstab commit=600 or 1200.
Or should i apply these commands in any specific order?
On top of that, i have a feeling they used to work with -S 120.
But on a random basis. Totally arbitrary behaviour.
I use hddtemp /dev/sd? to check the state.
Still i can't pin point the reason why. At this point it seems incomprehensible to me.
Where should i look next?
Last edited by Xelvet (2014-05-16 12:46:37)
Offline
Now there's been some development. If i leave the freshly booted sys alone,
standby performs as expected, apparently.
I have some reasons to beleive all this mess caused by that mf Wine.
winecfg alone wakes up all standby storages immediately for no f reason.
i do use wine all the time for my charting platform.
but this doesn't explain why the hdd standby is being prevented.
Last edited by Xelvet (2014-06-05 19:52:03)
Offline