Open GoogleCodeExporter opened 9 years ago
Hi
them temperature for my d drive reads the highest value and this updates! The
min and current just display as 0. I have tried other tools and its not a
hardware problem as the temps read in HW monitor pro. I prefer your software
and want to stick with it! I've tried googling the issue and same across a WMI
issue. Can i remove the wmi entry? could this be the problem? Can you
instruct me on how to remove the wmi entry, not a programmer i'm a 3d
animator/video editor and need to monitor temps for drives.
all my other drives read fine, 4 x drives in total. Only the D drive has an
issue!
Help appreciated
Regards
Original comment by philsou...@gmail.com
on 2 Jan 2013 at 11:43
THE DRIVE HAS WORKED BEFORE, I SHUTDOWN AS NORMAL AND THE NEXT TIME I RESTARTED
THE SYSTEM THE ISSUE OCCURRED!
Original comment by philsou...@gmail.com
on 2 Jan 2013 at 5:20
I have the same issue. Worked fine for months. Nothing is changed or
reconfigured. The maximum value shows the correct temperature, but current
value is zero. I have total of three hard disks, the other two are showing the
correct values.
Original comment by k.balabanov
on 12 Feb 2013 at 8:56
Attachments:
I have tested the previous versions and 0.4.0 HAVE the same issue, but 0.3.2
works fine.
Original comment by k.balabanov
on 12 Feb 2013 at 10:03
Attachments:
I may have found something on this...
I too am having trouble with an older Seagate drive. Viewing as
Celsius=0/Fahrenheit=32
It seems (on my old drive anyways) that the S.M.A.R.T. dataset may have been
corrupted, registering a false overheat.
Here, I'll attach S.M.A.R.T. reports from both. The 'bad' drive only adds a
word "Past" to the data string. So this might be a simple "string parse" issue.
In my cast this word "Past" is S.M.A.R.T. believing that the drive overheated
one day while sitting in the air-flow of a 120mm drive cage fan, btw its
neighboring HDD sits in the same air-flow as well.
Original comment by dewy...@gmail.com
on 17 Mar 2013 at 3:53
Attachments:
Issue 426 has been merged into this issue.
Original comment by moel.mich
on 25 Jun 2013 at 7:32
Original issue reported on code.google.com by
philsou...@gmail.com
on 31 Dec 2012 at 9:55Attachments: