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 disk parameters other scripts will attempt to read the disk. I am not a specialist in udev, but I imagine that the sequence of operations is something like this: 1. Detect disks (==> hdparm is called) 2. For each disk, find partitions and read their UUIDs (==> disk is accessed again) If that is the case, what you want may not be possible. You could do a quick test, though: comment out all the entries from /etc/fstab that point to partitions on that disk and see what happens. If that leaves the disk in standby after a reboot, try to add the "noauto" mount option to the fstab entries (of course, that means you will have to mount the partitions manually afterwards). -- 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/mailman/listinfo/ubuntu-bugs
