Whats the status of your SSD?


Recommended Posts

An honest question is why does this thread exists? Is they any proof that the numbers reported by SMART and this tool are reliable?

I certainly hope not!

Bought my Kingston SNV425-S2 64GB SSD in September 2010.

January 2011 (when I originally posted the following results in this topic)

SSD was 4 months old

Health was 85%

Work time: 2 months, 6 days

Powered on: 229 times

September 2011

SSD is 12 months old

Health is 62%

Work time: 6 months, 1 day

Powered on: 578 times

"Your drive health is in good condition and according to current use, estimated lifetime is August 2020."

October 2011

SSD is 13 months old

Health is 59%

Work time: 6 months, 15 days

Powered on: 646 times

"Your drive health is in good condition and according to current use, estimated lifetime is April 2020."

mine been 70% out of box with 0 hours

and it's still 70% (obviously this app do not support this samsung ssd)

http://online.hddlif...fa150a940922a98

but those unknown samsung smart parameters

EB

March 2011 (194 hours) : 7

September 2011 (5254 hours): 9

EC

March 2011 (194 hours) : 2

September 2011 (5254 hours): 55

ED

March 2011 (194 hours) : 15

September 2011 (5254 hours): 207

EE

March 2011 (194 hours) : 1196

September 2011 (5254 hours): 1196

I am sure the attraction to SSDs isn't their reliability, but their speed. I am not questioning the attraction to SSDs, but merely this topic. The point of posting reliability estimates would be to challenge those who see SSDs as less reliable than HDDs, otherwise why do it?

I have had more flash media die on me than anything other than Floppy Disks in my 13 years using PCs. This makes me wonder about the reliability of SSDs. As a result, looking at this thread aims to counter that, but offers nothing in the way of proof. I can find many people who are still running HDDs from over 5 years ago. A matter of fact, I have ones nearing 10 years old in use right now and they are still spinning fine. That doesn't mean HDDs never die. But if I told you my HDDs was going to last me another "3 years, 2 months, and 9 days" I should be showing why that number is so accurate and isn't just pulled out of someone backside.

Again, this isn't an attack on SSDs, but an inquiring as to what the point of posting the "status" of your SSD if the status is hogwash.

You make it sound like this program is randomly generating a date. You do realize that all drives (HHD or SSD) have a read/write rating of some sort, right? The manufacturers do actually test their product before they throw it out on the market, so they know exactly the amount of usage that an average user should get. So would you like to take a guess at how this program calculates that date?

Like I said before, both sides will obviously have failures. Shock, static charge, voltage spikes, temperature, etc. would all play a factor in the life of a drive. I don't have any proof to back this, but maybe SSD's are more commonly used in laptops since the majority of them come in the 2.5" form factor. If there's any truth to that, then obviously it would be prone to more outside forces. But if you put a SSD and HDD next to each other, in the same environment, and read/write the hell out of it, I'm willing to bet the SSD wins.

You make it sound like this program is randomly generating a date. You do realize that all drives (HHD or SSD) have a read/write rating of some sort, right? The manufacturers do actually test their product before they throw it out on the market, so they know exactly the amount of usage that an average user should get. So would you like to take a guess at how this program calculates that date?

Like I said before, both sides will obviously have failures. Shock, static charge, voltage spikes, temperature, etc. would all play a factor in the life of a drive. I don't have any proof to back this, but maybe SSD's are more commonly used in laptops since the majority of them come in the 2.5" form factor. If there's any truth to that, then obviously it would be prone to more outside forces. But if you put a SSD and HDD next to each other, in the same environment, and read/write the hell out of it, I'm willing to bet the SSD wins.

It seems the program does pull its number out of thin air, so to speak.

Thanks to the link in Coth's post I was able to get a little insight into how the program generates its life date:

It's a simple mathematical problem: in order to calculate it at once, we need to know at least the date when you wrote data to the drive the first time, but unfortunately, drives do not provide this information. That is why we need some time after the first launch of SSDLife to monitor how intensively you use your SSD in order to determine its average load. And as soon as we can calculate the approximate average amount of data written to the drive per day, we will be able to determine the time it will take you to use the entire lifetime capacity of the drive, which means we will be able to calculate the date when the lifetime of the SSD will be over. Of course, this date will keep changing depending on how the intensity of the drive usage changes.

Source: http://ssd-life.com/eng/how.html

So the program seems to be of dubious value. It is only able to guess that your drive will last x days based on how many writes it is supposed to handle and how often it thinks you write to the drive. It can't read real wear on the drive or report any underlying problems with the drive that aren't detected by SMART. And we all know how useful SMART is...

It seems the program does pull its number out of thin air, so to speak.

Thanks to the link in Coth's post I was able to get a little insight into how the program generates its life date:

Source: http://ssd-life.com/eng/how.html

So the program seems to be of dubious value. It is only able to guess that your drive will last x days based on how many writes it is supposed to handle and how often it thinks you write to the drive. It can't read real wear on the drive or report any underlying problems with the drive that aren't detected by SMART. And we all know how useful SMART is...

Did you not read my post?... Thanks for basically re-emphasizing what I said...

And no, it does not pull the date out of thin air. It's an educated prediction just like any other prediction/forecast in the world. Did you honestly think that this program could magically predict the exact day your drive will die?

A drive is rated for a certain amount of read/writes. It will keep record of your usage over time and then that program will build a prediction using it's algorithm. It's common sense that it will change over time since sometimes it will be running for a month straight and sometimes it will be off for a week. The program is still correct for the usage you've put on thus far. It's not like a prediction is a bad thing...

In the end, there have been plenty of people on here that have used their SSD's for a long time and the program still says they have years and years of life left. If somebody only has a few hours put on it, then yeah it's not exactly valid, but that's definitely not the case here. The proof is all contained in this thread. You can believe what you want, but saying it's wrong is just non-sense.

Did you not read my post?... Thanks for basically re-emphasizing what I said...

And no, it does not pull the date out of thin air. It's an educated prediction just like any other prediction/forecast in the world. Did you honestly think that this program could magically predict the exact day your drive will die?

A drive is rated for a certain amount of read/writes. It will keep record of your usage over time and then that program will build a prediction using it's algorithm. It's common sense that it will change over time since sometimes it will be running for a month straight and sometimes it will be off for a week. The program is still correct for the usage you've put on thus far. It's not like a prediction is a bad thing...

In the end, there have been plenty of people on here that have used their SSD's for a long time and the program still says they have years and years of life left. If somebody only has a few hours put on it, then yeah it's not exactly valid, but that's definitely not the case here. The proof is all contained in this thread. You can believe what you want, but saying it's wrong is just non-sense.

It is a very poor guess* as the program needs to run from Day 1 until the end to give a decent estimate, but even then it isn't guessing on anything more than estimated write capability from the drive maker. So it is really guessing how many estimated writes your drive has left not its "health".

That was my issue. If you look at the screenshots it implies that this product is able to read deeply into the SSD health and give an accurate estimate of how long it would last. That isn't the case. For even the one area it does monitor, wear level, there is no proof that their algorithm is even close to accurate.

* Poor guess as there is a lot of write activity it could miss due to formats, dual booting, virtual machines using hardware I/O virtualization, or any other scenario where this program can't record even write.

It is a very poor guess* as the program needs to run from Day 1 until the end to give a decent estimate, but even then it isn't guessing on anything more than estimated write capability from the drive maker. So it is really guessing how many estimated writes your drive has left not its "health".

That was my issue. If you look at the screenshots it implies that this product is able to read deeply into the SSD health and give an accurate estimate of how long it would last. That isn't the case. For even the one area it does monitor, wear level, there is no proof that their algorithm is even close to accurate.

* Poor guess as there is a lot of write activity it could miss due to formats, dual booting, virtual machines using hardware I/O virtualization, or any other scenario where this program can't record even write.

Why would the program need to run from day 1? I think you are really mistaken on how this program (and an SSD) works. The SSD itself is recording everything it does. All this program does is interpret that back-log and calculate a date for you.

There is no such thing as "wear" on an SSD. There are no mechanical parts, so the only thing that resembles "wear" is the completed read/write cycles.

That program truly is spot on since the SSD will die as soon as you use up those read/write cycles. That's just the physical nature of NAND memory. On the contrary, a mechanical HDD dies when the headers break or some other component fails. It's hard to predict the death of an HDD because it can still function as it goes "down hill". Whereas an SSD doesn't show symptoms; it just dies.

You should probably read their website to clear up your thoughts:

http://ssd-life.com/eng/how.html

Why would the program need to run from day 1? I think you are really mistaken on how this program (and an SSD) works. The SSD itself is recording everything it does. All this program does is interpret that back-log and calculate a date for you.

There is no such thing as "wear" on an SSD. There are no mechanical parts, so the only thing that resembles "wear" is the completed read/write cycles.

That program truly is spot on since the SSD will die as soon as you use up those read/write cycles. That's just the physical nature of NAND memory. On the contrary, a mechanical HDD dies when the headers break or some other component fails. It's hard to predict the death of an HDD because it can still function as it goes "down hill". Whereas an SSD doesn't show symptoms; it just dies.

You should probably read their website to clear up your thoughts:

http://ssd-life.com/eng/how.html

I'm not sure I understand what you're saying...

Using the SSD (write cycles) causes wear on the drive. Every time you write to the drive you wear it out just a little more... They don't wear the same way mechanical HDDs do, but they wear nonetheless.

No, the program is not "spot on". I quoted their site earlier where they stated the drive only shows how many writes it has had at the moment they request it. The drive doesn't tell them when the first write occurred or how long it has been in use (so they have no way of knowing if the 45% "wear" on the drive occurred in 1 day or 10 years). They also admit that without this data their result is nothing more than an educated guess and can fluctuate as a result.

And as I said earlier, it only shows the drive's wear level really. It isn't representative of the drive's overall health as the screenshots imply.

I'm not sure I understand what you're saying...

Using the SSD (write cycles) causes wear on the drive. Every time you write to the drive you wear it out just a little more... They don't wear the same way mechanical HDDs do, but they wear nonetheless.

No, the program is not "spot on". I quoted their site earlier where they stated the drive only shows how many writes it has had at the moment they request it. The drive doesn't tell them when the first write occurred or how long it has been in use (so they have no way of knowing if the 45% "wear" on the drive occurred in 1 day or 10 years). They also admit that without this data their result is nothing more than an educated guess and can fluctuate as a result.

And as I said earlier, it only shows the drive's wear level really. It isn't representative of the drive's overall health as the screenshots imply.

Then how does the program display "Work Time"? I highly doubt that all these people have run this program before this thread was created. By your logic, everybody's work time would be 0 days in their screenshots. An SSD stores a log of what it does along with a time stamp. The program is only doing a simple calculation based on what it reads from the SSD. Nothing more, nothing less.

You still don't understand that with an SSD, health and wear level are the same thing. That is dictated by the read/write cycles, and that's it. It's very very simple.

You just need to look past your knowledge of how a mechanical HDD works, because the two are very different.

I just recently put an order in for an OCZ 120GB Vertex 3. Should be $180 after rebate.

Hope I don't regret it :/

I have that same one and it's blazing fast. I believe it's still the best rated SSD by a pretty large margin.

Be sure to update it to the latest firmware if possible. Sometimes it helps with stability and such.

  • 5 weeks later...

Bought my Kingston SNV425-S2 64GB SSD in September 2010.

January 2011

SSD is 4 months old

Health is 85%

Work time: 2 months, 6 days

Powered on: 229 times

September 2011

SSD is 12 months old

Health is 62%

Work time: 6 months, 1 day

Powered on: 578 times

"Your drive health is in good condition and according to current use, estimated lifetime is August 2020."

October 2011

SSD is 13 months old

Health is 59%

Work time: 6 months, 15 days

Powered on: 646 times

"Your drive health is in good condition and according to current use, estimated lifetime is April 2020."

November 2011

SSD is 14 months old

Health is 56%

Work time: 6 months, 28 days

Powered on: 709 times

"Your drive health is in good condition and according to current use, estimated lifetime is June 2020."

Just noticed that the new Intel SSD toolbox has its own drive life estimate.

Bought my Kingston SNV425-S2 64GB SSD in September 2010.

January 2011

SSD is 4 months old

Health is 85%

Work time: 2 months, 6 days

Powered on: 229 times

September 2011

SSD is 12 months old

Health is 62%

Work time: 6 months, 1 day

Powered on: 578 times

"Your drive health is in good condition and according to current use, estimated lifetime is August 2020."

October 2011

SSD is 13 months old

Health is 59%

Work time: 6 months, 15 days

Powered on: 646 times

"Your drive health is in good condition and according to current use, estimated lifetime is April 2020."

November 2011

SSD is 14 months old

Health is 56%

Work time: 6 months, 28 days

Powered on: 709 times

"Your drive health is in good condition and according to current use, estimated lifetime is June 2020."

that seems like awfully quick wear =S

Bought my Kingston SNV425-S2 64GB SSD in September 2010.

January 2011

SSD is 4 months old

Health is 85%

Work time: 2 months, 6 days

Powered on: 229 times

September 2011

SSD is 12 months old

Health is 62%

Work time: 6 months, 1 day

Powered on: 578 times

"Your drive health is in good condition and according to current use, estimated lifetime is August 2020."

October 2011

SSD is 13 months old

Health is 59%

Work time: 6 months, 15 days

Powered on: 646 times

"Your drive health is in good condition and according to current use, estimated lifetime is April 2020."

November 2011

SSD is 14 months old

Health is 56%

Work time: 6 months, 28 days

Powered on: 709 times

"Your drive health is in good condition and according to current use, estimated lifetime is June 2020."

Theres something wrong with that drive..

Heres mine.....

Intel SSDSA2M080G2GC (Fw: 2CV102M3)

Total/free size: 80.0GB / 8.3GB

Work time: 8591 hours (11 months, 27 days, 23 hours)

Powered on: 124 times

Trime: supported, enabled

Health: 99%

Estimated lifetime: 8 Years, 8 months, 9 days

(T.E.C. date - July 24, 2020)

Data writen, GB: 3254.4

http://online.hddlif...21d01151899001a

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The laptop in the bedroom is an Acer with i7-10510U CPU. Acer's website states they will not be upgrading it so I had little choice other than disable secure boot. I know next to nothing on these matters so hopefully it will be fine.
    • GitHub removes manual model selection from Copilot free and student plans by Karthik Mudaliar GitHub is removing the ability to manually select an AI model from its Copilot Free and Student plans, making its automatic routing system the default and only way to choose a model. This means users on these tiers will no longer be able to deliberately select a particular OpenAI, Anthropic, Google, or Microsoft model for a task. In its announcement, GitHub said Copilot Auto will dynamically choose what it considers the best model for each request. Free and Student accounts will retain access to models from multiple families, although the available selection will continue to depend on the restrictions attached to each plan. GitHub did not identify a fixed pool of models that Auto will always use, and its documentation warns that model availability can change over time. GitHub describes Auto as more than a random fallback system. On supported surfaces, its task-optimization technology evaluates the complexity of a request alongside real-time information about model health and availability. Straightforward prompts can be routed to faster and less expensive models, while more demanding coding tasks may be sent to higher-cost reasoning models. The company says this approach should reduce rate limiting, latency, and failed requests. Auto generally selects one model along natural prompt-caching boundaries rather than repeatedly switching models during a session, as GitHub found that mid-session changes increased costs without producing sufficient improvements in output quality. Users can still check which model generated a response. In Copilot Chat, the information appears when hovering over an answer, while Copilot CLI and the Copilot cloud agent display the selected model alongside their output. Auto is available in Copilot Chat, Copilot CLI, and the cloud agent, with the exact implementation and release status varying between supported development environments. The latest restriction follows several months of adjustments to Copilot’s individual plans. GitHub temporarily halted new Pro, Pro+, and Student subscriptions in April as it sought to manage demand and service reliability. It later introduced token-based billing and began gradually reopening individual-plan registrations on June 17. Alongside the picker change, GitHub is retiring the “Preview” label from Microsoft-developed models. It argues that the label is no longer necessary because Auto handles model routing and models are continuously updated behind the scenes.
    • Look up 'inflation' kid. Ask an AI for the numbers between both games.
    • Google reportedly set to lose two key Gemini and DeepMind researchers to Anthropic by Karthik Mudaliar Google is reportedly preparing to lose two more prominent artificial intelligence researchers, with Gemini contributors Jonas Adler and Alexander Pritzel planning to join rival AI developer Anthropic. According to a report from Bloomberg, both researchers are viewed internally as important contributors to Google’s flagship Gemini model family. Adler worked on Google’s AI coding efforts, while Pritzel was involved in the process used to train AI systems. Neither company has publicly confirmed the moves. The report also does not say when the researchers will formally leave Google or what positions they will hold at Anthropic. Training a large AI model requires decisions covering its architecture, data preparation, distributed computing infrastructure, and post-training methods that shape how the finished system behaves. Researchers with experience operating at the scale of Gemini are consequently difficult to replace quickly. Both Adler and Pritzel have previously contributed to Google DeepMind’s scientific research as well. They are listed among the authors of the company’s work on expanding AlphaFold protein-structure predictions across entire proteomes, alongside AlphaFold researchers including John Jumper. The reported departures arrive shortly after another important change within Google’s Gemini organization. Gemini co-lead Noam Shazeer is leaving Google for OpenAI, after returning to the search company in 2024 through its deal with Character.AI. Shazeer is particularly well known as one of the authors of the Transformer paper, whose architecture became the foundation for most modern large language models. Anthropic, meanwhile, has been recruiting recognizable figures from other leading laboratories. OpenAI co-founder and former Tesla AI director Andrej Karpathy joined Anthropic’s pre-training team in May. His move, followed by the reported recruitment of several Google researchers, suggests Anthropic is strengthening the research teams responsible for the core capabilities of future Claude models rather than concentrating solely on product and enterprise sales. The competition is complicated by the companies’ extensive commercial relationships. Anthropic competes directly with Google’s Gemini models, but it also relies on Google as an infrastructure partner. In April, Anthropic announced an expanded agreement with Google and Broadcom covering multiple gigawatts of next-generation Tensor Processing Unit capacity. TPUs are Google-designed accelerators used to train and run large AI models. via Bloomberg
  • Recent Achievements

    • One Year In
      Philsl earned a badge
      One Year In
    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
  • Popular Contributors

    1. 1
      +primortal
      461
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      124
    4. 4
      Michael Scrip
      79
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!