Re "Power-On Hours never update again":
It's not a bug, it's a feature I've seen this on my Macbook Pro (Early 2011) ever since the SSD has been in use: The value advances but very slowly.
Depending on your driver settings and capabilities the drive will enter "slumber" state whenever it is not busy by virtue of DIPM (Device Initiated Power Management). If DIPM is enabled "Power-On Hours" will only account for the time when the drive is busy doing reads or writes. Thus the value will advance very slowly
Citation from Intel Solid-State Drive Toolbox :
09 – Power-On Hours Count
This attribute reports the cumulative number of power-on hours over the life of the device. Use the Raw value for this attribute.Note: The On/Off status of the device initiated power management (DIPM) feature will affect the number of hours reported.
- If DIPM is turned “On”, the recorded value for power-on hours does not include the time that the device is in a “slumber” state.
- If DIPM is turned “Off”, the recorded value for power-on hours should match the clock time, as all three device states are counted: active, idle and slumber.
Should I update if I don't have any problems?
I have 2 Intel 320 120GB in a mission-critical server. They have been working great without problems.
I know Intel recommends to update even if you don't have problems but there is at least one person here (harlekin) that had problems after the update.
Should I wait a couple of weeks to see how how many new problems this update will cause?
Watercool had an occurance of the bug after flashing the new firmware also. This is equivalent to a data loss - and if you take into consideration, that most likely fewer than one-tenth of a percent of users would know that a firmwareupgrade exists, and I'm sure that no one in this forum is eager to throw his drive in a circle of bootloops either - two occurances within the first day leave a very clear message...
Intel itself hasn't come back on weither the bug still can be reproduced. They packaged up some update and then went silent again in the face of new signes of the critical bug not having been fixed. Draw your own conclusions.