'hdparm -C' problems with libata-dev
Hi everyone,
I've been trying to get the hdparm and hddtemp tools to work with my Seagate SATA Drives.
I have 4 Drives connected to an nVidia nForce 3 SATA Controller, and 1 Drive connected to a Promise SATA 150 TX2.
After some reading, i found out that SMART support for reading the harddrive's temperature is not yet in the kernel, so i got the libata-dev patch from here: http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-libata-dev1.patch.bz2
and patched the 2.6.11.7 kernel with it. (Worked fine, but i'm not sure if that was the right patch file? The BK patches are newer, are those the "right" ones, or are they only for such a specific BK version of a kernel?)
Everything worked fine, and after updating hddtemp to the latest v0.3_beta13, i even am able to get temperature readings from the drives.
What's not fully working as expected, however, is hdparm. If I (for example) want to check the drive's power status, i get the following:
root # hdparm -C /dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde
/dev/sda: \ drive state is: standby /dev/sdb: \ drive state is: standby /dev/sdc: \ drive state is: standby /dev/sdd: \ drive state is: standby /dev/sde: \ drive state is: standby
The drives are of course, NOT in standby, but are in the state "active/idle".
When setting the standby parameter for a drive, everything seems to work normally.
root # hdparm -S 241 /dev/sda/dev/sda: setting standby to 241 (30 minutes)
I wasn't able to check that this really works (because of missing hdparm -C) but i think it acually does. At least hdparm -y is able to standby a drive.
I'm using hdparm v5.9, which is IMHO the most recent version.
Is there anything i can do to make this ('hdparm -C') work? Is this a libata bug or missing feature? A Seagate Firmware bug? A hdparm problem? Or just not possible with SATA Drives?
I'd gratefully appreciate any help/comments ;-)
Gerald
Quoted 3 lines · Gerald Hopf
Is there anything i can do to make this ('hdparm -C') work? Is this a libata bug or missing feature? A Seagate Firmware bug? A hdparm problem? Or just not possible with SATA Drives?
Sounds like a bug w/ my implementation of HDIO_DRIVE_CMD for libata. However, I have yet to take the opportunity to track it down. Plus, I'll be taking a little vacation over the coming weekend, so I likely won't get to this until sometime next week... :-(
Until then, please feel free to experiment more w/ hdparm to see if there are any other problems w/ hdparm on SATA. Please copy me on reports of any such problems (or send them to me directly). Thanks!
John
Signature · 2 lines
John W. Linville [email protected]
Quoted 15 lines · John W. Linville
Quoted 3 lines · Gerald Hopf
Is there anything i can do to make this ('hdparm -C') work? Is this a libata bug or missing feature? A Seagate Firmware bug? A hdparm problem? Or just not possible with SATA Drives?
Sounds like a bug w/ my implementation of
HDIO_DRIVE_CMDfor libata. However, I have yet to take the opportunity to track it down. Plus, I'll be taking a little vacation over the coming weekend, so I likely won't get to this until sometime next week... :-(Until then, please feel free to experiment more w/ hdparm to see if there are any other problems w/ hdparm on SATA. Please copy me on reports of any such problems (or send them to me directly). Thanks!
Quoted 9 lines
John
--
John W. Linville
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
I reported that "hdparm -r" was not working with PATA drives a couple months ago. I got no feedback, but if someone can test it with SATA I would be curious if it works.
Greg
Signature · 3 lines
Greg Freemyer The Norcross Group Forensics for the 21st Century