SSD lifetime crystaldiskinfo

[Vilsen]

lifetime SSD terabytes written


On youtube a guw is talking bout
cristaldiskinfo , aa program that can determine
where in its lifetime your SSD is present .

https://www.youtube.com/watch?v=hyHMuAdjzfI

In linux you have to use :







but where do I find it here : ? ? ?? ?

Is this : 241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 17017312484

the answer ? to how many TERABYTES is written compared to the maximum of
terabytes the SSD is supposed to manage during its lifetime ???

Am I supposed to know how to find out how many
terabytes written it is ??






smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.15.0-128-generic] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Samsung based SSDs
Device Model: Samsung SSD 860 EVO 1TB
Serial Number: S3Z9NB0KC52621Y
LU WWN Device Id: 5 002538 e40b2fa99
Firmware Version: RVT02B6Q
User Capacity: 1 000 204 886 016 bytes [1,00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Tue Apr 13 14:12:50 2021 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x53) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 85) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1221
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 909
177 Wear_Leveling_Count 0x0013 099 099 000 Pre-fail Always - 10
179 Used_Rsvd_Blk_Cnt_Tot 0x0013 100 100 010 Pre-fail Always - 0
181 Program_Fail_Cnt_Total 0x0032 100 100 010 Old_age Always - 0
182 Erase_Fail_Count_Total 0x0032 100 100 010 Old_age Always - 0
183 Runtime_Bad_Block 0x0013 100 100 010 Pre-fail Always - 0
187 Uncorrectable_Error_Cnt 0x0032 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0032 071 050 000 Old_age Always - 29
195 ECC_Error_Rate 0x001a 200 200 000 Old_age Always - 0
199 CRC_Error_Count 0x003e 099 099 000 Old_age Always - 3
235 POR_Recovery_Count 0x0012 099 099 000 Old_age Always - 240
241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 17017312484

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

[rene]

Is this

Code: Select all

  241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       17017312484

the answer ?

Yes. That value is in units of 512-byte sectors so you multiply by 512 for bytes, then divide by e.g. 1000^3 for GB:

Code: Select all

$ echo $(((17017312484 * 512) / 1000**3))
8712

So less than 9TB written. Your Samsung 860 EVO 1TB is warranted for 600TBW; https://www.samsung.com/semiconductor/m ... er/860evo/. It moreover pays to note that that's likely very conservatively put by Samsung: the drive may actually do 2, 3 or 4 times more than that before being in fact seriously degraded.

That total warranted TBW is not something that you (as far as I'm aware) can get programmatically from anywhere; will need to be had from an actual spec sheet such as above.

[Vilsen]

A very good but disturbing answer .

What did you mean by:

" That total warranted TBW is not something that you (as far as I'm aware) can get programmatically from anywhere; will need to be had from an actual spec sheet such as above."

I read the datasheet and found the same 1.5 million hours / 600TB / 5 year limited
whatever comes first.

I have a new exactly the same 1 TB and I´m thinking I should clone this one to that one .

The problem is that I have a windows 10 partition in the beginning and I am not sure it will work
due to there intricate copy protection scheme .


If I was sure that the windows partition will work I would immediately do a cloning.

I could of course also try the prg: crystaldiskinfo in windows but I am afraid
that it will destroy my windows 10 if there is some virus/trojans/"hacks" etc.

When I looked it up on https://crystalmark.info/en/software/crystaldiskinfo/
I found some disturbing cartoons - is it really a serious company ?

[Vilsen]

I forgot :

Unnecessary writing on SSD :

https://opensource.com/article/20/6/linux-noatime


Turning off atime is a small but effective way to improve system performance. Here's what it is and why it matters.


What about that ?

[rene]

Not sure what's disturbing. Yes, I meant that the 600TB write "limit" (as said, it's usallly in fact much more) is to be distilled from a specification listing, can not be read from the drive itself. What can be read, as demonstrated, is what HAS been written to the drive up to now and that's in your case less than 9TB. I.e., you're not even at 1.5% of your drive's warranted write-lifespan.

Crystal disk mark is fine but you don't need it then, since you yourself already identified how to get the info in Linux.

As to cloning: would normally work fine when placed back into the otherwise same system; the Windows copy-protection stuff is fine with only an SSD changing. It's only when e.g. the motherboard and/or CPU changes that Windows considers the computer new, and insists on a new license.

As to atime: basically, one should these days not feel in any way obliged to treat an SSD any other than one would historically an HDD. There's lots of ghosts of times past on the internet wrt SSDs, from back when they were tiny and without effective wear levelling and/or garbage collection. Disabling atime is on the other hand also not bad, and I often did so going back 20 years even and on old HDDs. It doesn't matter, really, but if you like...

[senjoz]

Lifetime of SSDs is not dependent only on the amount of cumulative data written to the disk. Other factors are also important. You can find more details about that in https://www.ni.com/sl-si/support/docume ... orage.html.

Regards, Jože

[Vilsen]

You seem to know a lot of important stuff !

I am amazed !

I will absolutely try to clone the SSD to another exactly same SSD
and the mobo and everything else is the same so........no change !

I just hope I don't get a message some day from windows that my
license is no longer valid.

I got the windows partition on to the SSD by a program called
Macrium Reflex and I noted when it was working that it wrote something in the registry
and that is what made me curious - could this be the secret ?

The whole idéa was coming from some people on youtube suggesting that
program so that the license still works.

I have a hardware-cloning-station where I can put 2 HD ( spinning or SSD)
and push a button and the cloning (forensic) starts.

How can I possible know if it will work ?

[rene]

Lifetime of SSDs is not dependent only on the amount of cumulative data written to the disk.

Certainly. How much lifetime it has left however is for the largest part dependent on the amount of cumulative data written as a percentage of the warranted amount as in this thread, latter after all already incorporating e.q. MLC vs. QLC and average consumer access patterns.

[rene]

I got the windows partition on to the SSD by a program called Macrium Reflex and I noted when it was working that it wrote something in the registry and that is what made me curious - could this be the secret ?

If you are specifically talking about "the secret" of not losing a Windows license, no, it wouldn't be, seeing as how there's no such secret to begin with. A Windows OEM license does not invalidate by small changes and HDD to SSD or SSD to SSD count as such. If as you say the new SSD is of the exact same size or even type as the older, a simple clone will work fine, even for Windows.

Note only that --- for Linux certainly, I don't in fact believe that Windows tends to care --- you'll not want to boot with both clones attached: Linux these days identifies filesystems by UUID and said UUIDs get cloned right alongside, so you'd introduce potential confusion. That's just a minor point though; all will be well.

[Vilsen]

I would - if I could - like to have
an explanation of the meaning of this:

Certainly. How much lifetime it has left however is for the largest
part dependent on the amount of cumulative data written

as a percentage of the warranted amount as in this thread,

latter after all already incorporating e.q.

MLC vs. QLC and average consumer access patterns.


What do I get out of this reasoning ? Do you mean that terabytes written / lba written
241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 17067917794
as in my case now is OF NO IMPORTANCE and it is IMPOSSIBLE to know
when the SSD suddenly do not operate properly any more ?

SUDDEN DEATH ????? No pre-warning ?




What is the point with for example CrystalDiskinfo telling me that so and so many TERABYTES is written
and comparing this with what the datasheet says ?

MTBF=1.5 million hours
5 year limited / TBW =600TB All documented endurance test
results are obtained in compliance with JESD218 Standards.
Please visit www.jedec.org for detailed information on JESD218 Standards600TB

[rene]

Nono, all is well. Senjoz mentioned that amount of data written is not the only thing that determines remaining lifetime of an SSD generally but what I pointed out in response is that however comparing said amount to the amount as warranted by the manufacture for that specific drive certainly does catch the vastly largest factors as to remaining lifetime.

For example, while a 1TB QLC SSD will stand less data writes than a 1TB SLC SSD, latter would also have a higher manufacturer-warranted TBW due to that. In your case your 860 EVO (a TLC SSD) is under "normal" consumer-grade access patterns and operating temperatures expected to stand at least 600TB (and will as said in reality do much more) so that your currently 9TB written means it's at not even 1.5% of its expected total, i.e., that you are as to data written at not even 1.5% of its expected lifetime.

I.e. and by the way, that you should stop worrying. Current SSDs warrant no more, in fact less, worries of failure than HDDs ever did, certainly unless you have quite special and specific usage patterns.

[Vilsen]

This is me again but from the CLONE !

This is the NEW SSD:

241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 2210395833

[Vilsen]

I also tried to start Win 10 and it worked.

Here is what Crystaldiskinfo said:

[Vilsen]

...on the cloned new SSD

[rene]

That seems to make sense yes, a bit more than 1TB written after you just cloned said 1TB drive. Looking good...

[Vilsen]

Well, I had done some "experiments" also before when I tried
to install i.a. openSUSE Tumbleweed but even though
the installation of this was impressive in some pieces,
I did not see the point of it and certainly remarkable,
this distro seems to have
more security finesse than MINT has so you can wonder .....



In any case, I am very grateful that you helped me and
cured my worries.

Without your professional knowledge, I would have been lost without rescue.

[Vilsen]

After a second cloning:
241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 4166367880

[Vilsen]

The new SSD has double the written bytes:

241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 4166367880


How is that possible ?

[rene]

Why is that unexpected "after a second cloning"? Your drive now has a bit more than 2T written to it which would be perfectly sensible after cloning a 1T drive twice, i.e., writing 1T to it twice.

[Vilsen]

Of course, how stupid I am, I thought wrong!
Thus, I have a long way to go to the 600 TBW that
are guaranteed.