*** This bug is a duplicate of bug 222458 ***
https://bugs.launchpad.net/bugs/222458
** This bug has been marked a duplicate of bug 222458
/lib/udev/hdparm Compares Against $DEVNAME.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Is this similar to Bug #595138 (10.04 LTS)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/227705
Title:
hdparm not being triggered with udev
To manage notifications about this bug go to:
https://bug
@Sundberg Pauli (#17): Read the man page for hdparm. A -B option >128
disables spin-down (standby).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/227705
Title:
hdparm not being triggered with udev
I take my words back. The unmodified file works as well. Setting 'set -x' and
running the /lib/udev/hdparm function by hand does show that with
DEVNAME=/dev/sda hdparm is called properly with options:
/sbin/hdparm -B254 -S1 /dev/sda
This does spin down the disk on manual run. After boot the dis
I take my words back. The unmod
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/227705
Title:
hdparm not being triggered with udev
To manage notifications about this bug go to:
https://bugs.launchpad
I confirm #6 working on fresh install (of linux mint 11, so i guess
this is still open at 11.04) with minor modification: File is
/lib/hdparm/hdparm-functions and line is 99.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I also used the patch provided by Mihai Osian in comment #6 with
success. Any chance of this making it into 11.04 (or sooner in an hdparm
update?).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/227705
The suggestion from #6 works, and I hope it gets included in future
versions of this package, since any local change will be overridden
silently on upgrades (it's not in a config file)
--
hdparm not being triggered with udev
https://bugs.launchpad.net/bugs/227705
You received this bug notificatio
running udev in debug mode (udevd --debug --debug-trace) i can see this
execution order
1) /lib/udev/rules.d/50-udev-default.rules for sda
2) /lib/udev/rules.d/85-hdparm.rules for sda
3) /lib/udev/rules.d/50-udev-default.rules for sda1
4) /lib/udev/rules.d/85-hdparm.rules for sda1
in 2, the hdp
I tested it by enabling tracing in /lib/udev/hdparm (insert a "set -x"
somewhere at the top), setting the "DEVNAME" variable to "/dev/sdb" and
running the script. So no, it was not during a boot.
. But now that I think of it, it is quite possible that immediately after udev
parses and sets the
hm yeah my presumption was wrong, and calling hdparm -q -S240 -q -Y /dev/sdb
does set the time and put the drive to sleep without spinning it up instantly
again. i should have tested that before, sorry.
question is, as mihai said, what does access the hd at that time. the
partitions are encrypte
Amenophis: I have just tested your configuration and what gets executed is the
following:
/sbin/hdparm -q -f /dev/sdb
/sbin/hdparm -q -S240 -q -Y /dev/sdb
This instantly spins down the disk and sets the standby time at the same time.
If your disk spins up again, then most likely something
** Changed in: hdparm (Ubuntu)
Status: New => Confirmed
--
hdparm not being triggered with udev
https://bugs.launchpad.net/bugs/227705
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.
** Tags added: patch
--
hdparm not being triggered with udev
https://bugs.launchpad.net/bugs/227705
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.ubuntu.com/mailma
yes that works for me too (amd64, hdparm 9.15-1ubuntu4).
remaining problem for me: id like to use the "sleep" commando to put a drive
into sleep mode (hdparm -Y) concurrently with setting the standby timer:
/dev/sdb {
spindown_time = 240
sleep
}
this gets executed with the patch,
** Patch added: "Attached patch for /lib/udev/hdparm"
http://launchpadlibrarian.net/41168632/hdparm.patch
--
hdparm not being triggered with udev
https://bugs.launchpad.net/bugs/227705
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It appears that updating line 93 from /lib/udev/hdparm is enough to
solve the issue.
Modify from:
DISC=$KEY
to:
DISC=$(readlink -f $KEY)
--
hdparm not being triggered with udev
https://bugs.launchpad.net/bugs/227705
You received this bug notification because you are a member of Ubuntu
Bu
I tried adding a debug log print to /lib/udev/hdparm to see which device
name is used. Looks like it is never called for ATA drives.
Using device names under /dev/[hs]d[a-z] is still quite bad, as the
device names may change.
--
hdparm not being triggered with udev
https://bugs.launchpad.net/bug
imho i have the same problem in karmic now. it worked for me in jaunty
(not sure why, and cant remember how it was in intrepid).
im trying to set the spindown timeout for my second disk with:
/dev/sdb {
spindown_time = 240
}
but obviously it does not work.
all my / (but /boot) is encryp
I'll try that, but hdparm does work when pointing to a partition though
(and just uses the underlying device).
--
hdparm not being triggered with udev
https://bugs.launchpad.net/bugs/227705
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note that by-uuid refers to partitions but you want to run hdparm on the
device. There is usually also a device id in /dev/disk/by-id/
--
hdparm not being triggered with udev
https://bugs.launchpad.net/bugs/227705
You received this bug notification because you are a member of Ubuntu
Bugs, which i
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.
--
hdparm not being triggered with udev
https:/
22 matches
Mail list logo
