On Sun, 2003-01-26 at 16:33, Ben Reser wrote: > My guess would be that hddtemp is configured to read the wrong smart > value as the temp. Right now this is all guess work. The values and > what they mean are not documented. Try running hddtemp --debug <drive> > to see all the values and see if there is a better one for your drive.
>From this it looks like it is using field(194). field(4) or field(12) look like they are more likely the temp. Anyone in particular I should send this to? TTFN, Lonnie Borntreger -> hddtemp --debug /dev/hd[ab] ================= hddtemp 0.3 beta3 ================== Model: MAXTOR 4K060H3 field(1) = 0 field(3) = 200 field(4) = 57 field(5) = 0 field(7) = 0 field(9) = 138 field(10) = 0 field(11) = 0 field(12) = 57 field(13) = 0 field(194) = 18 field(195) = 77 field(196) = 0 field(197) = 0 field(198) = 0 field(199) = 0 ================= hddtemp 0.3 beta3 ================== Model: MAXTOR 4K080H4 field(1) = 0 field(3) = 245 field(4) = 68 field(5) = 1 field(7) = 0 field(9) = 64 field(10) = 0 field(11) = 0 field(12) = 68 field(13) = 0 field(194) = 18 field(195) = 106 field(196) = 0 field(197) = 0 field(198) = 0 field(199) = 0
