Christopher ... I'm less inclined to now believe that you simply got a drive with dodgy NAND. Something else is killing the NAND prematurely.
Christopher ... I'm less inclined to now believe that you simply got a drive with dodgy NAND. Something else is killing the NAND prematurely.
What could kill just one part of one NAND device? Who knows?
I've prepped up a new drive, the M3P 128GB. I should start it up soon, but preliminary testing shows that it should be able to just about match the 830 256GB's speed at half the capacity, and that pleases me.
UPDATE
The M3P is baking in the oven now... it doesn't look like the MWI works (I'm terribly angered by this), unless MWI is based on >5KPE cycles or something. Either that, or it's based solely on reallocations (very possible). It's averaging around 270MB/s for the first couple of hours.
Last edited by Christopher; 05-26-2012 at 11:09 PM.
@Christopher/ canthearu
The V4 and Octane both used IMFT 25nm? The first post does not indicate the NAND part number. Do you know what it is?
Edit:
According to the info in the first page of the thread there is a consistent premature failure of all drives that have used Indilinx controllers, regardless of model or NAND type used. Only two of the Indilinx drives managed to get past the MWI, but considering the NAND that was used in those drives they should have lasted longer. The other three failed well before the MWI expired.
There is nothing wrong with the Marvell controller. It has been used problem free by Intel & Micron for years. I’d say that this is clear evidence that Indilinx firmware is the problem and not the NAND.
• Crucial M225 64 GB – Samsung 51nm (SLC?) = 880 TB (Exceeded)
• OCZ Vertex Turbo 64 GB – Samsung 51nm (SLC?) = 116 TB (MWI – 58)
• OCZ Vertex Turbo 64 GB – Samsung 51nm (SLC)? = 499 TB (Exceeded)
• Octane 128 GB – Intel 25nm = 303.82 TB (MWI – 85)
• Vertex 4 128GB – Intel 25nm = 393 TB (MWI – 31)
Last edited by Ao1; 05-27-2012 at 12:54 AM.
Bookmarks