The attachment "hdparm.patch" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, f
I fixed this by using this patch
(https://launchpadlibrarian.net/73763550/hdparm-functions.patch) that
translates (unlinks) HDD path symlink inside /etc/hdparm.conf to
/dev/sdX
but I also had to create this patch to the /lib/udev/hdparm, because I had to:
1) convert (readlink) DEVNAME input parame
hdparm.conf is still ignored in Xenial, as hard as that is to believe!
** Tags added: trusty xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595138
Title:
Settings in /etc/hdparm.conf are not
in 14.04.4 HDs spin down after resume but not after boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595138
Title:
Settings in /etc/hdparm.conf are not applied during boot
To manage notification
HDs not spinning down in 14.04.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595138
Title:
Settings in /etc/hdparm.conf are not applied during boot
To manage notifications about this bug go to:
h
Sorry, but I found this thread because I was searching for the reasons
for my HDs not spinning down in Xubuntu 13.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595138
Title:
Settings in /etc/hdp
I have just updated to server edition 12.04 (because I imagine 14.04
will be along soon) and notice that the problem with not reading
settings from /etc/hdparm.conf is still there. I guess whatever was
done in 13.04 was not backported to the LTS version.
Shame, that's what I thought LTS was for.
I did some research and it turned out my issue is a device specific bug
for certain Western Digital drives. I have posted a bug report and a
work around under pm-tools: https://bugs.launchpad.net/ubuntu/+source
/pm-utils/+bug/1225169
--
You received this bug notification because you are a member
I can confirm that in 13.04 settings from /etc/hdparm.conf are indeed
applied on boot from S5 state.
However settings are still not applied when booting from S3 or S4 state.
I am wondering if I need to create a new bug report for this
behaviour...
--
You received this bug notification because yo
Reading again the first posts from this thread, seems I made a mistake
posting my comment here.
Maxim Tikhonov could get udev to trigger /lib/udev/hdparm manually, but
not during boot sequence.
My problem was actually that of bug #222458 : a bug in hdparm-functions
that prevented it to "recognize
It appears to be fixed in 13.04. Apply the patch above.
Aside: You don't actually need to "patch". You can just edit the
/lib/hdparm/hdparm-functions file. It's a 7 line change. Find the line
that says DISC=$KEY and wrap it in an "if"
https://launchpadlibrarian.net/73763550/hdparm-functions.patc
Problem detected on Ubuntu Studio x64 12.10 and reproduced under Studio
x64 10.10 (both OSes running on same machine - two different hard
drives).
Slightly the same situation as jdblair above (need to disable write cache on a
disk at boot/resume time), except two differences :
- classic hard
I can confirm that the contents of /etc/hdparm.conf are not affecting
the drive settings in 12.04.1 LTS.
For performance reasons I need to turn off the write-cache for my SSD.
I set the correct setting in /etc/hdparm.conf, but the write-cache is
still on when I boot. Further, when I manually turn
still exists in 12.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595138
Title:
Settings in /etc/hdparm.conf are not applied during boot
To manage notifications about this bug go to:
https://bugs
Can confirm bug still exists in Ubuntu 12.04.1 LTS, spindown_time in
hdparm.conf is not respected.
I can spin down drives from command line using hdparm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Branch linked: lp:ubuntu/precise-proposed/hdparm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595138
Title:
Settings in /etc/hdparm.conf are not applied during boot
To manage notifications abou
Thanks Oscar.
I just tried apm = 255, 254, 128, 127, 1 and it made no difference.
At boot time the disks are not spun down as defined in hdparm.conf, but I can
do so from the command line
I also found this bug which says the man page is wrong:
https://bugs.launchpad.net/ubuntu/+source/hdparm/+b
On 29-6-2012 10:57 AM, Antonino Catinello wrote:
> Are you guys sure that it is a problem with hdparm and not with the apm
> configuration?
>
> Have you tried to enable it in hdparm.conf?
>
> apm = 255
>
also look at the B parameter of the disks with hdparm.
manpage:
-B Get/set Advanced Powe
Are you guys sure that it is a problem with hdparm and not with the apm
configuration?
Have you tried to enable it in hdparm.conf?
apm = 255
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595138
Titl
Thanks Bob for pointing me to this bug! On 2011-10-16 I filed a
duplicate of this bug: https://bugs.launchpad.net/bugs/875719. Apologise
for that. Here's a summary of my observation:
hdparm -S worked with 10.10. But with 11.04 my external hard disk
(Seagate) connected via eSATA ExpressCard on a Th
Hdparm.conf is not being respected in my new install of 12.04 server.
bug 875719 seems to be a duplicate, with 3 sufferers including me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595138
Title:
"This isn't exactly the right place to say it, but hdparm should be
extended to provide more ways of specifying devices in hdparm.conf other
than the /dev path, so disk label, disk serial number, physical path,
etc., could be used."
Try the patch from
https://bugs.launchpad.net/ubuntu/+source/hdpa
Apologies, the problem is not present in Precise, and hdparm is working
fine. (smartd was spinning up my disk.)
I suggest this bug be closed.
This isn't exactly the right place to say it, but hdparm should be
extended to provide more ways of specifying devices in hdparm.conf other
than the /dev p
Problem is still present in 12.04 Beta 2.
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595138
Title:
Settings in /etc/hdparm.conf are not applied during boot
To manage noti
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: hdparm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595138
Title:
Sett
I've noticed that the timeouts set with hdparm -S from the command line
are not respected (still running 10.04 LTS) but I can use hdparm -Y just
fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595
The problem is not in your configuration file.
Use a workaround posted above.
I think this is fixed in later version - 10.10 and above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595138
Title:
I'm running 10.04 LTS server edition, and this is affecting me. I can spin
down by hand with
hdparm -y /dev/sd{a,b,c,d}
but the contents of /etc/hdparm.conf appear to be ignored at boot time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
why has this issue not been resolved in 10.04 and only 10.10 i have
programs that only run on 10.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595138
Title:
Settings in /etc/hdparm.conf are not a
btw I meant clean install of 10.10
--
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
ubuntu-bugs@lists.ubuntu.c
I just installed Ubuntu Server 10.10 on a new machine last week. Changed
/etc/hdparam.conf and it seems to take effect (drives did spin down).
So did someone fix this?
I haven't tried my other installs of Kubuntu, Mythbuntu yet, so I can't
comment.
--
Settings in /etc/hdparm.conf are not applie
Yes definitly a bug - just discovered it by accident ...
The idea to use udev for this is quite nice, but has a design flaw. by
definition this is doomed to failure IMHO. At the time of add sd?
execute something which needs filesystem access on possibly the same
drive (right before mount) - not su
can only agree with above posters. My workaround was to revert back to
9.10. Still I agree it would be nice if this gets sorted properly. It
does not help users to post bugs if it seems like nothing gets done with
it.
--
Settings in /etc/hdparm.conf are not applied during boot
https://bugs.launch
+1 to post above, I can't understand why this won't be addressed or even
why not many users notice this fault.
I could attempt fixing if somebody pointed me in the right direction
(since I currently don't have time to learn the inner workings of the
whole hdparm+udev universe), but for the time be
Any chance someone can look into this issue, it's been going on for
months now and I'd really like my raid array disks to spin down please.
It's kind of basic fundamental functionality...even windows can do it
correctlyIt’s these kinds of problems that really let Linux down,
and it’s a real sha
I think I used that longer workaround, because "udevadm trigger" causes
add events to be called for all devices. My workaround only sets
settings for hard drives.
I didn't want to call "udevadm trigger" because I didn't want to spend
time investigating if it would affect anything else in the syste
Adding "udevadm trigger" to /etc/rc.local spins down my harddisks. Thanks for
pointing that out.
It does make me wonder why you chose a more complex workaround in #2.
--
Settings in /etc/hdparm.conf are not applied during boot
https://bugs.launchpad.net/bugs/595138
You received this bug notifica
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
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
39 matches
Mail list logo
