Look out Intel 320, the Samsung 470 is comin' for ya!
:sonic: :cheer2:
Printable View
C300 Update:
83.255TiB, 72 MWI, 1404 raw wear indicator, MD5 OK, 61.85MiB/sec, no reallocated anything.
176.14TB Host writes
MWI 4
Reallocated sectors : 6
MD5 OK
Getting closer to MWI stops reporting, a few more days left :)
Vapor, F8 (vendor specific) on your C300 is recording to writes to NAND :)
In what units?
86.323 TiB written in Anvils app, so maybe 86.45TiB total in its lifetime. F8 reads 947652212, raw wear indicator is at 1456 (71MWI).
F6 is still 8x F7 (almost exactly, makes me think bits vs. bytes), and F5 is still 1.04x F7. Haven't paused the load app yet to see if any of those are a timer. F7 is 23310291875, F5 and F6 can be found from that.
^ Don't know, but it is defiantly recording writes to nand. (Got that direct from Crucial)
Defiantly? Ok, I'll record these writes, but I'll have you know that I am doing it under protest! ;)
Does Crucial have a list of SMART attributes? Micron does, and there is no F8 -- the highest number listed is 0xCE. So if Crucial has a 0xF8, then either it is Crucial specific, or else Micron does not document all of the SMART attributes.
AFAIK, I'm the only one with access to F2-F8. Got them when I thought I messed up the flash to 0007 (flashed in AHCI, which isn't supposed to be possible...the retried in IDE and said it was already with 0007). 0xCE was the highest number I had access to before the pseudo-goofed flash.
If F8 is NAND writes then its number should be after WA. 1456 raw wear (should also align with NAND writes) was what it read at the time, not sure how far along into 1456 it was (could be anywhere between 1456.0 and 1456.99), so let's say 1456.5. 1456.5 * 64 = 93.216TiB of NAND writes compared to 947652212 F8 value and it's suddenly a lot harder to piece it together :eh:
And then I back again:
130.9436 TiB
442 hours
Avg speed 90.96 MiB/s.
AD gone from 26 to 24.
P/E 2283.
MD5 OK.
Attachment 118031
I'm really wondering how far will these go before they are degraded beyond usable. And how will that look like. I wish these test files were usable files which could be later inspected if they are still usable when SSD is starting to show severe symptoms od degradation. Because to date, i don't think anyone has seen a drive that was degraded that much. Anyway, very interesting test, too bad there aren't any SandForce 22xx series drives in it (like Corsair Force 3 and OCZ Vertex 3)...
179.08TB Host writes
WMI 2
Reallocated sectors : 6
MD5 OK, 33.1MiB/s on avg. (28 hours)
C300 Update
91.914TiB, 69 MWI, 1551 raw wear indicator, 1021590229 0xF8 value, 61.85MiB/sec, MD5 OK.
New: 2048 reallocated sectors; 1 reallocation event count; 1 grown failing block count; 1 erase fail count.
Attachment 118047
Just thought I had to post this milestone :)
Attachment 118048
excellent!!
been a long time coming, that kingston is a champ :)
219.480 TiB, 603 hours, sa177: 1/1/18053
Average speed reported by Anvil's app has been steady at about 112MB/s.
The other two unknown SMART attributes, 178 and 235, are still at 72/72/276 and 99/99/2, just as they were when the SSD was fresh out of the box.
10*365.25*64e9/1024^4 = 212.603TiB
Past the point where the writes are equivalent to writing the entire 64GB capacity of the SSD every day for 10 years.
well thats a stat you can sink your teeth into! very impressive! unbelievable actually :)Quote:
Past the point where the writes are equivalent to writing the entire 64GB capacity of the SSD every day for 10 years.
glad to see this moving along...getting a tad boring with no failures and this has been going on for two months or so....
(dont get me wrong, its a good type of boring :) )
Finally a little action... yet I'm not sure how I can interpret the data:
- when we have a reallocated sector, it means that block can still be erased but a certain page cannot be programmed?
- when we have a reallocated block it means that erase failed?
If this is correct, it means that you have a failed block and 1920 failed pages spread to at least 15 blocks (this assuming 4KB pages/128 pages per block). I would expect a rapid failure also for the other blocks that contain failed pages, maybe in next TB written.
Samsung 470 pseudo-passed the Intel 320 in writes, damn it's fast.
I'm pretty sure the 320 is still ahead, but it's been a few days since the last update on the 320 40GB and it's capable of racking up more than 2.5TiB in that time frame.
Very impressive from the 470 considering it appears to have a WA of ~5.1x
(very impressive of all the drives so far, really, with a partial exception of the V2 40GB's LTT)
I think Crucial/Micron considers an LBA sector (512B) as their 'sector' (as compared to Intel doing something else, it seems). So 2048 reallocated sectors is just 1MB. I don't know the specs of the NAND in the C300, but that's probably only 1 or 2 blocks--probably 1 based on "1 grown failing block count".
It makes sense, so probably we could consider this one block as one "Intel sector".
Nice to see these SSDs lasting as much as they are doing now !
M4 update:
143.1145 TiB
481 hours
Avg speed 89.77 MiB/s.
AD gone from 24 to 17.
P/E 2493.
MD5 OK.
Attachment 118101