@ Pjotr
Just found this and tried it. It makes no difference. Thanks anyway.
I am now running 12.04LTS, and the problem is unsolved.
I suspect this bug should be marked as a duplicate of Bug 595138 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
@Bob Harvey:
Maybe the syntax of your script is wrong: a missing space.
Your script is:
/dev/sda{
This should be:
/dev/sda {
Does adding the space help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I'm running 10.04 LTS server (no gui front end) and the contents of
hdparm.conf are ignored.
I can put the disks to sleep with hdparm -y without problems. But the
attached hdparm.conf never causes a spindown.
** Attachment added: "my hdparm.conf file that does nothing"
https://bugs.launchpad
@ cmcginty:
For testing purposes you can use this command in the terminal (use copy/paste):
sudo hdparm -B 254 /dev/sda
Press Enter. Type your password when required; this will remain entirely
invisible, not even dots will show, this is normal.
Then press Enter again.
As Jan Claeys already desc
How do you test the hdparm.conf settings? In other words, is there a way
to execute the udev rules from the command line?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/568120
Title:
[Lucid] hdparm.c
will choosing a lower apm value do anything? like.. 126/2 = 63 ?
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
The solution Jan Claeys wrote on post #21 works very well.
Thank you vary much guy! :)
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
[Correction for the record: Re my comments 44-46 previously. I am using
hdparm 9.27-2 and "-y" is spinning the drive down as expected. I'm not
sure why this was not the case when I tested previously.]
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You rec
The bug I am reporting fits the original description in this bug but not
the recently updated one. I apologize for not noticing that. Moving
this laptop-mode-tools bug into bug 513706 and undoing status change.
** Changed in: hdparm (Ubuntu)
Status: In Progress => Fix Released
--
[Lucid
THE BUG IS:
The file /usr/lib/pm-utils/power.d/95hdparm-apm owned by package
"hdparm" version 9.15-1ubuntu9 in lucid (32-bit) checks for presence of
laptop-mode-tools at the wrong location on the disk, then proceeds to
manage the APM setting for the hard drive itself when laptop-mode-tools
should
The files are not in these locations anymore, yet pm-utils still has
this in it's hdparm config:
if [ -e /usr/sbin/laptop_mode ] ; then
LMT_CONTROL_HD_POWERMGMT=$(. /etc/laptop-mode/laptop-mode.conf && ec
if [ "$LMT_CONTROL_HD_POWERMGMT" != 0 ] \
&& [
How can you say a fix was released?
My notebook's hard drive is still getting hundreds(!) of load cycles a
day, whether plugged in or not, because it's not at 255. The old way to
change it (in the old laptop-mode-related hdparm config files) didn't
fix this. hdparm.conf AFAIK is not executed on
Ok I created a separate bug for spindown issue #595138.
https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/595138
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Maxim,
> My findings are in comment #38, and a temp workaround in comment #40,
> but I don't know how to fix the actual issue properly.
That issue is also unrelated to the original bug reported here. Please
file a separate bug report if /lib/udev/hdparm is not being executed on
boot.
--
[Lucid
my hdparm.conf just in case
cat /etc/hdparm.conf
# 60/240 (5min/20min)
/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
Steve,
The problem is kind of related because previously init.d script used to
set the spindown interval during boot. After init.d script was removed,
the spindown interval is not being set during boot, which causes hard
drives to always spin.
However on the other hand side, it is different, beca
Oscar,
The original bug report only talks about use of the command_line block,
which is obsolete. You don't provide a copy of your hdparm.conf
anywhere in the bug history, so I don't know what problem you're having;
but it probably is not related.
--
[Lucid] hdparm.conf change doesn't have effe
@ steve:
What about the issue seen with spinning down disks also declared in
/etc/hdparm.conf, they're not classed in the command_line section, but I
cannot seem to spin down my disks when idle the way it is running with
ubuntu server 9.10, when I upgraded it to lucid, and when that not
worked ins
This bug was fixed in the package hdparm - 9.27-2ubuntu2
---
hdparm (9.27-2ubuntu2) maverick; urgency=low
* debian/hdparm.conf, debian/hdparm.conf.5: drop 'command_line' example
from the default hdparm.conf since it's no longer supported, and update
the manpage to match. LP
The 'command_line' feature of hdparm.conf is no longer supported and
there is no plan to reintroduce support for it. If you want to run an
hdparm command unconditionally on boot, you can add an init script or an
upstart job to your system; there's no reason this should be in a config
file like hdp
** Branch linked: lp:ubuntu/hdparm
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
I have been avoiding using my notebook for weeks now waiting on a fix.
I've changed laptop-mode.conf to 254 even on battery (and then
rebooted), and the age-old ubuntu problem of 100+ load cycles an hour
(until a fix is found) is still occurring. You are causing damage to
people's machines by not
Installed attached hdparm. -y still does not spin the drive down as it
did in Karmic :(
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Saw solution in comment 21 but missed details of patch in comment 20.
Thanks to pjotr12345.
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
I used to use hdparm -y /dev/sdb in Karmic to manually put a backup
drive into standby mode. This no longer works in Lucid, which is a pity.
I love these regression bugs. Examining the status of the drive with
hdparm -C /dev/sdb in Karmic after -y would show the drive in standby.
In Lucid, it shows
The solution of comment #21 works to me too, but when i shutdown the Ubuntu, i
got a big sound CLACK! in hd...
Anyone has any other solution for this?
My laptop: HP Compaq Presario CQ40-713BR
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received t
For now I use the following workaround to set the APM values after
resuming from Suspend-To-RAM. I created
/etc/pm/sleep.d/99_load_cycle_count_fix and made it executable and the
inserted the following script:
#!/bin/bash
case "$1" in
hibernate|suspend)
echo "nothing to do"
That's a nice workaround Maxim. I have reverted my server back to 9.10
as I wanted it to be working the way it was supposed to be. So I will
wait until this gets fixed before I will update the server to 10.04
again.
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs
I hope it gets sorted also. And I am happy I noticed this as this is
quite a sneaky bug / behaviour change. I have a 4 disk raid 5 array in a
server, and I only started looking into disk spindown because I was
suspicious of getting more SMART temperature warnings after upgrading to
10.04.
In any c
@Maxim,
Thanks for shining some light on this. Hopefully this gets sorted.
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I am just posting my findings after a couple of days snooping around. I
have removed the Debian package that I previously installed and I am
using Ubuntu hdparm package that comes with 10.04.
Just to clarify I am only concerned with disks not spinning down after
upgrade to 10.04, as I have AC powe
@Jan Claeys: Sorry for the misunderstanding, I'm using Ubuntu's built-in
function to suspend my notebook (= System -> Power Off -> Suspend in the
main menu; I don't know the exact english menu descriptions because I'm
using german as the system's main language), not the program s2ram or
sth else. I
Telling people to use the "newer hdparm from Debian" doesn't help fixing
this issue. Using the same package version of hdparm from Debian as is
in Ubuntu will work too, as nothing got fixed in the newer version, and
the fact that it works is only because Debian still uses a legacy
method. What we
OscarMuntenaar, I have the same issue. I think it is related to this bug
also. So far installing the package from Debian Squeeze and then doing
"/etc/init.d/hdparm restart", helps. But when I reboot the HDs still do
not spindown. I need to manually run "/etc/init.d/hdparm restart".
--
[Lucid] hdp
I've experienced the same with not being able to spin down idle disks.
Maybe this is a separate issue of hdparm / udev?
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
ok tried updating to the newer version of hdparm (hdparm_9.27-2_amd64)
this seems to work ok and the hdparm.conf is used during boot
hdparm -S24 /dev/sda this sets the drive standby time to 2 mins
i use sudo hdparm -C /dev/sda after 2-3 minutes but always returns
drive state is: active/idle
t
I just checked again and the solution definitively doesn't work on my
Asus F3JA.
Before suspending/standby (s2ram):
$ sudo hdparm -I /dev/sda | grep "Advanced power management level"
Advanced power management level: 254
After waking up:
$ sudo hdparm -I /dev/sda | grep "Advanced power man
I don't confirm. After suspend (standby) i checked hdparm -B value, and
it was unchanged. I checked load cycle count in 5 min and it didn't
increase.
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a membe
Correction: the solution does NOT work after waking up from standby. The
harddisk's load cyle count then still dramatically increases. Please
confirm.
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a memb
Yes, I confirm that the solution works on my toshiba NB200 netbook.
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
The solution in comment #21 works fine here, too.
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
** Description changed:
- In 10.04, changing /etc/hdparm.conf has no effect. I used to tame the hard
disk of my netbook in 9.10 by adding the following lines to /etc/hdparm.conf,
in order to stop the constant clicking:
+ 'hdparm' doesn't come with an init script anymore, and the udev script
+ d
I reverted the bug status to confirmed, as I'm not sure if this is
intended behaviour, it might be a bug in the udev script. I'd like
someone from the ubuntu foundations team to comment on this (either its
a bug in the udev script, or it's a bug in the manpage and other
documentation).
** Changed
Oh, I'd like to add: if you know any "how-to" or "guide" which
recommends to use the 'command_line' section, please inform them about
this and ask them to change this ASAP. The device-name sections that
work with udev also work with older Ubuntu versions (I'm not sure up to
which version?) so it s
Okay, so basically the "problem" is that there is no 'hdparm' init
script in Ubuntu anymore, and hdparm settings are set by an udev script.
The udev script doesn't use the "command_line { ... }" section of
hdparm.conf, so what's in there never gets executed.
Using udev for this makes more sense ac
@Jan
I to can comfirm your solution did the trick, replaced the lines in
hdparm.conf and rebooted, clicking is gone!!!
Thx
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which i
@ Jan: your solution seems to work.
I downgraded hdparm to the official Ubuntu version and added the lines
you mentioned, to hdparm.conf (after removing the old lines which I had
added, see the message with which I started this topic). Then I
rebooted.
The results of nearly two hours testing are
Thanks for intervening, Jan! I'll try your suggestion.
For the benefit of others: you can easily downgrade from the Debian
package to the official Ubuntu package, as follows:
System - Administration - Synaptic Package Management
Search for hdparm and click on the installed Debian package (9.27-
@Pjotr (and others)
Can you please try the following configuration in hdparm.conf with the hdparm
package from Ubuntu 10.04 (not the one from Debian!):
/dev/sda {
apm = 255
apm_battery = 254
}
Feel free to replace the values as you wish (e.g. some people might want
to use "apm = 254").
As said, the current hdparm version (9.27-2) in Debian Testing (Squeeze)
fixes the problem. Therefore I've attached a compressed file which
contains both the 32-bit version and the 64-bit version of hdparm
9.27-2. Simply double-click the .deb file and it'll install itself
automatically. Then reboot
after several restarts, the new hdparm is still working fine. No problems
anymore.
indeed, now its up to the developers to get this in place in the updates.
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are
Good stuff Pjotr!
Any developer here that can look into getting this in place in the
updates?
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
Marking it as confirmed again: a long test on my netbook shows that this
workaround works fine for me. For others as well, it seems. The
conclusion must be, that hdparm in Lucid is flawed and can easily be
replaced by the newer hdparm currently in Debian Squeeze.
I'm not a developer, so I can't ge
Let's hope it's gonna come as an update soon then :)
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
It works for me!!
Nice work pjotr!
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
The software repositories of Debian Squeeze hold a newer version of
hdparm. This newer version seems to have a positive effect on my
netbook. It installs fine in Ubuntu 10.04. Please help with testing!
You can get this newer version here:
32 bit: http://packages.debian.org/squeeze/i386/hdparm
64 b
I've also tried the laptop mode tools. Somehow this seemed to spindown the
disks while MD had not flushed its writes to the disks, or it did something
else so I ended up with 4 disks and no array. After some crash recovery I
managed to get a degraded array back with 3 out of the 4 disks.
I got t
Unfortunately, I just discovered that altering /etc/apm/event.d/20hdparm
doesn't work after all Please ignore my previous two messages in
this thread.
** Changed in: hdparm (Ubuntu)
Status: Incomplete => Confirmed
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpa
I've probably found the solution, but I need testers...
It seems that hdparm.conf isn't called anymore, because hdparm itself
isn't called during boot. So what you can do is forget about hdparm.conf
altogether, and alter the configuration file 20hdparm instead, which is
located in /etc/apm/event.d
How about when switching power mode? I.e. going from powered to battery,
or from battery to powered. Does /etc/hdparm.conf have any influence
here? Is it even supposed to?
I solved my problem by installing laptop-mode-tools and used that to set
my hdparm settings.
--
[Lucid] hdparm.conf change d
The the terminal command itself works fine, as usual. It's only the
automation of that command during boot, that has no effect. This would
suggest that hdparm itself is allright, and that the bug is in the boot
process
Anyway, I would very much like a reaction from the developers in this
threa
This bug is very sneaky in that way that i totally neglected is untill i
read a thread on the ubuntu forums about it and noticed my laptop HD was
doing it all the time while running on the battery.
Since it's killing my hard disk and i sometimes forget to manually input
the line in terminal i hope
Me too. /dev/sda {option, ...} blocks have no effect. Setting hdparm -B
... in /etc/rc.local doesn't do it neither. Unchecking "Park harddisk"
in the Gnome energy settings is being ignored as well. Only sudo hdparm
in terminal after login works. Was no problem in 9.10. Effect on two
note-/netbooks
Sorry my bad, there is no fix yet and status is still 'confirmed'.
I was interested in the different kinds of status. I didnt expect i was able to
change the status. Sorry.
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification
** Changed in: hdparm (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: hdparm (Ubuntu)
Status: Fix Released => Confirmed
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of
** Changed in: hdparm (Ubuntu)
Status: New => Confirmed
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
@pjotr12345, just clicked on the button, thanks for the tip.
It looks like it is hdparm, as all I did at first was an update of 9.10.
All software running on the server was updated nicely and no extra
services have been added in the proces. It could also be driver related
that the sata drivers do
@ Oscar: you can still help by clicking on "This bug affects me" in the
upper left corner of this bug report. If you wish to be kept informed
about new developments concerning this bug, you can subscribe to it
(upper right corner of this bug report).
I'm not sure whether the bug is hdparm related
No harddisk spindown anymore in 10.04
I have build my own nas box around an atom board, and in it I have 4 1.5
Tbyte disks. When I build it I had low power in mind, so the operating
system sits on a 2.5 disk that runs 24/7, and the disks that hold the
array spin down when not needed.
Two days ago
Hello, I have same problem.
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
https://wiki.ubuntu.com/Bug
71 matches
Mail list logo
