OCZ Releases First 1TB Laptop SSD

← Back to Stories (view on slashdot.org)

OCZ Releases First 1TB Laptop SSD

Posted by timothy on Thursday October 20, 2011 @10:24AM from the want-want-want-want dept.

Lucas123 writes "OCZ today released a new line of 2.5-in solid state drives that have up to 1TB of capacity. The new Octane SSD line is based on Indilix's new Everest flash controller, which allows it to reduce boot-up times by half over previous SSD models. The new SSD line is also selling for $1.10 to $1.30 per gigabyte of capacity, meaning you can buy the 128GB for about $166."

110 of 128 comments (clear)

Min score:

Reason:

Sort:

OCZ by hedwards · 2011-10-20 10:31 · Score: 1

Didn't they have reliability problems in the past? Am I wrong about that or have they finally fixed it?
1. Re:OCZ by Kjella · 2011-10-20 10:34 · Score: 5, Informative
  
  Supposedly the fixed one BSOD bug a few days ago. That wouldn't be with this controller anyway, but their record isn't spotless. Then again, Intel managed a SSD blemish too so... you're seeing an industry moving at breakneck speed, just make sure yours isn't on the line.
  
  --
  Live today, because you never know what tomorrow brings
2. Re:OCZ by __aardcx5948 · 2011-10-20 10:37 · Score: 1
  
  The problems with the Sandforce controller has been fixed. But yeah OCZ were in the SSD game early and had a few flaky firmwares in the wild. All is good now though.
3. Re:OCZ by blair1q · 2011-10-20 10:40 · Score: 1
  
  How do these things take to RAID configurations?
4. Re:OCZ by rhook · 2011-10-20 10:41 · Score: 1
  
  These drives are not Sandforce based. Did you even read the article?
  "The drive, based on the new Indilinx Everest controller, includes an "instant on" feature, that reduces boot times over previous OCZ SSDs by 50%."
5. Re:OCZ by kolbe · 2011-10-20 10:49 · Score: 2
  
  OCZ's reliability record is in no way different to any other Data Storage Manufacturer past or present.
  Seagate's recent 1TB woes: ST31000340AS
  Western Digital's recent woes: Caviar Green EARS 1.0TB and 1.5TB SATA
  Going further back, anyone who's been around in IT for a decade or longer recalls the old Micropolis 9GB drive failures that sent the company into bankruptcy. In any case, OCZ is a relatively good company and a notable innovator of SSD technology and I personally find most of their products to be just as reliable as any other in the same category.
6. Re:OCZ by silas_moeckel · 2011-10-20 10:49 · Score: 1
  
  Raid 0 1 and 10 are fine, raid 5 or 6 your quickly start getting the raid controller being the bottleneck, it's a whole lot of CPU grunt to do those calcs at a gigabyte or more a sec.
  
  --
  No sir I dont like it.
7. Re:OCZ by Sancho · 2011-10-20 10:52 · Score: 1
  
  I think that TRIM isn't supported in RAID5. Not sure about other RAID levels. I would expect that you'd be able to RAID1 just fine, though.
8. Re:OCZ by Kjella · 2011-10-20 10:58 · Score: 1
  
  You jumped from 1TB to 9GB, but forgot the biggest one in between. The IBM DeskStar aka DeathStar was a huge scandal and probably lead to them selling off the division.
  
  --
  Live today, because you never know what tomorrow brings
9. Re:OCZ by laffer1 · 2011-10-20 11:03 · Score: 1
  
  TRIM doesn't work with RAID, period. Most drives can work with RAID 0 or 1.
  
  --
  MidnightBSD: The BSD for Everyone
10. Re:OCZ by haruchai · 2011-10-20 11:04 · Score: 1
  
  Micropolis!! Haven't heard that name in 15 years! I sure hope OCZ doesn't suffer the same fate.
  
  --
  Pain is merely failure leaving the body
11. Re:OCZ by blair1q · 2011-10-20 11:04 · Score: 1
  
  Is there a chipset that does RAID 5 or 6 in HW?
12. Re:OCZ by iamhassi · 2011-10-20 11:13 · Score: 4, Informative
  
  10/17/2011 : After months of end user complaints, SandForce has finally duplicated, verified and provided a fix for the infamous BSOD/disconnect issue that affected SF-2200 based SSDs.
  
  wow, that's not something anyone wants to see, a bug in their hard drive. CPU I can replace, ram I can replace... pretty much everything I can swap out, but my hard drive is where everything is stored, I can't risk losing data because of a bug.
  
  Intel just had problems too that cause loss of data:
  "JULY 13TH, 2011 : Intel has recently acknowledged issues with the new SSD 320 series, where by repetitively power cycling the drives, some may become unresponive or report an 8MB drive capacity."
  
  I was waiting on an SSD until they worked out the bugs and there were no articles about problems for awhile but with stories like these I'll keep waiting, it's just not worth the risk.
  
  --
  my karma will be here long after I'm gone
13. Re:OCZ by kolbe · 2011-10-20 11:19 · Score: 1
  
  We all survived the 18GB Deathstar and avoided Fujitsu's sudden death syndrome and it further proves most have had their fair share of failures at one time or another. The only ones I cannot recall any fault with were Quantum and later Maxtor drives. I loved my Fireball and Atlas drives!
14. Re:OCZ by FyRE666 · 2011-10-20 11:31 · Score: 2
  
  Well my experience was that the issue wasn't fixed. I just returned one of these drives due to lockups, "disappearing drive" and random BSODs. This happened with a Corsair 120GB Force 3 SSD, but I know the OCZ drives are also affected. The issues have been going on for months.
  
  --
  Code, Hardware, stuff like that.
15. Re:OCZ by Anonymous Coward · 2011-10-20 11:34 · Score: 3, Insightful
  
  SSDs aren't meant/ready as a mass storage solution. They are a performance product aimed at system drives and portable devices -- situations where replacing them isn't a big deal data wise.
  Also. if you're storing data on one one drive you're an idiot no matter what kind of drive you are using.
16. Re:OCZ by Anonymous Coward · 2011-10-20 11:34 · Score: 1
  
  Miniscribe! Conner! Feel old yet?
17. Re:OCZ by silas_moeckel · 2011-10-20 11:35 · Score: 2
  
  It's not so easy they require reads to write. Say you have 5 drives that's 4 blocks of data and 1 block of parity info the OS has to be able to write out as little as a single block so you have to read 4 blocks then write out 5. In reality the stripe size is bigger than one block. Now the controller has to handle a pile of these at the same time, all real raid controllers do this in hardware. Not your el chepo motherboard built in raid but most of the add in cards over a couple hundred bucks. If you realy want to get more space on your ssd's try something like an adaptec 6q it does hot read and write caching, if your running linux dm-cache and similar will do the same thing. ioFusion and other have proprietary software to do this with there SSD's.in windows as well.
  
  --
  No sir I dont like it.
18. Re:OCZ by scalarscience · 2011-10-20 11:36 · Score: 1
  
  Maxtor had so many QA issues in their latter days that it contributed greatly towards the purchasing price that Seagate got when they bought them. Of course the CEO Bill Watkins promptly moved a huge bulk of the Seagate drive ops to the same plant (as a cost cutting measure it was presumed) that had issues for Maxtor and denied the 'bricking' issues that resulted for AS and ES series drives for at least 9 months... until the Seagate Board of Directors fired him and replaced him with the former CEO from 2004 (and subsequently addressed the firmware issues too.)
  
  I flashed all 3 of my ES.2's to SN06 'just in case' while all of this was underway, and though it was denied that they had issues in my serial # range quite a few reports cropped up down the line of ES.2's outside the reported serial range having problems also so I'm happy I did, they still run fine in an array to this day.
19. Re:OCZ by Cyberax · 2011-10-20 11:42 · Score: 5, Interesting
  
  Not so fast!
  You can use my https://github.com/Cyberax/mdtrim/ to periodically TRIM unused space on software RAID-1 on Linux (ext3/4 are supported right now).
  Extending it for RAID-0/5/6 is not hard, but right now I don't have time for this.
20. Re:OCZ by ShakaUVM · 2011-10-20 11:46 · Score: 1
  
  >>wow, that's not something anyone wants to see,
  There's been a LOT of "you lose everything" bugs in the SSD market up till now.
  Buying the latest and greatest is nice, but I like to wait until there's a couple hundred reviews of a product on Newegg before buying (filter at 1-egg level to see what can go wrong...)
21. Re:OCZ by kolbe · 2011-10-20 12:03 · Score: 1
  
  Weren't the problematic Deskstars in the 75GB+ range?
  IBM Deskstar 75GXP was the main one, yes. However, I think all of their hard drives at the time had similar issues revolving around the BLUE GLUE used to seal the canister
22. Re:OCZ by mikael · 2011-10-20 12:09 · Score: 1
  
  Remember that - happened to my workstation.
  Then my laptop hard disk drive (TravelStar) fried. Had to do the recommended trick of putting the disk drive in a freezer bag, chill it out, and give it a good whack on power-up. Managed to get one final incremental backup before it went up to the great server rack in the sky..
  
  --
  Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
23. Re:OCZ by sunderland56 · 2011-10-20 12:35 · Score: 1
  
  wow, that's not something anyone wants to see, a bug in their hard drive. CPU I can replace, ram I can replace... pretty much everything I can swap out, but my hard drive is where everything is stored, I can't risk losing data because of a bug.
  So, you're storing important data on a single drive with no backup? And you expect a typical rotating-magnetic hard drive to last forever and never fail?
  
  Studies show that, overall, long-term failure rates for SSD drives are *lower* than traditional hard drives.
24. Re:OCZ by dark_requiem · 2011-10-20 12:47 · Score: 1
  
  I've been using an OCZ Vertex 3 120GB since April. Throughout that time, their firmware releases have variously resolved certain bluescreen issues, while introducing others. Since installing 2.13, I have had major issues, and just last week was complaining that I would have to return the thing to OCZ and demand my money back. However, I installed 2.15 the day it was released, and all bluescreen issues have stopped.
  
  Through all that, I have never lost any data. I was rather panicked at first (the drive won't show back up after one of these bluescreens until you cold boot the machine), but once I realized I could recover with a cold boot each time, I was merely annoyed. That being said, I knew going in that SSDs in general weren't that mature a product, and that issues like this crop up. I would never have placed important data on those drives, and would have kept a backup even if I had. Just as I never put any important data on an HDD without a backup (or at least a bit of RAID action).
25. Re:OCZ by aztracker1 · 2011-10-20 13:06 · Score: 1
  
  I had a few 20GB IBM Death/DeskStar drives when they came out... raid-0, fast as sin at the time.. dead in 2 months, both of them.
  
  --
  Michael J. Ryan - tracker1.info
26. Re:OCZ by Runaway1956 · 2011-10-20 13:28 · Score: 2
  
  So - I'm wondering why, exactly, do people want to do RAID with SSD? There are really only two reasons (that I'm aware of) for a RAID. Either you need performance - which the SSD delivers, or you need redundant security for your data. Even in a corporate setting, it seems that running the OS and applications from from the SSD, while keeping data on RAID would be a good solution. Investing in enough SSD's for RAID arrays seems a bit of a waste.
  Servers, on the other hand, might make good use of SSD's in RAID arrays. I wonder if Google or Amazon are going that route yet? About the time that they both finish upgrading all of their servers to SSD RAIDs, the price of SSD's should be down where I can afford a terrabyte drive!
  
  --
  "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
27. Re:OCZ by Luckyo · 2011-10-20 13:28 · Score: 1
  
  It's worth noting that if you desperately need more speed, you should look at Revo line of OCZ's drives. Those are SSDs mounted in a cluster of four separate drives linked to a single raid 0 controller all on the same PCI-E card.
  The reason why I'm not touching that is that raid controller doesn't let TRIM commands through, so after a year or so, drive will slow down significantly. That said, at raid 0 and PCI-E interface, it will still smoke any and all SATA solutions.
28. Re:OCZ by Luckyo · 2011-10-20 13:33 · Score: 1
  
  In vast majority of cases, modern hard drive's SMART will start screaming its mechanical lungs out at you long before failure comes. Even if you ignore that, physical errors with the drive will often cause noise that will lead you to suspect that drive is failing. The "holy shit, it just died" failures are in minority.
  On the other hand, SSD dies like that in vast majority of times. Add to that unreliability of the new controllers (not the drive itself which is what you were talking about), and you get a perfect storm where SSD is easily an order of magnitude less reliable when it comes to not losing data.
  Personally, I really want a 60ish GB SSD for my OS and most used software, but I just can't justify a purchase with severe reliability issues that everyone seems to be having with both controllers and drives at the moment.
29. Re:OCZ by Luckyo · 2011-10-20 13:40 · Score: 1
  
  For the record, seagate's 7200.11 was the only instance of buggy controller in that line of drives. I have two of 7200.7 drives that clocked over 50.000 hours uptime in raid0 as OS drive pair with no issues (and hilariously, one raid controller failure), and I have several 7200.12 drives (including the warranty replacement drive for 7200.11 that had a controller bug mentioned on the TH.com). No problems.
  Problem with OCZ is that they do not have a proper solution for their clients' woes, and they don't send you a fixed drive if you ask for warranty replacement on ones that BSOD. That alone is a huge negative that stops me from getting SSD from them, in spite of really wanting one for an OS drive.
30. Re:OCZ by hawkinspeter · 2011-10-20 13:53 · Score: 2
  
  I seem to remember a while ago that google published stats on their hard disk failures and that SMART wasn't particularly useful in predicting failure times of drives.
  
  I've personally seen several drives fail with no warning whatsoever and that's without anything dramatic like a nearby electrical storm to fuse the drive controller. If you don't have your data replicated, then either you don't care about the data (easy to recreate) or you will eventually become wiser.
  
  --
  You're a temporary arrangement of matter sliding towards oblivion in a cold, uncaring universe
31. Re:OCZ by epine · 2011-10-20 14:08 · Score: 1
  
  Yes, IIRC, the Google report indicated that SMART murmured not a peep in about half of all failures.
32. Re:OCZ by nabsltd · 2011-10-20 14:13 · Score: 1
  
  TRIM doesn't work with RAID, period. Most drives can work with RAID 0 or 1.
  I just installed a pair of SSDs in RAID-1 using Fedora 15. I had searched far and wide to see if TRIM was supported, and didn't find anything conclusive, so I installed anyway, since I'm only using 16GB out of the 64GB drive (which means that even non-TRIM-aware wear-leveling would last 4 times as long). After I had installed, I did some more searching, and somewhere I found info that said the 3.0 kernels (which Fedora 15 uses, although renumbered to keep some apps from breaking) supported it. I didn't bookmark it, but I think it was part of the kernel mailing list.
  Based on the fact that /sys/block/[device]/queue/discard_granularity contains 512 for every device in the stack (LVM/dm -> md -> sd[ab]) and there are no warnings at mount time with ext4 using the "discard" option, I believe it. Also, for any device not on top of an SSD, "discard_granularity" is 0 and you get warnings at mount time if you try to use the "discard" option.
33. Re:OCZ by nabsltd · 2011-10-20 14:22 · Score: 2
  
  So - I'm wondering why, exactly, do people want to do RAID with SSD? There are really only two reasons (that I'm aware of) for a RAID.
  And both are as valid for SSD as they are for spinning disks.
  RAID-0 can turn SSDs from fast to insane (if you have the controller bandwidth). Any of the data-protection RAID levels will help if your drive-with-really-new-and-somewhat-untested-technology dies an untimely death.
34. Re:OCZ by Cyberax · 2011-10-20 14:37 · Score: 2
  
  It's not easy to implement it completely correctly, even in software. My approach is to create a large file which takes almost all free space, then TRIM its content and then just remove this file. Obviously, it's a bit racy if you have services which could suddenly need several more gigabytes of disk. On the other hand, TRIM-ing 160Gb SSD drives takes about 5 seconds, so I don't worry about it.
  Here is a thread about it on linux-raid: http://thread.gmane.org/gmane.linux.raid/31941/focus=32022
  As far as I know, there are no hardware RAIDs with TRIM support.
35. Re:OCZ by Just+Some+Guy · 2011-10-20 14:45 · Score: 2
  
  I was waiting on an SSD until they worked out the bugs and there were no articles about problems for awhile but with stories like these I'll keep waiting, it's just not worth the risk.
  You didn't think HDDs have similar dumb BIOS errors?
  
  --
  Dewey, what part of this looks like authorities should be involved?
36. Re:OCZ by kungfuj35u5 · 2011-10-20 15:18 · Score: 1
  
  A stripe would be glorious from a performance perspective. It would only take a few to saturate the bus to the CPU.
37. Re:OCZ by A12m0v · 2011-10-20 15:32 · Score: 1
  
  My SSD is only for the OS and most used Applications, everything else is stored on a network drive that is mirrored in 3 different machines. If my SSD buys the farm right now I will lose nothing of importance.
  
  --
  GENERATION 25: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
38. Re:OCZ by dbraden · 2011-10-20 15:40 · Score: 1
  
  Were you using the firmware update that was just released three days ago? I'm not being a dick, just genuinely curious.
39. Re:OCZ by ShakaUVM · 2011-10-20 15:43 · Score: 1
  
  >>My SSD is only for the OS and most used Applications, everything else is stored on a network drive that is mirrored in 3 different machines. If my SSD buys the farm right now I will lose nothing of importance.
  Me, too, actually, but going through the process of reinstalling Windows and my applications is something I'd rather avoid with a little bit of research.
  One of the SSDs I almost bought had a firmware bug which could very occasionally cause you to lose everything. The problem, though, was that patching the firmware also wiped the drive. Damned if you do, damned if you don't...
  I didn't buy that one.
40. Re:OCZ by tlhIngan · 2011-10-20 16:15 · Score: 1
  
  There's been a LOT of "you lose everything" bugs in the SSD market up till now.
  There's plenty of "you lose everything" bugs in spinning rust drives as well.
  From Western Digital drive failures that led to them being nicknamed "Western Digicrap", to IBM's Deathstar drives, Seagate's logfile one, etc.
  Every manufacturer has come up with a line of drives that proved to be lemons, and we're talking about very mature technology here - it's been around since the IBM RAMAC.
  SSDs are a game changer in that any idiot with a soldering iron and a few tools can build one in their garage - there's only a few controller chips out there from SandForce, Indilinx, J-Micron, Intel, and maybe a few others (Samsung, Toshiba, etc). And you buy the flash chips. Plop them on a board and you've made a storage deivce. Whereas hard drives require clean rooms, chemicals, mechanical engineering, etc.
  Here's a funny question. Apple's probably the largest consumer of SSDs on the market (for their Macs, not the ones that go into iPhones/iPods/iPads). Yet there doesn't seem to be much about SSD sudden failure or loss of data or other thing. I wonder why that is...?
  Perhaps it's the relative immaturity of the high-speed cutting edge SSDs and Apple goes for last-gen chips that give "good enough" performance and deliver on reliability?
41. Re:OCZ by Alamais · 2011-10-20 16:21 · Score: 1
  
  Yeah, I've had drives in my research group fail and lose a bunch of data, and then have their SMART kick in hours/days later while we're trying to recover what's left. Thanks a lot.
42. Re:OCZ by vaporland · 2011-10-20 16:27 · Score: 1
  
  i'm immune - i keep MY data in the cloud! :-p
  
  --
  Ask Me About... The 80's!
43. Re:OCZ by Joce640k · 2011-10-20 17:26 · Score: 2
  
  Just when their controller matures a bit they switch to a different one....?
  
  --
  No sig today...
44. Re:OCZ by ShakaUVM · 2011-10-20 17:26 · Score: 1
  
  >>There's plenty of "you lose everything" bugs in spinning rust drives as well.
  I can't recall the last time there was a firmware bug in a HDD that caused catastrophic loss of data... I can think of a couple RAID controllers, but nothing baked into the drives themselves. There's a lot of such problems in SSDs.
  I know it's a generalization, but HDDs tend to fail more gracefully (though SMART is by no means foolproof, don't get me wrong) whereas SSD failures are characterized by simply not working one day.
45. Re:OCZ by kmoser · 2011-10-20 17:34 · Score: 1
  
  Another reason: to be able to address the RAID as a single, contiguous (virtual) volume.
46. Re:OCZ by Wolfling1 · 2011-10-20 17:36 · Score: 1
  
  I ran an OCZ 60GB SSD in my desktop until I ditched it for a laptop. It fully KICKS ASS. I did Windows XP and Windows 7 startup comparisons (seemed to be the easiest 'controlled' test). The SSD on a clean/fresh/fully patched install on WinXpSP3 or Win7 (not SP1 at the time) was four times faster than a conventional drive. And that is including the POST.
  
  To be more specific, my test was 'power on to an open Windows Explorer displaying a network drive directory'.
  
  On a traditional drive (200Gb Seagate Barracuda), Win 7 did it in roughly 60 seconds - whereas the SSD did it consistently in under 15.
  
  Over a 12 month period, the SSD performed flawlessly.
  
  The only reason I have discontinued using it is the switch to a lappie, and the need for more drivespace in a single drive. I'll upgrade to a 500Gb SSD as soon as the price is a bit more tolerable.
47. Re:OCZ by Anonymous Coward · 2011-10-20 18:56 · Score: 1
  
  Google's analysis (which someone else mentioned) is correct here -- SMART will generally not trip the overall SMART health status from OK to FAIL. Why doesn't this happen sooner? Because the vendors themselves are the ones who decide the thresholds for when an attribute goes from OK/good to FAILING/bad. On most drives -- consumer-grade and "enterprise-grade" (yes, BOTH!) -- the thresholds are set to the point where the drive will have already experienced so many failures that the end-user notices it as I/O operations which either time out, return EIO, or ENXIO (drive falling off the bus).
  It's important to remember that SMART attributes VALUE, WORST, THRESH metrics are all calculated based off of proprietary formulas which are not disclosed. The same applies to the RAW_DATA section (64-bits of data which can be encoded in any format the vendor chooses -- this is why you can't read RAW_VALUE and assume it's a 1:1 number ratio. It's not, especially on Seagate drives; "oh my god, Hardware_ECC_Recovered is 84384928! My drive is failing!" "No it isn't, it's perfectly normal, the data is encoded in a proprietary format" "Oh."). These formulas and encoding methods absolutely vary per vendor, but quite often also vary per drive model. T13/ATA specification also does not cover any of this; the vendors are given free reign to decide what's what.
  I'd provide an example of SMART data taken from a Western Digital WD2001FASS-00U0B0 disk, but, well, see my last line...
  Out of all the attributes, approximately 90% of them have THRESH set to 000. Focusing on SMART attribute 197 (which indicates how many suspect LBAs there are -- these are LBAs which the drive, during read operations, has to do repetitive reads or auto-correct with ECC to get valid data from (excessively), so it marks them as unreadable until they can be re-examined (by submitting a write to that individual LBA)), the VALUE of a good/clean drive is 200, and WORST is also therefore 200. The drive is in perfect shape.
  Now let's pretend RAW_VALUE increases to 1 (meaning on this model of drive, there is 1 suspect LBA). What should VALUE become? Nobody knows; not even Bruce Allen knows. Because vendors have proprietary formulas that calculate what VALUE should be (calculated/adjusted based on how many counts anomalous behaviour here are), we have no idea if 1 suspect LBA should diminish VALUE from 200 to 199 or not. Will it? No, it won't. So at what point would this happen? It's hard to say for certain, but I estimate around 300 LBAs being marked suspect would cause the drive to drop VALUE down a bit. Meaning: it will almost certainly never reach THRESH.
  The "overall SMART health status" value, which tells people "your drive is good" vs. "your drive is bad" will therefore never state the latter. So why do vendors pick such outrageous THRESH values? You should already know the answer to that -- because being too aggressive means higher RMA rates, which means more returns, which means loss in revenue and decrease in cash flow, which means a drop in stock price. Yup, it's that simple.
  Readers of this post will almost certainly state "so SMART is worthless, I knew it! Fuck SMART!" No, SMART is actually extremely useful, just not for immediate detection of a drive failure. It's extremely useful for *diagnosis* if you think your hard drive is experiencing issues. I help on average ~10 Internet users a month get their hard disks into a working state (or recommend RMA) using SMART, in addition to a series of manual tests (something similar to Bruce Allen's bad-block-howto, but much easier to understand -- that document does not read well and is also filled with some mistakes).
  Takeaway points:
  * SMART is a really great thing to have, but the viewer of the data needs to become familiar with how to read SMART data, and how to understand the data that's being shown to them.
  * SMART is absolutely a necessity for diagnosing problems with a drive, especially those which are not of a physical nature (e.g. actuat
48. Re:OCZ by dropadrop · 2011-10-20 19:20 · Score: 1
  
  I think just about everyone had reliability problems with Sandforce based drives, but as OCZ was one of the closest partners to Sandforce they have generally released drives before others; often containing older firmware with more bugs.
  It does seem their QA process is not especially robust looking at their track record though, where ever the problem is, you would think they would pick it up and delay shipment until it's fixed (especially seeing how widespread they where).
49. Re:OCZ by AmiMoJo · 2011-10-20 19:37 · Score: 1
  
  I have an older Intel SSD (160GB XM25) and have already had it replaced under warranty once because it ran out of spare sectors. Looking at the spec it is rated for about 17TB of writes, and the SMART attributes report 650GB of writes after a few months of use.
  At the time I bought it the expected life time was supposed to be at least 5 years, and I only put the OS and apps on it (data is on a traditional HDD). It looks like I will just have to do another warranty claim next year, and them when the warranty has expired get a partial refund (Sale of Goods Act) and buy a replacement. Very annoying, especially since the performance is fantastic and otherwise I am very happy with it.
  
  --
  const int one = 65536; (Silvermoon, Texture.cs)
  SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
50. Re:OCZ by dbIII · 2011-10-20 20:19 · Score: 1
  
  I've been paranoid about mine (sync to other drives every hour) but apart from the annoyance of successive 120GB models not being the same size they've been OK so far (Vertex and Vertex2).
  Setting up a couple of striped disks took three attempts before I got something with good read and write speeds. You know when you've got the wrong stripe size because it ends up being noticably slower than a mechanical disk.
51. Re:OCZ by ttong · 2011-10-20 20:46 · Score: 1
  
  That's what Logical Volume Management its friends are for.
52. Re:OCZ by TheRaven64 · 2011-10-20 22:27 · Score: 1
  
  Not to mention Maxtor's 20GB and 40GB drives. Out of about 20 of those bought over a period of a year (so not just one bad batch), none lasted more than two years and most died in under one.
  
  --
  I am TheRaven on Soylent News
53. Re:OCZ by FyRE666 · 2011-10-20 22:28 · Score: 2
  
  Well I had used the firmware available on the same day this article was posted. I returned the drive on that day, after it still failed to fix the issues. I had tried the drive on 2 different machines with different motherboards, and in each case the problems occured in the same way when the drive was used. There are plenty of other people on the forums who have had the same experience so basically I had no faith whatsoever in the Sandforce controller-based SSDs. I've bought several in the past - my gaming rig has a RAID(0) setup with the OCZ SSDs, and it experiences random lockups as one or other drive disappears. On the gaming rig the problem seems less frequent, and as it's just used for games it isn't so much of an issue - although I'll be replacing them soon.
  
  --
  Code, Hardware, stuff like that.
54. Re:OCZ by Cyberax · 2011-10-20 23:16 · Score: 1
  
  Try my https://github.com/Cyberax/mdtrim/ , we use it to periodically TRIM empty space. Works fine with md RAIDs on raw devices, it won't work with LVM though.
  Unfortunately, RAID on stock md devices does NOT work, even if LVM/dm TRIM works. You won't get any warnings from ext4, TRIM just silently won't work because md doesn't pass through TRIM requests. There's a thread (dated August of this year) on linux-raid where md maintainer says that TRIM is not his priority.
55. Re:OCZ by Cyberax · 2011-10-20 23:20 · Score: 1
  
  Keeping OS on SSDs doesn't make any sense in for server applications. You don't need to worry about boot speed and all your code is usually in RAM anyway.
  However, databases and SSDs are a natural fit. We accelerated our server code more than 10 times just by moving it to SSDs. And since we're storing critical data, RAID-1 are a must (backups are the last resort - you inevitably lose some data if you have to restore from backups).
56. Re:OCZ by sentimental.bryan · 2011-10-20 23:26 · Score: 1
  
  Supposedly the fixed one BSOD bug a few days ago. That wouldn't be with this controller anyway, but their record isn't spotless. Then again, Intel managed a SSD blemish too so... you're seeing an industry moving at breakneck speed, just make sure yours isn't on the line.
  Using OCZ 8 months now. I tend not to get BSOD's on Linux anyhow.
57. Re:OCZ by Luckyo · 2011-10-21 00:21 · Score: 1
  
  You have a good point. I made it a habit to quickly check some important statuses of drives through gsmartcontrol, usually parts like reallocated sector counts and other pre-failure marked parts every couple of months. Essentially parts that show that drive is starting to really suffer from wear and tear, and I should pay more attention to backing it up and probably replacing it sometime soon.
  I tend to do that long before it trips the threshold set on the drive because I know that those are artificially high.
58. Re:OCZ by amorsen · 2011-10-21 01:46 · Score: 1
  
  The best RAID accelerators are sold by Intel and AMD under the brand names "Xeon" and "Opteron"...
  
  --
  Finally! A year of moderation! Ready for 2019?
59. Re:OCZ by amorsen · 2011-10-21 01:57 · Score: 1
  
  Quantum had their share of troubles. The Bigfoot drives would once in a while need a good kick to the side to get going again.
  
  --
  Finally! A year of moderation! Ready for 2019?
60. Re:OCZ by gstrickler · 2011-10-21 03:13 · Score: 1
  
  SMART hasn't predicted a single one of the HD failure's that my client's or I have experienced. SMART is useful, but not at a predictor of failure.
  
  --
  make imaginary.friends COUNT=100 VISIBLE=false
61. Re:OCZ by petermgreen · 2011-10-21 03:54 · Score: 1
  
  I seem to remember a while ago that google published stats on their hard disk failures and that SMART wasn't particularly useful in predicting failure times of drives.
  I've read that study. The trouble with it is that it doesn't distinguish types of failure. As far as that study is concerned a drive that died completely, a drive that developed the odd unreadable sector and a drive that dropped out of a raid despite testing out fine as an individual disk are all "failures".
  
  --
  note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
62. Re:OCZ by tlhIngan · 2011-10-21 03:55 · Score: 2
  
  I can't recall the last time there was a firmware bug in a HDD that caused catastrophic loss of data... I can think of a couple RAID controllers, but nothing baked into the drives themselves. There's a lot of such problems in SSDs.
  I know it's a generalization, but HDDs tend to fail more gracefully (though SMART is by no means foolproof, don't get me wrong) whereas SSD failures are characterized by simply not working one day.
  Seagate was the most recent one - depending on how you rebooted your PC, it could just up and not show up. It was traced to a logfile bug - if the logfile reached a multiple of N, the next reset would hang the drive unless you cleared it manually. Heck, there are stupid firmware bugs in optical drives as well (I remember a Fedora release that killed drives merely because LG decided to use a common command as "firmware update").
  And anyhow, blaming SSD problems on firmware is disingenous compared to hard drives - in an SSD, practically the only reason it dies prematurely are due to firmware bugs. A hard drive can fail is more ways that firmware errors are but a small part of the failure modes.
  IBM's death star was due to using platters that weren't certified for the data density (an error when testing the platters).
  And as I mentioned before, Apple buys and sells more SSD-equipped computers than anyone else (mostly Macbook Airs, but a few Pros are preconfigured with SSDs as well). They've sold enough that if there was a genuine SSD problem, it would've been big news. I don't know exact figures, but Apple would've shipped millions by now.
  If you avoid the cutting edge super-high-performance SSDs, then you really ought to be fine, like Apple. They're not the fastest (still getting transfers around 150MB/sec rather than 250MB+/sec these new SSDs get), but they work reliably.
  The only reason you may get warnings with hard drives is when they're failing mechanically. They can still up and die suddenly (usually more due to mechanical issues, but like Seagate, they can die due to firmware), especially if something happens that corrupts the on-disk firmware (hard drives "boot" from the platters - there's a bit of firmware that's just capable of spinning up the drive and seeking to the right spot in order to load the real drive firmware).
63. Re:OCZ by tlhIngan · 2011-10-21 04:05 · Score: 1
  
  Just when their controller matures a bit they switch to a different one....?
  Of course, because for some reason, these guys are making SSDs that push the performance envelope. There seems to be a big vacuum of "slower but stable" drives as everyone is racing to try to get 1GB/sec transfer speeds.
  Then again, Apple probably is soaking up all the "slow, solid, reliable" SSDs. Plenty of computers and plenty of users who can get by with a slower drive that still does 150MB/sec - most of the speedup comes from the fact that random I/O on an SSD is an order of magnitude or more faster than a hard drive (most hard drives can only do just over 100 I/O a second. An SSD can do over 1000, and 10,000 is pretty common for a "slow" drive).
  It just makes general day-to-day use snappier.
64. Re:OCZ by Cute+Fuzzy+Bunny · 2011-10-21 04:25 · Score: 1
  
  Most current drives will do their own garbage collection during idle time. So once a week, log out of windows (or whatever) and let it sit for 20-30 minutes. It'll be all good after that.
65. Re:OCZ by Cute+Fuzzy+Bunny · 2011-10-21 04:28 · Score: 1
  
  Oh and yes OCZ is STILL having problems with their drives. I just bought a 60gb vertex plus drive, and it corrupts data regularly, forcing windows to do a chkdsk on boot almost every time. They have a new 3.5 firmware out, but it still seems to be problematic for some users. OCZ also does not recommend loading image backups to their drives, suggesting that if you dont do a secure erase (which requires a cd/usb boot and a stripped machine with no other drives in it) and a regular windows install then your drives may experience corruption.
  Now if this were 1982 and that requirement came with a storage product...well...I'd still think it was stupid.
  But even though it was a fairly well known problem and not a hardware issue, OCZ happily allowed many of their customers to pay $12 out of their own pocket to ship their perfectly good hardware with bad firmware to them so they could send back a used/refurbished drive with the same bad firmware on it. Nice of them...
66. Re:OCZ by vetman · 2011-10-21 05:10 · Score: 1
  
  I though RAID 5 was 2 blocks XOR'd for parity to a 3rd block regardless of how many drives are in the array. Therefore 1 block write only requires 2 blocks read (2 data) and a 2 block write minimum(1 xor & 1 data), 3 block maximum(1 xor & 2 data). RAID 6 increases the XOR storage block to another drive equals a 4 block maximum. Subsequent blocks of data and xor(s) are rotated through the drive set so that parity blocks are never aligned to a single drive (RAID 3).
67. Re:OCZ by Luckyo · 2011-10-21 05:40 · Score: 1
  
  I obviously do not know who "your client" is so I cannot address the issue, but for a knowledgeable home user maintaining his own and his family/friends machines, it certainly does.
68. Re:OCZ by ShakaUVM · 2011-10-21 06:05 · Score: 1
  
  >>If you avoid the cutting edge super-high-performance SSDs, then you really ought to be fine
  Which is basically what I said. I finally bit the bullet, imaged my drive, cloned it over to an SSD, but only after carefully going through all the 1-Egg reviews on Newegg for the models I was interested in, and avoided the ones that had the catastrophic failure bugs.
  >>in an SSD, practically the only reason it dies prematurely are due to firmware bugs
  Well, and when it runs out of writes, I guess. Though you'll be able to detect that well in advance of the limit.
69. Re:OCZ by Coren22 · 2011-10-21 06:24 · Score: 1
  
  RAID 5 is n-1, therefore there is one parity written for every write, and all drives write for every disk write activity. If you want speed, you don't use RAID 5; RAID 10 or RAID 1 are much better for performance.
  
  --
  APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
70. Re:OCZ by Coren22 · 2011-10-21 06:25 · Score: 1
  
  That would be an expensive RAID controller to dedicate a whole Xeon to acceleration.
  
  --
  APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
71. Re:OCZ by amorsen · 2011-10-21 06:39 · Score: 1
  
  That would be an expensive RAID controller to dedicate a whole Xeon to acceleration.
  Would it really? At the mid range an extra Xeon is a few hundred USD; obviously a bit more if you have to go for a server with more sockets. At the low end you just pick a 6-core CPU instead of a 4-core. Neither case seems unreasonably expensive to me. With a bit of luck you save an expansion slot.
  
  --
  Finally! A year of moderation! Ready for 2019?
72. Re:OCZ by gstrickler · 2011-10-21 07:50 · Score: 1
  
  I meant to type "clients" (plural, not possessive). Many hundreds of HD's and many dozens of failures over the 15+ years that HDs have had SMART. Only one or two of the failures were predicted by SMART. I'll put my much larger sample, and Google's vastly larger sample up against your friend's/family's machines any day. SMART is NOT a reliable predictor of HD failure and never has been.
  
  --
  make imaginary.friends COUNT=100 VISIBLE=false
73. Re:OCZ by Luckyo · 2011-10-21 08:04 · Score: 1
  
  And when talking about servers, I will be forced to agree with you. My disks don't come close to those levels of wear and tear.
74. Re:OCZ by Coren22 · 2011-10-21 08:11 · Score: 1
  
  Sorry, I forgot my sarcasm tag :)
  
  --
  APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
75. Re:OCZ by haruchai · 2011-10-21 08:48 · Score: 1
  
  Ok, got me there. Never heard of them before.
  
  --
  Pain is merely failure leaving the body
76. Re:OCZ by haruchai · 2011-10-21 08:52 · Score: 1
  
  Yeah, I'm pretty old, and I do remember Conner, the Compaq spinoff. Y'know, I might even have a box of Dysan double-sided, double-density 5.25" floppies kicking around. Wonder if the (worthless) data is still readable
  
  --
  Pain is merely failure leaving the body
How long until... by Alwin+Henseler · 2011-10-20 10:56 · Score: 2
- Largest-capacity milestones are presented in the form of a SSD before good old magnetic HDDs?
- Annual sales (in $$) of SSDs tops that of magnetic HDDs?
- Price/TB for SSDs drops below that of magnetic HDDs?
- Major OEM builder announces they remove magnetic HDDs as an option?
- Well-known manufacturers do the same, turning magnetic HDDs into a niche product only produced by 1 or 2 specialist companies?
- Most retailers drop magnetic HDDs from their inventory?
- Dad, what's a magnetic HDD?
1. Re:How long until... by kolbe · 2011-10-20 11:13 · Score: 2
  
  SSD's must meet or surpass all of your mentioned categories and overall capacity limits before Magnetic HDD's are cast the way of the floppy disk drive. Even then, look at how long it took to get rid of the floppy disk drive:
  Beginning of end for Floppy Disk Drive: 1998 with a CD-ROM drive but no floppy drive
  End of the Floppy Disk Drive: 2009 Hewlett-Packard, the last supplier, stopped supplying Floppy Disk Drives on all systems
  It could be stated that the HDD is more entwined in technology than the FDD was and so it may be more well more than 11 years before we see Magnetic HDD's disappear from the consumer marketplace.
2. Re:How long until... by CheshireDragon · 2011-10-20 11:19 · Score: 2
  
  I think it will be when: the SSDs $/MB/GB/TB is below the HDD. That I believe will be the biggest milestone to pave the way for the rest. inexpensive. I will only switch over when I feel they are extremely reliable, which would be about the time any one of the many options above is true.
  
  --
  "That's right...I said it."
3. Re:How long until... by DigiShaman · 2011-10-20 12:06 · Score: 1
  
  Two things really.
  1. When the cost per GB become cheaper than what's available in an HDD.
  2. Proven track of reliability.
  Currently only the Dell PERC 6/i and above will work well with SSDs. Once the two major hurdles have been achieved, we can kiss the ol winchester drive goodbye. Honestly, HDD technology is a marvel of technology. But its time has come.
  
  --
  Life is not for the lazy.
4. Re:How long until... by bill_mcgonigle · 2011-10-20 12:55 · Score: 1
  
  1. When the cost per GB become cheaper than what's available in an HDD.
  Heck, I'd probably pay $200 for a 500GB SSD for my laptop. That's way more than a hard drive, but I'd get something more for it. That's forty cents a GB, these guys want triple that currently.
  2. Proven track of reliability.
  Yeah, I'm only using SSD's for caches now because of their failure mode, and write caches get mirrored. If OCZ wants to make that 500GB drive a 750GB drive, and put four controllers onboard with a SATA multilane interface so I can run RAIDZ on my laptop, they'd make this storage geek smile. There's plenty of room in a 2.5" drive.
  OK, so I'm pretending the laptop's motherboard can support it (AHCI doesn't by default, right?).
  
  --
  My God, it's Full of Source!
  OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
5. Re:How long until... by DigiShaman · 2011-10-20 13:49 · Score: 1
  
  The newer SSD drives are SATA3 now. But even with a SATA2 motherboard, these drives fetch data at amazing speeds even if you were to fully saturate the port. Unless you need the performance of an Avid workstation working with multimedia over a fiber channel SAN, I don't think you'll personally see the difference between SATA2 and SATA3 connectivity in a laptop. YMMV of course.
  Anyways, I've got an Intel M25 160GB in my MacBook 13". When booting up my Windows XP VM in Fusion, for a moment my CPUs are maxed out. That's sick (awsome maybe?). Now my laptops bottle neck is the bloody processor. I never would have thought in a million years. 0_o
  
  --
  Life is not for the lazy.
6. Re:How long until... by WuphonsReach · 2011-10-20 14:09 · Score: 1
  
  When the cost per GB become cheaper than what's available in an HDD.
  
  For laptops, it happens once SSDs get cheap enough for large enough that you don't feel like you're trying to live with a gold-plated shoebox sized amount of storage.
  
  By a lot of metrics, we've hit that point with it being possible to pickup 128GB SSDs for about $1.50/GB. That's plenty for most machines and the responsiveness puts it far ahead of the competition.
  
  Once it drops below $1/GB and starts heading down to about $0.50/GB, you're going to see more and more mass adoption for cases where you just don't need a few TB of storage.
  
  --
  Wolde you bothe eate your cake, and have your cake?
7. Re:How long until... by timeOday · 2011-10-20 15:01 · Score: 1
  
  SSDs are better in enough other respects that I'll bet they take over before they're the rock-bottom $/MB choice. CRT TV's and monitors exited the market, or at least were on a very sharp downturn, even when they were still somewhat cheaper than the same-sized LCD.
8. Re:How long until... by EETech1 · 2011-10-20 15:16 · Score: 1
  
  I just love booting my pc in 6 seconds and going to my photo manager and before you can blink an eye... Scrolling through thousands of photos as thumbnails, and seeing every one no matter how fast I scroll, or what size the pics are, and changing zoom is instantaneous! I have sold 5 SSDs now to friends just based on that!
  I never see an IOWait anymore. Truly magical!
9. Re:How long until... by bill_mcgonigle · 2011-10-20 15:21 · Score: 1
  
  That's sick (awsome maybe?). Now my laptops bottle neck is the bloody processor.
  Awesome - in my opinion, that's where you always want to be.
  
  --
  My God, it's Full of Source!
  OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
10. Re:How long until... by tlhIngan · 2011-10-20 16:05 · Score: 1
  
  1. When the cost per GB become cheaper than what's available in an HDD.
  That won't happen for a LONG time.
  SSDs only get cheaper in line with Moore's law (the number of transistors limits the size of the flash chips).
  Hard drives, it seems, grow in capacity faster than Moore's law. At some point in the future they'll slow down, but that's a huge gap to catch up to.
11. Re:How long until... by TheRaven64 · 2011-10-20 22:44 · Score: 1
  
  Heck, I'd probably pay $200 for a 500GB SSD for my laptop
  Laptops aren't the only place people use disks. I've bought two new machines this year. My laptop has a 256GB SSD and the difference that it makes to performance is amazing. I'd hate to go back to using a hard disk. The other machine is a NAS. It has three 2TB disks in a RAID-Z configuration. I am mostly going to be accessing it over WiFi, so as long as the disks can manage 2MB/s I really don't care about performance. I care a lot about capacity though, because it's having things like snapshotted backups of my laptop dumped on it. If I paid $200 extra per 500GB, then the machine would have been insanely expensive.
  If SSDs had cost the same per GB as mechanical disks, I'd have gone with SSDs in both cases.
  
  --
  I am TheRaven on Soylent News
12. Re:How long until... by jbolden · 2011-10-21 00:41 · Score: 1
  
  The cost per gig is unlikely to ever get below the HDD cost. The multiplier used to be around 20x. Maybe it is down to about 15x 2 years later. So if we assume something like the multiplier halves every 4 yrs you still need another dozen years before HDDs are even close. I don't think HDD has that long.
  At this point most people experience essentially unlimited storage. Generally the switches: 14 in -> 8 in -> 5 1/4 -> 3 1/2... all happened when the larger drives still had better performance but lower price per gig. I think this is likely to happen in reverse where HDD is being used for external storage.
13. Re:How long until... by CSMoran · 2011-10-21 01:01 · Score: 1
  
  Now my laptops bottle neck is the bloody processor. I never would have thought in a million years. 0_o
  Actually, your processor is probably doing wait-states waiting for the RAM.
  
  --
  Every end has half a stick.
14. Re:How long until... by jones_supa · 2011-10-21 01:36 · Score: 1
  
  Interesting list. For an even easier goal, it would be nice to see when will most high-end laptops ($1500+) start to have a SSD. Only very select models currently have.
15. Re:How long until... by CSMoran · 2011-10-21 01:42 · Score: 1
  
  However, SSDs will likely soon start reaping the benefits of scale.
  
  --
  Every end has half a stick.
16. Re:How long until... by gstrickler · 2011-10-21 03:23 · Score: 1
  
  It could be stated that the HDD is more entwined in technology than the FDD was and so it may be more well more than 11 years before we see Magnetic HDD's disappear from the consumer marketplace.
  No. If price and capacity are similar, SSD is a complete replacement for HDD. They use the same form factors and same interfaces. FDD survived so long because of existing removable media. CD/DVD drives will persist for the same reason. HDDs have no backward compatibility issues to maintain other than form factor and interface. If/when SSDs approach the price and capacity of HDD, the HDD will die rapidly because the SSD has huge advantages in latency and portable durability, plus advantages in power, weight, and transfer rate.
  
  --
  make imaginary.friends COUNT=100 VISIBLE=false
17. Re:How long until... by bill_mcgonigle · 2011-10-21 03:25 · Score: 1
  
  Buy a cheap SSD, partition it, and add part of it as a cache device to your RAID-Z - the L2ARC will be kept fresh and you'll make the cost back in electric costs. If you can buy two SLC's (~$115 each) make a mirror of two partitions and add that as a log device, to save on the write side too (but don't trust a single SSD as a zil, and MLC probably isn't great for constant writes).
  I have more data on my laptop hard drive than is economically feasible for an SSD right now. Two more years, I figure. For now, I have a Momentus XT which has 4GB of MLC cache on it.
  
  --
  My God, it's Full of Source!
  OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
18. Re:How long until... by petermgreen · 2011-10-21 04:02 · Score: 1
  
  The reason the floppy drive phaseout took so long is that it wasn't the CD alone that killed it. It was the USB flash drive that killed it. CDs are good, but they're a bit clumsy to work with compared to the floppy drive.
  More specifically the vendors screwed up on packet writing. Had packet writing been made a standard feature of windows with a standard format I expect things would have turned out rather differently.
  
  --
  note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
19. Re:How long until... by TheRaven64 · 2011-10-21 04:11 · Score: 1
  
  I have an 8GB USB flash stick working as L2ARC, but even without it I never notice the hard disks being slow. The main advantage is that the disks can spin down completely after filling up the ARC and L2ARC when I've got a nice predictable read-only workload (e.g. watching a movie). Given that the drives consume a total of 15W in normal operation, and about 3W when idle, I doubt that I'd save enough for it to be worthwhile with a better SSD...
  
  --
  I am TheRaven on Soylent News
20. Re:How long until... by bill_mcgonigle · 2011-10-21 04:51 · Score: 1
  
  Yeah, depends on your workload. IIRC I worked out a 24/7-busy 5-disk Raid-Z2 to cost about $9/mo in electricity here (counting cooling, 40% or so). If Sun's math is to be believed, SSD L2ARC and ZIL get that down to $2/mo or so.
  If your disks are mostly idle most of the time, I can't see how the payback would be fast enough. I don't know of any reliable way to figure carbon load.
  
  --
  My God, it's Full of Source!
  OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
21. Re:How long until... by TheRaven64 · 2011-10-21 06:15 · Score: 1
  
  It absolutely makes sense for a busy server, but not really for a home NAS. Adding a SSD for the ZIL might make sense though, because Time Machine backups tend to be about 20MB and they wake up the disks.
  
  --
  I am TheRaven on Soylent News
22. Re:How long until... by DigiShaman · 2011-10-21 10:42 · Score: 1
  
  I don't see how. RAM is far and away faster than any SSD drive on the market. Unless of course you mean the CPU is waiting to load data from the SSD into RAM prior to executing code, I might buy that. But I thought DMA was supposed to get rid of CPU wait-states penalties. Right?
  
  --
  Life is not for the lazy.
23. Re:How long until... by CSMoran · 2011-10-22 01:26 · Score: 1
  
  I think we misunderstand one another. My understanding of your comment was that by having replaced a HDD with an SSD, you removed the bottleneck (HDD) from your system and claim the CPU is now the bottleneck, i.e. that you no longer spend significant time in I/O waits, but rather observe a 100% CPU utilization. What I then meant to say was that whenever this happens, it's likely that the CPU is actively waiting for the RAM. With CPU speeds and numbers of cores increasing steadily, the performance of RAM has not kept up, especially when there is thread contention involved. Thus, it's actually likely that it's the RAM that becomes the bottleneck. The fact that RAM is way faster than SSD is not relevant to this point.
  
  --
  Every end has half a stick.
Re:Who hasn't had reliability problems? by mug+funky · 2011-10-20 11:22 · Score: 1

there's a freeBSD shill floating round these parts. i think they might be using the same script the rather humourous microsoft bot was using.
buy em' now by loVolt · 2011-10-20 11:46 · Score: 1

wd and seagate hard drive prices are roofing and will keep going up over the months to come, ssd will be the way as energy costs go up..time for spinning crap to leave anyway

--
Darwin Enforcement Agent
1. Re:buy em' now by Luckyo · 2011-10-20 13:42 · Score: 1
  
  What makes you think that energy costs will go up? It's very country-dependent and at least where I live, electricity is far more likely to go down in price as next nuclear power plant is built in a couple of years.
Pass by p51d007 · 2011-10-20 15:30 · Score: 1

If/when SSD's get to the price point of mechanical drives, I'll get one. Not worth it now.
5000-10000 program/erase cycles? by hackertourist · 2011-10-20 19:31 · Score: 1

I was wondering how long this SSD will last in typical use. Let's take the 128 GB unit; thats 128Gx10000 write cycles.
Some numbers for my system: I've got 4 GB RAM, and at the moment it's using 1.5 GB of swap. Let's say the swap gets overwritten once a day. I hibernate 2x/day. New data: that won't be too much, Time Machine backs up maybe 1 GB in a week.
In total 10GB of writing per day. That's 120,000 days, not bad.
Worse case would be rewriting the entire SSD each day, that still 5000-10,000 days. Still good enough.
I wonder how those early failures happen? (see the Hot/Crazy scale and SSDs)
1. Re:5000-10000 program/erase cycles? by sheepe2004 · 2011-10-20 20:34 · Score: 1
  
  You've assumed that the writes will be evenly distributed throughout the disk. It seems more likely that a few large chunks of it will be written once then largely left alone (OS, key applications), whereas other parts will be re-written constantly, multiple times per day even. So it seems likely that the time before some part of the drive fails is more likely to be somewhat lower than 10,000 days. I'm not sure how catastrophic small regions of an ssd failing is. It could be possible to work around even fairly large numbers of transistors failing as long as the lost data isn't essential. Having said that maybe the firmware is smart enough to shuffle things around to get a more even distribution of writes? Although this could only help to a certain extent - if you shuffle things around constantly you could even up with even more writes.
  
  --
  http://compsoc.man.ac.uk/~shep/
2. Re:5000-10000 program/erase cycles? by hackertourist · 2011-10-20 20:58 · Score: 1
  
  As I understand it, write leveling is already being done.
  The number of extra writes necessary could be an issue if the leveling mechanism is too agressive (e.g. not allowing three consecutive writes in the same location). The other extreme would be allowing 5000 writes before you move a block of data to a new location (ie only moving the data once in the lifetime of a drive).
3. Re:5000-10000 program/erase cycles? by pjc50 · 2011-10-20 21:57 · Score: 1
  
  I think the early failures are other problems than the flash wearing out; as these things are so price-sensitive, corners are being cut on the controller, controller firmware, and mechanical construction of the PCB etc.
Who cares anymore by dgas · 2011-10-21 01:19 · Score: 2

I know I'm supposed to care that an SSD is unreliable, but the truth is you have to back up everything anyway because hard drives aren't reliable. I have a server with conventional drives in a raid array for data security, I want my main machine to fly.... and SSD lets you do that. I just wish it didn't cost so much.