Whats the status of your SSD?


Recommended Posts

Nope, the most stable one would be Samsung, I had 1 X25-M G2, 1 Kingston-branded X25-M G1 and 1 X25-E failing on me. Intel doesn't hold the record for having the most reliable SSD, Samsung does...

You had 3 SSDs failing on you? Now, that's what I call bad luck.

Nope, the most stable one would be Samsung, I had 1 X25-M G2, 1 Kingston-branded X25-M G1 and 1 X25-E failing on me. Intel doesn't hold the record for having the most reliable SSD, Samsung does...

Be interesting to see how a Samsung SSD does on this test, nobody has posted one yet...anyone got a Samsung?....

Be interesting to see how a Samsung SSD does on this test, nobody has posted one yet...anyone got a Samsung?....

Here you go:

Samsung 64GB SLC SATA II (MCCO*) installed on my X61 tablet. I bought it in 2007 and it is still running strong.

Next one is Samsung 256GB PB22J installed in my desktop (bought it in 2009).

The next one is Intel G1 80GB installed in my X200 tablet (bought it in 2009).

The last one is the most recent Kingston-branded G2 80GB installed in my X201 (I sent in my G1 to Kingston for repair and they sent me back this one in 2010).

post-120462-0-11707400-1296222088.png

post-120462-0-49471700-1296222104.png

post-120462-0-74047900-1296222191.png

post-120462-0-88966000-1296222226.png

Here you go:

Samsung 64GB SLC SATA II (MCCO*) installed on my X61 tablet. I bought it in 2007 and it is still running strong.

Next one is Samsung 256GB PB22J installed in my desktop (bought it in 2009).

The next one is Intel G1 80GB installed in my X200 tablet (bought it in 2009).

The last one is the most recent Kingston-branded G2 80GB installed in my X201 (I sent in my G1 to Kingston for repair and they sent me back this one in 2010).

Shame you Haven't run the 3rd (Intel G1) one as long as the Samsungs, would have made for a good comparison, the Intel G1 has had as many power ons but not as much run time, tho I'd say it probably still looks best out of the 4.

I don't know if power ons or run time do more damage...

I don't know if power ons or run time do more damage...

Neither should do much in terms of the SSD lifetime unless the PSU is surging during power up.

It's usually the number of write cycles that can do it, each flash cell has a finite number of write cycles it can sustain.

I think it's that drives that use SLC flash rather than MLC can sustain a higher number of write cycles but I might be wrong.

Shame you Haven't run the 3rd (Intel G1) one as long as the Samsungs, would have made for a good comparison, the Intel G1 has had as many power ons but not as much run time, tho I'd say it probably still looks best out of the 4.

I don't know if power ons or run time do more damage...

I bought the 2 x Intel G1 later than the Samsung 64GB and one of them craps out first. What does it tell you ? Intel SSD is not reliable...

Neither should do much in terms of the SSD lifetime unless the PSU is surging during power up.

It's usually the number of write cycles that can do it, each flash cell has a finite number of write cycles it can sustain.

I think it's that drives that use SLC flash rather than MLC can sustain a higher number of write cycles but I might be wrong.

But the SLC has a very early-stage controller so the write-leveling is not as good. Also the Intel one craps out because of the controller ... You can do all these flashy MTBF calculation but it is usually the controller that fails before the flash ...

I bought the 2 x Intel G1 later than the Samsung 64GB and one of them craps out first. What does it tell you ? Intel SSD is not reliable...

It tells me that you were very unlucky with drives.

apart from your I havn't heard of many problems with intel drives, and most of the posts in the thread have been for Intels, all so far good.

Not saying Samsung is bad, we use them at work for some very high end kit.

but I think you've just had bad luck with the Intels.

But the SLC has a very early-stage controller so the write-leveling is not as good. Also the Intel one craps out because of the controller ... You can do all these flashy MTBF calculation but it is usually the controller that fails before the flash ...

Yeah that doesn't surprise me, what controllers do the Samsungs have? indilinx or sandforce?

It tells me that you were very unlucky with drives.

apart from your I havn't heard of many problems with intel drives, and most of the posts in the thread have been for Intels, all so far good.

Not saying Samsung is bad, we use them at work for some very high end kit.

but I think you've just had bad luck with the Intels.

Yeah that doesn't surprise me, what controllers do the Samsungs have? indilinx or sandforce?

No, Samsung develops its own controllers. It is actually quite good, even for the 1st generation...

Whoa... after browsing this thread, it makes me think twice before buying an SSD :/ seriously

ive been using my 30GB OCZ Vertex for nearly 2 years and it's fine. However, i just had TWO Hitachi 1TB hd's die on me in a single month. both were <1.5yrs old.

This one has only been in the computer I did the reading on for just over four months. It started out back in Nov 2009 in my laptop (laptop went away), however, the SSD got transferred into my HP. So the use time is probably closer to eight months (actual use).

No, Samsung develops its own controllers. It is actually quite good, even for the 1st generation...

Ah ok, I'll look into them, should be getting a bonus in Feb pay packet so I think it'll go on the SSD and a new graphics card. :D
  • 2 months later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • No, size is not the only selling point. I did not even remotely say that. Your claim was that "building your own will be faster and cheaper". This is false. You cannot build something close to that form factor with off-the-shelf parts. You can build a Mini-ITX PC and pay more, or something larger and pay less. But these are different market segments. It's apples and oranges.
    • There is a default resolution setting in Settings > Display that can be changed with a click. You can also change the settings on a per-game basis. No CLI needed. Also, Steam has countless games that are not "[perpetual] alpha/beta games", so no need for the straw man. Plus you can use other stores as well. And console games (e.g. PS5) cost a fortune, which itself more than negates the price subsidy on the system, unless you plan on exclusively playing 1 or 2 games. It's true that you shouldn't buy a system that doesn't support the game(s) you want to play, but I think that's kinda obvious, and applies to every console as well as PC. I don't game in the living room and have no need of a Steam Machine, but there is a clear market segment that would find it useful.
    • RSS Guard 5.2.0 by Razvan Serea RSS Guard is a simple (yet powerful) feed reader. It is able to fetch the most known feed formats, including RSS/RDF and ATOM. It's free, it's open-source. RSS Guard currently supports Czech, Dutch, English, French, German, Italian. RSS Guard will never depend on other services - this includes online news aggregators like Feedly, The Old Reader and others. RSS Guard is developed on top of the Qt library and it supports these operating systems: Windows GNU/Linux OS/2 (eComStation) Mac OS X xBSD (possibly) Android (possibly) other platforms supported by Qt The core features of RSS Guard are: support for online feed synchronization via plugins, Tiny Tiny RSS (from RSS Guard 3.0.0). multiplatform, support for all feed formats, simplicity, import/export of feeds to/from OPML 2.0, downloader with own tab and support for up to 6 parallel downloads, message filter with regular expressions, feed metadata fetching including icons, simple Adblock functionality, customized popup notifications, Google-based auto-completion for internal web browser location bar, ability to cleanup internal message database with various options, enhanced feed auto-updating with separate time intervals, multiple data backend support, SQLite (in-memory DBs too), MySQL. is able to specify target database by its name (MySQL backend), “portable” mode support with clever auto-detection, feed categorization, drap-n-drop for feed list, automatic checking for updates, ability to discover existing feeds on websites, full support of podcasts (both RSS & ATOM), ability to backup/restore database or settings, fully-featured recycle bin, printing of messages and any web pages, can be fully controlled via keyboard, feed authentication (Digest-MD5, BASIC, NTLM-2), handles tons of messages & feeds, sweet look & feel, fully adjustable toolbars (changeable buttons and style), ability to check for updates on all platforms + self-updating on Windows, hideable main menu, toolbars and list headers, KFeanza-based default icon theme + ability to create your own icon themes, fully skinnable user interface + ability to create your own skins, “newspaper” view, plenty of skins, support for "feed://" URI scheme, ability to hide list of feeds/categories, open-source development model based on GNU GPL license, version 3, tabbed interface, integrated web browser with adjustable behavior + external browser support, internal web browser mouse gestures support, desktop integration via tray icon, localizations to some languages, Qt library is the only dependency, open-source development model and friendly author waiting for your feedback, no ads, no hidden costs. RSS Guard 5.2.0 changelog: Added: Feed auto-fetch can now also be delayed while Feral GameMode is active on Linux and startup auto-fetch is skipped when GameMode is already active. (#2265) WebEngine builds can now use RSS Guard generated proxy auto-config (PAC) rules so article/web browsing follows per-account and per-feed proxy settings more closely. (#2273) Generated PAC rules now also cover related subdomains and use Public Suffix List data, so feeds such as feeds.bbc.co.uk can also proxy resources from images.bbc.co.uk. (#2273) Standard feeds can now define extra proxy domains, useful when article images, stylesheets or other page resources are loaded from a CDN or another domain that should use the same feed proxy. (#2273) RSS Guard now asks for proxy credentials when a WebEngine page needs proxy authentication and can fill credentials from the current feed proxy when available. (#2273) Network settings again include an option to ignore all cookies, which clears stored cookies and prevents new cookies from being accepted. Standard RSS/ATOM feeds can now individually ignore cookies while downloading feed data. Stored cookies can now be deleted from the Tools menu. Custom skin colors can now override the feed list article count color separately from feed titles, including a separate highlighted color. (#2275) Settings dialog can now search across available settings and highlight matching controls. (#1754) Standard RSS/ATOM feeds can now optionally be reported as broken when they are valid but contain no articles. (#2039) Standard RSS/ATOM feeds can now override the application-wide feed connection timeout per feed. (#1023) Tray icon can now use a custom background color and unread-count text color, with an option to reuse the generated icon as the application icon. (#1973) Support for more benevolent parsing of Gemlog entries (#2295). Article list can now show when an article was received by RSS Guard. (#947) Feed deep discovery now actually scrapes all links found in the website and checks if they are feeds or not. This greatly enhances usability of the deep discovery mode and discovers many more feeds than before. (#2306) Search boxes now show a small dot when the feed or article list is hiding some items because of active filtering. (#873) Articles now have a shortcut-assignable action to open the homepage of the feed they belong to. (#2060) Fixed: Parallel feed updates no longer crash when multiple update results are processed at the same time. (64cf521) Links in WebEngine articles opened from feeds such as Kill the Newsletter now open correctly instead of being swallowed by the embedded page. (#2272) Relative article URLs resolution was kinda broken. (#2282) Clicking article URL did not work when the URL had "fragment" set. (#2293) The default proxy setting now uses Qt/system default proxy behavior instead of forcing no proxy. (e0263ad) WebEngine article loading now keeps the current feed context, so feed-specific proxy credentials remain available while the article page loads. (fdd0f00) Download: RSS Guard 5.2.0 (64-bit) | Portable | ~ 130.0 MB (Open Source) Link: RSS Guard Home Page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • This is gonna separate the creeps from the rest of the crowd.
  • Recent Achievements

    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      461
    2. 2
      +Edouard
      161
    3. 3
      PsYcHoKiLLa
      110
    4. 4
      Michael Scrip
      83
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!