02-08-2014 10:56 AM
I´m using a M500 with 480GB (firmware MU03) in a Lenovo Z710 Notebook. The disk runs perfect but when I´m reading out the SMART values the value (09) "power-on hours" says "1" even after 20 hours of use. The counter seems frozen.
I´ve tried many different SMART tools, everywhere the same.
Does anybody know what could cause this problem?
02-09-2014 09:49 AM
Today the counter has increased to "2", what is quite strange, cause the ssd is meanwhile more than 20 hours in operation in a notebook.
Could it be that the "power-on hours" counter only counts the access times of the ssd? Even with that its hard to imagine, that the total access time is only 2 hours, cause I´ve flashed an image at the beginning on the ssd, which itself has taken 30 minutes time.
Does anybody know more how the counter "0x09 comes to its values?
02-09-2014 11:33 AM
It is meant to be hours that its powered on. Mine is over 4000 but to be honest I've not studied it to know how accurate it is. My gut feeling is actually that it was rather higher than expected for me.
02-12-2014 09:16 AM
Now I´ve ordered a new SSD and already got it. Same abnormal behaviour!!!
So in my opinion only 2 conclusions are possible:
a) The internal hours counter has a bug. Perhaps only in the new firmware MU03?
b) Windows dynamically switches on and off the SSD in very short cycles, so that the hours counter almost counts access times. Btw I´m using Win8.1
Would be nice if anyone from Crucial could give an opinion to that! Thanks
02-12-2014 10:09 AM - edited 02-12-2014 10:20 AM
targetbsp is using MU03 too ;-)
Would you be able to test the drive (leave it powered on for few hours) in other system or external usb enclosure? It seems that your laptop may be from Haswell line and Haswell support new DevSleep power management state (M500 support it too). Maybe it's because of DevSleep is in use?
02-12-2014 11:11 AM
Yes, I have a Haswell processor (i7-4700MQ).
Will test the SSD in a USB enclosure attached to an older laptop and report here the result.
A new question would be if the "power on hours" counter shouldn´t respect this considering the "power-on count" value? Latter correctly counts the power on processes of the pc. So one of both couters is atm definitely wrong
02-14-2014 10:15 AM
Just for the sake of completeness, my "problem" was caused by the devsleep function.
The counter works normal with a non Hasswell hardware setup. Anyhow, it would be nice, when the upcoming firmware could respect this in any way
02-14-2014 10:23 AM - edited 05-08-2014 12:46 PM
I also would say that the firmware/controller should be able to distinguish power states being in use. We will see