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

    • Thank you for the feedback! I updated the image
    • Hmm wonder if I can share/resell the 'physical' edition like I can now.
    • Movavi Video Editor Plus 26.18.0 by Razvan Serea With Movavi Video Editor Plus, you can either enhance your video files with two or three simple steps, or turn them into something completely new. Create your own movies using multiple filters, transitions, and special effects: show multiple videos on one screen with the Picture in picture effect or change the background with the Chroma Key effect, imitate the camera zoom or make your video look like an old-style movie. Adjust video parameters such as brightness, contrast and colors. Stabilize shaky footage, improve video quality and remove defects. Create video presentations, tutorials or educational videos: add titles and record your own narration to create a video with voiceover. Import video from any source: TV-tuner, webcam, camcorder, or VHS. Drop multiple media files onto a timeline and let your imagination do the rest! Features at a glance: Video and audio editing on a timeline Edit, enhance videos Add background music Apply titles and effects Image quality improvement Hollywood-worthy effects High-grade titles and fades Digitize VHS tapes, record video from TV tuners Stabilize any shaky sections Support for a wide range of formats Prepare your videos for uploading to YouTube, Facebook, Vimeo, or any other website New in Movavi Video Editor 2026: 30+ fresh subtitle styles. Upgrade your automatic captions with new designs. Customize your text in the Styles tab with a single click. Optional advanced settings are also available in the dedicated Design tab. Subtitles in English – instantly! Translate auto-subtitles into English with a click – no dictionaries or online services needed. Once translated, configure and fine-tune the subtitles using the standard editing tools. 40+ adjustable effects. Enhance your videos in a click with new realistic effects – from dust particles and light leaks to retro-style and VHS. Every effect is fully customizable – so it will fit any clip perfectly and bring an extra spark to your edits. Ultra-fast playback. Show more in less time with video speed control of up to 100x. Perfect for epic time-lapses, long process recaps, or whenever you want to add some extra energy to your content. Magnetic zones are marked with dots, and the 1x value is indicated by a vertical line. Silence removal – in a click. Cut out unwanted pauses automatically or fine-tune the pause length and volume threshold yourself. Skip the tedious cleanup and make your videos more dynamic. Fast effect copying. Effortlessly duplicate any effect from one video to another: click Clip effects in the dropdown menu and proceed to copy or paste. Movavi Video Editor Plus 26.18.0 changes: This version includes small improvements for better editing. Download: Movavi Video Editor Plus 26.18.0 | 2.7 MB (Shareware) View: Movavi Video Editor Plus Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • JBL BAR 800 5.1.2 Dolby Atmos soundbar is an amazing deal today by Sayan Sen This Amazon Prime Day 2026 sales so far we have had a couple of nice deals related to sound and audio. First we have the Sennheiser HD 600 at its lowest ever price of just $225. Next we also have the Beats Studio Pro at its lowest price ever at just $150. However perhaps you prefer your gear to sound great on a larger scale, like throughout the room. In that case an all-in-one soundbar system can help and currently JBL's BAR 800 is a great deal for sure as it's up for grabs at just $600 (purchase link under the specs table down below). One thing that should be appreciated a lot about these JBL soundbars is their spec sheet and the frequency response data it provides. The firm is honest about it as JBL confirms the subwoofer is able to go down to 35 Hz at -6dB or F6. This means it should be covering 40Hz and up very well, where most of the bass lies. You miss out on a lot of sub-bass but that is to be expected given the price point and the subwoofer driver size. Speaking of which, it is a 10-inch driver and promises a max output power of 300 watts at 1% THD (total harmonic distortion). JBL also claims the system will provide you with a "True Dolby Atmos" experience. The surround speakers are wireless and battery-powered which means setting them up should be really convenient. The technical specs of the JBL BAR 800 are given in the table below: Specification Value Channel Configuration 5.1.2-channel soundbar system Dolby Atmos Yes, with 2 up-firing drivers Total System Power Output 720 W Soundbar Power Output 340 W Surround Speaker Power Output 2 × 40 W Subwoofer Power Output 300 W Soundbar Drivers 3 × 46×90 mm racetrack drivers, 3 × 20 mm tweeters, 2 × 70 mm up-firing full-range drivers Surround Speaker Drivers 1 × 46×90 mm racetrack driver (each speaker) Subwoofer Driver 10-inch (260 mm) wireless subwoofer Frequency Response 35 Hz – 20 kHz (-6 dB) Audio Inputs Optical, Bluetooth, Chromecast built-in, AirPlay, Alexa Multi-Room Music (MRM), USB* HDMI Inputs 1 HDMI video input HDMI Output 1 HDMI eARC output HDCP Version 2.3 HDR Pass-Through HDR10, Dolby Vision Bluetooth Version 5.0 Wi-Fi Version 6, 6E Streaming Services Chromecast built-in, Apple AirPlay, Alexa MRM Get it at the link below: JBL Bar 800-5.1.2-Channel Dolby Atmos soundbar with Detachable Surround Speakers (Black): $599.85 (Sold and Shipped by Amazon US with Prime) Prime subscription can be cancelled within three business days. Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • Microsoft releases PowerToys v0.100.1, fixes a bug that made remapped keys misbehave by Ivan Jenic Microsoft just released PowerToys v0.100.1, a patch update that addresses several stability and behavior issues found in v0.100.0. The v0.100.0 patch was a significant update for PowerToys, as it introduced all sorts of new features and additions, such as a rebuilt Shortcut Guide, a Command Palette Extension Gallery, webcam overlay support in ZoomIt, and more. However, the v0.100.0 version also introduced some bugs and stability issues. And now, Microsoft is addressing these issues in the new patch. The most impactful fix in this release perhaps is in Keyboard Manager, where remapped modifier keys were being delivered as system-key events, causing unexpected behavior in apps. The clearest example of this was Alt-to-Backspace remaps, deleting whole words instead of a single character. So, if you thought there was an issue with your keyboard, Microsoft just confirmed that it was PowerToys. Beyond the Keyboard Manager fix, v0.100.1 also addresses several other issues. It fixes a bug with Power Display that was preventing monitors from waking from standby correctly. Additionally, the new update patches Quick Access crashes on launch, and resolves a Shortcut Guide crash that occurred when switching between sidebar sections. Here’s the full changelog: Color Picker Fixed a bug where the main Color Picker window could appear inside the zoomed-in picker view Command Palette Fixed Run history initialization in AOT builds Fixed a bug where the Performance Monitor dock item could show ??? after restart Fixed the Hibernate command using the Sleep icon Limited the "pin to dock" dialog to displays where the dock is enabled Keyboard Manager Fixed modifier keys remapped to non-modifier keys being delivered as system-key events, which caused unexpected behavior in apps such as Alt-to-Backspace deleting whole words Power Display Fixed a bug where selecting On in the monitor power-state control did not wake a monitor from standby Fixed built-in display detection and brightness control on dual-GPU laptops where the internal panel is driven by the discrete GPU PowerToys Run Fixed VS Code Workspaces discovery after VS Code moved recently opened workspace data to shared storage Quick Access Fixed Quick Access flyout crashes caused by unhandled XAML exceptions during launch or page navigation Shortcut Guide Fixed a crash when navigating between Shortcut Guide sidebar sections Fixed number-key rendering in shortcut manifests and added a Postman shortcut manifest Updated bundled shortcut manifests to use the literal number-key token so number keys render correctly across apps ZoomIt Fixed a race condition in audio initialization for ZoomIt video recording You can download PowerToys v0.100.1 from the official GitHub releases page.
  • Recent Achievements

    • One Year In
      OHI Accounting earned a badge
      One Year In
    • First Post
      Almohandis earned a badge
      First Post
    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      122
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      74
  • Tell a friend

    Love Neowin? Tell a friend!