Bug 1054593
Summary: | Two new drive strings for the hddtemp database for Samsung SSD drives | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Edward Kuns <eddie.kuns> |
Component: | hddtemp | Assignee: | Ville Skyttä <ville.skytta> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | eddie.kuns, ville.skytta |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | hddtemp-0.3-0.30.beta15.fc19 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-01-28 04:39:22 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Edward Kuns
2014-01-17 05:44:11 UTC
Some searching around the web tells me that these aren't the only drives that lack attribute 194 but do have useful data in 190, so here's a try for something more generic: try 190 if 194 doesn't exist by default (smartd does that too): http://koji.fedoraproject.org/koji/buildinfo?buildID=492107 Could you try it out and let me know if it works for you? It's built for Rawhide but can be installed as is on F-19. I tried it and it works perfectly. Thank you. Great idea to keep the database to only exceptions. It's probably a good idea, however, to keep a header describing the data. Something like this: # Minimal database for drives not covered by defaults (attributes 194 and 190). # hddtemp will first try S.M.A.R.T. attribute 194. If it does not exist, it will # try attribute 190. # # The four columns are: # 1) Regular expression matching the drive identification, which you see as the # Model in the output of: hddtemp --debug /dev/drive # 2) S.M.A.R.T. attribute number to get drive temperature. A value of zero # means that we know that the drive doesn't have a temperature sensor. # 3) Temperature units reported (C or F). # 4) Human readable string representing the drive model I assume when (if?) this gets pushed to F19, I'll have to uninstall this version to be able to install the Fedora 19 update? Thanks for the db description comments, adopted a slightly modified version in 0.3-0.30.beta15. The upcoming F-19 update will be 0.30.beta15.fc19 so it'll upgrade your 0.29.beta15.fc21, no need for uninstall or downgrade first. hddtemp-0.3-0.30.beta15.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/hddtemp-0.3-0.30.beta15.fc19 hddtemp-0.3-0.30.beta15.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/hddtemp-0.3-0.30.beta15.fc20 Package hddtemp-0.3-0.30.beta15.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing hddtemp-0.3-0.30.beta15.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-1152/hddtemp-0.3-0.30.beta15.fc19 then log in and leave karma (feedback). Tested hddtemp-0.3-0.30.beta15.fc19 from updates-testing repo and it works perfectly. hddtemp-0.3-0.30.beta15.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. hddtemp-0.3-0.30.beta15.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |