Red Hat Bugzilla – Bug 507963
hdparm can't spin down my pata drives
Last modified: 2009-08-15 04:15:39 EDT
Description of problem:
after issuing hdparm -Y /dev/sdb, my drive is entering sleep mode then going immediately active
for another drive it just ignore the sleep mode command and stay active
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.hdparm -Y /dev/sdb
drive doesn't sleep
drive should enter sleep mode
bugfix is to update hdparm to version v9.15 which works ok
This is a bug in 7.3 <= hdparm < 9.14. It is caused by hdparm opening the device with O_RDRW instead of O_RDONLY and triggered if udevd is running.
Relevant entries from hdparm ChangeLog:
- switch back to O_RDONLY for everything, to keep Debian/udevd happy
Note that the kernel returns EFAULT rather than EPERM from SG_IO for
non-root users, and *no* SG_IO functions work for non-root users now.
- use O_RDWR instead of O_RDONLY for better SG_IO compatibility
see also bug #494711, which is incorrectly filed as a kernel bug and essentially describes the same issue
bug #511936 is another duplicate of this bug
*** Bug 494711 has been marked as a duplicate of this bug. ***
*** Bug 511936 has been marked as a duplicate of this bug. ***
hdparm-9.16-1.fc11 has been submitted as an update for Fedora 11.
As expected, the update fixes the problem.
re comment #5: Please add this comment at our updates website so that the new package will be pushed to the stable repository automatically when enough positive comments were entered. The link is available in comment #4
hdparm-9.16-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update hdparm'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7829
hdparm-9.16-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.