Beta Tester Wanted (new Windows app for ReadyNAS)

dsm1212 wrote:
That's a frontview bug that has been reported before. And, think about it, cpu temp should always be higher than sys temp.

Thanks, Steve. Yeah, I thought about that... And:

a) I don't think it's necessarily true that CPU temp must be higher than system temp -- there are a lot of things in the box that generate heat (the disk drives at 40 degrees C with all their thermal mass, for example), and most of those things run even when the CPU is idling, and
b) the "system" temp reported by NAS Herder instantly spikes whenever the CPU is heavily loaded, and just as quickly drops back to normal when the load is removed, but the "cpu" temp stays almost constant; when it does change, the slopes are more gradual and the amplitude is a lot lower.

Here's NAS Herder's graph of the last ten days:

The yellow trace, marked "System", spikes every four hours when rsnapshot does a "du" on a multi-million-file external USB drive (the big spike near the right edge of the graph is "updatedb" running on that drive). Meanwhile, the blue trace marked "CPU" hardly moves during those periods of high CPU load. Shouldn't the "CPU" graph behave like the "System" graph, and vice-versa?

Also, see the big dislocation midday on the 22nd? That's when I opened up the box and blew a ton of dust out of the fans. All the temperatures are lower afterward, but the "CPU" temperature is MUCH lower. Why would that be? I'd expect CPU temp to be very well-controlled by the tight feedback loop between the CPU and its huge heatsink/fan, and I'd expect the System temperature to be allowed to drift a lot more so long as it wasn't too close to the high-temperature limit. That's exactly opposite the behavior shown by the NAS Herder graph.

So... Maybe I'm missing something obvious (and please let me know if I am -- it's late here and maybe I'm just not thinking clearly), but to me it looks as though all signs point to the graphs being switched in NAS Herder rather than in Frontview.