I have a 500gb WD hdd in my rig. I used CPUID hwmonitor to watch my temps while playing a game for about an hour. Everything is good except the "assembly" temps for the hdd which was 142c, but "airflow" and "drive" for the same hdd both read 28c. Is this an error or something? What is "assembly" anyway, and how can it be that much hotter than the other two readings i just posted, because theres no way the "drive" is 28c if the "assembly" temp is that high.
So is this article saying that if the hdd was that hot I'd be getting some type of warning? I also downloaded "HDD Temperature v.4" and havent seen any temp. jumps on that program. Seems to be that CPUID is the only thing getting those astronomical temps. Is it safe to say CPUID is wrong?
I don't know where the other programs are getting their information, but HDDScan and HD Sentinel read the HDD's SMART sectors. The Airflow Temperature in WD drives is often displayed as a temperature difference from 150, so a normalised value of 100 would correspond to an actual temperature of 50C.
A program such as smartctl (from smartmontools) also reports a temperature history for the drive. The drive maintains a log of the number of times that it has exceeded its allowable temperature maximum.
I have no idea what the author of CPUID hwmonitor means by "assembly" temperature.
I have noticed that even WD's own DATA LifeGuard diagnostic sometimes has trouble accessing the SMART data via certain SATA drivers and/or controllers. AIUI there are usually two ways (IOCTLs) to access these data. HD Sentinel seems to get it right nearly all the time. I suspect that it tries both ways and is intelligent enough to realise when the data are bogus.
If you examine HD Sentinel's report, you should see two attributes, Temperature and Airflow Temperature. I think the concept of "assembly" temperature must mean something in German, but whatever it is got lost in the translation.