List, Some of you may recall a message I sent last month about some problems that I was getting with my hard drive. One of the suggestions I got was to ensure that the cable was 80pin, so I went out and bought one of those ATA-133 round cables and installed it. Sure enough, as I reported, the problems seemed to go away. Another suggestion I got was to run smartd. I thought it was a good idea, so I did. I got very nervous when logwatch was showing me that the drive temp was averging between 81 and 84 degrees Celsius. That's pretty darned hot! After reading online that cooling a drive by only 5 degrees can significantly improve performance and drive life, I decided that I'd do what I could to improve the thermal cooling in my system, since I'm still having problems with my hdb. I installed two new 80mm fans, replaced all of my ribbon cables with round cables, and bought a 5 1/4" metalic casing that incorporates a fan for my 3 1/2" drive, which blows directly upon it. I figured that should do it, especially since, before the switch, my hda was sandwiched between my floppy and my hdb, so didn't have any kind of airflow. Imagine my surprise when logwatch started showing that my hda temp, as reported by smartd, had climed to between 85 and 87 degrees Celsius! The temp had actually gone UP by three degrees with the incorporation of the extra airflow! (and no, myoffice is not that hot! LOL) The drive is a Maxtor 6L060J3, which dmesg picks up. However, smartd says that the drive isn't in its database. Could this just be a deal where smartd doesn't know how to interpret the raw values correctly? It seems strange that *more* airflow would provide a *higher* temp. I've put the output from smartctl -a /dev/hda in the following spot: http://www.benjamin.weiss.name/hda.html I'd appreciate any insight. Thanks! Ben -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
