Very good with the no LTT drive. Can the end user modify the firmware and remove LTT is my question :) ?
Printable View
Very good with the no LTT drive. Can the end user modify the firmware and remove LTT is my question :) ?
I can't find data to match the last two letters, but other than that here are the specs:Quote:
Originally Posted by Vapor
Page size: 8,640 bytes (8,192 + 448)
Block size: 256 pages (2M+112 bytes
Plane size: 1,024 blocks
P/E: 3,000
I'm really looking to see what happens without throttling getting in the way :D
Attachment 118496
204.43TB Host writes
Reallocated sectors 6
MD5 OK
33.00MiB/s on avg for the last 51.7 hours.
M225->Vertex Turbo 64GB Update:
10.31TiB, MWI 92, 421 Raw Wear, 45.30MiB/s for the last 22.1 hours (<-stopped, ran wiper, then restarted)
No MD5 Testing yet.
Also, noticed change in C3 from 0 to 1 and CE from 1 to 214.
Attachment 118499
m4 update:
New milestone passed 200TiB with no reallocated sectors :)
200.3614 TiB
668hours
Avg speed 88.71 MiB/s.
AD gone from 243 to 240.
P/E 3505.
MD5 OK.
Still no reallocated sectors
Attachment 118535
Very impressive :)
Also of note, your WA has been creeping upward for a long time now. At 20TiB, it was 1.0626x; at 40TiB, it was 1.0727x; at 91TiB, it was 1.078x; at 130TiB, it was 1.089x; at 200TiB, it's 1.0933x. Before 20TiB (when calculation is less precise), it climbed from 1.028x to 1.0626x pretty smoothly and quickly....it's been a very smooth climb the entire time actually.
302.868 TiB, 826 hours, sa177: 1/1/24873, sa178: 71/71/290Quote:
Originally Posted by johnw
Average speed reported by Anvil's app has been steady at about 113MB/s.
The other unknown SMART attribute 235 is still at 99/99/2, just as it was when the SSD was fresh out of the box.
64GB Samsung 470
300TiB broken :D
Interesting observations! Maybe SSD is trying to leverage the wear more aggressively thus doing more static data rotation and increasing writes?Quote:
Originally Posted by Vapor
The more I think about it, the more it sounds like sizable chunk of data being unaccounted for in the early lifetime of the drive. If there were 100GB unaccounted for in the beginning, its impact as a percentage would get smaller and smaller as writes increased, basically asymptotic behavior. I haven't done any math to see what size that would be, but it might match up nicely with the attempts of getting the right amount of static data on the drive (or even the 39GB itself).
That might be it. First I ran 1 run of Anvils benchmark, ATTO and AS SSD. Then I copied the static of 39,3GiB and started the endurance test. I don't know how much AS SSD and ATTO writes but Anvils app is supposed to keep the write to an minimum.
Very good to see the 300 TB barrier being broken so quickly by the Samsung !
C300 Update
139.04TiB, 53 MWI, 2350 raw wear, reallocations still at 2048/1, MD5 OK
SF-1200 nLTT Update
13.563TiB Host writes, 7.53TiB NAND writes, 99 MWI, 120.5 raw wear, wear range delta 1.
Interesting.
The V2 (34nm) took 11.60TiB before the MWI dropped to 99%. Out of that 11.6TiB approx 4TB was 0fill.
The V3 (25nm) took 11,078 GiB (NAND writes) before the MWI dropped to 99%.
207TB Host writes
Reallocated sectors 6
MD5 OK
34.22MiB/s on avg for the last 21 hours.
M225->Vertex Turbo 64GB Update:
14.14TiB, MWI 89, 557 Raw Wear, 49.70MiB/s for the last 21.25 hours (<-stopped, ran wiper, then restarted)
No MD5 Testing yet.
Also, C3 from 1 to 2 and CE from 214 to 235.
Attachment 118571
EDIT: When should I start MD5 Testing?
Whoa, that is a savage reduction in the MWI considering the drive has 5K P/E. Personally I would not bother with MD5 Testing until the MWI gets very low or unless C3/ CA/ CB start changing significantly.
Looks like the health status is established by D0 (avg erase count) / PE specification count.
I now alot of people notice their drive life drop by 50% or more when they went from Indilinx FW 1916 to FW 2030.
It changed the P/E count from 10k to 5k to cover other NAND I believe.
I think we're good for 10k P/E myself :)
Did you post which type of NAND the SSD is using? (Product ID) If not do you know? If you could let me know I can try to find the product literature. Then we can be sure about the P/E spec.
NAND is Samsung K9LBG08U0M-PCB0
EDIT: Not sure if this helps ya... http://www.datasheetarchive.com/inde...DSA0038979.pdf
Looks like it is 51nm and at some stage the P/E cycle specification was changed from 5k down to TBD
Attachment 118572
m4 update:
Getting close to Anvil now :)
The rigg was down 2 hours last night due to some maintenance.
206.0306 TiB
684hours
Avg speed 91.69 MiB/s.
AD gone from 240 to 236.
P/E 3601.
MD5 OK.
Still no reallocated sectors
Attachment 118573
I have these notes for some reason in my M255 junk. Don't know where they came from though:Quote:
Originally Posted by Ao1
revision history
endurance
April 12th 2006 : 10,000 times
Dec. 22th 2006 : 10,000 times -> 5,000 times
Jan. 12th 2007 : 5,000 times -> TBD
C300 Update
142.01TiB, 52MWI, 2401 raw wear, 2048/1 reallocations, MD5 OK
SF-1200 nLLT 60GB Update
17.188TiB host writes, 10.063TiB NAND writes, 98 MWI, 161 raw wear, wear range delta of 3. Still doing compression tests so still no static data or MD5 testing.
312.510 TiB, 851 hours, sa177: 1/1/25623, sa178: 71/71/292Quote:
Originally Posted by johnw
Average speed reported by Anvil's app has been steady at about 113MB/s.
The other unknown SMART attribute 235 is still at 99/99/2, just as it was when the SSD was fresh out of the box.
64GB Samsung 470
sa178 raw increase of 2 this time