[Bug 199094] Re: hdparm.conf settings (other than apm) are lost on suspend/resume?

[Rafał Ochmański]

I'm affected by this bug. After suspend APM_level is reset to 254

# hdparm -B /dev/sda
/dev/sda:
 APM_level	= 254

Settings in /etc/hdparm.conf are ignored

command_line {
        hdparm -S 12 -B 48 /dev/sda
}

Even a workaround with /etc/pm/sleep.d/20_resume

#!/bin/sh
case "${1}" in
 resume|thaw)
  killall ssh
  hdparm -S 12 -B 48 /dev/sda
  ;;
esac

somehow doesn't work. I need to manually run hdparm after every suspend.

** Changed in: hdparm (Ubuntu)
       Status: Incomplete => Confirmed

** Changed in: pm-utils (Ubuntu)
       Status: Expired => Confirmed

** Tags added: quantal

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to hdparm in Ubuntu.
https://bugs.launchpad.net/bugs/199094

Title:
  hdparm.conf settings (other than apm) are lost on suspend/resume?

Status in “hdparm” package in Ubuntu:
  Confirmed
Status in “pm-utils” package in Ubuntu:
  Confirmed

Bug description:
  Update: This is on Intrepid.

  Problem:
  - Hard disks lose settings (the APM level for example) when they are powered off.
  => Settings in /etc/hdparm.conf persist only from boot to next suspend.

  Expected:
  All settings in /etc/hdparm.conf should persist across {suspend,hibernate}/resume.

  Effects:
  At least the apm setting in hdparm.conf is lost. This makes https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695 so bad - users are not able to set the apm value without messing with their system (installing stuff from forums) because of this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/199094/+subscriptions