SSD Write Endurance 25nm Vs 34nm

[Christopher]

How does Vertex Turbo come with 1.7 already loaded? Isn't 1.7 fairly recent, and the Turbo is an older drive??
You might want to pop that sucker open and take a looksee!

Yes. It's a brand-new drive. Came with 1.7FW on it. It's also using the new style plastic chassis (What I call revision 2 -- the first plastic chassis was not sized right and won't fit in many laptops).

I bought a 128GB Turbo last October as well. It had the mis-sized plastic chassis and came with 1.7FW.

BUT -- I second your concern. I asked OCZ about the 128GB Turbo, and got a response -- just a bizzare one. What I was trying to figure out it if OCZ was taking RMAs and returns, doing a new "factory flash" and putting the drives in a new plastic chassis (the metal ones get scratched really easy). I'm not saying that's what they're doing, but I at least consider it a possibility. They would have some drives in stock for RMAs/warraties, so it could be that they do maintain some old stock.

[Anvil]

Kingston SSDNow 40GB (X25-V)

648.80TB Host writes
Reallocated sectors : 05 21
Available Reserved Space : E8 99
POH 5855
MD5 OK

32.95MiB/s on avg (~86 hours)

--

Corsair Force 3 120GB

01 92/50 (Raw read error rate)
05 2 (Retired Block count)
B1 49 (Wear range delta)
B6 1 (Erase Fail Count)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 745973 (Raw writes) ->728TiB
F1 992732 (Host writes) ->969TiB

MD5 OK

106.83MiB/s on avg (~86 hours)

power on hours : 2828

[Christopher]

I've not been power cycling the Samsung for PE count updates because I thought maybe 177 would start working... and a few hours ago, it did. So right now, if I power cycle the drive, I could get a true PE count... but then the drive would stop updating for a few days. It takes maybe 60 - 72 hours of continuous usage after 02FW update for the drive to update WLCount in real time.

[devsk]

F1 992732 (Host writes) ->969TiB

Next update it crosses 1000TB of host writes... Awesome!

[Christopher]

I'm trying to order a 520 right now... A couple places have them in stock here.

One place that had some 60GB models took them down after midnight here; I ordered a 120GB model from another retailer. If I can find the 60GB model, it's getting tested!

[Ao1]

Host writes: 13,691 GiB
MWI: 27
P/E Cycles: 2,636
POH: 355
Relocated sectors: 4,096
MB/s: 6.27

[Anvil]

The test-rig was unresponsive when I checked so I had to re-boot.

From what I can find there are no problems but it was caused by the Force 3.
There were 0 files and so it is related to the cleanup part of the loop, as in delete->TRIM.

Looks like it happened last night so there are a few hours lost, will be re-starting the test shortly, just performing a few checks.
edit:
I re-checked and it stopped working 5 hours ago, not that bad, it's been months since there were issues though.

[Anvil]

Kingston SSDNow 40GB (X25-V)

651.07TB Host writes
Reallocated sectors : 05 21
Available Reserved Space : E8 99
POH 5875
MD5 OK

38.28MiB/s on avg (~5 hours)

--

Corsair Force 3 120GB

01 94/50 (Raw read error rate)
05 2 (Retired Block count)
B1 48 (Wear range delta)
B6 1 (Erase Fail Count)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 751464 (Raw writes) ->734TiB
F1 1000026 (Host writes) ->977TiB

MD5 OK

106.96MiB/s on avg (~5 hours)

power on hours : 2848

It's finally past 1PB but there's still a few days more until 1PiB is reached.

[Christopher]

1000TB is pretty impressive, but the X25-V is the better story. If it can make it for another four months or so, it will have been a year.

[Christopher]

Samsung 830 64GB Update, Day 48
B]FW:[/B]CXM02B1Q

TiB Written:
307209.83

GiB written:
300.0096

Avg MB/s
129.20

PE Cycles
15107 <-- not the true count as it stopped realtime updates
Reallocated Sectors

40960
20 Blocks, holding steady

1138 hours




OCZ Vertex Turbo 64 Update Day 3

TiB 20.4309
GiB 20921.24
Avg MB/s 83.03

Avg Erase Count
370 up from 205

MWI 93 down from 96


1 Program Fail
16 Erase Fail (up from 14)
0 Read Fail
81 Hours




The 830's PE cycle count is working. The Turbo is still much slower than I was hoping it would be.

Still no more reallocations on the Samsung, and it just turned up 300TiB.

[Ao1]

Host writes: 14,202 GiB
MWI: 21
P/E Cycles: 2,853
POH: 378
Relocated sectors: 8,192
MB/s: 5.96

From HD Sentinel:
“There are 8192 bad sectors on the disk surface. The contents of these sectors were moved to the spare area. 2 errors reported during write to the device”.

[Christopher]

Since upgrading to 02FW I've not had another bad block. Incidentally, I also believe there was something wrong with the 01FW's wear leveling and... possibly everything else too.

The first thirty days saw 20 reallocated blocks, where it's been for the past 120TiB. I also figured wear leveling count was not average erase count but possibly maximum erase count, but you'd figure there would be an upper boundary to PE cycles. I just find it hard to believe the Samsung, using 27nm NAND and traditional ECC could hit those kinda numbers (15000+ PE cycles at the moment.).

[Ao1]

One of my X25-M’s has 7 bad sectors. MWI = 99 and I only have 4,990 GB of host writes on it. I can’t be 100% sure, but I believe the 7 bad sectors occurred after I switched the drive from being an OS drive to a static data drive.

[Christopher]

I think that the 01FW was really whacky on the 830, and that WA/WL were not as awesome as I'd hoped. Also, the drive while much faster now, uses about the same PE cycles as it did when it was only writing 5TB a day.

3.3698TiB was written (since the last update) with 59PE cycles, which means every 58.49GiB the drive consumes one cycle. This is much, much better than the drive was doing on 01FW. I assume this is partly why the drive isn't flagging blocks like it used to. Speed continues to increase a little every day.

The Turbo uses 1PE for ever 56.83GiB I also believe this means I shouldn't expect much of a speed increase over time -- maybe a little more).

[Ao1]

From a Micron spec sheet:

1 page = 4,096K
1 block – 1 MiB
1 LUN = 4,096 MiB
Min number of valid blocks per LUN = 3,996
Difference between max and minimum = 100 blocks or 100 MiB

An invalid block is one that contains at least one page that has more bad bits than can be corrected by the minimum required ECC.


If a sector = one page (4k) 40,960 pages (sectors) = 40MiB.

Even is all bad sectors were on one LUN (unlikely) the LUN would still be operating within acceptable parameters.

[Christopher]

I think the Samsung uses 8K pages (based on some info on a far flung part of the Samsung website that I can't seem to find at the moment), but I'm not positive. 20 blocks is nothing... (it's still at 99/0/20). I was just expecting some more, especially if PE count is accurate.

Also, if you look at the smart data for my 830, notice that Program Fail = 0, Erase Fail = 10, Runtime Fails = 10 blocks, but the total number of reallocated blocks is 20. This could mean that the attributes are mislabeled, but I don't think so. Replaced blocks just = 2x Runtime fails.

[Ao1]

Allegedly the 830 uses K9GAG08UOE, 27nm NAND. As the cases are sealed I haven’t broken mine apart (yet) to verify. The fact that a sector is reported as 4K makes me think the page size must be 4K.

I have 2 number Erase Fail counts and 2 number Runtime Bad Block counts. Each event occurred on a relocated sector event.

[Christopher]

You'll never get 3 erase fails and 2 runtime, for example. If the pages are 8KB, they could just be doubling up the numbers.

From the Samsung Website:
http://www.samsung.com/global/busine...NANDFlash.html

[Ao1]

I’ve got 3 data sheets for Samsung, none of which are for K9GAG08UOE.

• K9ABG08UOA/ K9BCG08U1A/ K9CDG08U5A = 8,192 page/ 1.5M erase block (3Bit)
• K9MDG08U5M/ K9LBG08U0M/ K9HCG08U1M = 4,096 page/ 512K erase block (2 Bit - MLC)
• K9LBG08U0M-P/ K9HCG08U1M-P/ K9HCG08U1M-Z/ K9MDG08U5M-P/ K9MDG08U5M-Z = 4,096 page/ 512K erase (2Bit/ - MLC)

Toggle is the equivalent to the ONFI standard. I still think the page size is 4K based on the relocated sector size (you can’t relocate half a sector).

Samsung don’t state the P/E count on their spec sheets. They only state TBC

[johnw]

From a Micron spec sheet:

1 page = 4,096K
1 block – 1 MiB
1 LUN = 4,096 MiB
Min number of valid blocks per LUN = 3,996
Difference between max and minimum = 100 blocks or 100 MiB

Does the spec sheet really make that mistake (1 page = 4096K)? Or did you copy it incorrectly?

[Ao1]

No mistake. I’ve got two product sheets for Micron. Note the difference in P/E cycles, it’s the opposite to what you might expect. Intel quote 5K P/E for 25nm nand. As far as I can tell the specific NAND part that Intel use for their SSD’s is not used by anyone else.

[johnw]

No mistake.

LOL. Yes, mistake (yours, apparently). Pages are NOT 4096K. They are 4096 = 4K = 4KiB.

[Ao1]

Whoops, sorry.

[Anvil]

Kingston SSDNow 40GB (X25-V)

653.71TB Host writes
Reallocated sectors : 05 21
Available Reserved Space : E8 99
POH 5898
MD5 OK

34.44MiB/s on avg (~28 hours)

--

Corsair Force 3 120GB

01 90/50 (Raw read error rate)
05 2 (Retired Block count)
B1 46 (Wear range delta)
B6 1 (Erase Fail Count)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 757920 (Raw writes) ->740TiB
F1 1008605 (Host writes) ->985TiB

MD5 OK

106.65MiB/s on avg (~28 hours)

power on hours : 2871

[B.A.T]

Todays update. It's been a while now but I've had a crazy family weekend and no time to make an update.
Kingston V+100
343.5438 TiB
1997 hours
Avg speed 26.05 MiB/s
AD still 1.
168= 1 (SATA PHY Error Count)
P/E?
MD5 OK.
Reallocated sectors : 00


Intel X25-M G1 80GB
269,45 TiB
20440 hours
Reallocated sectors : 00
MWI=131 to 126
MD5 =OK
48.83 MiB/s on avg


m4
288.0025 TiB
1063 hours
Avg speed 81.28 MiB/s.
AD gone from 203 to 187.
P/E 5071.
MD5 OK.
Reallocated sectors : 00


SSDLife Pro has crashed and no reinstall seems to fix it so no screenshot today. I'll mail them to see if it's possible to repair or reinstall.