The software you are using is not Intel software therefore we cannot guarantee the information it is displaying is correct.
You can use the Toolbox software from our side. Here is the download link:
Intel is aware that some new Intel® 520 SSD’s display an incorrect power on hours value. This condition does not affect the operation of the drive or the warranty status. The issue is logged with our engineering team but there is currently no timeline for a corrective action
according to me is the condition and the impact of the work as intel gives
MTBF 1200000 trouble-free operation for hours, and then sells used my ssd drive to the course of nearly 900,000 hours as new !
for what your engineers take money if they release such shoddy. if I fill ssd drive and wait like a failure occurs at 1200000 causing loss of data?
I want a new efficient drive ssd, because I paid for this!
the counter to zero hours works
Try some tool capable to display ATA Device Statistics log. The Power on Hours counter of this log is not affected by this bug and provides a reasonable value.
See the smartmontools FAQ for a sample output.
All Intel SSDs support the Device Statistics log (introduced in ATA ACS-2) but interestingly Intel SSD toolbox is still unable to display it :-)
This is not correct. Both drives are also affected by the bug. See the "Raw Values" column of ID 9. The hours are encoded in the lower 4 bytes:
000DA76E hex = 894830 decimal
000DA77C hex = 894844 decimal
The values displayed in the extra "Betriebsstunden" or "Power On Hours" field look sane because these are corrected by CrystalDiskInfo itself.
Fortunately this tool is open source, so to be convinced please have a look at the following lines in AtaSmart.cpp from CrystalDiskInfo6_2_2Src.zip:
// Workaround for Intel SSD
if (asi.Model.Find(_T("Intel")) == 0 && asi.MeasuredPowerOnHours > 0x0DA753)
asi.PowerOnRawValue -= 0x0DA753;
asi.DetectedPowerOnHours -= 0x0DA753;
asi.MeasuredPowerOnHours -= 0x0DA753;
@Intel: Could you please confirm that the offset 0x0DA753 (894803) used by CrystalDiskInfo is the correct one to compensate this bug?
CrystalDiskInfo is not a tool we normally use, so we cannot confirm if the values used by this tool are correct.
We advise you to confirm the power-on hours with SmartmonTools.
You can download this tool here:
- Install the application
- Open a Command prompt with Administrator privileges.
- Change to the directory where smartmontools is installed. The default folder is c:\program files (x86)\smartmontools so the command would be:
Cd \program files (x86)\smartmontools\bin
- Run the command:
Smartctl –l devstat /dev/sda
(note, it may be /dev/sdb or other, depending on how many drives the you have installed. Also, that’s lower case L after the dash in the command line)
The output will look like the picture below. Look for Power On Hours.
as the author of many parts of smartmontools (including the Windows port and the Device Statistics support), I'm very glad that you recommend this tool. See the Copyright line from above screenshot :-)
My question was whether the offset used by CrystalDiskInfo is the correct one to compensate this bug in SMART attributes. I would like to add this info to the related smartmontools FAQ entry.
BTW: I really don't understand why Intel SSD Toolbox does not support Device Statistics. Intel SSDs were the first devices implementing this useful feature, but the related tool still ignores it.
We checked about this with our additional resources and the correct offset is 894794.
We hope this information helps. Please let us know if you have further inquiries about this topic.
Thanks for the info!