Standby timeout setting ignored after system suspend/resume

[Graeme Hewson]

If a standby timeout setting is applied in Drive Settings, this works fine at first when the setting is made, and after the system is rebooted. However, if the system is suspended and resumed, the timeout setting is ignored and the disk continues to spin.

Using Ubuntu 15.10, gnome-disk-utility 3.16.2.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Graeme Hewson (ghewson)]

See also https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/199094/comments/29

[groby (groby)]

Hi Mr. Hewson,
thanks for your fast response!
I'm a programmer-dummy, so I have to ask first, if I understand the instruction of your link correctly:

1. Because I don't have the folder "system-sleep", I have to create it
2. In that folder I put the script
3. In the script, I have to write "suspend", "hibernate" or "hybrid-sleep", behind the "$2" characters. (In my case it must be "suspend")
4. I have to make the script executable.

Is that also working for reboot and boot? Because the problem affects reboot and boot too.

Thanks and regards!

[groby (groby)]

Subsequent correction: Reboot and Boot works for me as well as said in the Bug Description.
Sorry for making confusion!

But please still check my procedure of creating the script.

Thanks!

[Graeme Hewson (ghewson)]

1. Yes, if /lib/systemd/system-sleep/ doesn't exist, create it with mkdir.
2. Yes.
3. No, unless for some reason you want to limit the script to suspend only, or something. Here's my script:

#!/bin/sh

case $1/$2 in
  pre/*)
    ;;
  post/*)
    hdparm -B 254 -S 120 /dev/sdb
    ;;
esac

4. Yes, with chmod u+x <filename>.

[groby (groby)]

Works for me! Just had to change the target device in the script.
It's not really fixing the Gnome-Disk-Utility Bug, I guess. But the script keeps my harddrive on 254 APM-Level after suspend/resume.
Thanks again!