As a temporary workaround for disk spindown I added the following to
"/etc/rc.local".

# workaround for hdparm disk spindown in 10.04
(echo "\n$(date)" && for devname in $(cat /etc/hdparm.conf | grep -o 
"/dev/sd[a-z]"); do export DEVNAME="$devname" && (/lib/udev/hdparm || true); 
done) >> /var/log/hdparm_fix.log

This looks into "/etc/hdparm.conf", gets all "sd*" device names and then
runs "/lib/udev/hdparm" script in the same way the
"/lib/udev/rules.d/85-hdparm.rules" rule does. This helps to set the
settings I have in "/etc/hdparm.conf" during boot. For new devices
plugged into the system after boot, the standard rule should work just
fine. In case if anybody uses it, check the "/var/log/hdparm_fix.log"
after boot to make sure it set the settings you have in your config.

** Description changed:

  Binary package hint: hdparm
  
  After upgrade to Lucid the hard drives never spindown. The hdparm
  spindown settings (and most likely others) in /etc/hdparm.conf are not
  being applied during boot.
  
  This seems to have happened after removing the init.d script.
  
+ 
  lsb_release -rd
  Description:    Ubuntu 10.04 LTS
  Release:        10.04
  
+ 
  apt-cache policy hdparm
  hdparm:
-   Installed: 9.15-1ubuntu9
-   Candidate: 9.15-1ubuntu9
-   Version table:
-  *** 9.15-1ubuntu9 0
-         500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
-         100 /var/lib/dpkg/status
+   Installed: 9.15-1ubuntu9
+   Candidate: 9.15-1ubuntu9
+   Version table:
+  *** 9.15-1ubuntu9 0
+         500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
+         100 /var/lib/dpkg/status
+ 
+ 
+ cat /etc/hdparm.conf
+ /dev/sda {
+     spindown_time = 240
+ }
+ /dev/sdb {
+     spindown_time = 240
+ }
+ /dev/sdc {
+     spindown_time = 240
+ }
+ /dev/sdd {
+     spindown_time = 240
+ }
+ /dev/sde {
+     spindown_time = 240
+ }
+ /dev/sdf {
+     spindown_time = 240
+ }
+ /dev/sdg {
+     spindown_time = 240
+ }

-- 
Settings in /etc/hdparm.conf are not applied during boot
https://bugs.launchpad.net/bugs/595138
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to