hdparm not being triggered with udev
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hdparm (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: hdparm
Since hdparm was switched from init.d to being triggered by udev it has stopped working on my machine.
Originally I thought it was the missing rule for /dev/sdx disks but even with that change (https:/
The bigger problem is I have no idea how to debug it, since nothing is outputted on boot in regards to it. I assume it is ran
during the initramfs stage? How should I check to see why it is not working?
my /etc/hdparm.conf has 4 lines like
/dev/disk/
spindown_time = 30
apm = 1
}
and the problem is that the disks are not spinning down. This used to work fine when hdparm was run from init.d
I also tried using /dev/sda1 etc in case the /by-uuid symlinks were not available at the stage udev is triggering hdparm, but it made no difference. However I need to reference the disks by uuid (or label) as they may not always be on the same device. I thought the problem might also be to do with the disks being set to power on in standby mode, however after a reboot when they are spun up, the problem still occurs.
Another issue related to this is that there is no easy way to test your hdparm.conf. Before you could manually run the init.d script but this is no longer possible. I think this is not ideal, as hdparm configs can be quite complex, and a missing space between keyword and value etc can cause problems.
tags: | added: patch |
Changed in hdparm (Ubuntu): | |
status: | New → Confirmed |
Updated to intrepid and the problem still remains. I have to use debians init.d script to get my hdparm settings working.
There is still no obvious way of testing the hdparm.conf either as you cannot do /etc/init.d/hdparm to see that is works fine.