Some of my comments regarding the issue from #568120.
It looks like the stuff from "/etc/init.d/hdparm" was moved into "/lib/udev/hdparm" and "/lib/hdparm/hdparm-functions". Which is fine, as /etc/hdparm.conf should still work.
The udev rule in "/lib/udev/rules.d/85-hdparm.rules" calls "/lib/udev/hdparm" when udev "add" event is triggered for new drives, which in turn should set spindown intervals or any other settings you specified in "/etc/hdparm.conf" for your drives.
If I run "sudo udevadm trigger", which triggers udev "add" events for all devices, the settings do get applied just fine.
However if I reboot, then the settings do not get applied during boot.
So it seems the functionality in the new scripts works as it should, its just that they are not triggered during boot.
I added some "echo" lines to "/lib/udev/hdparm" just to debug, and when I manually trigger "add" events, my debug logs are created. After reboot no debug logs are created.
So I am guessing that either the rules script does not get triggered during boot, or may be it is triggered to early, which causes it to fail (e.g. file system not mounted etc).
Some of my comments regarding the issue from #568120.
It looks like the stuff from "/etc/init. d/hdparm" was moved into "/lib/udev/hdparm" and "/lib/hdparm/ hdparm- functions" . Which is fine, as /etc/hdparm.conf should still work.
The udev rule in "/lib/udev/ rules.d/ 85-hdparm. rules" calls "/lib/udev/hdparm" when udev "add" event is triggered for new drives, which in turn should set spindown intervals or any other settings you specified in "/etc/hdparm.conf" for your drives.
If I run "sudo udevadm trigger", which triggers udev "add" events for all devices, the settings do get applied just fine.
However if I reboot, then the settings do not get applied during boot.
So it seems the functionality in the new scripts works as it should, its just that they are not triggered during boot.
I added some "echo" lines to "/lib/udev/hdparm" just to debug, and when I manually trigger "add" events, my debug logs are created. After reboot no debug logs are created.
So I am guessing that either the rules script does not get triggered during boot, or may be it is triggered to early, which causes it to fail (e.g. file system not mounted etc).