After upgrade this firmware on a Intel SSD 320 160GB, SMART value "Power-On Hours" will be reset to "0" and the timer never update again.
Is a new bug?
updating here fine, reseted at 0 after flash and now its at 40
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 CountThis 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.
I did the Firmware update (MacBook pro) --> installed w7 on bootcamp -> SSD has 8mb now! Well Done Intel
This is the second confirmation of the update not fixing the bug at hand and the drive becoming unusable well after the update was applied. Intel hasnt issued a statement yet.
How can I do a secure erase to restore the operational state? The SSD isn't shown in the intel toolbox software
edit: did a secure erase, still 8mb.. bricked?
edit2: back at 120gb now.
Update is useless after all? What a marvelous achievement!
Update went smoothly. It's now being taken to work for active use. Fingers crossed...
I am in contact with SSDelighful now to see what happened on my side. Maybe the Bootcamp drivers screwed my SSD? Can this happen?
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?
No I don't. Please read the posts. Two other users in here have triggered the bug after updating already - and I'm sure with many more to come.
It looks like only zanary with his MacBook Pro has problems as Watercool seems to be fine.
So, we have a total of 1 problem in a MacBookPro.
Anyone aware of any other problems?
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.
+1 user not able to update in a macbook pro. tried another pc, did not work neither. tried another unibody 2010 macbook pro, update successful. now hoping it will not brick (as before).
Watercool had an occurance of the bug after flashing the new firmware also. [...]
Aha, just when I wanted to happily report that installing the new firmware on a 2011 MacBook Pro worked without any problems ... the update went fine, and so far no problems.