++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

This bug was originally as 
https://bugzilla.redhat.com/show_bug.cgi?id=1270838

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Description of problem:
After setting the APM level of my hard disk to 255 by means of gnomedisk-utility, the APM level is actually set to 255 as verifified by means of executing 'hdparm -B /dev/sda'. However, after suspend and resume, the APM level is set to 128 as verified by executing 'hdparm -B /dev/sda' again.

Version-Release number of selected component (if applicable):
udisks2-2.1.6-1.fc23

How reproducible:
Always.

Steps to Reproduce:
1. Set APM level to 255.
2. Suspend and resume.
3. Run 'hdparm -B /dev/sda'.

Actual results:
The APM level is 128.

Expected results:
The APM level is 255.

Additional info:
- The hard disk is a Hitachi HTS723216L9SA60 installed in a Lenovo ThinkPad T400.
- Moreover, after resume from suspend, gnome-disk-utility erroneously reports the target value 255 instead of the real value 128.
- It seems that udisk2 needs to provide systemd support with a script in /usr/lib/systemd/system-sleep/ similar to the following which resets the APM level to 254 after resume from suspend:

--
#!/bin/sh
[ "$1" = "post" ] && exec /usr/sbin/hdparm -B 255 /dev/sda
exit 0
--